Instructions: Scope: Define Each Stage/Step of The SDLC Process and Provide Templates For Deliverables

Instructions
Scope: Define each

Stage/Step of the SDLC
Process and provide
templates for Deliverables
1. Sheet 1 is the ONLY sheet where the details

have to be filled in- ONLY Column B, C, D have
to be Filled in.
2. Please use the internet and other resources
to fill in the details.
3. All other "Sheets" EXCEPT "SHEET 1" in the
workbook are Only for Reference- HELPFUL
LINKS
4. I have provided helpful links for exactly the
reason. For guidance but this should not be
Included Documents used as theB-only source
1. Column Fill in Description for Each
Stage/Step- Begin with filling this column.
2. Column C- Find 1to2 Questions that defines
the scope of that Stage/Step
3. Column D- Deliverables- Which Deliverables
are required to complete Stage/Step?
4. Column E/Separate Folder-
Template/Documentation- Find and Insert
templates for documentation required to
complete the Step.
5. Validate and insert any additional Steps
Necessary
Steps- Column A has all the 6. (Optional)- Similar DSDM methodology and
Stage/Steps steps
Stage Description
Requirement analysis:
Trying to gather requirements to
define an idea
Brainstorming Phase
Feasibility Analysis
Minute Requirement Details
Existing Problems
Research
Cost
Scope
Risk Management
Design:
Turn requirement system design
Start with high level design
Move to functional design
Technical details - risk,
technology, capability,
constraints, time, budget
Risk
Technology
Capability
Constraints
Time
Budget
Develop:
Build software of work in small
Assignment
units
Completion of units
Deliver the units
Unit testing
Automated unit testing
Integration and Testing:

All units come together, teams
combine work
Debugging
Make sure functionality works
when units put together
Manual Testing
Automated testing
Implementation/Deployment: -
installation of newly developed
system
Necessary training is provided
Data and components are
moved from higher
environments (from integration
to user test)
User acceptance testing
Defects are logged
A solid system and fixed is
for production
prepared
Operation and Maintenance:

Maintenance of the system
Updates or patches as required
to fix bugs
Slowly working of the system
moving to user control
Change management takes
place - users identify
change
Helpful Links Helpful Links:
- DO NOT USE THIS SHEET
SOLELY FOR THIS TASK. All
other "Sheets" EXCEPT
"SHEET 1" in the
workbook are Only for
Reference. This is to help
provide some guidance on
this project but it should
not be used as the only
reference (please use your
expertise and google).The
reference sheet questions
are based on Waterfall
Method. We are trying to
fill in information for Agile
Method.
https://www.aits.uillinois.edu/common/pages/DisplayFile.aspx?itemId=102351
Similar
1 question to be Insert Template/ DSDM
answered for each Documentation for Each Methodolo
phase? Deliverables Deliverable gy
1. Business Requirements
Document
2. Requirements Traceability
Matrix
Software Development Project Checkl
NOTE: All steps are required for Class A projects
Opportunity Assessment Phase

