SYSTEM DEVELOPMENT LIFECYCLE

NOTE :: Various file formats are used on this page that may require download. If larger than 1mb, it will take longer to download. For instructions or more information, please visit our download page.

SYSTEM DEVELOPMENT LIFECYCLE 1.1

Download the entire document. [File date: May 8, 2007 Rev. 1]
(pdf, 1.6mb | doc, 1.5mb)

Supporting documents and deliverables templates.

Strategic IT Planning Phase
- DPI-Technical Standards [File date: Oct. 16, 2007 Rev. 5]
  This document describes the technical standards used by NCDPI.
  (pdf, 165kb | doc, 191kb)
System Planning Phase
- Buy vs Build Analysis - pending
- Change Management Process [File Date: Aug 2, 2007, Rev. 0]
  A project will undergo changes during some point in the software development life cycle (SDLC). The key is controlling the changes to manage the impact to the project plan, budget, and implementation schedule.
  (pdf, 210kb | doc, 265kb)
- Concept of Operations [File date: May 4, 2007 Rev. 0]
  The Concept of Operations (CONOPS) document is a high-level requirements document that provides a mechanism for users to describe their expectations of the system.
  (pdf, 104kb | doc, 102kb)
- Configuration Management Plan [File date: May 4, 2007 Rev. 1]
  In the early planning phase every IT plan all configuration items need to be identified and baselined.
  (pdf, 88kb | doc, 155kb)
- Cost Benefit Analysis [File date: June 6, 2007 Rev. 3]
  In the initial planning phase a cost-benefit analysis needs to be conducted to evaluate the value of implementing the system.
  (pdf, 141kb | doc, 263kb)
- Procurement Plan [File date: Oct. 18, 2006 Rev. 4]
  A Project Procurement Plan is required when the decision to purchase Information Technology (IT) has been made by the Project Team.
  (pdf, 389kb | doc, 743kb)
- Project Management Plan [File date July 26 2007, Rev. 1]
  To provide a plan, appropriate for the project, that will be used to manage the project and provide a means for updating the plan as the project progresses.
  (pdf, 291kb | doc, 398kb)
- TS Addendum to PMP [File Date: July 26, 2007, Rev. 1]
  (pdf, 81kb | doc, 101kb)
- Quality Assurance/Software Test Plan [File Date: Aug. 23, 2007, Rev.0]
  The main purpose of the Quality Assurance/Software Test Plan (QA/STP) is to guarantee that the standards and procedures established, by the NC Department of Public Instruction – Technology and Information Services Division, for ensuring quality software are followed throughout the system development life cycle (SDLC).
  (pdf, 103kb | doc, 124kb)
- Risk Identification Plan - pending
- Risk Management Plan [File date: May 4, 2007 Rev. 1]
  The Risk Management Plan (RMP) is tracking risks in a risk identification list which is a critical facet of successful system development management.
  (pdf, 57kb | doc, 135kb)
- Software Development Plan [File date: May 4, 2007 Rev. 0]
  The Software Development Plan (SDP) describes a developer's plans for conducting a software development effort.
  (pdf, 215kb | doc, 264kb)
- Software Installation Plan [File date: May 8, 2007 Rev. 0]
  The Software Installation Plan (SIP) is a plan for installing software at user sites, including preparations, user training, and conversion from existing systems.
  (pdf, 94kb | doc, 132kb)
- Software Transition Plan [File date: May 4, 2007 Rev. 0]
  The Software Transition Plan (STrP) identifies the hardware, software, and other resources needed for life cycle support of deliverable software and describes the developer's plans for transitioning deliverable items to the support agency.
  (pdf, 86kb | doc, 155kb)
- System Architecture & Component Definition - pending
- System Boundary Definition [File date: June 27, 2007 Rev. 0]
  The System Boundary Document (SBD) provides guidance on how to establish the boundaries of an information technology (IT) project.
  (pdf, 104kb | doc, 169kb)
- System Engineering Management Plan [File date: June 6, 2007 Rev. 1]
  The System Engineering Management Plan describes the system engineering process to be applied to the project and assigns specific organizational responsibilities for the technical effort, to include contracted or subcontracted technical tasks.
  (pdf, 104kb | doc, 172kb)
- System - Level Scope Document - pending
- System Security Plan [File date: Dec. 15, 2006 Rev. 0]
  This document identifies the system, the level of sensitivity, management controls to govern the access of the system from internal and external accounts as well as the operational and technical controls.
  (pdf, 186kb | doc, 169kb)
