The State’s SDLC deliverables provide a framework to ensure that all aspects of the project are properly and consistently defined, and communicated. Deliverables are required for each MITDP to ensure projects are appropriately planned, managed and executed. These deliverable templates provide a clear structure of required content along with boilerplate language agencies may utilize and customize.
The development and distribution of SDLC deliverables:
- Ensure common understanding among project team members and stakeholders
- Serve as a reminder of specified plans as projects become increasingly complex
- Provide agency senior management and other State officials insight into project risks and ongoing performance
- Encourage the execution of repeatable and consistent processes
The State’s SDLC mandates deliverables in the Planning and Implementation Phase and may vary pending the solution type: Software as a service (SaaS), Custom-off-the-Self (COTS) or Custom development, as identified below. Agencies may use additional deliverables, as needed, for specific project related solutions.
|
Software as a service (SaaS)
|
Commercial-off-the-Shelf (COTS)
|
Custom
|
|
SaaS is a software licensing and delivery model in which software is licensed on a subscription basis and is centrally hosted. It is sometimes referred to as "on-demand software". SaaS is typically accessed by users using a thin client via a web browser.
|
A COTS product is usually a ready-made computer hardware or software product tailored for specific uses and made available to the general public. These products are designed to be readily available and configurable to meet specific pre-defined needs. A COTS product is generally any product available off-the-shelf and does not require
custom development before installation.
|
Custom development is when an organizational need requires a custom software solution. This type of solution is built to satisfy an organizations individual business need.
|
Below are both the required and recommended deliverables based on project phase and type of solution. Please refer to the
Templates section for the respective deliverable templates.
Planning
|
Planning
|
Type
|
Type
|
Type
|
|
Document Name
|
SaaS
|
COTS
|
Custom
|
|
1. ITPR
|
ü
|
ü
|
ü
|
|
2. Project Charter
|
ü
|
ü
|
ü
|
|
3. Project Management Plan
|
ü
|
ü
|
ü
|
|
4. Solution Roadmap
|
ü
|
ü
|
ü
|
|
5. Responsibility Assignment Matrix
|
ü
|
ü
|
ü
|
|
6. Non-Functional Requirements
|
ü
|
ü
|
ü
|
|
7. Functional Requirements Document
|
ü
|
ü
|
ü
|
|
8. Agile Maturity Matrix - Team
|
ü
|
ü
|
ü
|
|
9. Agile Maturity Matrix - Organization
|
–
|
–
|
–
|
Implementation
|
Implementation
|
Type
|
Type
|
Type
|
|
Document Name
|
SaaS
|
COTS
|
Custom
|
|
1. Updated ITPR
|
ü
|
ü
|
ü
|
|
2. Updated Solution Roadmap
|
ü
|
ü
|
ü
|
|
3. System Design Document
|
ü
|
–
|
ü
|
|
4. Data Conversion Plan
|
ü
|
ü
|
ü
|
|
5. Interface Control Document
|
ü
|
ü
|
ü
|
|
6. System Security Plan
|
ü
|
ü
|
ü
|
|
7. Agile Implementation Plan
|
ü
|
ü
|
ü
|
|
8. System Administration Manual
|
–
|
ü
|
ü
|
|
9. Disaster Recovery Plan
|
ü
|
ü
|
ü
|
|
10.
Disposition Plan
|
–
|
–
|
ü
|
|
11.
MITDP Closeout
|
ü
|
ü
|
ü
|