Class B
Required
Activity Steps Completed
Idea Generation
Receive or solicit ideas from the customers/clients Yes
Define the Opportunity Assessment Team Yes
Refine the idea through discussions with the customer, research
and benchmarking of similar areas Yes
Idea Structuring
Identify and confirm sponsorship Yes
Document high level business need and significant milestones. Yes
Identify customers, users, and stakeholders Yes
Define high-level business benefits Yes
Identify high-level requirements and critical success factors Yes
Identify related projects/affected systems. List below: Yes
Outline scope, schedule and resources for the next phase Yes
Opportunity Assessment Approval
Prepare and submit the Project Initiation Document Yes
Prioritize idea based on business criteria and resource Yes
constraints
Conduct the Opportunity Assessment Review and obtain approval Yes
Enter information into the project tracking system and time
reporting system
Phase Closure
Assess the Opportunity Assessment Process to capture lessons
learned Yes
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:
430821513.xlsx 7 of 48
are Development Project Checklist
Project Name
Program Mgr.
Project Mgr.
Deliverable Leader Participants
Identify Sponsor
Project Initiation Document
Project Initiation Document, Project Schedule
Lessons Learned
ceptual solution
Date:
430821513.xlsx 8 of 48
Software Development Project Checklist
Concept Phase
Class B
Required
Phase Start Up
Define /refine Concept (Initiating) Team and identify project
manager Yes
Conduct project planning meeting.
Review lessons learned Yes
Develop Concept Phase schedule Yes
Implement time tracking status reporting Yes
High-Level Requirements Identification
Understand and further define business need Yes
Define/refine business requirements, vision, scope, critical
requirements, and risks for the project Yes
Define assumptions and dependencies Yes
Options Analysis
Develop and analyze potential concepts to meet business need Yes
Conduct initial enterprise architecture, data architecture, and
technical planning review Yes
Notify and include future support services and operations
organizations Yes
Develop a recommended approach Yes
Executive presentation of recommended approach
430821513.xlsx 9 of 48
Project Definition
Develop ROM estimate for resources/costs and high-level
schedule/timeline for the project Yes
Finalize Concept Analysis Document and architecture diagram Yes
Continue to develop the Business Case Yes
Refine Project Initiation Document and complete Project Charter Yes
Plan for next phase by developing schedule, budget, and identify
resources Yes
Concept Approval
Prepare for and participate in Concept Checkpoint Review Yes
Phase Closure
Document lessons learned from Concept Phase Yes
Exit Criteria
 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:
430821513.xlsx 10 of 48
Development Project Checklist
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist, Organizational Chart

Project Phase Kickoff Presentation
Project Schedule
Project Initiation Document, Project Charter

Project Charter
Concept Analysis Document

Concept Analysis Executive Summary
430821513.xlsx 11 of 48
(Schedule and Costs Summary section) of
Business Case
Business Case
Project Initiation Document, Project Charter,
Project Schedule, Project Timeline
Lessons Learned
ect plan
Date:
430821513.xlsx 12 of 48
Software Development Project Checklis
Requirements Phase
Class B
Required
Phase Start Up
Define/refine the Requirements (Planning) team and review roles
and responsibilities Yes
Initiate controlling processes. Yes

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 Yes
Initiate engagement with dependent areas. This includes
operations, training, support services, data, and documentation
management. Yes
Initiate development of a work breakdown structure. Review
example in SD Handbook. Yes
Identify Configuration Management Plan, requirements
management process, work products, change control, version
control, requirements with status tracking. Yes
Select change control, version control, and traceability tools Yes

Review and revise business objectives, scope and vision from
Concept phase, document the "As-Is" and "To-Be" business
processes and any process improvement opportunities Yes
430821513.xlsx 13 of 48
User Requirements Definition
Identify the project requirements, decision process, and decision
makers Yes
Define approach for requirements definition, documenting,

communicating requirements and identify log tool Yes
Develop and prioritize use cases for portions of the software
application to be developed Yes
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
Technical Requirements Definition
Define data requirements. Create data models to document, as
needed. Yes
Identify, define, and document technology, infrastructure, and
support requirements. Conduct/refine enterprise and data
architectural reviews. Yes
Define the user documentation deliverable types and the training
deliverables needed for the application/system.
Elaborate the use cases into the necessary functional
requirements Yes
Develop user interface prototypes.
Develop and evaluate application/system input and output
requirements, screens, menus, reports, and forms
430821513.xlsx 14 of 48
Requirements Documentation and Review
Prioritize features and/or functional requirements Yes
Develop Software Requirements Specification Yes

Plan and conduct Requirements Walkthrough with the
Development Team. Gather feedback and approval for the
Software Requirements Specification Yes
Plan and conduct User Requirements Walkthrough. Gather
feedback and approval for the Software Requirements
Specification Yes
Test Planning
Begin development of Test Plan. Evaluate test risks to determine
an appropriate test strategy. Include a high level test schedule. Yes
Develop conceptual test cases Yes
Develop initial draft of User Acceptance Criteria Yes

