1.

Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. The Overall Description
2.1 Product Perspective
2.1.1 System Interfaces
2.1.2 Interfaces
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
2.1.5 Communications Interfaces
2.1.6 Memory Constraints
2.1.7 Operations
2.1.8 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumptions and Dependencies
2.6 Apportioning of Requirements
3. Specific Requirements
3.1 External interfaces
3.2 Functions
3.3 Performance Requirements
3.4 Logical Database Requirements
3.5 Design Constraints
3.5.1 Standards Compliance
3.6 Software System Attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organizing the Specific Requirements
3.7.1 System Mode
3.7.2 User Class
3.7.3 Objects
3.7.4 Feature
3.7.5 Stimulus
3.7.6 Response
3.7.7 Functional Hierarchy
 3.8 Additional Comments
4. Change Management Process

5. Document Approvals

6. Supporting Information
Table of Contents
1 Introduction
1.1. Document Purpose
1.2. Intended Audience
1.3. Project Background
1.4. Purpose of the Business Requirements
1.5. Business Goals/Objectives to be achieved
1.6. Benefits/Rationale
1.7. Stakeholders
1.8. Dependencies on existing systems
1.9. References
1.10. Assumptions
2 Requirements Scope
2.1. In Scope
2.2. Out of Scope
3 Functional Requirements
3.1. Actor Profiles Specification
3.2. Essential Use Case Diagram
3.3. Essential Use Case Specifications
3.4. Function Hierarchy Diagram
3.5. Function Definition Report
3.6. Business Rules
4 Data Requirements
4.1. Data Architecture
4.1.1. Domain Class Diagram
4.1.2. Entity Relationship Diagram
4.2. Data Volumes
4.3. Data Conversion
4.4. Data Retention and Archiving
4.5. FOI/Privacy Implications
4.6. Data Definition Reports
4.6.1. Domain Class Definition Report
4.6.2. Entity Definition Report
5 Non-Functional requirements
5.1. Security Requirements
5.1.1. Authentication
5.1.2. Authorization and Access Controls
5.1.3. Information Security Classification and labelling
5.2. Availability Requirements
5.3. Usability Requirements
5.4. System Help Requirements
5.5. Performance Requirements
 5.6. Scalability Requirements
5.6.1. User Scalability
5.6.2. Application Scalability
6 Interface Requirements
6.1. User Interface Requirements
6.2. System Interface Requirements
7 Business Glossary
 Software Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Opportunity Assessment Phase

Activity Deliverable
Idea Generation
Receive or solicit ideas from the customers/clients
Define the Opportunity Assessment Team
Refine the idea through discussions with the customer, research and
benchmarking of similar areas
Idea Structuring
Identify and confirm sponsorship Identify Sponsor
Document high level business need and significant milestones. Project Initiation Document
Identify customers, users, and stakeholders Project Initiation Document
Define high-level business benefits Project Initiation Document
Identify high-level requirements and critical success factors Project Initiation Document
Identify related projects/affected systems. List below: Project Initiation Document
Outline scope, schedule and resources for the next phase Project Initiation Document, Project Schedule
Opportunity Assessment Approval
Prepare and submit the Project Initiation Document Project Initiation Document
Prioritize idea based on business criteria and resource constraints
Conduct the Opportunity Assessment Review and obtain approval
Enter information into the project tracking system and time reporting
system
Phase Closure
Assess the Opportunity Assessment Process to capture lessons learned
Lessons Learned

Exit Criteria
 Identified Sponsor
 Identified resources to continue next phase
 Key deliverables prepared
 "Go" decision and approval to further define business need and conceptual solution
Signature:

539046147.xlsx 5 of 46
Checklist

Leader Participants

Date:

539046147.xlsx 6 of 46
 Software Development Project Checklist

Concept Phase
Activity
Phase Start Up

Define /refine Concept (Initiating) Team and identify project manager

Conduct project planning meeting.
Review lessons learned
Develop Concept Phase schedule
Implement time tracking status reporting
High-Level Requirements Identification
Understand and further define business need
Define/refine business requirements, vision, scope, critical requirements,
and risks for the project
Define assumptions and dependencies
Options Analysis
Develop and analyze potential concepts to meet business need
Conduct initial enterprise architecture, data architecture, and technical
planning review

