Editing Systems development life cycle (section)

== Life cycle ==
=== Management and control ===
[[File:SDLC Phases Related to Management Controls.jpg|thumb|SDLC phases related to management controls<ref name="USHR99">U.S. House of Representatives (1999). [http://www.house.gov/content/cao/procurement/ref-docs/SDLCPOL.pdf ''Systems Development Life-Cycle Policy'']. p.13. {{Webarchive|url=https://web.archive.org/web/20131019091833/http://www.house.gov/content/cao/procurement/ref-docs/SDLCPOL.pdf |date=2013-10-19 }}</ref>]]

SDLC phase objectives are described in this section with key deliverables, a description of recommended tasks, and a summary of related control objectives for effective management. It is critical for the project manager to establish and monitor control objectives while executing projects. Control objectives are clear statements of the desired result or purpose and should be defined and monitored throughout a project. Control objectives can be grouped into major categories (domains), and relate to the SDLC phases as shown in the figure.<ref name="USHR99"/>

To manage and control a substantial SDLC initiative, a [[work breakdown structure]] (WBS) captures and schedules the work. The WBS and all programmatic material should be kept in the "project description" section of the project notebook.{{Clarify|reason=What project notebook is that? What does it look like? What sections does it have?|date=January 2023}} The project manager chooses a WBS format that best describes the project.

The diagram shows that coverage spans numerous phases of the SDLC but the associated MCD (Management Control Domains) shows mappings to SDLC phases. For example, Analysis and Design is primarily performed as part of the Acquisition and Implementation Domain, and System Build and Prototype is primarily performed as part of delivery and support.<ref name="USHR99" />

=== Work breakdown structured organization ===
[[File:SDLC Work Breakdown Structure.jpg|thumb|Work breakdown structure<ref name="USHR99"/>]]

The upper section of the WBS provides an overview of the project scope and timeline. It should also summarize the major phases and milestones. The middle section is based on the SDLC phases. WBS elements consist of milestones and tasks to be completed rather than activities to be undertaken and have a deadline. Each task has a measurable output (e.g., analysis document). A WBS task may rely on one or more activities (e.g. coding). Parts of the project needing support from contractors should have a [[statement of work]] (SOW). The development of a SOW does not occur during a specific phase of SDLC but is developed to include the work from the SDLC process that may be conducted by contractors.<ref name="USHR99"/>

=== Baselines ===
Baselines{{Clarify|reason=What is a baseline?|date=January 2023}} are established after four of the five phases of the SDLC, and are critical to the [[Iteration|iterative]] nature of the model.<ref>[[Blanchard, B. S.]], & [[Fabrycky, W. J.]](2006) ''Systems engineering and analysis'' (4th ed.) New Jersey: Prentice Hall. p.31</ref> Baselines become milestones.

* functional baseline: established after the conceptual design phase.
* allocated baseline: established after the preliminary design phase.
* product baseline: established after the detail design and development phase.
* updated product baseline: established after the production construction phase.