Unified Process Best Practices Construction Phase

Author: (Canada) Ambler
Publisher:
Publish Date: 2005-11-01
Features: Is the Unified Process the only process and standard process for object-oriented, component-based software development? These four series of books offer critical comments on the Unified Process and present third-party perspectives. The author introduces alternative software processes and integrates the Unified Process with other software processes to form a more complete and robust process for handling real-world software development and product needs. After elaborating on a more comprehensive Unified Process, each volume introduces the experience and wisdom of masters in implementing the various phases of the Unified Process (Inception, Elaboration, Construction, Transition, and Production). Gathering the collective wisdom of industry luminaries. Articles from Peter Coad, Martin Fowler, David Linthicum, Mary Loomis, Steve Maguire, Steve McConnell, Clemens Szyperski, and Karl Wiegers discuss the following topics:
● How to develop and maintain large-scale, mission-critical software.
● How programming fits into the overall software development lifecycle.
● Improving professional skills and technical expertise.
And employs best practices such as code reviews, configuration management, change control, and architectural modeling to address the details of implementing a software process. A detailed plan fills the gap between theory and practice. During the Construction phase, the software team's focus is on developing technical prototypes developed in the Elaboration phase into a mature system. A preliminary version of the system needs to be implemented early in the lifecycle to control quality. This book introduces the best practices that project teams should follow, focusing on the key elements of the Construction phase, including how to:
● Achieve and maintain satisfactory quality as early as possible.
● Develop software models to guide implementation.
● Collaborate with user groups to validate the implementation of requirements.
● Implement and test different system components.
● Develop a practical version of the system as early as possible.
● Establish baselines for verified components.
● Effectively manage project resources (including risks).
The content of this book is provided by the U.S. Software Development magazine. This four-volume set combines the rich software process experience of the two authors, the firsthand insights of over 10 industry luminaries, and excellent articles from the Software Development and Computer Language magazines, proposing best practices for software development. It guides readers to execute these processes effectively and efficiently. At the same time, the authors integrate the Unified Process with other software processes to form a more complete and robust Unified Process for handling real-world software development and product needs. This four-volume set introduces best practices corresponding to the four phases of the Unified Software Process: Inception, Elaboration, Construction, Transition, and Production. This book is the third volume in the set, focusing on best practices related to the Construction phase of the Unified Software Process. It can serve as a reference for software project managers, software development engineers, process engineers, system engineers, and other professionals, as well as for students in computer science and related fields at universities and colleges.