Notify and include future support services and operations organizations

Develop a recommended approach
Executive presentation of recommended approach

539046147.xlsx 7 of 46
Project Definition
Develop ROM estimate for resources/costs and high-level
schedule/timeline for the project
Finalize Concept Analysis Document and architecture diagram
Continue to develop the Business Case
Refine Project Initiation Document and complete Project Charter
Plan for next phase by developing schedule, budget, and identify
resources
Concept Approval
Prepare for and participate in Concept Checkpoint Review
Phase Closure
Document lessons learned from Concept Phase

Exit Criteria
 Key deliverables prepared
 Identified resources to continue next phase
 Sponsor confirmed
 Project Manager is identified
 Support services and operations organizations points-of-contact identified
 "Go" decision to commit resources define requirements and develop a project plan
 Notify HEI Liaison of system (if applicable)
Signature:

539046147.xlsx 8 of 46
ftware Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deliverable Leader Participants

SD Phase Checklist, Organizational Chart

Project Phase Kickoff Presentation

Project Schedule

Project Initiation Document, Project Charter

Project Initiation Document, Project Charter

Project Charter

Concept Analysis Document

Concept Analysis Document

Concept Analysis Executive Summary

539046147.xlsx 9 of 46
 (Schedule and Costs Summary section) of Business
Case
Concept Analysis Document
Business Case
Project Initiation Document, Project Charter
Project Initiation Document, Project Charter, Project
Schedule, Project Timeline

Lessons Learned

t identified
elop a project plan

Date:

539046147.xlsx 10 of 46
 Software Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Requirements Phase
Activity Deliverable
Phase Start Up
Define/refine the Requirements (Planning) team and review roles and
responsibilities SD Phase Checklist
Conduct project planning meeting. Project Phase Kickoff Presentation
PM Executing / Controlling templates, Project Plan,
Initiate controlling processes. Project Notebook
Project Approach
Review project approach and validate that the modified waterfall project
lifecycle, identify the project team to complete the phases of the project,
and define project measures of success

Initiate engagement with dependent areas. This includes operations,

training, support services, data, and documentation management.
Initiate development of a work breakdown structure. Review example in
SD Handbook. Work Breakdown Structure (WBS)
Identify Configuration Management Plan, requirements management Request for Change, Change Management Log,
process, work products, change control, version control, requirements Software Requirements Specification, Requirements
with status tracking. Traceability Matrix
Request for Change, Change Management Log, and
Software Requirements Specification, Requirements
Select change control, version control, and traceability tools Traceability Matrix
Review and revise business objectives, scope and vision from Concept
phase, document the "As-Is" and "To-Be" business processes and any Business Requirements Catalog, Concept Analysis
process improvement opportunities Document

539046147.xlsx 11 of 46
User Requirements Definition

Identify the project requirements, decision process, and decision makers Business Requirements Catalog
Business Requirements Catalog, Software
Define approach for requirements definition, documenting, Requirements Specification, Requirements Traceability
communicating requirements and identify log tool Matrix
Develop and prioritize use cases for portions of the software application
to be developed Use Case

Further define complex use cases (if required) with additional techniques
such as data flow diagrams, entity relationship diagrams, state-transition
diagrams, and object class and interaction diagrams Use Case
Technical Requirements Definition
Software Requirements Specification, Requirements
Define data requirements. Create data models to document, as needed. Traceability Matrix

Identify, define, and document technology, infrastructure, and support

requirements. Conduct/refine enterprise and data architectural reviews. Technical Evaluation, Support Expectations
Define the user documentation deliverable types and the training Documentation Plan (no template), Training Plan,
deliverables needed for the application/system. Project Schedule
Software Requirements Specification, Requirements
Elaborate the use cases into the necessary functional requirements Traceability Matrix
Develop user interface prototypes.
Develop and evaluate application/system input and output requirements,
screens, menus, reports, and forms

