|
|
.Net-A Complete Development Cycle This article discusses the software development practices that were used before the inception of .NET detailing which ones worked and which ones didn't. The .NET development lifecycle and how to implement it for your team is also explained.
|
Gunther Lenz, Siemens Corporate Research
|
|
|
The Soft Side of Software - People Factors in Software Development Developing software is all about communicating effectively. It's important to understand requirements and document project information appropriately. These tips and more are provided in this article to help your team work together more effectively.
|
Gary Pollice, Rational Software
|
|
|
Applying Software Inspections Through the Software Lifecycle Setting the priority and severity of a bug is a business decision. Changing business conditions impact the priority and severity of a bug. It's important to ensure that the staff that is assigning the priority and severity are aware of all relevant business drivers. This article discusses
conducting software inspections through the software lifecycle.
|
Robert Sabourin, AmiBug.com, Inc.
|
|
|
Turning Data into Information -Tricks of the Trade This article explains the difference between a measure and a metric.
|
Edward Weller, Software Technology Transition
|
|
|
Project Management and Collaboration: Using the Web to Improve Your Projects The speaker requested that these proceedings not be available online.
|
Marnie Hutcheson, Ideva
|
|
|
Software Development on Internet Time-Faster, Cheaper, Worse? This article details high profile corporate disasters and how your company can avoid making the same mistakes. Checklists and tips on how to get your team to communicate better are also included.
|
Girish Seshagiri, Advanced Information Services
|
|
|
Team Size and Its Effect on Peer Reviews This article discusses the prerequisites to quantitative management. How to create effective teams by determining recommended team size for inspections is also discussed.
|
Mark Paulk, Carnegie Mellon University
|
|
|
SM/ASM 2003: The Power of Retrospectives This paper discusses and explains the differences between post project reviews and retrospectives. Three retrospective case studies are also detailed.
|
Esther Derby, Esther Derby Associates Inc
|
|
|
Software Engineering Optimization: Measurement and Managing Change Technical leaders and software managers face constant changes in the technology and processes used to develop and deliver applications. Discover appropriate measurements to assess and manage your projects. Discover where the optimization opportunities are in your organization, and learn what to where the optimization opportunities are in your organization, and learn what to do when things don't work out, and see how to rapidly diagnose and correct the problems. You'll also find out whether your engineering processes match the needs of your customers.
|
Ram Chillarege, Chillarege Inc.
|
|
|
Testing and Implicit Requirements: Expanding the Unwritten Specification Testers should be encouraged to test against and report deviations from implicit specifications. There is a Universal Implicit Specification that is based on
fundamental principles. These principles are: the system will not lie, the system will impose no gratuitous keyholes or other constraints, and the system won’t do anything that’s just plain stupid.It’s worthwhile to identify, elaborate, and make explicit the fundamental principles and
common manifestations of deviations from these principles.
|
Scott Meyers, Aristeia.com
|