Use the test cases to verify use cases, technical requirements,
and prototypes Yes
430821513.xlsx 15 of 48
Requirements Refinement
Repeat requirements definition steps, as required. Refine SRS, if
required. Yes
Define/revise the System diagram Yes
Project Planning
Refine/validate project approach and project lifecycle. Yes
Begin development of the Project Notebook and management
approaches Yes
Identify Project Team Members and document the project
organization. Yes
Establish Communication strategy. Yes
Create Steering Committee presentation
Starting with the WBS, develop a project schedule and budget.
Estimate work effort and duration for the project activities. Yes
Refine the Business Case. Yes
Review the project schedule, budget and SRS with the project
team, sponsors, and other appropriate stakeholders. Yes
Prepare Project Funding deliverables and review with the funding
approval authority Yes
Review the Project Funding deliverables with senior staff.
Plan for next phase Yes
Planning/Funding Approval
Prepare for, schedule, and participate in Project Funding
Checkpoint Review. Obtain Project Funding number Yes
Phase Closure
Baseline requirements, schedule, and budget and place all
configurable documents (e.g., SRS, Project Plan, etc.) in the
project repository Yes
Document lessons learned. Yes
Exit Criteria
 "Go" decision for resources for remainder of the lifecycle and resource commitment for the design phase
 Project Funding number obtained
Signature:
430821513.xlsx 16 of 48
e Development Project Checklist
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist
PM Executing / Controlling templates, Project
Plan, Project Notebook
Work Breakdown Structure (WBS)

Request for Change, Change Management Log,
Software Requirements Specification,
Requirements Traceability Matrix
Request for Change, Change Management Log,
and Software Requirements Specification,
Business Requirements Catalog, Concept Analysis

Document
430821513.xlsx 17 of 48
Business Requirements Catalog
Business Requirements Catalog, Software
Requirements Specification, Requirements
Traceability Matrix
Use Case
Use Case

Technical Evaluation, Support Expectations

Documentation Plan (no template), Training Plan,
Project Schedule
430821513.xlsx 18 of 48
Test Plan (Master) or Test Plan (Minor), Project

Schedule (Test Phase)

Requirements Traceability Matrix, Test Plan
430821513.xlsx 19 of 48
Systems Diagram
Organization Chart
Communications Matrix
Steering Committee Presentation
Project Schedule, Timeline, Project Budget

Business Case

Requirements Traceability Matrix, Project
Schedule, Project Budget
Lessons Learned
commitment for the design phase
Date:
430821513.xlsx 20 of 48
Design Phase
Class B
Required
Phase Start Up
Initiate Design Acivities Yes

Implement Control processes and activities. Yes

Create mechanisms for tracking, managing, and changing design
specs. (Configuration Management) Yes
Define/Refine project team roles and responsibilities Yes
High-Level Design
Establish a design strategy
Create a high level design based on requirements and identify
impact risks Yes
Decompose the system into subsystems and outline the
communications Yes
Create Prototype with inputs and outputs Yes
Create logical data models and design data model Yes
Identify DBMS platform, hardware, operating system Yes
Conduct high level architecture design review Yes
Baseline High Level Design Document Yes
430821513.xlsx 21 of 48
Detailed Design
Create physical databases Yes
Create Detailed Design, design system inputs and outputs, user
interfaces, and dialogues Yes
Update traceability matrix Yes

Test and Documentation Planning
Continue development of test plan Yes
Continue development of documentation approach Yes
Design Approval
Obtain design approval Yes
Phase Closure
Begin development of the Deployment Strategy and Plan,
focusing on the Strategy section. Yes
Begin development of the System/Application Support Document
to be used for long-term support issues. Yes
Revise Project Schedule and Project Budget as required, and
plan for the next phase. Yes
Document Lessons Learned Yes
Exit Criteria
 Key Deliverables prepared
 Go decision to develop the application
Signature:
430821513.xlsx 22 of 48
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist, Software Requirements

Specification, Requirements Traceability Matrix
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
430821513.xlsx 23 of 48
Detailed Design (no template)
Test Plan (Master) or Test Plan (Minor)
Deployment Strategy and Plan
Support Expectations
Project Schedule, Project Budget