539046147.xlsx 12 of 46
Requirements Documentation and Review
Prioritize features and/or functional requirements
Software Requirements Specification, Requirements
Develop Software Requirements Specification Traceability Matrix
Plan and conduct Requirements Walkthrough with the Development
Team. Gather feedback and approval for the Software Requirements
Specification

Plan and conduct User Requirements Walkthrough. Gather feedback

and approval for the Software Requirements Specification
Test Planning
Begin development of Test Plan. Evaluate test risks to determine an Test Plan (Master) or Test Plan (Minor), Project
appropriate test strategy. Include a high level test schedule. Schedule (Test Phase)
Develop conceptual test cases
Software Requirements Specification, Requirements
Develop initial draft of User Acceptance Criteria Traceability Matrix, Test Plan
Use the test cases to verify use cases, technical requirements, and
prototypes

539046147.xlsx 13 of 46
Requirements Refinement
Repeat requirements definition steps, as required. Refine SRS, if Software Requirements Specification, Requirements
required. Traceability Matrix
Define/revise the System diagram Systems Diagram
Project Planning
Refine/validate project approach and project lifecycle.
Begin development of the Project Notebook and management
approaches

Identify Project Team Members and document the project organization. Organization Chart
Establish Communication strategy. Communications Matrix
Create Steering Committee presentation Steering Committee Presentation
Starting with the WBS, develop a project schedule and budget. Estimate
work effort and duration for the project activities. Project Schedule, Timeline, Project Budget
Refine the Business Case. Business Case
Review the project schedule, budget and SRS with the project team,
sponsors, and other appropriate stakeholders.
Prepare Project Funding deliverables and review with the funding
approval authority
Review the Project Funding deliverables with senior staff.
Plan for next phase
Planning/Funding Approval
Prepare for, schedule, and participate in Project Funding Checkpoint
Review. Obtain Project Funding number
Phase Closure

Baseline requirements, schedule, and budget and place all configurable Software Requirements Specification, Requirements
documents (e.g., SRS, Project Plan, etc.) in the project repository Traceability Matrix, Project Schedule, Project Budget
Document lessons learned. Lessons Learned

Exit Criteria
 Key deliverables prepared
 "Go" decision for resources for remainder of the lifecycle and resource commitment for the design phase
 Project Funding number obtained
Signature:

539046147.xlsx 14 of 46
ecklist

Leader Participants

539046147.xlsx 15 of 46
539046147.xlsx 16 of 46
539046147.xlsx 17 of 46
Date:

539046147.xlsx 18 of 46
 Software Development Project Checklist

Design Phase
Activity
Phase Start Up

Initiate Design Acivities

Conduct project planning meeting.

Implement Control processes and activities.

Create mechanisms for tracking, managing, and changing design specs.
(Configuration Management)
Define/Refine project team roles and responsibilities
High-Level Design
Establish a design strategy
Create a high level design based on requirements and identify impact
risks

Decompose the system into subsystems and outline the communications

Create Prototype with inputs and outputs
Create logical data models and design data model
Identify DBMS platform, hardware, operating system
Conduct high level architecture design review
Baseline High Level Design Document

539046147.xlsx 19 of 46
Detailed Design
Create physical databases
Create Detailed Design, design system inputs and outputs, user
interfaces, and dialogues

Update traceability matrix

Test and Documentation Planning
Continue development of test plan
Continue development of documentation approach
Design Approval
Obtain design approval
Phase Closure
Begin development of the Deployment Strategy and Plan, focusing on
the Strategy section.
Begin development of the System/Application Support Document to be
used for long-term support issues.
Revise Project Schedule and Project Budget as required, and plan for
the next phase.
Document Lessons Learned

Exit Criteria
 Key Deliverables prepared
 Go decision to develop the application
Signature:

539046147.xlsx 20 of 46
oftware Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deliverable Leader Participants

SD Phase Checklist, Software Requirements

Specification, Requirements Traceability Matrix
Project Phase Kickoff Presentation

PM Executing / Controlling templates, Project Notebook

Configuration Management Plan, Change Control
Management Plan
Organization Chart