- Validation and Verification Plan [File date: Jan. 30, 2007 Rev. 0]
  Software verification and validation (V & V) is an aid in determining that the software requirements are implemented correctly and completely and are traceable to system requirements.
  (pdf, 72kb | doc, 80kb)
Requirements Phase
- Business Requirements Specification - [File Date: July 26, 2007, Rev. 1]
  This document will provide the users with a formal written high level description of what the proposed system will do.
  (pdf, 111kb | doc, 322kb)
- Technical and Other Requirements Specification - [File Date: Aug 3, 2007, Rev. 1]
  This document will provide the users with a formal written high level description of technical and other non-business requirements for the proposed system
  (pdf, 112kb | doc, 312kb)
- Integration Document [File date: Nov. 16, 2006 Rev. 0]
  The integration document defines the activities necessary to integrate the software units and software components into the software item.
  (pdf, 62kb | doc, 84kb)
- Interface Requirements Specification [File date: June 6, 2007 Rev. 0]
  The Interface Requirements Specification (IRS) specifies the requirements imposed on one or more systems, subsystems, Hardware Configuration Items (HWCIs), Computer Software Configuration Items (CSCIs), manual operations, or other system components to achieve one or more interfaces among these entities.
  (pdf, 63kb | doc, 124kb)
- Operational Concept Description [File date: June 6, 2007 Rev. 0]
  The Operational Concept Description (OCD) describes a proposed system in terms of the user needs it will fulfill, its relationship to existing systems or procedures, and the ways it will be used.
  (pdf, 99kb | doc, 164kb)
- Requirement Document - pending
- Software Product Specification [File date: June 6, 2007 Rev. 0]
  The Software Product Specification (SPS) contains or references the executable software, source files, and software support information, including "as built" design information and compilation, build, and modification procedures, for a Computer Software Configuration Item (CSCI).
  (pdf, 58kb | doc, 125kb)
- Software Requirements Specification [File date: June 6, 2007 Rev. 0]
  The Software Requirements Specification (SRS) specifies the requirements for a Computer Software Configuration Item (CSCI) and the methods to be used to ensure that each requirement has been met.
  (pdf, 111kb | doc, 183kb)
- System Requirements - pending
- System Specification [File date: June 6, 2007 Rev. 0]
  The System Specification (SS) specifies the requirements for a system or subsystem and the methods to be used to ensure that each requirement has been met.
  (pdf, 96kb | doc, 164kb)
- Test and Evaluation Plan - pending
Design Phase
- Conversion Plan File date: [May 3, 2007 Rev. 0]
  The Conversion Plan describes the strategies involved in converting data from an existing system to another hardware or software environment.
  (pdf, 103kb | doc, 165kb)
- Database Design Description [File date: June 6, 2007 Rev. 0]
  The Database Design Description (DBDD) describes the design of a database, that is, a collection of related data stored in one or more computerized files in a manner that can be accessed by users or computer programs via a database management system (DBMS).
  (pdf, 66kb | doc, 140kb)
- Implementation Plan [File Date: July 20, 2007 Rev. 1]
  The Implementation Plan describes how the information system will be deployed, installed and transitioned into an operational system.
  (pdf, 179kb | doc, 285kb)
- Interface Control Document [File date: May 3, 2007 Rev. 0]
  The Interface Control Document (ICD) created using this template will define one or more interfaces between two systems.
  (pdf, 108kb | doc, 172kb)
- Interface Design Description [File date: June 6, 2007 Rev. 0]
  The Interface Design Description (IDD) describes the interface characteristics of one or more systems, subsystems, Hardware Configuration Items (HWCIs), Computer Software Configuration Items (CSCIs), manual operations, or other system components.
  (pdf, 54kb | doc, 120kb)
- Software Design Description [File date: June 6, 2007 Rev. 0]
  The Software Design Description (SDD) describes the design of a Computer Software Configuration Item (CSCI).
  (pdf, 73kb | doc, 141kb)
- Software User Manual
  The Software User Manual (SUM) tells a hands-on software user how to install and use a Computer Software Configuration Item (CSCI), a group of related CSCIs, or a software system or subsystem
  (pdf, 78kb | doc, 142kb)
- System Design Description [File date: June 6, 2007 Rev. 0]
  The System Design Description (SDD) describes the system- or subsystem-wide design and the architectural design of a system or subsystem.
  (pdf, 66kb | doc, 136kb)
- System Design-Technical Architecture [File date: Nov. 16, 2006 Rev. 0]
  The System Design Template has been designed to enable agencies to provide an increasing amount of detail to Enterprise Technology Strategies (ETS) over the life of a project.
  (pdf, 176kb | doc, 293kb)