Lessons Learned
Date:
430821513.xlsx 24 of 48
Development Phase
Class B
Required
Phase Start Up
Initiate Development Activities Yes
Implement Control processes and use the management
approach. Yes
Development Strategy and Planning
Review/revise software integration process Yes
Define development strategy to build application Yes
Evaluate resources for the Development Phase. Yes
Create Unit Test Plan and expected results. Yes
Define/Refine test team. Yes
Determine specific test types and update the Test Plan as
required. Yes
Decompose schedule into logical ‘work packages’ Yes
Review/revise time tracking, status reporting, issues tracking,
communication procedures Yes
Review/revise defects tracking process Yes
Code Development
Develop code for each module/component. Yes
Perform code analysis Yes
430821513.xlsx 25 of 48
Code Verification
Unit Test each module and document defects in a defect-tracking
process. Yes
Review code to ensure meets specifications Yes
Conduct Code Peer Reviews Yes
Test Planning
Implement “build” procedures, execute smoke tests and fix any
errors that prohibit the build from being tested. Yes
Conduct a walkthrough of the application/system to the test team
and support team and provide tester training and support training Yes
Develop test scripts based on requirements, design
specifications, and code development. Yes
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. Yes
Review the System/Application Support Checklist and update
support documents, as appropriate. Yes
Working with the development team, business partners, and
client, develop test data to be used in testing the application. Yes
430821513.xlsx 26 of 48
Documentation Planning
Conduct a walkthrough of the application/system with the
documentation team.
Create a User Documentation prototype and obtain user Yes
approval.
Development Approval
Prepare for and conduct final development approval. Yes
Phase Closure
Maintain communications and change control processes, project
scheduling and status reporting, and continue to manage any
project issues. Yes
Identify any additional risks, develop appropriate responses, and
update risk log, as appropriate. Yes
Plan for the next phase Yes
Exit Criteria
 Go decision for system testing of the application
Signature:
430821513.xlsx 27 of 48
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist
Organization Chart
Notebook
Organization Chart, Project Schedule

Unit Test Plan (no template)
Organization Chart
Team Member Status Report, Issues Log,

Communications Matrix
Defects Tracking Log
Software Code (no template)
430821513.xlsx 28 of 48
430821513.xlsx 29 of 48
Risk and Response Log
Lessons Learned
Date:
430821513.xlsx 30 of 48
Testing Phase
Class B
Required
Phase Start Up
Initiate Testing Activities Yes

approach. Yes
Test Planning
Review/refine or create the Test Plan. Yes
Review the results of the system verifications. Yes
Determine test tracking tools, defects tracking list, and prepare
Defect tracking log. Yes
Define the type and frequency of interim test reports Yes
Refine test cases and test scripts, as required. Yes
430821513.xlsx 31 of 48
System Validation
Refine the data and load data into the test environment. Yes
Execute test scripts and create a test report. Yes
Report results of test scripts and update test issues and defect
tracking list. Develop interim reports for the project. Yes
Store the data collected during testing in accordance with
configuration management procedures. Yes
Validate the system with functional and structural testing. Yes
Test the support functions for the system defined in the
System/Application Support Document. Revise the
System/Application Support Document Yes
Evaluate test reports to determine accomplishments and report
status. Update the test log. Yes
Refine Acceptance Criteria, and perform User Acceptance

Testing. Obtain User sign off. Yes
430821513.xlsx 32 of 48
Deployment Preparation
Plan for the deployment of the new application/system. Define
process and transitional period for transitioning support. Yes
Identify Deployment team. Yes
Provide training for support staff on the new system/application. Yes
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. Yes
Select appropriate site(s)/users for initial deployment, as required.
Prepare a Deployment Strategy and Plan (DS&P). Yes
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. Yes
Plan and conduct test Review. Gather feedback and approval for
the testing. Yes
Phase Closure
Revise Project Schedule as required, and plan for the
Deployment Phase. Yes
Exit Criteria
 Go decision to deploy the application including user acceptance of the test results
Signature:
430821513.xlsx 33 of 48
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist, Software Requirements

Specification, Requirements Traceability Matrix
Organization Chart
Notebook, Project Schedule (Test Phase)
Defect Tracking Log

Test Report Format (no template - referenced in
the Test Plan Master)
Test Cases (no template), Test Scripts (no
template)
430821513.xlsx 34 of 48
Test log (no template - referenced in the Test Plan
Master)
Requirements Traceability Matrix, Acceptance
Testing
430821513.xlsx 35 of 48
Organization Chart
Project Schedule
Lessons Learned
results
Date:
430821513.xlsx 36 of 48
Documentation and Training Phase