High Level Design, Risk and Response Log

High Level Design

High Level Design

High Level Design

539046147.xlsx 21 of 46
Detailed Design (no template)
Software Requirements Specification, Requirements
Traceability Matrix

Test Plan (Master) or Test Plan (Minor)

Deployment Strategy and Plan

Support Expectations

Project Schedule, Project Budget

Lessons Learned

Date:

539046147.xlsx 22 of 46
 Software Development Project Checklist

Development Phase
Activity
Phase Start Up
Initiate Development Activities
Conduct project planning meeting.
Define/Refine project team roles and responsibilities

Implement Control processes and use the management approach.

Development Strategy and Planning
Review/revise software integration process
Define development strategy to build application
Evaluate resources for the Development Phase.
Create Unit Test Plan and expected results.
Define/Refine test team.

Determine specific test types and update the Test Plan as required.
Decompose schedule into logical ‘work packages’
Review/revise time tracking, status reporting, issues tracking,
communication procedures
Review/revise defects tracking process
Code Development
Develop code for each module/component.
Perform code analysis

539046147.xlsx 23 of 46
Code Verification
Unit Test each module and document defects in a defect-tracking
process.
Review code to ensure meets specifications
Conduct Code Peer Reviews
Test Planning
Implement “build” procedures, execute smoke tests and fix any errors
that prohibit the build from being tested.
Conduct a walkthrough of the application/system to the test team and
support team and provide tester training and support training
Develop test scripts based on requirements, design specifications, and
code development.

Create the test environment and setup automated test procedures, as

appropriate. Adapt test reporting procedures based on size, complexity,
and specific project needs. Develop test data management strategy.
Review the System/Application Support Checklist and update support
documents, as appropriate.
Working with the development team, business partners, and client,
develop test data to be used in testing the application.

539046147.xlsx 24 of 46
Documentation Planning
Conduct a walkthrough of the application/system with the documentation
team.
Create a User Documentation prototype and obtain user approval.
Development Approval
Prepare for and conduct final development approval.
Phase Closure
Maintain communications and change control processes, project
scheduling and status reporting, and continue to manage any project
issues.
Identify any additional risks, develop appropriate responses, and update
risk log, as appropriate.
Plan for the next phase
Document Lessons Learned

Exit Criteria
 Key Deliverables prepared
 Go decision for system testing of the application
Signature:

539046147.xlsx 25 of 46
ftware Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deliverable Leader Participants

SD Phase Checklist
Project Phase Kickoff Presentation
Organization Chart

PM Executing / Controlling templates, Project Notebook

Organization Chart, Project Schedule

Unit Test Plan (no template)
Organization Chart

Test Plan (Master) or Test Plan (Minor)

Team Member Status Report, Issues Log,

Communications Matrix
Defects Tracking Log

Software Code (no template)

539046147.xlsx 26 of 46
Test Plan (Master) or Test Plan (Minor)

Support Expectations

539046147.xlsx 27 of 46
Risk and Response Log

Lessons Learned

Date:

539046147.xlsx 28 of 46
 Software Development Project Checklist

NOTE: All steps are required for Class A projects

Testing Phase
Activity
Phase Start Up

Initiate Testing Activities

Conduct project planning meeting.
Define/Refine project team roles and responsibilities

Implement Control processes and use the management approach.

Test Planning
Review/refine or create the Test Plan.
Review the results of the system verifications.
Determine test tracking tools, defects tracking list, and prepare Defect
tracking log.

Define the type and frequency of interim test reports

Refine test cases and test scripts, as required.

539046147.xlsx 29 of 46
System Validation
Refine the data and load data into the test environment.
Execute test scripts and create a test report.
Report results of test scripts and update test issues and defect tracking
list. Develop interim reports for the project.
Store the data collected during testing in accordance with configuration
management procedures.
Validate the system with functional and structural testing.
Test the support functions for the system defined in the
System/Application Support Document. Revise the System/Application
Support Document
Evaluate test reports to determine accomplishments and report status.
Update the test log.

Refine Acceptance Criteria, and perform User Acceptance Testing.

