The Harmony Process The Transition from Systems to Software Engineering英文电子书.pdfVIP

The Harmony Process Bruce Powel Douglass Chief Evangelist I-Logix The Transition to Software Engineering The Harmony process is an integrated product development process taking product development from requirements capture through systems engineering, an iterative development design lifecycle and into final test and validation. An overview of the process is shown in Figure 1. Its heritage as an elaborated “V-Process” is clear. The systems engineering work is done prior to the iterative analysis-design-implement-test cycle. After the handoff to software engineering, the iterative development cycle (IDC), carries the project forward. The IDC is an incremental development process, in which the system is developed as a series of vertical slices of increasing capability and completeness. The system (referred to as the “prototype” even though it is fully production quality code) is constructed incrementally, with new vertical slices adding new system-level capabilities to the increasingly complete system. The advantage of such an incremental approach are well documented in the literature, and include higher quality, lower cost of quality, and even reduced development time. The details of the execution of the development cycle are discussed in another paper “The Harmony Process: The Incremental Development Cycle”. In this paper, we will focus on how the handoff from systems engineering to software engineering occurs. In the progression of that discussion, we will touch on both the system engineering development side (also discussed elsewhere, in “The Harmony Process: Systems Engineering”) and on the work done within the IDC. Nevertheless, our main focus in this paper will be to discuss how we do