- System Security Risk Assessment - pending
- User and Operators Training Plan - pending
- Preliminary Design Review [File Date: July 20, 2007, Rev. 0]
  The Preliminary Design Review (PDR) is a formal inspection of the high-level architectural design of an automated system and its software, which is conducted to achieve confidence that the design satisfies the functional and nonfunctional requirements and is in conformance with ITS / DPI enterprise architecture.
  (pdf, 55kb | doc, 88kb)
- Critical Design Review [File Date: July 20, 2007, Rev. 0]
  The Critical Design Review (CDR) is a multi-disciplined product and process assessment to ensure that the system under review can proceed into system fabrication, demonstration, and test, and can meet the stated performance requirements within cost (program budget), schedule (program schedule), risk, and other system constraints.
  (pdf, 63kb | doc, 108kb)
Development Phase
- Contingency Plan - pending
- Integration Configuration Document - pending
- Software Version Description [File date: June 6, 2007 Rev. 0]
  The Software Version Description (SVD) identifies and describes a software version consisting of one or more Computer Software Configuration Items (CSCIs).
  (pdf, 51kb | doc, 114kb)
- System / Application Software - pending
- Test Files and Test Data - pending
Integration and Test Phase
- Integration Configuration Document - pending
- Software Test Description [File date: June 6, 2007 Rev. 0]
  The Software Test Description (STD) describes the test preparations, test cases, and test procedures to be used to perform qualification testing of a Computer Software Configuration Item (CSCI) or a software system or subsystem.
  (pdf, 66kb | doc, 135kb)
- Software Test Plan [File date: June 6, 2007 Rev. 0]
  The Software Test Plan (STP) describes plans for qualification testing of Computer Software Configuration Items (CSCIs) and software systems.
  (pdf, 76kb | doc, 139kb)
- Software Test Report [File date: June 6, 2007 Rev. 0]
  The Software Test Report (STR) is a record of the qualification testing performed on a Computer Software Configuration Item (CSCI), a software system or subsystem, or other software-related item.
  (pdf, 57kb | doc, 123kb)
- System / Application Security Certification - pending
- Test Analysis Document - pending
- User Acceptance Signoff - pending
Deployment Phase
- Change Implementation Process - pending
- Computer Unit Operations Manual [File date: June 6, 2007 Rev. 0]
  The Computer Unit Operations Manual (CUOM) provides information needed to operate a given computer and its peripheral equipment.
  (pdf, 58kb | doc, 122kb)
- Hosting Center Operator Manual [File date: June 6, 2007 Rev. 0]
  The Hosting Center Operator Manual (HCOM) provides personnel in a computer center or other centralized or networked software installation information on how to install and operate a software system.
  (pdf, 69kb | doc, 131kb)
- Post-Deployment Review - pending
- Production Configuration Management Document - pending
- Software Input/Output Manual
  The Software Input/Output Manual (SIOM) tells a user how to access, submit inputs to, and interpret output from, a batch or interactive software system that is run by personnel in a computer center.
  (pdf, 94kb | doc, 157kb)
- Software Vault Check-in and Confirmation - pending
Operations / Maintenance Phase
- Computer Programming Manual - pending
- Firmware Support Manual - pending
- Maintenance Manual
  The Maintenance Manual provides information needed to maintain a given computer system.
  (pdf, 67kb | doc, 134kb)
- System Administration Manual [File Date: June 27, 2007 Rev. 0]
  Setup and configuration of the system, maintenance schedule, account management, system backup procedures, etc.
  (pdf, 212kb | doc, 143kb)
- System Operations Manual File date: [Nov. 15, 2006 Rev. 0]
  Documents Day-to-Day batch runs, diagnostic procedures, error messages and problem resolution, etc.
  (pdf, 81kb | doc, 93kb)
- User Satisfaction Review - pending
Disposition Phase
Other Supporting Documents
- Lessons Learned Checklist [File Date: June 26, 2007, Rev. 0]
  (pdf, 37kb | doc, 258kb)
- NC Project Closeout Review [File Date: June 26, 2007, Rev. 0]
  (pdf, 51kb | doc, 57kb)
- State EPMO Staffing Plan [File Date: June 26, 2007, Rev. 0]
  (xls, 143kb)
- User Satisfaction Review [File Date: August 3, 2007, Rev. 0]
  The User Satisfaction Review Survey is used to gather the data needed to analyze current user satisfaction with the performance capabilities of an existing application.
  (pdf, 52kb | doc, 110kb)