Obtain User sign off.

539046147.xlsx 30 of 46
Deployment Preparation
Plan for the deployment of the new application/system. Define process
and transitional period for transitioning support.
Identify Deployment team.
Provide training for support staff on the new system/application.
Ensure the business users who will be verifying the final deployed
solution are familiar with the documentation and trained in the use of the
new release.
Select appropriate site(s)/users for initial deployment, as required.
Prepare a Deployment Strategy and Plan (DS&P).
Schedule a date and time for the introduction/migration of the new
release.
Testing Approval
Develop Final Test document summarizing all tests, results, defects
found, etc.
Plan and conduct test Review. Gather feedback and approval for the
testing.
Phase Closure
Revise Project Schedule as required, and plan for the Deployment
Phase.
Document Lessons Learned

Exit Criteria
 Key Deliverables prepared
 Go decision to deploy the application including user acceptance of the test results
Signature:

539046147.xlsx 31 of 46
ftware Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deliverable Leader Participants

SD Phase Checklist, Software Requirements

Specification, Requirements Traceability Matrix
Project Phase Kickoff Presentation
Organization Chart
PM Executing / Controlling templates, Project Notebook,
Project Schedule (Test Phase)

Test Plan (Master) or Test Plan (Minor)

Defect Tracking Log

Test Report Format (no template - referenced in the
Test Plan Master)

Test Cases (no template), Test Scripts (no template)

539046147.xlsx 32 of 46
Support Expectations
Test log (no template - referenced in the Test Plan
Master)

Software Requirements Specification, Requirements

Traceability Matrix, Acceptance Testing

539046147.xlsx 33 of 46
 Deployment Strategy and Plan
Organization Chart

Deployment Strategy and Plan

Project Schedule
Lessons Learned

e of the test results

Date:

539046147.xlsx 34 of 46
 Software Development Project Checklist

Documentation and Training Phase

Activity
Phase Start Up
Initiate Documentation and Training Activities
Conduct project planning meeting.
Define/Refine project team roles and responsibilities

Implement Control processes and use the management approach.

Documentation Planning and Training Preparation
Determine User documentation requirements
Schedule training facilities and instructors for conducting training, if
appropriate.

Prepare User documentation deliverables and report on achievements.

Deployment Training and Documentation
Establish a transition process and transitional support period for the
system/application and review.
Create documentation for the support procedures and review.
Develop technical training documentation and provide detailed technical
training to the support services representative.
Provide technical training to the support staff.
Prepare user training material.
Coordinate user training dates and scheduling of attendees.

539046147.xlsx 35 of 46
Documentation and Training Approval
Edit and validate User documentation deliverables. Conduct checkpoint
review.

Edit and validate User training material. Conduct checkpoint review.

Conduct tech training doc checkpoint review.
Plan for publication and distribution of User Documentation.
Phase Closure
Review training schedule. Modify as appropriate.
Store and control the documents in a secured library.
Revise Project Schedule and Project Budget, as required, and plan for
next phase.
Document Lessons Learned

Exit Criteria
 Key Deliverables prepared
 Go decision from the user and client that documentation is complete and acceptable
Signature:

539046147.xlsx 36 of 46
ftware Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deliverable Leader Participants

SD Phase Checklist
Project Phase Kickoff Presentation
Organization Chart

PM Executing / Controlling templates, Project Notebook

User Documentation (no template)

Technical Training Documentation for Support Analysts

(no template), Support Expectations

Training Plan, User Training materials (no template)

539046147.xlsx 37 of 46
 Project Schedule, Project Budget
Lessons Learned

plete and acceptable

Date:

539046147.xlsx 38 of 46
 Software Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deployment Phase
Activity Deliverable
Phase Start Up
Initiate Deployment Activities SD Phase Checklist
Conduct project planning meeting. Project Phase Kickoff Presentation
Define/Refine project team roles and responsibilities Organization Chart

