Over the last several decades, various software development models have been articulated and discussed in literature. These models (stagewise, waterfall, spiral, iterative and incremental, etc.) have evolved in an effort to accommodate project environments' distinguishing characteristics: business volatility, organization and technical complexity, validation and delivery strategies. A project must consider these characteristics in choosing an appropriate development method, hence underlying development model. A project's adoption of a given development method however, often leaves the systems engineer with questions on how to integrate systems engineering planning and control, specifically technical reviews, into the development and integration effort. A pattern is proposed that abstracts the problem of applying systems engineering's reviews across various development models to achieve the benefits of the systems engineering technical reviews in conjunction with the benefits of a development model other than the waterfall model. The pattern is demonstrated with the stagewise and the RUP iterative development model and the resulting benefits are described.
[1]
Sanford Friedenthal,et al.
4.4.4 Adapting UML for an Object Oriented Systems Engineering Method (OOSEM)
,
2000
.
[2]
Daniel D. McCracken,et al.
Life cycle concept considered harmful
,
1982,
ACM SIGSOFT Softw. Eng. Notes.
[3]
H. D. Benington,et al.
Production of Large Computer Programs
,
1983,
Annals of the History of Computing.
[4]
Kevin Forsberg,et al.
The Relationship of Systems Engineering to the Project Cycle
,
1992
.
[5]
Barry W. Boehm,et al.
Understanding and Controlling Software Costs
,
1988,
IEEE Trans. Software Eng..
[6]
Barry W. Boehm,et al.
A spiral model of software development and enhancement
,
1986,
Computer.