Class B
Required
Phase Start Up
Initiate Documentation and Training Activities Yes
approach. Yes
Documentation Planning and Training Preparation
Determine User documentation requirements Yes
Schedule training facilities and instructors for conducting training,
if appropriate. Yes
Prepare User documentation deliverables and report on
achievements. Yes
Deployment Training and Documentation
Establish a transition process and transitional support period for
the system/application and review. Yes
Create documentation for the support procedures and review. Yes
Develop technical training documentation and provide detailed
technical training to the support services representative. Yes
Provide technical training to the support staff. Yes
Prepare user training material. Yes
Coordinate user training dates and scheduling of attendees. Yes
430821513.xlsx 37 of 48
Documentation and Training Approval
Edit and validate User documentation deliverables. Conduct
checkpoint review. Yes
Edit and validate User training material. Conduct checkpoint
review. Yes
Conduct tech training doc checkpoint review. Yes
Plan for publication and distribution of User Documentation. Yes
Phase Closure
Review training schedule. Modify as appropriate. Yes
Store and control the documents in a secured library. Yes
Revise Project Schedule and Project Budget, as required, and
plan for next phase. Yes
Exit Criteria
 Go decision from the user and client that documentation is complete and acceptable
Signature:
430821513.xlsx 38 of 48
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist
Organization Chart
Notebook
User Documentation (no template)
Technical Training Documentation for Support

Analysts (no template), Support Expectations
Training Plan, User Training materials (no
template)
430821513.xlsx 39 of 48
Project Schedule, Project Budget
Lessons Learned
cceptable
Date:
430821513.xlsx 40 of 48
Deployment Phase
Class B
Required
Phase Start Up
Initiate Deployment Activities Yes
approach. Yes
Review and update the Deployment Strategy and Plan developed
during the Testing Phase, as required. If applicable, review initial
site preparation and training requirements. Yes
Initial Deployment Preparation if applicable)
Confirm that site staff is available to support the deployment.
Review agreement on transitional support period. Yes
Verify the hardware and software configurations for target
installation meet specification. Yes
Confirm that the technology, infrastructure, and support
requirements have been fulfilled. Yes
Create a Deployment Package. Yes

Define and archive the software configuration items for the
release package. Store the release package in the software
configuration library. Yes
Conduct a Release Readiness Review to ensure the package is
installable and operational. Obtain Release Sign-off Yes
Prepare for the initial deployment of the application/system (new
release). Reconfirm scheduled dates, site management
involvement, and involvement of all participating site personnel. Yes
430821513.xlsx 41 of 48
Initial Deployment (if applicable)
Conduct a Deployment Kickoff Meeting at the initial installation
site (if applicable).
Conduct initial deployment test in a pre-production environment
using production data, if possible. Yes
Prepare for Site Business Transition. Yes
Conduct Installation Test and complete User Acceptance Test
Report. Yes
Production-Ready Review and get sign-off of Program Manager. Yes
Monitor initial installation in the production environment.
General Release Preparation
Formalize support procedures for system/application. Yes
Application supportability during transitional period and modify
support plans, as required. Yes
Conduct Readiness Review to determine if software is ready for
general release. Yes
Submit required changes for approval. Yes
Update Deployment phase plan (if required). Yes
Set up managing processes for deploying to other sites. Yes
Verify site staff availability and system structure. Yes
430821513.xlsx 42 of 48
General Release
Install software and test installation at sites. Yes
Monitor installation in the production environment. Yes
Conduct support assessment meeting to develop a plan for
formal transition of support services. Yes
Transition support of the system/application to support services. Yes
Final Client Acceptance
Prepare for and conduct Client Acceptance Review and obtain
customer approval. Yes
Phase Closure
Initiate project closeout procedures. Close out all logs. Yes
Evaluate project performance against Project Plan and archive all
project files and media. Yes
Prepare a written evaluation of the support interaction.
Begin preparing the Project Closeout Report. Document all final
actions. Yes
Prepare and conduct Post-Project Review. Yes

Review and submit lessons learned Yes
Distribute the Post-Project Review report to appropriate staff, and
add to project repository. Yes
Exit Criteria
 Confirmation that project deliverables are accepted and the client is satisfied
 Confirmation that the project is complete
