Unified Process Best Practice Construction Phase

Author: (Canada/Australia) Ambler (Canada/Australia) Constantine
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 critiques of the Unified Process and present third-party perspectives. The authors introduce alternative software processes and integrate the Unified Process with other software processes to form a more comprehensive and robust process for handling real-world software development and product needs. After elaborating on a more complete Unified Process, each volume of the series 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 leaders. 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 employ 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 the technical prototypes developed during the Elaboration phase into a mature system. At this stage, a preliminary version of the system needs to be implemented to test and control quality early in the lifecycle. This book introduces the best practices that project teams should follow to master 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. magazine Software Development. This four-volume set combines the rich software process experience of the two authors, the firsthand insights of over 10 industry leaders, and the excellent articles from Software Development and its predecessor Computer Language magazines, offering best practices for software development processes to guide readers in executing them effectively and efficiently. At the same time, the authors have integrated the Unified Process with other software processes to form a more complete and robust Unified Process to handle 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, and Transition and Production. This book is the third volume in the set, focusing on the 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 majoring in computer science and related fields at universities.