<P> The SDLC phases serve as a programmatic guide to project activity and provide a flexible but consistent way to conduct projects to a depth matching the scope of the project . Each of the 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 during each SDLC phase while executing projects . Control objectives help to provide a clear statement of the desired result or purpose and should be used throughout the entire SDLC process . Control objectives can be grouped into major categories (domains), and relate to the SDLC phases as shown in the figure . </P> <P> To manage and control any SDLC initiative, each project will be required to establish some degree of a work breakdown structure (WBS) to capture and schedule the work necessary to complete the project . The WBS and all programmatic material should be kept in the "project description" section of the project notebook . The WBS format is mostly left to the project manager to establish in a way that best describes the project work . </P> <P> There are some key areas that must be defined in the WBS as part of the SDLC policy . The following diagram describes three key areas that will be addressed in the WBS in a manner established by the project manager . The diagram shows coverage spans numerous phases of the SDLC but the associated MCD has a subset of primary mappings to the 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 . </P> <P> The upper section of the work breakdown structure (WBS) should identify the major phases and milestones of the project in a summary fashion . In addition, the upper section should provide an overview of the full scope and timeline of the project and will be part of the initial project description effort leading to project approval . The middle section of the WBS is based on the seven systems development life cycle phases as a guide for WBS task development . The WBS elements should consist of milestones and "tasks" as opposed to "activities" and have a definitive period (usually two weeks or more). Each task must have a measurable output (e.x. document, decision, or analysis). A WBS task may rely on one or more activities (e.g. software engineering, systems engineering) and may require close coordination with other tasks, either internal or external to the project . Any part of the project needing support from contractors should have a statement of work (SOW) written to include the appropriate tasks from the SDLC phases . 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 external resources such as contractors . </P>

The primary output of the analysis phase is the system proposal