10.12 Alternative SDLC Work Patterns

 < Day Day Up > 



An important objective of an SDLC methodology is to provide flexibility that allows tailoring of the methodology to suit the characteristics of a particular system development effort. One methodology does not fit all sizes and types of system development efforts. For instance, it is not reasonable to expect a very small system development project to produce 35 deliverables. However, a different approach might be needed for a high-risk system development project that has very uncertain functional and technical requirements at the beginning of development. Therefore, the SEP methodology provides for a full sequential SDLC work pattern and for alternative SDLC work patterns. It also provides a work pattern to accommodate the acquisition and implementation of a commercial off-the-shelf (COTS) product. In the standard SEP methodology, from the Initiation phase through the Closeout phase, this process is termed a full sequential work pattern, which creates the maximum number of deliverables.

During the Planning phase, the Project Manager evaluates the documentation of the system concept, as contained in supporting documentation, and determines if the standard SEP methodology should be used or if an alternative work pattern should be selected instead. The selection of work patterns is based on the selection criteria and the judgement of the involved management. In general, the full sequential work pattern is used (1) if the development type is new or a large modification, (2) if the system development size is large, (3) if the associated mission is critical, (4) if the system development risks are normal or high, and (5) if the complexity of the system development effort is normal or high.

In the full sequential work pattern, a project is divided into phases; the phases are conducted sequentially, and the initiation of each phase depends on a decision to continue that is made during a formal review near the end of the immediately preceding phase. This work pattern reflects a desire to follow a conservative approach to project management.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net