Signature:
430821513.xlsx 43 of 48
Project Name
Program Mgr.
Project Mgr.
SD Phase Checklist
Organization Chart
Notebook
Software Requirements Specification (includes

Traceability Matrix), Change Management Log
Release Readiness Review
Installation Test, Issues Log
430821513.xlsx 44 of 48
Acceptance Test, Installation Test
Initial Release - Final Report
Release Readiness Review

Request for Change, Change Management Log
Project Schedule, Timeline, Project Budget
430821513.xlsx 45 of 48
Deliverables Acceptance
Support Interaction Final Report
Project Closeout Report

Client Satisfaction Survey, Project Survey,
Contractor Exit Checklist
Lessons Learned
Team Member Evaluation
ed
Date:
430821513.xlsx 46 of 48
Post-Deployment Phase
Class B
Required
Operations
Receive and install non-major releases including patches and
minor feature/function upgrades Yes
Conduct on-going operations, including processing, security, data
integrity, backup and disaster recovery and performance
monitoring Yes
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 Yes
Process Improvement
Summarize and analyze program/performance issues, Technical
Defects, and other trends as part of a Post-Deployment Review Yes
Conduct a user satisfaction survey and use this information to
improve practices and processes and to identify deficiencies that
need to be addressed Yes
Measure benefits, cost savings, ROI and compare with initial
project estimates. Update appropriate Knowledge Bases (e.g.,
risk, estimating, lessons learned) Yes
Exit Criteria
Not Applicable
Signature:
430821513.xlsx 47 of 48
Project Name
Program Mgr.
Project Mgr.
Date:
430821513.xlsx 48 of 48

Instructions: Scope: Define Each Stage/Step of The SDLC Process and Provide Templates For Deliverables

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Instructions: Scope: Define Each Stage/Step of The SDLC Process and Provide Templates For Deliverables

Hochgeladen von

Copyright:

Verfügbare Formate

Instructions

Scope: Define each

1. Sheet 1 is the ONLY sheet where the details

Integration and Testing:

Operation and Maintenance:

NOTE: All steps are required for Class A projects

Opportunity Assessment Phase

Deliverable Leader Participants

Project Initiation Document

NOTE: All steps are required for Class A projects

Deliverable Leader Participants

SD Phase Checklist, Organizational Chart

Project Initiation Document, Project Charter

Project Initiation Document, Project Charter

Concept Analysis Document

Concept Analysis Document

NOTE: All steps are required for Class A projects

Initiate controlling processes. Yes

Select change control, version control, and traceability tools Yes

Define approach for requirements definition, documenting,

Further define complex use cases (if required) with additional

Develop Software Requirements Specification Yes

Develop initial draft of User Acceptance Criteria Yes

Deliverable Leader Participants

Work Breakdown Structure (WBS)

Business Requirements Catalog, Concept Analysis

Software Requirements Specification,

Technical Evaluation, Support Expectations

Test Plan (Master) or Test Plan (Minor), Project

Software Requirements Specification,

Project Schedule, Timeline, Project Budget

Software Requirements Specification,

commitment for the design phase

NOTE: All steps are required for Class A projects

Initiate Design Acivities Yes

Implement Control processes and activities. Yes

Update traceability matrix Yes

Deliverable Leader Participants

SD Phase Checklist, Software Requirements

High Level Design, Risk and Response Log

High Level Design

High Level Design

Test Plan (Master) or Test Plan (Minor)

Deployment Strategy and Plan

Project Schedule, Project Budget

NOTE: All steps are required for Class A projects

Create the test environment and setup automated test

Deliverable Leader Participants

Organization Chart, Project Schedule

Test Plan (Master) or Test Plan (Minor)

Team Member Status Report, Issues Log,

Software Code (no template)

NOTE: All steps are required for Class A projects

Initiate Testing Activities Yes

Define the type and frequency of interim test reports Yes

Refine test cases and test scripts, as required. Yes

Refine Acceptance Criteria, and perform User Acceptance

Deliverable Leader Participants

SD Phase Checklist, Software Requirements

Test Plan (Master) or Test Plan (Minor)

Defect Tracking Log

Deployment Strategy and Plan