ٍSDLC+(System+Development+LifeCycle)

**The code is tested at various levels in [|software testing]. Unit, system and user acceptance testings are often performed. This is a grey area as many different opinions exist as to what the stages of testing are and how much if any iteration occurs. Iteration is not generally part of the waterfall model, but usually some occur at this stage.** **Following are the types of testing:**
 * **Defect testing**
 * **Path testing**
 * **Data set testing.**
 * **Unit testing**
 * **System testing**
 * **Integration testing**
 * **Black box testing**
 * **White box testing**
 * **Regression testing**
 * **Automation testing**
 * **User acceptance testing**
 * **Performance testing**
 * **Production process that ensures that the program performs the intended task.**

===<span style="background-attachment: initial; background-clip: initial; background-color: initial; background-image: none; background-origin: initial; background-position: initial initial; background-repeat: initial initial; border-bottom-color: initial; border-bottom-style: none; border-bottom-width: initial; color: black; font-size: 17px; margin-bottom: 0.3em; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 0.17em; padding-top: 0.5em; width: auto;"> Management and control === <span style="background-color: transparent; border: initial none initial; clear: right; display: block; float: right; margin-bottom: 0.8em; margin-left: 1.4em; margin-right: 0px; margin-top: 0.5em; width: auto;"><span style="background-color: #f9f9f9; border: 1px solid #cccccc; display: block; font-size: 12px; min-width: 100px; overflow-x: hidden; overflow-y: hidden; padding: 3px !important; text-align: center; width: 402px;"><span style="background-attachment: initial; background-clip: initial; background-color: initial; background-image: none; background-origin: initial; background-position: initial initial; background-repeat: initial initial; color: #0645ad; text-decoration: none;"> <span style="border: initial none initial; display: block; font-size: 11px; line-height: 1.4em; padding: 3px !important; text-align: left;"><span style="background-attachment: initial !important; background-clip: initial !important; background-color: initial !important; background-image: none !important; background-origin: initial !important; border: initial !important; color: #0645ad; display: block; float: right; text-decoration: none;"> **SDLC Phases Related to Management Controls.<span style="background-attachment: initial; background-clip: initial; background-color: initial; background-image: none; background-origin: initial; color: #0645ad; font-style: normal; font-weight: normal; line-height: 1em; text-decoration: none; white-space: nowrap;">[|[7]] ** <span style="line-height: 1.5em; margin-bottom: 0.5em; margin-left: 0px; margin-right: 0px; margin-top: 0.4em;">**The Systems Development Life Cycle (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.** <span style="line-height: 1.5em; margin-bottom: 0.5em; margin-left: 0px; margin-right: 0px; margin-top: 0.4em;">**To manage and control any SDLC initiative, each project will be required to establish some degree of a <span style="background-attachment: initial; background-clip: initial; background-color: initial; background-image: none; background-origin: initial; background-position: initial initial; background-repeat: initial initial; color: #0645ad; text-decoration: none;">[|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. 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**