Implement Control processes and use the management approach. PM Executing / Controlling templates, Project Notebook
Review and update the Deployment Strategy and Plan developed during
the Testing Phase, as required. If applicable, review initial site
preparation and training requirements. Deployment Strategy and Plan
Initial Deployment Preparation if applicable)
Confirm that site staff is available to support the deployment. Review
agreement on transitional support period.
Verify the hardware and software configurations for target installation
meet specification.
Confirm that the technology, infrastructure, and support requirements
have been fulfilled.
Software Requirements Specification (includes
Create a Deployment Package. Traceability Matrix), Change Management Log

Define and archive the software configuration items for the release
package. Store the release package in the software configuration library.
Conduct a Release Readiness Review to ensure the package is
installable and operational. Obtain Release Sign-off Release Readiness Review
Prepare for the initial deployment of the application/system (new
release). Reconfirm scheduled dates, site management involvement, and
involvement of all participating site personnel. Installation Test, Issues Log

539046147.xlsx 39 of 46
Initial Deployment (if applicable)
Conduct a Deployment Kickoff Meeting at the initial installation site (if
applicable). Project Phase Kickoff Presentation
Conduct initial deployment test in a pre-production environment using
production data, if possible.
Prepare for Site Business Transition.

Conduct Installation Test and complete User Acceptance Test Report. Acceptance Test, Installation Test
Production-Ready Review and get sign-off of Program Manager.
Monitor initial installation in the production environment. Initial Release - Final Report
General Release Preparation
Formalize support procedures for system/application.
Application supportability during transitional period and modify support
plans, as required.
Conduct Readiness Review to determine if software is ready for general
release. Release Readiness Review
Submit required changes for approval. Request for Change, Change Management Log
Update Deployment phase plan (if required). Project Schedule, Timeline, Project Budget
Set up managing processes for deploying to other sites.
Verify site staff availability and system structure.

539046147.xlsx 40 of 46
General Release
Install software and test installation at sites.
Monitor installation in the production environment.
Conduct support assessment meeting to develop a plan for formal
transition of support services.
Transition support of the system/application to support services.
Final Client Acceptance
Prepare for and conduct Client Acceptance Review and obtain customer
approval. Deliverables Acceptance
Phase Closure
Initiate project closeout procedures. Close out all logs.
Evaluate project performance against Project Plan and archive all project
files and media.
Prepare a written evaluation of the support interaction. Support Interaction Final Report

Begin preparing the Project Closeout Report. Document all final actions. Project Closeout Report
Client Satisfaction Survey, Project Survey, Contractor
Prepare and conduct Post-Project Review. Exit Checklist
Review and submit lessons learned Lessons Learned
Distribute the Post-Project Review report to appropriate staff, and add to
project repository. Team Member Evaluation

Exit Criteria
 Key Deliverables prepared
 Confirmation that project deliverables are accepted and the client is satisfied
 Confirmation that the project is complete
Signature:

539046147.xlsx 41 of 46
klist

Leader Participants

539046147.xlsx 42 of 46
539046147.xlsx 43 of 46
Date:

539046147.xlsx 44 of 46
 Software Development Project Checklist

Post-Deployment Phase
Activity
Operations
Receive and install non-major releases including patches and minor
feature/function upgrades

Conduct on-going operations, including processing, security, data

integrity, backup and disaster recovery and performance monitoring

Monitor project effectiveness and collect performance statistics. Track

issues and defects identified by category and provide information to
business partner and development organizations. Identify any gaps in
performance or quality and take corrective actions. Collect and submit
Technical Defects (i.e., bugs) to Change Control Board or designated
support services
Process Improvement
Summarize and analyze program/performance issues, Technical
Defects, and other trends as part of a Post-Deployment Review
Conduct a user satisfaction survey and use this information to improve
practices and processes and to identify deficiencies that need to be
addressed
Measure benefits, cost savings, ROI and compare with initial project
estimates. Update appropriate Knowledge Bases (e.g., risk, estimating,
lessons learned)

Exit Criteria
Not Applicable
Signature:

539046147.xlsx 45 of 46
ftware Development Project Checklist
Project Name
Program Mgr.
Project Mgr.

Deliverable Leader Participants

Date:

539046147.xlsx 46 of 46