Documentation Traceability Matrix

Life Cycle / SDS Documentation Standards
(SDS Release 3.2 (INTERIM))
Documentation
Type
Acronym
Phase, Activity, Task Where Originated
Phase, Activity, Task Where Updated
Phase, Activity, Task Where Used
External Source
External Destination
Legend: Phases: 0 = Pre-Systems Acquisition; I = Concept and Technology Development; II = System Development and Demonstration; III = Production and Deployment Documentation Types: S = Documentation Standard; N = Non-Standard Entrance/Exit Criteria; R = Reference Acquired Assets and Services N I, II, Program Planning/Management and II, III, Technical Project Planning/ Management - Manage Acquisition
Acquisition Program Baseline
APB
I, Program Planning/Management - Establish/Maintain Acquisition Program Baseline
II, Program Planning/Management - Update Program Documentation
I, Program Planning/Management - Conduct Milestone B Review I, Configuration Management/Quality Assurance - Establish Program Baseline I, II, Program Planning/Management, II, III, Technical Project Planning/ Management - Manage Acquisition II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Configuration Management/ Quality Assurance - Manage Changes to Program Baseline
Acquisition Strategy
I, Program Planning/Management - Determine Acquisition Strategy
I, Program Planning/Management - Establish/Maintain Acquisition Program Baseline - Establish Risk Management Strategy - Conduct Milestone B Review I, II, Program Planning/Management - Estimate Life Cycle Resources II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review I, II, Program Planning/Management, II, III, Technical Project Planning/ Management - Manage Acquisition
August 3, 2001

Allocated Baseline (SAD, SIDD, DBDD, SDD)
II, Deployment Planning - Issue User Advisory
Application
II, Configuration Management/Quality Assurance - Establish Application Allocated Baseline
II, Configuration Management/Quality Assurance - Manage Changes to Application Allocated Baseline
Corporate (Enterprise)
II, Configuration Management/Quality Assurance - Establish Corporate Allocated Baseline
II, Configuration Management/Quality Assurance - Manage Changes to Corporate Allocated Baseline
Analysis of Alternatives Report
AOA
I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives
I, Program Planning/Management - Perform Economic Analysis/CostBenefit Analysis - Certify Compliance with ClingerCohen Act - Conduct Decision Review - Conduct Milestone B Review
Application Release Checklist
II, Software Architecture Design - Prepare Application Release Checklist III, Technical Design - Build Software Development Plan
II, Configuration Management/Quality Assurance - Package Products for Release to Test - Package Products for Release to Production III, Deployment - Convert and Verify Data
Approved Changes to Business Data Model
III, Software Requirements Analysis - Approve Business Model Changes
III, Software Requirements Analysis - Update Business Models III, Software Requirements Analysis - Update Business Models II, Software Requirements Analysis - Update Business Models
Approved Changes to Business Function Model
III, Software Requirements Analysis - Approve Business Model Changes
Approved Changes to Business Process Model
II, Software Requirements Analysis - Approve Business Model Changes
August 3, 2001

Architecture Acquisition/ Installation Plan
I, System Architecture Design - Plan Execution Environment Changes
Architecture Improvement Proposals
III, Operational Performance Oversight - Audit Production System - Measure System Performance
III, Systems Management - Manage System Operations and Maintenance
Architecture Modeling Tools
I, System Architecture Design - Determine Execution Environment Solution
ASBP Inputs
I, Program Planning/Management - Determine Program Management Plans
Automated Strategic Business Plan
I, II, Program Planning/Management - Estimate Life Cycle Resources
Available Functional Analysis Resources
III, Functional Analysis - Prepare Functional Analysis Schedule
Available Staff Hours by Individual
III, Technical Design - Build Software Development Plan
Available Technical Design Resources
III, Technical Design - Prepare Technical Design Schedule
Available Testing Resources
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, (Enterprise Level Performance Test), Enterprise Level Acceptance Test, Operational Test and Evaluation - Train Test Users - Prepare Test Schedule III, System Testing - Develop Test Schedule
August 3, 2001

Baseline/Physical Configuration Audit Checklist Baseline
III, Development - Conduct Baseline Configuration Audit
Physical
II, Configuration Management/Quality Assurance - Conduct Physical Configuration Audit III, System Testing - Perform Physical Configuration Audit
Budget Preparation Guidance
I, Program Planning/Management - Develop Budget Submissions
Business Data Model
II, Software Requirements Analysis - Update Business Models
0, Business Process Review and Improvement - Review Current Business Process 0, Mission Need Establishment - Establish Mission Need I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives - Establish Project Support I, System Requirements Analysis - Define Internal Data Requirements II, Software Requirements Analysis - Perform Detailed Data Analysis - Define Data Conversion Requirements - Integrate Requirements - Approve Business Model Changes - Collect Capacity Planning Data
Business Function Model
0, Business Process Review and Improvement - Review Current Business Process 0, Mission Need Establishment
August 3, 2001

- Establish Mission Need I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives - Establish Project Support II, Software Requirements Analysis - Perform Detailed Function Analysis - Integrate Requirements - Approve Business Model Changes - Collect Capacity Planning Data
Business Process Model
II, Software Requirements Analysis - Perform Detailed Process Analysis - Integrate Requirements - Approve Business Model Changes - Collect Capacity Planning Data
Business Process Reengineering Report
0, Business Process Review and Improvement - Review Current Business Process
0, Mission Need Establishment - Establish Mission Need - Conduct Milestone A Review 0, Customer Relationship - Establish Customer Relationship I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives - Perform COTS Availability Research - Certify Compliance with ClingerCohen Act - Conduct Decision Review - Conduct Milestone B Review I, System Requirements Analysis - Define Systems Operations Requirements II, Program Planning/Management - Conduct Interim Progress Review
Calendar (Holidays)
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation
August 3, 2001

- Prepare Test Schedule III, Technical Design - Build Software Development Plan III, System Testing - Prepare Test Schedule III, Deployment - Develop Delivery Schedule X
Capacity Planning Tools
I, System Requirements Analysis - Determine Capacity Requirements
CCB Report
I, II, III, Program Planning/Management - Maintain Customer Relationship
III, Technical Design - Conduct Configuration Control Board Meeting
Chairman of Joint Chiefs of Staff Instruction (CJCSI) 3170.01B)
0, Mission Need Establishment - Establish Mission Need I, Operational Requirements Definition - Define Operational Requirements
CI Maintenance Form
III, Technical Design - Maintain Configuration Items
CI Size
III, Technical Design - Prepare Release Package Proposal
Clinger-Cohen Act Compliancy Report
I, Program Planning/Management 0, Mission Need Establishment - Certify Compliance with ClingerCohen Act - Conduct Milestone A Review I, Program Planning/Management - Conduct Milestone B Review II, Program Planning/Management - Conduct Milestone C Review
CMIS
II, Technical Project Planning/ Management
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Conduct Testing Peer Review
- Perform Impact Analysis
August 3, 2001

II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Acceptance Test, II, III, Operational Test and Evaluation - Perform Tests III, Requirements Initiation - Record and Analyze Problem - Determine Routing - Evaluate Problem - Resolve Problem Trouble Report - Convert PTR to SCR - Define System Change Requirements - Validate System Change Request - Rank or Prioritize System Change Requests III, Functional Analysis - Prepare Functional Analysis Estimates - Perform Functional Analysis - Establish Analysis Baseline III, Technical Design - Prepare Technical Design Estimates - Perform Technical Design - Maintain Configuration Items - Impact Configuration Change Orders - Establish Design Baseline - Conduct Configuration Control Board Meeting - Lock Release III, Development - Develop Configuration Items III, System Testing - Build Test CIs (Scripts and Data)
III, Technical Design
- Prepare Release Package Proposal III, Development - Conduct Unit Test/Module Test - Update User's Procedures - Update Operating Procedures - Establish Development Baseline III, System Testing - Develop Test Schedule
Command, Control, Communications, Computers, and Intelligence Support Plan
C4ISP
I, Program Planning/Management - Prepare C4I Support Plan
Compliance Certification
II, Program Planning/Management - Conduct Milestone C Review III, Systems Management
August 3, 2001

- Conduct Implementation Readiness Review
Component Cost Analysis
I, Program Planning/Management - Conduct Milestone B Review
Configuration Audit Report Baseline
III, Development
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Conduct Test Readiness Review II, Enterprise Level Acceptance Test - Conduct Enterprise Level Test Readiness Review III, System Testing - Perform Test Readiness Review
- Conduct Baseline Configuration Audit
Functional
II, Configuration Management/Quality Assurance - Conduct Functional Configuration Audit III, System Testing - Perform Functional Configuration Audit
II, Program Planning/Management - Conduct Milestone C Review II, Deployment Planning - Issue User Advisory II, Configuration Management/Quality Assurance - Conduct Physical Configuration Audit - Establish Product Baseline III, System Testing - Certify Testing III, Deployment - Deliver User Advisory - Deliver Release
Physical
II, Configuration Management/Quality Assurance - Conduct Physical Configuration Audit
II, Program Planning/Management - Conduct Milestone C Review
August 3, 2001

III, System Testing - Perform Physical Configuration Audit
II, Configuration Management/Quality Assurance - Establish Product Baseline III, System Testing - Certify Testing
Configuration Management Plan
CMP
I, Configuration Management/Quality Assurance - Develop Enterprise Configuration Management Strategy
I, Configuration Management/Quality Assurance - Establish Configuration Management Strategy III, Systems Management - Establish System Configuration Management Strategy III, Technical Design - Maintain Configuration Items - Build Software Development Plan III, Tracking and Analysis
I, Program Planning/Management - Conduct Milestone B Review I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition I, Configuration Management/Quality Assurance - Establish Program Baseline II, Technical Project Planning/ Management - Assess Technical Project Risks
- Perform Project Tracking and Oversight
II, Configuration Management/ Quality Assurance - Manage Changes to Program Baseline - Establish Other Application Functional Baseline - Establish Corporate Functional Baseline - Manage Changes to Application Functional Baseline - Manage Changes to Corporate Functional Baseline - Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Manage Changes to Application Allocated Baseline - Manage Changes to Corporate Allocated Baseline - Conduct Functional Configuration Audit
August 3, 2001

- Conduct Physical Configuration Audit - Establish Product Baseline III, Systems Management - Establish System Configuration Management Strategy III, Technical Project Planning/ Management - Define Project Process III, Functional Analysis - Establish Analysis Baseline III, Technical Design - Establish Design Baseline - Conduct Configuration Control Board Meeting III, Development - Establish Development Baseline - Conduct Baseline Configuration Audit III, System Testing - Perform Functional Configuration Audit - Perform Physical Configuration Audit
Configuration Management Policy
III, Systems Management - Establish System Configuration Management Strategy
Configuration Management Procedures
I, Configuration Management/ Quality Assurance - Develop Enterprise Configuration Management Strategy - Establish Configuration Management Strategy
I, Configuration Management/ Quality Assurance - Establish Program Baseline Il, Configuration Management/Quality Assurance - Manage Changes to Program Baseline - Establish Other Application Functional Baseline
August 3, 2001
10

- Establish Corporate Functional Baseline - Manage Changes to Other Application Functional Baseline - Manage Changes to Corporate Functional Baseline - Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Manage Changes to Application Allocated Baseline - Manage Changes to Corporate Allocated Baseline - Conduct Functional Configuration Audit - Conduct Physical Configuration Audit - Establish Product Baseline
Continuity of Operations Plan
COOP
II, Program Planning/Management - Develop Continuity of Operations Plan
II, Deployment Planning - Establish Continuity of Operations Capability
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification - Conduct DITSCAP Phase 3, Validation
Conversion Data
II, Software Requirements Analysis - Validate Data Requirements
Corporate Contingency Planning (DFAS 3020.26-R)
II, Program Planning/Management - Develop Continuity of Operations Plan II, Deployment Planning - Establish Continuity of Operations Capability
Cost-Benefit Analysis
I, Program Planning/Management - Perform Economic Analysis/CostBenefit Analysis
August 3, 2001
11

COTS Acceptability Report
II, Program Planning/Management - Determine COTS Acceptability
COTS Product Functional Documentation
I, Program Planning/Management - Evaluate COTS Functional Capability II, Software Architecture Design - Evaluate COTS Technical Capability II, Program Planning/Management - Determine COTS Acceptability II, Software Architecture Design - Evaluate COTS Technical Capability II, Program Planning/Management - Determine COTS Acceptability
COTS Functional Analysis
I, Program Planning/Management - Evaluate COTS Functional Capability
COTS Technical Evaluation
II, Software Architecture Design - Evaluate COTS Technical Capability
Course Evaluation
III, Tracking and Analysis - Obtain Training
Critical Application Software Modules
II, Application Level Software Integration Test - Analyze System Performance
Critical Computer Resources
Current Business Area Data
Current Business Area Processes
Current System Workload Data
0, Business Process Review and Improvement - Determine Business Performance Requirements - Business Process Analysis - Determine Business Performance Requirements - System Requirements Analysis
August 3, 2001
12

Customer Acceptance
I, II, III, Program Planning/Management - Maintain Customer Relationship II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, III, Operational Test and Evaluation - Approve and Certify Test Results
Customer Certification Report
III, System Testing - Certify Testing
Customer Program Charter
III, Technical Project Planning/ Management - Prepare Project Staffing Profile - Prepare Project Funding Profile
Customer Relationship Memorandum of Understanding
MOU
Customer Satisfaction Survey
III, Operational Performance Oversight - Measure System Performance
Data Management Plan
DMP
I, Program Planning/Managemenet - Establish Data Standardization Strategy
I, Program Planning/Management - Conduct Milestone B Review II, Software Requirements Analysis - Perform Detailed Data Analysis
Database Design Description
DBDD
II, Software Architecture Design - Transform Design Data Model
II, Software Architecture Design - Identify and Incorporate Reusable Design Components - Perform Data Conversion Unit/ Module Design II, Software Detailed Design - Complete Database Design III, Technical Design - Perform Technical Design
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Test Planning - Prepare Test Plans II, Software Architecture Design - Identify Corporate Application Program Interfaces (APIs)
August 3, 2001
13

- Identify Application-Internal Application Program Interfaces (APIs) - Transform Design Function/ Process Models - Perform Interface Module Design - Prepare Application Release Checklist - Perform Critical Design Review II, Software Detailed Design - Perform Physical User Interface Design - Define Test Scripts - Design Application Program Interfaces (APIs) - Conduct Peer Review for Design - Perform Integrated Critical Design Review II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces - Test Physical Database and Application Program Interfaces - Construct Functional Process Modules - Construct User Interface Units/ Modules - Conduct Peer Review for Development II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Build Test Environment II, Application Level Software Integration Test - Analyze System Performance II, Enterprise Level Performance Test - Conduct Performance Testing II, Configuration Management/Quality Assurance
August 3, 2001
14

- Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production III, Requirements Initiation - Evaluate Problem III, Development - Establish Development Baseline
Database Scripts
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Build Test Environment
DCII Development Standards and Guidelines Chapter 3, Strategy/ Analysis
N II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Define Interface Requirements - Define Data Conversion Requirements - Conduct Peer Review for Software Requirements - Integrate Requirements - Update Business Models - Validate Data Requirements - Validate Functional Requirements
Chapter 4, Design Standards
II, Software Detailed Design - Complete Process Module Design - Complete Database Design
August 3, 2001
15

- Perform Physical User Interface Design - Design Application Program Interfaces (APIs) - Conduct Peer Review for Design - Perform Integrated Critical Design Review (ICDR)
Chapter 5, Build Standards
II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces - Construct Functional Process Modules - Create On-Line Help Screens - Construct User Interface Units/ Modules - Conduct Peer Review for Development
Chapter 7, Application Environment
I, System Architecture Design - Determine Execution Environment Solution - Determine Execution Environment Release Requirements II, Software Architecture Design - Develop Integrated Software Architecture
DCII Extend Copy Request Form
II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis
II, Software Architecture Design - Establish Design Model
DCII Specification
I, Program Planning/Management - Establish Test and Evaluation Strategy
DD Form 1556
August 3, 2001
16

Decision Review Report
I, Program Planning/Management - Conduct Decision Review
Decision Review Brief
I, Program Planning/Management - Conduct Decision Review
Defense Data Dictionary System
I, Program Planning/Management - Establish Data Standardization Strategy
Design Data Model
II, Software Architecture Design - Develop Integrated Software Architecture - Identify and Incorporate Reusable Design Components - Identify Corporate Application Program Interfaces (APIs) - Identify Application-Internal Application Program Interfaces (APIs) - Perform Interface Module Design - Perform Data Conversion Unit/ Module Design II, Software Detailed Design - Design Application Program Interfaces (APIs)
II, Software Architecture Design - Transform Design Data Model - Generate Developmenjt/Unit Test Database II, Software Detailed Design - Define Test Scripts
Design Function Model
II, Software Architecture Design - Design Integrated Menu Structure - Design Data Handling Screens
II, Software Architecture Design - Develop Integrated Software Architecture - Identify and Incorporate Reusable Design Components - Transform Design Function/Process Models II, Deployment Planning - Establish Transition Strategy II, Software Detailed Design - Define Test Scripts II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces - Create On-Line Help Screens
August 3, 2001
17

Design Process Model
II, Software Architecture Design - Develop Integrated Software Architecture - Identify and Incorporate Reusable Design Components - Identify Corporate Application Program Interfaces (APIs) - Identify Application-Internal Application Program Interfaces (APIs) - Perform Interface Module Design - Perform Data Conversion Unit/ Module Design II, Software Detailed Design - Complete Process Module Design - Design Application Program Interfaces (APIs)
II, Software Architecture Design - Transform Design Function/Process Models II, Deployment Planning - Establish Transition Strategy II, Software Detailed Design
- Define Test Scripts II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces
Design Server Model
II, Software Architecture Design - Transform Design Data Model
II, Software Detailed Design - Complete Database Design
II, Software Architecture Design - Generate Development/Unit Test Database II, Software Coding and Unit/Module Testing - Conduct Peer Review for Development
Development Platform
Development Tool Manuals
II, Technical Project Planning/ Management - Identify/Implement Project Standards - Obtain Technical Training
Development/Unit Test Database
II, Software Architecture Design - Generate Development/Unit Test Database II, Software Coding and Unit/Module Testing
II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces - Conduct Database Performance Test
August 3, 2001
18

- Execute Data Conversion Procedures
- Perform Unit Test/Module Test
DFAS Labor Rate
III, Technical Project Planning/ Management - Prepare Project Staffing Profile
DFAS Resource Management Policy concerning "A" Goals and "C" Goals
DFAS Standard Software Process
III, Technical Project Planning/ Management - Define Project Process
DFAS 3020.26-R, Corporate Contingency Planning
DFAS 8000.1-R, Part C, Chap 1, Life Cycle Management Policy
0, Mission Need Establishment - Perform Milestone A Review
DFAS 8000.1-R, Part C, Chap 2, Configuration Management Policy
I, Configuration Management/Quality Assurance - Develop Enterprise Configuration Management Strategy - Establish Configuration Management Strategy
DFAS 8000.1-R, Part C, Chap 3, Test and Evaluation Policy
II, Test Planning - Prepare Test Plans II, Deployment Planning - Prepare Site Acceptance Test Plans
DFAS 8000.1-R, Part D, Chap 6, Std Sys Eng Prc
N/R
August 3, 2001
19

DFAS 8000.1-R, Part E, Chap 4, Data Administration/ Data Management Program Policy
0, Business Process Review and Improvement - Review Current Business Process I, Program Planning/Management - Establish Data Standardization Strategy
DFAS 8000.1-R, Part F, Chap 1, Acq of IT Equip, Software, and Software Services
I, System Architecture Design - Determine Execution Environment Release Requirements - Define and Establish System II, Security ProgramArchitecture Planning/Management, II, III, Technical Project - Manage Acquisition
DFAS 8000.1-R, Part G, Chap 1, App 2, DFAS Certification and Accreditation Repository
I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification - Conduct DITSCAP Phase 3, Validation
Documented Risks
III, System Management - Establish System Risk Management Strategy
III, Functional Analysis - Prepare Functional Analysis Schedule - Perform Functional Analysis - Conduct Peer Review for Analysis - Conduct Functional Turnover Review III, Technical Design - Prepare Technical Design Schedule - Perform Technical Design - Perform Peer Review for Design - Conduct Preliminary Design Review - Conduct Critical Design Review - Prepare Release Package Proposal - Conduct Configuration Control Board Meeting - Build Software Development Plan III, Development
August 3, 2001
20

- Develop Configuration Items - Conduct Unit Test/Module Test - Perform Peer Review for Development - Conduct Baseline Configuration Audit III, System Testing - Develop Test Schedule - Build Test CIs (Scripts and Data) - Conduct Peer Review for Testing - Create Test Environment - Perform Test Readiness Review - Perform System Tests - Perform Functional Configuration Audit - Perform Physical Configuration Audit - Certify Testing III, Deployment - Deliver Release Instructions - Deliver Release - Conduct Post Implementation Review - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Tracking and Analysis
Documented TAR Request
III, Technical Design - Perform Technical Design
III, Technical Design - Perform Peer Review for Design
DOD Global Information Grid (GIG) Information Assurance Implementation Guidance (IA-8510)
I, System Requirements Analysis - Define Information Assurance/ Security Requirements
DOD Information Technology Security Certification and Accreditation Process (DITSCAP) Application Manual (DOD 8510.1-M)
I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification - Conduct DITSCAP Phase 3, Validation
August 3, 2001
21

DoD Joint Technical Architecture
I, Program Planning/Management - Establish Test and Evaluation Strategy I, System Requirements Analysis - Develop Joint Technical Architecture (JTA) Profile
DOD 5000.2-R
I, Program Planning/Management - Prepare C4I Support Plan
Part 2 Appendix B
- Determine Acquisition Strategy - Establish Test and Evaluation Strategy
DODI 5000.2, "Operation of the Defense Acquisition System"
0, Mission Need Establishment - Conduct Milestone A Review I, Program Planning/Management - Certify Compliance with ClingerCohen Act
Economic Analysis
EA
I, Program Planning/Management - Perform Economic Analysis/CostBenefit Analysis
I, Program Planning/Management - Develop Program Objective Memorandum (POM) - Develop Budget Submissions - Perform Funds Allocation and Execution - Certify Compliance with ClingerCohen Act - Conduct Milestone B Review II, Program Planning/Management - Conduct Milestone C Review
Effective Work Day Factor
III, Technical Design - Prepare Release Package Proposal - Build Software Development Plan
Effort Estimates
III, Technical Design - Prepare Release Package Proposal - Build Software Development Plan
Engineering Standards
August 3, 2001
22

- Identify/Implement Project Standards - Obtain Technical Training
Enterprise Development Environment
I, Program Planning/Management - Establish Requirements Definition Development Environment II, Technical Project Planning/ Management - Establish Software Engineering/ Testing Development Environment
Enterprise Execution Environment
I, System Architecture Design - Plan Execution Environment Changes - Define and Establish System Security Architecture
I, System Requirements Analysis - Determine Capacity Requirements I, System Architecture Design - Integrate Execution Environment Requirements - Determine Execution Environment Solution - Conduct Technical Architecture Review - Define Operating Procedures II, Program Planning/Management - Develop Contijnuity of Operations Plan II, Software Architecture Design - Develop Integrated Software Architecture - Perform Critical Design Review II, Software Detailed Design - Perform Integrated Critical Design Review III, Systems Management - Establish System Release Strategy
Enterprise Technical Architecture
I, System Architecture Design - Determine Execution Environment Solution - Define and Establish System Security Architecture
I, Program Planning/Management - Perform COTS Evaluation I, System Requirements Analysis
August 3, 2001
23

- Define Environmental Requirements - Define External Design Constraints - Define Software Distribution and Installation Requirements - Develop Joint Technical Architecture (JTA) Profile
I, Architecture Design - System Integrate Execution Environment Requirements - Conduct Technical Architecture Review - Define Operating Procedures II, Program Planning/Management - Develop Continuity of Operations Plan II, Technical Project Planning/ Management - Identify/Implement Project Standards - Perform Critical Design Review II, Software Detailed Design - Perform Integrated Critical Design Review III, Technical Project Planning/ Management - Prepare Project Staffing Profile
ESG Meeting Minutes
0, Customer Relationship - Establish Customer Relationship
Estimating
III, Functional Analysis - Prepare Functional Analysis Estimates III, Technical Design - Prepare Technical Design Estimates - Impact Configuration Change Orders
Executable Object Code Record
EOCR
II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces
II, Software Coding and Unit/Module Testing - Construct Functional Process Modules
August 3, 2001
24

III, Development - Develop Configuration Items
- Construct User Interface Units/ Modules III, Development - Conduct Unit Test/Module Test
II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces - Conduct Database Performance Test - Conduct User Interface Test - Conduct User Interface Performance Test - Perform Unit Test/Module Test II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Build Test Environment II, Software Coding and Unit/Module Testing - Execute Data Conversion Procedures II, Configuration Management/Quality Assurance - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production III, Operational Test and Evaluation - Conduct Implementation Readiness Review III, Development - Establish Development Baseline III, Deployment - Convert and Verify Data
Existing Organizational/ Personnel Documentation
I, System Requirements Analysis - Define Personnel and Logistics Requirements
Existing System Quality Guidance
I, System Requirements Analysis - Define Quality Requirements
August 3, 2001
25

Existing Systems Maintenance and Support Documentation
I, System Requirements Analysis - Define Personnel and Logistics Requirements
Function Point Baseline
II, Software Requirements Analysis - Perform Function Point Analysis
Function Point Counting Rules, Version 4.1
Function Point Productivity Rate
II, Technical Project Planning/ Management - Perform Impact Analysis
Functional Acquisition Requirements
II, Program Planning/Management, II, III, Technical Project Planning/ Management - Manage Acquisition III, Functional Analysis - Perform Functional Analysis
I, System Architecture Design
- Plan Execution Environment Changes III, Functional Analysis - Conduct Peer Review for Analysis
Functional Analysis
Functional Baseline (SRS, SARAD, SRD, Rqmts Func, Data, & Prc Models) Application
II, Configuration Management/Quality Assurance - Conduct Functional Configuration Audit II, ConfigurationManagement/Quality Assurance - Establish Other Application Functional Baseline II, Configuration Management/Quality Assurance - Manage Changes to Application Functional Baseline
Enterprise (Integrated)
II, ConfigurationManagement/Quality Assurance - Establish Corporate Functional Baseline
II, Configuration Management/Quality Assurance - Manage Changes to Corporate Functional Baseline
Functional Configuration Audit Checklist
II, Configuration Management/Quality Assurance
August 3, 2001
26

- Conduct Functional Configuration Audit III, System Testing - Perform Functional Configuration Audit
- Conduct Physical Configuration Audit
Functional Manager Acceptance Letter
0, Mission Need Establishment - Establish Mission Need
Funding Allocation Document
FAD
I, Program Planning/Management - Perform Funds Allocation and Execution
III, Systems Management - Manage Systems Operations and Maintenance
FY01 National Defense Appropriation Act, Section 8102(a) and Section 811(a)
I, Program Planning/Management - Certify Compliance with ClingerCohen Act
GUI Guidelines
II, Software Architecture Design - Design Integrated Menu Structure - Design Data Handling Screens
Help Desk Procedures
III, Deployment - Establish Help Desk Support
Help Desk Support
III, Deployment - Establish Help Desk Support
Help Objects
II, Software Coding and Unit/Module Testing - Create On-Line Help Screens
II, Software Coding and Unit/Module Testing - Construct User Interface Units/ Modules - Conduct Peer Review for Development
Historical Data from LRS
III, Technical Project Planning/ Management - Prepare Project Staffing Profile - Prepare Project Funding Profile
August 3, 2001
27

Historical Release Information (Trend Analysis)
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Prepare Test Schedule III, Technical Design - Build Software Development Plan III, System Testing - Develop Test Schedule
Implementation Readiness Review/Full Rate Production Review Presentation Outline
III, Operational Test and Evaluation - Conduct Implementation Readiness Review
III, Operational Test and Evaluation - Conduct Full-Rate Production Decision Review
Individual Development Plan
IDP
II, Technical Project Planning/ Management - Obtain Technical Training III, Technical Project Planning/ Management - Develop Individual Development Plans
III, Technical Project Planning/ Management - Develop Project Training Plan III, Tracking and Analysis - Obtain Training
Individual Training Record
II, Technical Project Planning/ Management - Obtain Technical Training
Infrastructure Requirements Description
II, Software Requirements Analysis - Integrate Requirements
III, Functional Analysis - Perform Functional Analysis
II, Program Planning/Management - Conduct Interim Progress Review II, Software Architecture Design - Establish Design Model - Perform Critical Design Review II, Software Detailed Design - Perform Integrated Critical Design Review
Infrastructure Services Request Enterprise
ISR I, System Architecture Design - Determine Execution Environment Release Requirements I, Program Planning/Management - Conduct Milestone B Review
August 3, 2001
28

- Define and Establish System Security Architecture II, Technical Project Planning/ Management - Establish Software Engineering/ Testing Development Environment
I, System Architecture Design - Conduct Technical Architecture Review - Plan Execution Environment Changes I, Program Planning/Management - Conduct Milestone C Review
Application
I, System Architecture Design - Determine Execution Environment Release Requirements I, Program Planning/Management - Establish Requirements Definition Development Requirements
I, System Architecture Design - Conduct Technical Architecture Review - Plan Execution Environment Changes II, Program Planning/Management - Conduct Milestone C Review
Initialized Files and Databases
II, Software Coding and Unit/Module Testing - Execute Data Conversion Procedures III, Deployment - Convert and Verify Data
Installation Notification
III, Deployment - Install Release
III, Deployment - Conduct Post Implementation Review
Installation Plan
II, Deployment Planning - Prepare Software Installation Plans
Installed Release
Integrated Product Team Charter Capacity/Performance
I, Program Planning/Management - Determine Program Management Plans
I, Program Planning/Management - Conduct Decision Review - Conduct Milestone B Review
COTS Evaluation
- Perform COTS Availability Research
- Perform COTS Evaluation - Conduct Decision Review
Requirements - Determine Program Management Plans
- Conduct Milestone B Review
August 3, 2001
29

Test - Establish Test and Evaluation Strategy
- Conduct Decision Review - Conduct Milestone B Review
Integrated Proposed Changes to Business Data Model
Integrated Proposed Changes to Business Function Model
Integrated Proposed Changes to Business
Process Model
Integrated Release Plan N
II, Technical Project Planning/ Management - Integrate Technical Project Plans
Interface Memorandum of Agreement
I, System Requirements Analysis - Define External Interface Data Requirements
Interim Progress Review Brief
II, Program Planning/Management - Conduct Interim Progress Review
Interim Progress Review Memorandum
II, Program Planning/Management - Conduct Interim Progress Review
II, Program Planning/Management - Conduct Milestone C Review I, Program Planning/Management - Conduct Milestone B Review
Joint Technical Architecture Profile
I System Requirements Analysis - Develop Joint Technical Architecture (JTA) Profile
Labor Reporting System
III, Technical Design - Obtain Release Funding
III, Tracking and Analysis - Establish Metrics Collection
Legacy Shut Down Notification
III, Deployment - Shut Down Legacy Systems
August 3, 2001
30

Legacy System Documentation
0, System Requirements Analysis - Define Internal Data Requirements II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Define Data Conversion Requirements - Prepare Functional Requirements Validation Test Scripts II, Software Detailed Design - Define Test Scripts
Legislative/Policy-Based System Requirements
Lessons Learned in PAL
III, Deployment - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Trend Analysis
Life Cycle Cost Estimates
LCCE
I, II, Program Planning/Management - Estimate Life Cycle Resources
I, Program Planning/Management - Perform Economic Analysis/CostBenefit Analysis - Develop Budget Submissions - Perform Funds Allocation and Execution - Establish Risk Management Strategy - Conduct Milestone B Review II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Technical Project Planning/ Management - Assess Technical Project Risks
List of Unranked (New) SCRs
III, Technical Design - Conduct Configuration Control Board Meeting
August 3, 2001
31

Living Disaster Recovery Planning System (LDRPS) Database
Management Guidance for Actions and Continuation Decision
II, Program Planning/Management - Perform Program Management Reviews II, Technical Project Planning/ Management - Perform Technical Project Tracking and Oversight
I, Program Planning/Management - Determine Program Management Plans II, Technical Project Planning/ Management - Develop Technical Project Plan
Metrics Repository
Milestone A Decision Brief
0, Mission Need Establishment - Conduct Milestone A Review
Milestone B Decision Brief
Milestone C Decision Brief
II, Program Planning/Management - Conduct Milestone C Review I, Program Planning/Management - Perform Funds Allocation and Execution III, Systems Management - Manage System Operations and Maintenance III, Technical Project Planning/ Management - Prepare Project Funding Profile III, Technical Design - Obtain Release Funding
MIPR
MIPR
Mission Area Analyses
August 3, 2001
32

Mission Need Statement
MNS
0, Mission Need Establishment - Conduct Milestone A Review I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives - Develop Budget Submissions - Conduct Decision Review I, Operational Requirements Definition - Define Operational Requirements I, System Requirements Analysis - Define Functional Requirements - Define Information Assurance/ Security Requirements I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition I, Configuration Management/Quality Assurance - Establish Program Quality Assurance Strategy II, Deployment Planning - Establish Transition Strategy
Mission Need Statement Generation (CJCSI 3170.01A
Model Completeness Reports
II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis
II, Software Requirements Analysis - Perform Functional Requirements Review (FRR) - Perform Integrated Functional Requirements Review (IFRR)
Network Diagrams
I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition
August 3, 2001
33

New or Significantly Modified Mission Need
Operational Architecture
I, System Requirements Analysis - Define Operational Architecture
I, Program Planning/Management - Conduct Milestone B Review II, Program Planning/Management - Conduct Interim Progress Review
Operational Requirements Document
ORD
I, Operational Requirements Definition - Define Operational Requirements
I, II, III, Program Planning/Management - Maintain Customer Relationship II, Program Planning/Management - Update Program Documentation
I, Program Planning/Management - Determine Acquisition Strategy - Establish/Maintain Acquisition Program Baseline - Perform Release Planning - Perform Economic Analysis/CostBenefit Analysis - Prepare C4I Support Plan - Certify Compliance with ClingerCohen Act - Develop Budget Submissions - Perform Funds Allocation and Execution - Establish Data Standardization Strategy - Establish Test and Evaluation Strategy - Maintain Acquisition - Establish Project Support - Establish Risk Management Strategy - Conduct Milestone B Review I, System Requirements Analysis - Define Functional Requirements - Identify User/Customer Organizations - Define Information Assurance/ Security Requirements - Define External Interface Data Requirements - Determine Systems Operations Requirements - Define Human Factors Requirements - Define Environmental Requirements
August 3, 2001
34

- Define External Design Constraints - Define Internal Data Requirements - Determine System Access Requirements - Define Software Distribution and Installation Requirements - Define Personnel and Logistics Requirements - Define Quality Requirements - Determine Business Performance Requirements - Sys Rqmts Anal - Perform System Requirements Review I, System Architecture Design - Define Application Systems Architecture I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Technical Project Planning/ Management - Develop Technical Project Plan - Assess Technical Project Risks II, Software Requirements Analysis - Perform Detailed Process Analysis II, Test Planning - Prepare Test Plans II, Deployment Planning - Establish Transition Strategy - Prepare Site Acceptance Test Plans - Prepare User Training Plans I, Configuration Management/Quality Assurance - Establish Program Quality Assurance Strategy - Establish Program Baseline II, Configuration Management/ Quality Assurance - Manage Changes to Program Baseline
August 3, 2001
35

Operational Requirements Generation (Chairman of Joint Chiefs of Staff Instruction (CJCSI) 3170.01B)
I, Operational Requirements Definition - Define Operational Requirements
Operations Performance Data
III, Operational Performance Oversight - Measure System Performance
Operations Resource Utilization
III, Operational Performance Oversight - Audit Production System
Operator's Manual
OM
I, System Architecture Design - Define Operating Procedures
III, Development - Update Operating Procedures
II, Program Planning/Management - Develop Continuity of Operations Plan - Conduct Interim Progress Review - Conduct Milestone C Review II, Deployment Planning - Establish Transition Strategy - Prepare Software Installation Plans - Prepare Site Acceptance Test Plans - Prepare User Training Plans - Produce User Class Materials II, Configuration Management/Quality Assurance - Package Products for Release to Production III, Development - Establish Development Baseline III, Deployment - Establish Help Desk Support
Performance Modeling Tool(s)
President's Budget Submission
I, Program Planning/Management - Develop Budget Submissions
0, Mission Need Establishment - Conduct Milestone A Review I, Program Planning/Management - Conduct Decision Review - Conduct Milestone B Review
August 3, 2001
36

II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review III, Operational Test and Evaluation - Conduct Implementation Readiness Review
Process Asset Library
Product Baseline (SDD, SIDD, DBDD, SAD, EOCR, SCRD, SCIR, UM, OM)
II, Configuration Management/ Quality Assurance - Establish Product Baseline III, Development - Establish Development Baseline
III, Development - Conduct Baseline Configuration Audit
III, System Testing - Create Test Environment III, Deployment - Conduct Post Implementation Review III, Tracking and Analysis - Perform SQA Audit of Product
Product Delivery Plan
III, Deployment - Develop Delivery Schedule - Deliver Release
Production Library
III, Deployment - Deliver Release
III, System Testing - Create Test Environment III, Deployment - Install Release
Program Baselline (ORD, TEMP, APB)
I, Configuration Management/Quality Assurance - Establish Program Baseline
II, Configuration Management/ Quality Assurance - Manage Changes to Program Baseline
Program Management Plan
PMP
I, Program Planning/Management - Determine Program Management Plans - Determine Integration Management Plans
I, Program Planning/Management - Perform Release Planning - Establish Risk Management Strategy I, II, Program Planning/Management - Estimate Life Cycle Resources
I, Program Planning/Management - Develop Program Objective Memorandum (POM) - Develop Budget Submissions - Perform Funds Allocation and Execution - Establish Test and Evaluation Strategy
August 3, 2001
37

II, Program Planning/Management - Perform Program Management Reviews II, Deployment Planning - Establish Transition Strategy
- Establish Project Support - Establish Requirements Definition Development Environment - Conduct Milestone B Review I, Configuration Management/Quality Assurance - Establish Configuration Management Strategy - Establish Program Quality Assurance Strategy II, Program Planning/Management - Determine Release Content II, Technical Project Planning/ Management - Develop Technical Project Plan - Integrate Technical Project Plans - Establish Software Engineering/ Testing Development Environment - Assess Technical Project Risks - Develop Software Process Improvement Plan - Perform Technical Project Tracking and Oversight II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Conduct Peer Review for Software Requirements II, Test Planning - Prepare Test Plans
Program Management Policy
Program Manager's Charter
I, Program Planning/Management - Appoint Program Manager
I, Program Planning/Management - Establish Project Support
0, Mission Need Establishment - Conduct Milestone A Review I, Program Planning/Management
August 3, 2001
38

- Determine Program Management Plans - Determine Integration Management Plans - Conduct Milestone B Review
Program Objective Memorandum Guidance
I, Program Planning/Management - Develop Program Objective Memorandum (POM)
Program Objective Memorandum (POM) Submission
I, Program Planning/Management - Develop Program Objective Memorandum (POM)
0, Mission Need Establishment - Conduct Milestone A Review I, Program Planning/Management - Conduct Decision Review - Conduct Milestone B Review II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review III, Operational Test and Evaluation - Conduct Implementation Readiness Review
Program Quality Assurance Plan
I, Configuration Management/Quality Assurance - Establish Program Quality Assurance Strategy
III, Systems Management - Establish System Quality Assurance Strategy III, Technical Design - Build Software Development Plan III, Tracking and Analysis - Perform Project Tracking and Oversight
I, Program Planning/Management - Conduct Milestone B Review II, Technical Project Planning/ Management - Develop Technical Project Plan - Assess Technical Project Risks II, Software Architecture Design - Perform Critical Design Review II, Software Detailed Design - Perform Integrated Critical Design Review II, ConfigurationManagement/Quality Assurance - Perform SQA Audit/Review of Products and Processes III, Systems Management
August 3, 2001
39

- Establish System Quality Assurance Strategy III, Technical Project Planning/ Management - Define Project Process III, Operational Test and Evaluation - Conduct Implementation Readiness Review III, Tracking and Analysis - Perform SQA Audit of Product - Perform SQA Review of Process
Program Trouble Report
III, Requirements Initiation - Record and Analyze Problem
III, Requirements Initiation - Determine Routing - Evaluate Problem - Resolve Program Trouble Report
III, Requirements Initiation - Convert PTR to SCR III, Deployment - Conduct Post Implementation Review
Project Core Competency Requirements
III, Technical Project Planning/ Management - Develop Training Program Plan - Develop Individual Development Plans
Project Historical Data
III, Tracking and Analysis - Perform Project Trend Analysis
Project Metrics
II, Technical Project Planning/ Management - Perform Technical Project Tracking and Oversight
III, Deployment - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Tracking and Oversight - Perform Project Trend Analysis
Project Staffing Profile
III, Systems Management - Manage System Operations and Maintenance III, Technical Project Planning/ Management - Prepare Project Funding Profile III, Technical Design - Prepare Release Package Proposal
August 3, 2001
40

Project Status
II, Technical Project Planning/ Management - Perform Technical Project Tracking and Oversight
Project Training Plan
III, Technical Project Planning/ Management - Develop Project Training Plan
Project-Applicable Standards
II, Technical Project Planning/ Management - Identify/Implement Project Standards
II, Configuration Management/ Quality Assurance - Perform SQA Audits/Reviews of Products and Processes
Project's Defined Software Process
III, Technical Design - Build Software Development Plan III, Deployment - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Tracking and Oversight III, Tracking and Analysis - Perform SQA Review of Process
Project's Tailored Software Process
Proposed Application Program Interface Changes
II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces
II, Software Detailed Design - Design Application Program Interfaces (APIs)
Proposed Changes to the Business Data Model
II, Software Requirements Analysis - Perform Detailed Data Analysis - Validate Data Requirements - Validate Functional Requirements
II, Software Requirements Analysis - Integrate Requirements - Approve Business Model Changes
Proposed Changes to the Business Function Model
II, Software Requirements Analysis - Perform Detailed Data Analysis
August 3, 2001
41

- Validate Data Requirements - Validate Functional Requirements Proposed Changes to Business Process Model N II, Software Requirements Analysis - Perform Detailed Data Analysis - Validate Data Requirements - Validate Functional Requirements Proposed Changes to Development/Unit Test Database N II, Software Coding and Unit/Module Testing - Conduct Database Performance Test - Perform Unit Test/Module Test
- Approve Business Model Changes
II, Software Requirements Analysis - Integrate Requirements - Approve Business Model Changes
II, Software Detailed Design - Complete Database Design
Proposed Changes to Requirements Data Model
II, Software Architecture Design - Establish Design Model - Identify and Incorporate Reusable Design Components
Proposed Changes to Requirements Function Model
Proposed Changes to Requirements Process Model
Proposed Changes to User Screens
II, Software Coding and Unit/Module Testing - Conduct User Interface Test - Conduct User Interface Performance Test - Perform Unit Test/Module Test
II, Software Detailed Design - Perform Physical User Interface Design
Proposed Design Changes
August 3, 2001
42

Proposed Engineering Standards
II, Technical Project Planning/ Management - Identify/Implement Project Standards - Perform Technical Project Tracking and Oversight
Proposed Software Module Design Changes
II, Software Coding and Unit/Module Testing - Perform Unit Test/Module Test
II, Software Architecture Design - Transform Design Function/Process Models - Perform Interface Module Design II, Software Detailed Design - Complete Process Module Design
Proposed Technical Architecture Standards
II, Technical Project Planning/ Management - Identify/Implement Project Standards
Ranked or Prioritized SCR List
III, Requirements Initiation - Rank or Prioritize System Change Requests
III, Functional Analysis - Prepare Functional Analysis Estimates - Prepare Functional Analysis Schedule
III, Technical Design - Prepare Technical Design Estimates - Prepare Technical Design Schedule - Prepare Release Package Proposal - Conduct Configuration Control Board Meeting
Release Function Point Count
Release Guidance
III, Systems Management - Manage System Operations and Maintenance III, Functional Analysis - Prepare Functional Analysis Schedule III, Technical Design - Prepare Technical Design Schedule - Prepare Release Package Proposal III, System Testing - Develop Test Schedule
August 3, 2001
43

III, Deployment - Develop Delivery Schedule
Release Impact Analysis
II, Program Planning/Management - Determine Release Content III, Deployment - Install Release
Release Instructions
III, Deployment - Deliver Release Instructions
Release Package
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Prepare Test Schedule III, Technical Design - Obtain Release Funding - Build Software Development Plan - Lock Release III, System Testing - Develop Test Schedule
- Prepare Release Package Proposal
- Conduct Configuration Control Board Meeting
Release Package
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Train Test Users II, Configuration Management/Quality Assurance - Conduct Functional Configuration Audit - Conduct Physical Configuration Audit
- Package Products for Release to Test - Package Products for Release to Production
Release Plan
II, Program Planning/Management - Determine Release Content
I, System Architecture Design - Determine Execution Environment Release Requirements II, Program Planning/Management - Conduct Interim Progress Review
August 3, 2001
44

II, Technical Project Planning/ Management - Perform Impact Analysis II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Define Interface Requirements - Define User Interface/Human Factors Requirements - Define Data Conversion Requirements - Integrate Requirements - Perform Functional Requirements Review (FRR) - Perform Integrated Functional Requirements Review (IFRR) II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Prepare Test Schedule
Repository Application Request Form
Request for Information
I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives
Requirements Data Model
I, System Requirements Analysis - Identify User/Customer Organizations
I, System Requirements Analysis - Define Internal Data Requirements - Determine System Access Requirements II, Software Requirements Analysis
I, System Requirements Analysis - Define Functional Requirements - Define Information Assurance Security Requirements - Define External Interface Data Requirements - Determine Business Performance Requirements - System Requirements Analysis - Perform System Requirements Review
- Perform Detailed Data Analysis
- Define Data Conversion Requirements
August 3, 2001
45

- Integrate Requirements - Prepare Functional Requirements Validation Test Scripts - Validate Data Requirements - Validate Functional Requirements - Determine Function/Data Access Requirements
II, Software Requirements Analysis - Perform Detailed Process Analysis - Define Interface Requirements - Collect Capacity Planning Data - Transform Requirements Data Model - Perform Function Point Analysis II, Software Architecture Design - Establish Design Model
Requirements Definition
III, Requirements Initiation - Define System Change Requirements
Requirements Function Model
I, System Requirements Analysis - Define Functional Requirements
I, System Requirements Analysis - Identify User/Customer Organizations - Define Information Assurance Security Requirements - Define External Interface Data Requirements - Define Systems Operations Requirements - Define Human Factors Requirements - Define Environmental Requirements - Define External Design Constraints - Determine System Access Requirements - Define Software Distribution and Installation Requirements - Define Personnel and Logistics Requirements - Define Quality Requirements - Determine Business Performance Requirements - System Requirements Analysis I, System Architecture Design - Determine Execution Environment Release Requirements - Define and Establish System Security Architecture II, Software Requirements Analysis
I, System Requirements Analysis - Define Internal Data Requirements - Determine Capacity Requirements - Perform System Requirements Review II, Software Requirements Analysis - Perform Detailed Process Analysis - Define Interface Requirements - Define User Interface/Human Factors Requirements - Collect Capacity Planning Data - Transform Requirements Function/ Process Models - Generate Requirements Validation User Interface - Perform Function Point Analysis II, Software Architecture Design
- Establish Design Model
August 3, 2001
46

- Perform Detailed Function Analysis - Integrate Requirements - Prepare Functional Requirements Validation Test Scripts - Validate Functional Requirements - Determine Function/Data Access Requirements
Requirements Process Model
I, System Requirements Analysis - Determine System Access Requirements
II, Software Requirements Analysis - Perform Detailed Process Analysis - Integrate Requirements - Prepare Functional Requirements Validation Test Scripts - Validate Functional Requirements - Determine Function/Data Access Requirements
I, System Requirements Analysis - Determine Capacity Requirements II, Software Requirements Analysis - Collect Capacity Planning Data - Transform Requirements Function/ Process Models II, Software Architecture Design - Establish Design Model
Requirements Server Model
II, Software Requirements Analysis - Transform Requirements Data Model
II, Software Requirements Analysis - Generate Requirements Validation Database
Requirements Validation Database
II, Software Requirements Analysis - Generate Requirements Validation Database
Requirements Validation Module Designs
II, Software Requirements Analysis - Transform Requirements Function/ Process Models
II, Software Requirements Analysis - Generate Requirements Validation Modules
Requirements Validation Modules
II, Software Requirements Analysis - Generate Requirements Validation Modules
II, Software Requirements Analysis - Validate Functional Requirements
Requirements Validation User Interface
II, Software Requirements Analysis - Generate Requirements Validation User Interface
August 3, 2001
47

Review Checklist
I, System Requirements Analysis - Perform System Requirements Review I, System Architecture Design - Perform Systems Architecture Review II, Software Requirements Analysis - Conduct Peer Review for Software Requirements - Perform Functional Requirements Review - Perform Integrated Functional Requirements Review (IFRR) II, Software Architecture Design - Perform Critical Design Review II, Software Detailed Design - Conduct Peer Review for Design - Perform Integrated Critical Design Review II, Software Coding and Unit/Module Testing - Conduct Peer Review for Development II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Conduct Testing Peer Review - Conduct Test Readiness Review II, Enterprise Level Acceptance Test - Conduct Enterprise Level Test Readiness Review III, Operational Test and Evaluation - Conduct Implementation Readiness Review III, Functional Analysis - Conduct Peer Review for Analysis - Conduct Functional Turnover Review III, Technical Design - Perform Peer Review for Design
II, Configuration Management/ Quality Assurance - Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production III, Functional Analysis - Establish Analysis Baseline
August 3, 2001
48

- Conduct Preliminary Design Review - Conduct Critical Design Review III, Development - Perform Peer Review for Development III, System Testing - Conduct Peer Review for Testing - Perform Test Readiness Review III, Deployment - Conduct Post Implementation Review Review Report S I, System Requirements Analysis - Perform System Requirements Review I, System Architecture Design - Perform Systems Architecture Review II, Software Requirements Analysis - Conduct Peer Review for Software Requirements - Perform Functional Requirements Review - Perform Integrated Functional Requirements Review (IFRR) I, Program Planning/Management - Conduct Milestone B Review II, Technical Project Planning/ Management - Perform Technical Project Tracking and Oversight II, ConfigurationManagement, Quality Assurance - Establish Other Application Functional Baseline - Establish Corporate Functional Baseline II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Acceptance Test, II, III, Operational Test and Evaluation - Perform Tests II, Configuration Management, Quality Assurance - Conduct Functional Configuration Audit - Conduct Physical Configuration Audit III, Operational Test and Evaluation - Conduct Full-Rate Production Decision Review III, Functional Analysis
II, Software Architecture Design - Perform Critical Design Review
II, Software Detailed Design - Conduct Peer Review for Design - Perform Integrated Critical Design Review II, Software Coding and Unit/Module Testing - Conduct Peer Review for Development
August 3, 2001
49

II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Conduct Testing Peer Review - Conduct Test Readiness Review II, Enterprise Level Acceptance Test - Conduct Enterprise Level Test Readiness Review III, Operational Test and Evaluation - Conduct Implementation Readiness Review III, Functional Analysis - Conduct Peer Review for Analysis - Conduct Functional Turnover Review III, Technical Design - Perform Peer Review for Design - Conduct Preliminary Design Review - Conduct Critical Design Review III, Development - Perform Peer Review for Development III, System Testing - Conduct Peer Review for Testing - Perform Test Readiness Review III, Deployment - Conduct Post Implementation Review - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Trend Analysis
- Conduct Functional Turnover Review
III, Technical Design Design - Perform Technical - Conduct Preliminary Design Review - Conduct Critical Design Review - Impact Configuration Change Orders - Establish Design Baseline III, Development - Establish Development Baseline III, System Testing - Perform System Tests III, Deployment - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Tracking and Oversight
Revisions to Requirements Data Model
II, Software Requirements Analysis - Perform Detailed Data Analysis II, Software Requirements Analysis - Perform Detailed Function Analysis
Revisions to Requirements Function Model
August 3, 2001
50

Revisions to Requirements Process Model
II, Software Requirements Analysis - Perform Detailed Process Analysis I, Program Planning/Management - Establish Risk Management Strategy
Risk Management Guide for DoD Acquisition, DSMC
Risk Management Plan
Schedule Software Process Improvement
S III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan III, Deployment - Conduct Release Analysis Review III, Tracking and Analysis - Perform Project Tracking and Oversight
Functional Analysis
III, Functional Analysis - Prepare Functional Analysis Schedule
III, Functional Analysis - Perform Functional Analysis - Conduct Peer Review for Analysis - Conduct Functional Turnover Review
Technical Design
III, Technical Design - Perform Technical Design - Perform Peer Review for Design - Conduct Preliminary Design Review - Conduct Critical Design Review
Test
III, System Testing - Develop Test Schedule
III, System Testing - Conduct Peer Review for Testing - Perform Test Readiness Review - Perform System Tests
Delivery
III, Deployment - Develop Delivery Schedule
III, Deployment - Deliver Release Instructions
August 3, 2001
51

- Deliver User Advisory - Deliver Release
Release
Service Level Agreements (SLAs) System Operations
III, Systems Management - Establish System Release Strategy
System Maintenance/ Development
- Manage System Operations and Maintenance
III, Systems Management - Establish System Release Strategy - Establish System Configuration Management Strategy III, Technical Project Planning/ Management - Prepare Project Staffing Profile
Miscellaneous
II, Deployment Planning - Establish Continuity of Operations Capability
Site Accreditation Surveys
II, Information Assurance/Security - Conduct DITSCAP Phase 3, Validation
Software Architecture Description
SAD
II, Software Architecture Design - Develop Integrated Software Architecture
II, Software Architecture Design - Design Integrated Menu Structure - Design Data Handling Screens III, Technical Design - Perform Technical Design
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Test Planning - Prepare Test Plans II, Software Architecture Design - Prepare Application Release Checklist II, Application Level Software Integration Test - Analyze System Performance II, Enterprise Level Performance Test - Conduct Performance Testing
August 3, 2001
52

II, Configuration Management/Quality Assurance - Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production III, Requirements Initiation - Evaluate Problem III, Development - Establish Development Baseline
Software Configuration Index Record
SCIR
II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces
II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces - Construct Functional Process Modules - Construct User Interface Units/ Modules
II, Program Planning/Management - Conduct Milestone C Review II, Deployment Planning - Prepare Software Installation Plans II, Configuration Management/Quality Assurance - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production III, Development - Establish Development Baseline
Software Design Description
SDD
II, Software Architecture Design - Identify and Incorporate Reusable Design Components
II, Software Architecture Design - Transform Design Function/ Process Models - Perform Interface Module Design - Design Integrated Menu Structure - Design Data Handling Screens - Perform Data Conversion Unit/ Module Design II, Software Detailed Design
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Test Planning - Prepare Test Plans II, Software Architecture Design - Identify Corporate Application Program Interfaces (APIs)
August 3, 2001
53

(SDS Release 3.2 (INTERIM)) - Identify Application-Internal Application Program Interfaces (APIs) - Prepare Application Release Checklist - Perform Critical Design Review II, Software Detailed Design - Perform Physical User Interface Design - Define Test Scripts - Conduct Peer Review for Design - Perform Integrated Critical Design Review II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces - Test Physical Database and Application Program Interfaces - Construct Functional Process Modules - Create On-Line Help Screens - Construct User Interface Units/ Modules - Conduct User Interface Test - Conduct User Interface Performance Test - Complete User's Procedures - Conduct Peer Review for Development II, Application Level Software Integration Test - Analyze System Performance II, Enterprise Level Performance Test - Conduct Performance Testing II, Configuration Management/Quality Assurance - Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production
- Complete Process Module Design - Design Application Program Interfaces (APIs) III, Technical Design - Perform Technical Design
August 3, 2001
54

III, Requirements Initiation - Evaluate Problem III, Development - Establish Development Baseline Software Development Plan S III, Technical Design - Build Software Development Plan III, Development - Perform Peer Review for Development III, System Testing - Build Test CIs (Scripts and Data) III, Tracking and Analysis - Perform Project Tracking and Analysis III, Development - Develop Configuration Items - Conduct Unit Test/Module Test - Conduct Baseline Configuration Audit III, System Testing - Develop Test Schedule - Perform Test Readiness Review - Perform System Tests - Perform Physical Configuration Audit III, Deployment - Develop Delivery Schedule - Convert and Verify Data - Conduct Release Analysis Review Software Interface Design Description S SIDD II, Software Architecture Design - Identify and Incorporate Reusable Design Components II, Software Architecture Design - Identify Corporate Application Program Interfaces (APIs) - Identify Application-Internal Application Program Interfaces (APIs) - Perform Interface Module Design - Design Integrated Menu Structure - Design Data Handling Screens II, Software Detailed Design - Perform Physical User Interface Design III, Technical Design - Perform Technical Design II, Program Planning/Management - Conduct Interim Progress Review
- Conduct Milestone C Review
II, Test Planning - Prepare Test Plans II, Software Architecture Design - Prepare Application Release Checklist - Perform Critical Design Review II, Software Detailed Design - Design Application Program Interfaces (APIs) - Define User's Procedures - Conduct Peer Review for Design - Perform Integrated Critical Design Review
August 3, 2001
55

II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces - Construct Functional Process Modules - Create On-Line Help Screens - Construct User Interface Units/ Modules - Complete User's Procedures - Conduct Peer Review for Development II, Application Level Software Integration Test - Analyze System Performance II, Enterprise Level Performance Test - Conduct Performance Testing II, Configuration Management/Quality Assurance - Establish Application Allocated Baseline - Establish Corporate Allocated Baseline - Package Products for Release to Test - Establish Product Baseline - Package Products for Release to Production III, Operational Test and Evaluation - Conduct Implementation Readiness Review III, Requirements Initiation - Evaluate Problem III, Development - Establish Development Baseline
Software Maintenance and Development Bills
Software Process Improvement Plan
II, Technical Project Planning/ Management - Develop Software Process Improvement Plan
III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan
II, Technical Project Planning/ Management - Develop Technical Project Plan
August 3, 2001
56

- Perform Technical Project Tracking and Oversight III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan - Define Project Process
Software Quality Assurance Policy
III, Systems Management - Establish System Quality Assurance Strategy
Software Requirements Description Functionality of the Software Item
SRD II, Software Requirements Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Collect Capacity Planning Data - Validate Data Requirements - Determine Function/Data Access Requirements
I, System Architecture Design - Extend Requirements Traceability to System Architecture II, Program Planning/Management - Determine Release Content - Conduct Interim Progress Review II, Technical Project Planning/ Management - Develop Technical Project Plan - Perform Impact Analysis
Requirements for Interfaces External to the Software Item
II, Software Requirements Analysis - Define Interface Requirements - Collect Capacity Planning Data - Validate Data Requirements - Determine Function/Data Access Requirements
II, Software Requirements Analysis - Conduct Peer Review for Software Requirements - Transform Requirements Function/ Process Model - Transform Requirements Data Model - Generate Requirements Validation Modules - Perform Functional Requirements Review
Requirements for Services from the Infrastructure
II, Software Requirements Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Collect Capacity Planning Data
- Perform Integrated Functional Requirements Review II, Test Planning - Prepare Test Plans II, Software Architecture Design - Establish Design Model
Security and Privacy Specifications
II, Software Requirements Analysis
- Develop Integrated Software Architecture
August 3, 2001
57

- Determine Function/Data Access Requirements
- Identify and Incorporate Reusable Design Components - Identify Corporate Application Program Interfaces (APIs) - Identify Application-Internal Application Program Interfaces (APIs) - Transform Design Function/ Process Models - Perform Interface Module Design
Human-Factors Engineering
II, Software Requirements Analysis - Define User Interface/Human Factors Requirements
Data Definition and Database
II, Software Requirements Analysis - Collect Capacity Planning Data - Validate Functional Requirements - Determine Function/Data Access Requirements
- Design Integrated Menu Structure - Design Data Handling Screens - Perform Data Conversion Unit/ Module Design - Perform Critical Design Review II, Software Detailed Design
Software Quality Characteristics
II, Software Requirements Analysis - Collect Capacity Planning Data
- Perform Physical User Interface Design - Conduct Peer Review for Design - Perform Integrated Critical Design Review
Design and Implementation Constraints
II, Software Requirements Analysis - Collect Capacity Planning Data
II, Software Coding and Unit/Module Testing - Conduct User Interface Performance Test II, Information Assurance/Security
Computer Communications Requirements
II, Software Requirements Analysis
- Conduct DITSCAP Phase 2, Verification II, ConfigurationManagement/ Quality Assurance - Establish Other Application Functional Baseline
- Collect Capacity Planning Data
Requirements for Conversion to the Software Item
II, Software Requirements Analysis - Define Data Conversion Requirements - Validate Data Requirements
- Establish Corporate Functional Baseline - Manage Changes to Application Functional Baseline III, Operational Test and Evaluation - Conduct Implementation Readiness Review
Precedence and Criticality
II, Software Requirements Analysis - Perform Detailed Process Analysis
August 3, 2001
58

- Perform Detailed Function Analysis - Define Interface Requirements - Define User Interface/Human Factors Requirements - Define Data Conversion Requirements - Integrate Requirements - Collect Capacity Planning Data - Validate Data Requirements - Validate Functional Requirements - Determine Function/Data Access Requirements
Requirements Traceability
II, Software Requirements Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Define Interface Requirements - Define User Interface/Human Factors Requirements - Define Data Conversion Requirements - Integrate Requirements - Collect Capacity Planning Data - Prepare Functional Requirements Validation Test Scripts - Validate Data Requirements - Validate Functional Requirements - Determine Function/Data Access Requirements III, Functional Analysis - Perform Functional Analysis
Software Test Plan
S II, Software Requirements Analysis II, Software Detailed Design - Define Test Scripts II, Software Coding and Unit/Module Testing - Perform Unit Test/Module Test
???? - Prepare Functional Requirements Validation Test Scripts
Application Software Integration
II, Test Planning - Prepare Test Plans
II, Program Planning/Management - Conduct Interim Progress Review II, Technical Project Planning/ Management
August 3, 2001
59

- Assess Technical Project Risks II, Application Level Software Integration Test - Train Test Users - Prepare Test Schedule - Perform Tests
Application Functional Validation
II, Program Planning/Management - Conduct Interim Progress Review II, Technical Project Planning/ Management - Assess Technical Project Risks II, Deployment Planning - Prepare Site Acceptance Test Plans II, Application Level Functional Validation Test - Train Test Users - Prepare Test Schedule - Perform Tests
Enterprise System Integration
II, Program Planning/Management - Conduct Interim Progress Review II, Technical Project Planning/ Management - Assess Technical Project Risks II, Deployment Planning - Prepare Site Acceptance Test Plans II, Enterprise Level Integration Test - Train Test Users - Prepare Test Schedule - Perform Tests
Enterprise System Performance
II, Test Planning - Prepare Test Plans II, Technical Project Planning/ Management - Assess Technical Project Risks II, Enterprise Level Performance Test - Prepare Test Schedule - Perform Tests
August 3, 2001
60

Enterprise System Acceptance
II, Program Planning/Management - Conduct Interim Progress Review II, Technical Project Planning/ Management - Assess Technical Project Risks II, Enterprise Level Acceptance Test - Train Test Users - Prepare Test Schedule - Perform Tests
Operational Test and Evaluation
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Technical Project Planning/ Management - Assess Technical Project Risks II, Operational Test and Evaluation - Train Test Users - Prepare Test Schedule II, III, Operational Test and Evaluation - Perform Tests
Site Acceptance Software Test Report Software Unit S
II, Deployment Planning - Prepare Site Acceptance Test Plans II, Information Assurance/Security - Conduct DITSCAP Phase 3, Validation
Software Integration
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Acceptance Test, II, III, Operational Test and Evaluation - Perform Tests
II, Program Planning/Management
August 3, 2001
61

II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, III, Operational Test and Evaluation - Approve and Certify Test Results II, Information Assurance/Security - Conduct DITSCAP Phase 3, Validation
Functional Validation
- Conduct Milestone C Review II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, III, Operational Test and Evaluation - Approve and Certify Test Results II, Information Assurance/Security - Conduct DITSCAP Phase 3, Validation
Enterprise Integration
- Conduct Milestone C Review II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, III, Operational Test and Evaluation
August 3, 2001
62

- Approve and Certify Test Results II, Information Assurance/Security - Conduct DITSCAP Phase 3, Validation
Enterprise Performance
II, Enterprise Level Performance Test
- Conduct Performance Testing
Enterprise Acceptance
August 3, 2001
63

Operational Test and Evaluation
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, III, Operational Test and Evaluation - Approve and Certify Test Results III, Operational Test and Evaluaton - Conduct Implementation Readiness Review
Miscellaneous
II, Configuration Management/Quality Assurance - Conduct Functional Configuration Audit - Conduct Physical Configuration Audit
Source Code Record Document
SCRD
II, Software Coding and Unit/Module Testing - Construct Database Application Program Interfaces III, Development
II, Software Coding and Unit/Module Testing - Construct Functional Process Modules - Construct User Interface Units/ Modules III, Development - Conduct Unit Test/Module Test
II, Program Planning/Management - Conduct Milestone C Review II, Software Coding and Unit/Module Testing - Conduct Peer Review for Development II, Enterprise Level Performance Test - Conduct Performance Testing II, Configuration Management/Quality Assurance - Establish Product Baseline III, Development - Perform Peer Review for Development - Establish Development Baseline
- Develop Configuration Items
SQA Report
II, Configuration Management/ Quality Assurance
August 3, 2001
64

- Perform SQA Audit/Review of Products and Processes III, Tracking and Analysis - Perform SQA Audit of Product - Perform SQA Review of Process
- Perform Technical Project Tracking and Oversight
Stakeholder acceptance
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, III, Operational Test and Evaluation - Approve and Certify Test Results
Standard Software Process (System Development Scenario) Statement of Work
III, Tracking and Analysis - Perform SQA Review of Process
SOW
I, Program Planning/Management - Perform Funds Allocation and Execution II, Program Planning/Management II, III, Technical Project Planning/ Management - Manage Acquisition
I, II, Program Planning/Management - Manage Contract Performance
System Architecture and Requirements Allocation Description (Enterprise)
SARAD I, Program Planning/Management I, System Architecture Design - Integrate Execution Environment Requirements I, System Architecture Design - Determine Execution Environment Release Requirements - Extend Requirements Traceability to System Architecture III, Requirements Initiation - Define System Change Requirements - Establish Test and Evaluation Strategy - Conduct Milestone B Review I, System Architecture Design - Define Application Systems Architecture - Determine Execution Environment Solution II, Program Planning/Management - Develop Continuity of Operations Plan - Conduct Interim Progress Review II, Technical Project Planning/ Management
August 3, 2001
65

- Assess Technical Project Risks II, Test Planning - Define Test Plans II, Software Architecture Design - Perform Critical Design Review II, Software Detailed Design - Perform Integrated Critical Design Review II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification II, ConfigurationManagement/Quality Assurance - Establish Corporate Functional Baseline III, Systems Management - Establish System Release Strategy III, Operational Test and Evaluation - Conduct Implementation Readiness Review
(Application)
I, System Architecture Design - Define Application Systems Architecture
I, System Architecture Design - Determine Execution Environment Release Requirements - Extend Requirements Traceability to System Architecture III, Requirements Initiation - Define System Change Requirements
I, Program Planning/Management - Establish Test and Evaluation Strategy I, System Architecture Design - Perform System Architecture Review - integrate Execution Environment Requirements II, Program Planning/Management - Develop Continuity of Operations Plan - Conduct Interim Progress Review II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis - Define Interface Requirements - Define User Interface/Human Factors Requirements II, ConfigurationManagement/Quality Assurance
August 3, 2001
66

- Establish Other Application Functional Baseline III, Requirements Initiation - Define System Change Requirements
System Change Request
III, Requirements Initiation - Convert PTR to SCR - Define System Change Requirements III, Operational Performance Oversight - Measure System Performance
III, Requirements Initiation - Validate System Change Request - Rank or Prioritize System Change Requests III, Functional Analysis - Prepare Functional Analysis Estimates - Perform Functional Analysis - Conduct Functional Turnover Review III, Technical Design - Prepare Technical Design Estimates - Perform Technical Design
III, Functional Analysis - Prepare Functional Analysis Schedule - Conduct Peer Review for Analysis - Establish Analysis Baseline III, Technical Design - Prepare Technical Design Schedule - Maintain Configuration Items - Perform Peer Review for Design - Conduct Preliminary Design Review - Conduct Critical Design Review - Impact Configuration Change Orders - Establish Design Baseline - Prepare Release Package Proposal III, Development - Develop Configuration Items - Perform Peer Review for Development III, System Testing - Build Test CIs (Scripts and Data) - Perform Functional Configuration Audit III, Deployment - Deliver User Advisory
System Decision Memorandum Milestone A
N 0, Mission Need Establishment - Conduct Milestone A Review I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives - Appoint Program Manager - Determine Acquisition Strategy - Determine Program Management Plans - Perform COTS Availability Research - Determine Integration Management Plans
August 3, 2001
67

- Conduct Decision Review - Establish Project Support - Conduct Milestone B Review I, System Requirements Analysis - Define Operational Architecture I, II, III, Program Planning/Management - Maintain Customer Relationship II, Program Planning/Management - Conduct Milestone C Review
Milestone B
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification
Milestone C
III, Systems Management - Conduct Full-Rate Production Decision Review
Full-Rate Production Decision Review
III, Operational Test and Evaluation - Conduct Full-Rate Production Decision Review
System Development Scenario
I, Program Definition and Risk Reduction - Perform Technical Project Tracking and Oversight
System Development Scenario Documentation Standards System Funding Profile
III, Tracking and Analysis - Perform SQA Audit of Product
III, Systems Management - Establish System Quality Assurance Strategy - Establish System Release Strategy - Establish System Configuration Management Strategy - Establish System Test and Evaluation Strategy
August 3, 2001
68

- Establish System Risk Management Strategy III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan - Develop Training Program Plan III, Requirements Initiation - Record and Analyze Problem - Define System Change Requirements - Validate System Change Request III, Functional Analysis - Prepare Functional Analysis Estimates III, Technical Design - Prepare Technical Design Estimates III, Development - Develop Configuration Items III, System Testing - Develop Test Schedule III, Deployment - Develop Delivery Schedule
System Integration and Implementation Plan
I, Program Planning/Management - Perform Release II, Technical ProjectPlanning Planning/ Management - Integrate Technical Project Plans
System Release Strategy
III, Systems Management - Establish System Release Strategy
System Requirements Specification
SRS
I, System Requirements Analysis
I, Program Planning/Management - Perform Release Planning
General
- Establish Test and Evaluation Strategy - Maintain Acquisition
Functional and Performance
- Define Functional Requirements
- Determine System Access Requirements - Determine Business Performance Requirements - Sys Rqmts Anal
- Conduct Milestone B Review I, System Requirements Analysis - Develop Joint Technical Architecture (JTA) Profile
August 3, 2001
69

Organizational
- Identify User/Customer Organizations
- Perform System Requirements Review I, System Architecture Design
Security, and Privacy Protection
- Define Information Assurance/ Security Requirements - Determine System Access Requirements
- Define Application Systems Architecture - Extend Requirements Traceability to System Architecture - Define and Establish System Security Architecture
Human-Factors Engineering
- Define Human Factors Requirements
Operations and Maintenance
- Determine Systems Operations Requirements
- Assess Technical Project Risks II, Software Requirements Analysis
System External Interface
- Define External Interface Data Requirements - Determine System Access Requirements
- Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis
Design Constraints and Qualification
- Define External Design Constraints
- Define Interface Requirements - Define User Interface/Human Factors Requirements
Computer Resource: Computer Hardware Computer Hardware Resource Computer Software Computer Communications - Determine Capacity Requirements - Determine Capacity Requirements - Determine Capacity Requirements - Define Environmental Requirements
- Define Data Conversion Requirements - Integrate Requirements - Determine Function/Data Access Requirements - Perform Functional Requirements Review - Perform Integrated Functional Requirements Review II, Test Planning
Internal Data
- Define Internal Data Requirements - Determine System Access Requirements
- Prepare Test Plans II, Deployment Planning - Prepare Site Acceptance Test Plans
Personnel, Training, and Logistics
- Define Personnel and Logistics Requirements
- Prepare User Training Plans - Produce User Class Materials
Distribution and Installation
- Define Software Distribution and Installation Requirements
II, Software Coding and Unit/Module Testing
August 3, 2001
70

- Conduct User Interface Performance Test Precedence and Criticality - Define Functional Requirements II, Application Level Software Integration Test - Analyze System Performance System Quality Characteristics - Define Quality Requirements II, Enterprise Level Performance Test - Conduct Performance Testing - Define Functional Requirements - Define Information Assurance/ Security Requirements - Define External Interface Data Requirements - Determine Systems Operations Requirements - Define Human Factors Requirements - Define Environmental Requirements - Define External Design Constraints - Define Internal Data Requirements - Define Software Distribution and Installation Requirements - Define Personnel and Logistics Requirements - Define Quality Requirements - Determine Business Performance Requirements - Sys Rqmts Anal - Determine Capacity Requirements II, ConfigurationManagement/ Quality Assurance - Establish Other Application Functional Baseline - Establish Corporate Functional Baseline III, Systems Management - Establish System Release Strategy III, Operational Performance Oversight - Measure System Performance
Requirements Traceability
III, Requirements Initiation - Define System Change Requirements
System Security Authorization Agreement
SSAA
I, Information Assurance/Security - Conduct DITSCAP Phase 1, Definition
II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification - Conduct DITSCAP Phase 3 Validation
I, Program Planning/Management - Certify Compliance with ClingerCohen Act - Establish Risk Management Strategy - Conduct Milestone B Review I, System Requirements Analysis - Define Information Assurance/ Security Requirements I, System Architecture Design - Define Application Systems Architecture
August 3, 2001
71

- Define and Establish System Security Architecture II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Technical Project Planning/ Management - Assess Technical Project Risks III, Operational Test and Evaluation - Conduct Implementation Readiness Review
Systems Development Plan
III, Systems Management - Establish System Quality Assurance Strategy - Establish System Release Strategy - Establish System Configuration Management Strategy - Establish System Test and Evaluation Strategy - Establish System Risk Management Strategy III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan - Define Project Process - Prepare Project Staffing Profile - Prepare Project Funding Profile - Develop Training Program Plan III, Deployment - Shut Down Legacy Systems
Systems Integration and Implementation Plan Issues
Systems Inventory Database
SID
I, System Architecture Design - Define Application System Architecture
Systems Operations Bills
August 3, 2001
72

Technical Architecture Requirements
I, System Architecture Design - Determine Execution Environment Release Requirements - Define and Establish System Security Architecture II, Program Planning/Management, II, III, Technical Project Planning/ Management - Manage Acquisition
II, Software Architecture Design - Perform Critical Design Review II, Software Detailed Design - Perform Integrated Critical Design Review
Technical Architecture Review Approval/ Disapproval
I, System Architecture Design - Conduct Technical Architecture Review
Technical Architecture Review Board Policy (SM-04) and Technical Architecture Guidance Policy, SM-09
I, System Architecture Design
- Determine Execution Environment Solution - Conduct Technical Architecture Review
Technical Architecture Review Submission
I, System Architecture Design - Determine Execution Environment Solution III, Technical Design - Perform Technical Design
I, System Architecture Design - Conduct Technical Architecture Review III, Technical Design - Perform Peer Review for Design
Technical Design
Technical Performance Requirements Specification ????
Technical Project Officer Appointment Letter
I, Program Planning/Management - Establish Project Support
Technical Project Plan
TPP
II, Technical Project Planning/ Management - Assess Technical Project Risks
I, Configuration Management/ Quality Assurance - Establish Configuration Management Strategy
August 3, 2001
73

- Obtain Technical Training - Perform Technical Project Tracking and Oversight II, Test Planning - Prepare Test Plans II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Prepare Test Schedule - Conduct Testing Peer Review - Conduct Test Readiness Review - Perform Tests III, Operational Test and Evaluation - Perform Tests II, Enterprise Level Acceptance Test - Conduct Enterprise Level Test Readiness Review III, Technical Design - Build Software Development Plan III, Tracking and Analysis - Perform Project Tracking and Oversight
II, Program Planning/Management - Conduct Interim Progress Review II, Technical Project Planning/ Management - Integrate Technical Project Plans - Establish Software Engineering/ Testing Development Environment
- Develop Software Process Improvement Plan II, Software Requirements Analysis - Perform Detailed Data Analysis - Perform Detailed Process Analysis - Perform Detailed Function Analysis II, Software Architecture Design - Prepare Application Release Checklist - Perform Critical Design Review II, Deployment Planning - Establish Transition Strategy - Issue User Advisory II, Software Detailed Design - Perform Integrated Critical Design Review II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Performance Test, Enterprise Level Acceptance Test, Operational Test and Evaluation - Train Test Users III, Systems Management - Establish System Quality Assurance Strategy - Establish System Configuration Management Strategy
August 3, 2001
74

- Establish System Test and Evaluation Strategy - Establish System Risk Management Strategy III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan - Define Project Process - Prepare Project Staffing Profile - Prepare Project Funding Profile - Develop Training Program Plan
Technical Project Plan Adjustments
II, Technical Project Planning/ Management - Develop Technical Project Plan - Perform Technical Project Tracking and Oversight
Technology Changes
Test and Evaluation Master Plan
TEMP
I, Program Planning/Management - Establish Test and Evaluation Strategy
II, Program Planning/Management - Update Program Documentation II, Test Planning - Prepare Test Plans III, System Management - Establish System Test and Evaluation Strategy
I, Program Planning/Management - Conduct Milestone B Review I, Configuration Management/Quality Assurance - Establish Program Baseline II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review III, ConfigurationManagement/ Quality Assurance - Manage Changes to Program Baseline II, Deployment Planning - Prepare Site Acceptance Test Plans II, Information Assurance/Security - Conduct DITSCAP Phase 2, Verification III, System Management
August 3, 2001
75

- Establish System Test and Strategy III,Evaluation Technical Project Planning/ Management - Define Project Process III, System Testing - Develop Test Schedule - Perform System Tests
Test Data (Sets)
III, Software Requirements Analysis - Prepare Functional Requirements Validation Test Scripts II, Software Detailed Design - Define Test Scripts
III, Development - Conduct Unit Test/Module Test III, System Testing - Build Test CIs (Scripts and Data)
III, Software Requirements Analysis - Validate Data Requirements II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces - Conduct Database Performance Test - Conduct User Interface Test - Conduct User Interface Performance Test - Perform Unit Test/Module Test II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, (Enterprise Level Performance Test), Enterprise Level Acceptance Test, Operational Test and Evaluation - Conduct Testing Peer Review - Perform Tests III, Operational Test and Evaluation - Perform Tests III, System Testing - Conduct Peer Review for Testing
Test Database
August 3, 2001
76

Test Discrepancy Report
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, Enterprise Level Acceptance Test, II, III, Operational Test and Evaluation - Perform Tests II, Enterprise Level Performance Test - Conduct Performance Tests III, System Testing - Perform System Tests
Test Environment
III, System Testing
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, (Enterprise Level Performance Test), Enterprise Level Acceptance Test, Operational Test and Evaluation - Train Test Users - Conduct Test Readiness Review - Perform Tests II, Enterprise Level Acceptance Test - Conduct Enterprise Level Test Readiness Review III, Operational Test and Evaluation - Perform Tests III, System Testing - Perform Test Readiness Review - Perform System Tests
- Create Test Environment
Test Interface Files
August 3, 2001
77

Test Library
III, System Testing
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, (Enterprise Level Performance Test), Enterprise Level Acceptance Test, II, III, Operational Test and Evaluation - Perform Tests III, System Testing - Perform System Tests - Perform Physical Configuration Audit
III, System Testing
- Create Test Environment
- Perform Functional Configuration Audit III, Deployment - Deliver Release
Test Results
III, Systems Management - Conduct Full-Rate Production Decision Review
Test Scripts
II, Software Requirements Analysis - Prepare Functional Requirements Validation Test Scripts II, Software Architecture Design - Transform Design Function/Process Models - Perform Interface Module Design - Perform Data Conversion Unit/ Module Design II, Software Detailed Design - Define Test Scripts III, Development - Conduct Unit Test/Module Test
III, Development - Conduct Unit Test/Module Test
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Software Requirements Analysis - Prepare Functional Requirements Validation Test Scripts - Generate Requirements Validation User Interface - Validate Data Requirements - Validate Functional Requirements I, Software Detailed Design - Define Test Scripts (previous) II, Software Coding and Unit/Module Testing - Test Physical Database and Application Program Interfaces - Conduct Database Performance Test - Conduct User Interface Test - Conduct User Interface Performance Test
August 3, 2001
78

II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, (Enterprise Level Performance Test), Enterprise Level Acceptance Test, Operational Test and Evaluation - Train Test Users - Conduct Testing Peer Review - Perform Tests II, Enterprise Level Performance Test - Conduct Performance Testing III, Operational Test and Evaluation - Perform Tests III, System Testing - Build Test CIs (Scripts and Data - Conduct Peer Review for Testing - Perform Functional Configuration Audit Testing Analysis Report S
System Testing
III, System Testing - Perform System Tests
III, System Testing - Perform Functional Configuration Audit - Perform Physical Configuration Audit - Certify Testing III, Deployment - Deliver User Advisory
Testing Policy
III, System Management - Establish System Test and Evaluation Strategy
To-Be Business Data Model (see BPR Report)
0, Business Process Review and Improvement - Determine Business Performance Requirements - Business Process Analysis
To-Be Business Process Model (see BPR Report)
0, Business Process Review and Improvement
August 3, 2001
79

- Determine Business Performance Requirements - Business Process Analysis
- Define Functional Requirements
- Identify User/Customer Organizations - Define Information Assurance Security Requirements - Define External Interface Data Requirements - Define Systems Operations Requirements - Define Environmental Requirements - Define External Design Constraints - Define Internal Data Requirements - Define Software Distribution and Installation Requirements - Define Personnel and Logistics Requirements - Define Quality Requirements - Determine Business Performance Requirements - System Requirements Analysis - Determine Capacity Requirements
Trained Testing Group
II, Application Level Software Integration Test, Application Level Functional Validation Test, Enterprise Level Integration Test, (Enterprise Level Performance Test), Enterprise Level Acceptance Test, Operational Test and Evaluation - Train Test Users
Training Certificate
III, Deployment - Train Users
Training Database (History)
III, Technical Project Planning/ Management - Develop Individual Development Plans - Develop Project Training Plan
Training Materials
II, Deployment Planning
III, Development
III, Deployment
August 3, 2001
80

- Produce User Class Materials II, Deployment Planning - Prepare User Training Plans
- Update User's Procedures
- Train Users
Training Plan
II, Program Planning/Management - Conduct Milestone C Review II, Deployment Planning - Produce User Class Materials
Training Program Plan
III, Technical Project Planning/ Management - Develop Training Program Plan
III, Technical Project Planning/ Management - Define Project Process - Develop Project Training Plan - Develop Individual Development Plans
Transition Plan
II, Deployment Planning - Establish Transition Strategy
II, Program Planning/Management - Conduct Milestone C Review III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan X
TSO Site Assessment Results
TSO Site Software Process Improvement Plan
III, Technical Project Planning/ Management - Prepare/Update Software Process Improvement Plan
Unit Test Checklist
II, Software Coding and Unit/Module Testing - Perform Unit Test/Module Test III, Development - Conduct Unit Test/Module Test
III, Development - Perform Peer Review for Development
User Advisory
II, Deployment Planning - Issue User Advisory III, Deployment - Deliver User Advisory
User Interface Standards
II, Software Detailed Design - Perform Physical User Interface Design II, Software Coding and Unit/Module Testing
August 3, 2001
81

- Conduct User Interface Test
User Screens
II, Software Architecture Design - Design Integrated Menu Structure - Design Data Handling Screens II, Software Detailed Design - Perform Physical User Interface Design II, Software Coding and Unit/Module Testing - Create On-Line Help Screens - Construct User Interface Units/ Modules
II, Software Coding and Unit/Module Testing - Conduct User Interface Test - Conduct User Interface Performance Test - Complete User's Procedures - Conduct Peer Review for Development - Perform Unit Test/Module Test
User Staffing Plan
II, Deployment Planning - Prepare User Training Plans
User's Manual
UM
II, Software Detailed Design - Define User's Procedures
II, Software Coding and Unit/Module Testing - Complete User's Procedures III, Development - Update User's Procedures
II, Program Planning/Management - Conduct Interim Progress Review - Conduct Milestone C Review II, Deployment Planning - Establish Transition Strategy - Prepare Software Installation Plans - Prepare Site Acceptance Test Plans - Prepare User Training Plans - Produce User Class Materials II, Configuration Management/Quality Assurance - Package Products for Release to Production III, Development - Establish Development Baseline III, Deployment - Train Users - Establish Help Desk Support
Written or Oral Communication of Problem
III, Requirements Initiation - Record and Analyze Problem
August 3, 2001
82
Life Cycle / SDS Documentation Standards Coordination / Approval

Documentation Standards Acronym Std. No. Submitter Coordination Approval Authority
APB
S-PM-043
Program Manager/Functional Project Officer
Dir, DCII Applications Architecture Program Director Chief Financial Officer Functional Manager Functional Manager Dir, DCII Applications Architecture Dir, Systems Integration Dir, Resource Management Dir, DCII Applications Architecture Program Director Chief Information Officer Chief Financial Officer
Chief Information Officer
AS
S-PM-047
AOA
S-PM-034
Functional Manager
Application Release Checklist Baseline/Physical Configuration Audit Checklist
S-SE-029 S-CM-008 Configuration Management Analyst Program Manager/Functional Project Officer Technical Project Officer
Business Process Reengineering Report
S-PM-069
Product Line Executive
Business Integration Executive Director, Requirements Integration Customer Representative
Business Line Executive
Clinger-Cohen Compliancy Act Report
S-PM-065
Business/Product Line Executive Director, Systems Integration
Director, Information and Technology
Compliance Certification Configuration Audit Report S-CM-007 Configuration Management Analyst Technical Project Officer Program Manager/Functional Project Officer Director, Systems Integration Director, DCII Engineering
8/3/2013, 6:26 PM
83

Configuration Management Plan CMP S-PM-061 Configuration Manager Program Manager/Functional Project Officer Technical Project Officer(s) Director, DCII Application Architecture
Command, Control, Communications, Computers, and Intelligence (C4I) Support Plan (C4ISP) Continuity of Operations Plan
C4ISP
S-PM-059
COOP
S-PM-029
Director, Systems Integration Director, DCII Engineering Corporate Continuity of Operations Coordinator Chief Information Officer DFAS Business or Product Line Executive DFAS Client Service Executive Program Manager/Functional Project Officer Director, DCII Engineering
Director, Resource Management
Customer Relationship Memorandum of Understanding
MOU
S-PM-068
DFAS Program Manager Senior Customer Representative
---
DMP
S-PM-031
Data Analyst
Functional Data Manager
Database Design Description Documented Risks Economic Analysis
DBDD
S-PM-042 S-PM-013
Database Administrator Functional Analyst Program Manager/Functional Project Officer Systems Manager or Project Manager Technical Project Officer Functional Manager Program Director Director, DCII Engineering Director, Systems Integration ---
Technical Project Officer System Manager Chief Financial Officer
EA
S-PM-044
Functional Acquisition Requirements
FAR
S-PM-052
Functional Proponent
Functional Analysis Functional Configuration Audit Report Individual Development Plan IDP S-CM-004 S-PM-033
---
---
Software Engineer
Project Manager
Infrastructure Requirements Document
IRD
S-PM-045
DCII Technical Project Officer
Program Manager/Functional Project Officer Dir, DCII Applications Architecture
Dir, DCII Engineering
8/3/2013, 6:26 PM
84
Infrastructure Services Request
ISR
S-PM-046
Chairman, TARB Dir, DCII Applications Architecture Dir, DCII Engineering Technical Project Officer Systems Manager Release Manager
S-PM-19
Operations Manager
---
Installation Plan Joint Technical Architecture Profile
S-PM-063 S-PM-048 Program Manager/Functional Project Officer Dir, Systems Integration Dir, DCII Engineering Chief Information Officer Dir, DCII Applications Architecture Program Director Chief Information Officer Chief Financial Officer DISA Center for Standards
LCCE
S-PM-032
Functional Manager
MIPR Mission Need Statement
MIPR MNS
S-PM-015-sds S-PM-026 Functional Analyst Dir, Systems Integration Dir, Resource Management Dir, Information and Technology Dir, Systems Integration Dir, Information and Technology Business Line Executive
Operational Architecture
OA
S-PM-049
Product Line Manager
ORD
S-PM-023
Program Manager/Functional Project Officer Software Engineer
Dir, Systems Integration Deputy for Information and Technology Technical Project Officer End User Technical Project Officer Dir, DCII Applications Architecture Program Director Chief Information Officer
Business Line Executive
Operator's Manual
OM
S-SE-026
Director, DCII Engineering
Product Delivery Plan Program Management Plan PMP
S-PM-005 S-PM-025
Functional Analyst Program Manager/Functional Project Officer
Systems Manager Functional Manager
8/3/2013, 6:26 PM
85

Program Manager's Charter PMC S-PM-030 Program Manager/Functional Project Officer Chief Information Officer Program Director Functional Manager DFAS Program Advocate DFAS Program Manager Program Manager/Functional Project Officer Technical Project Officer Technical Project Officer --Technical Project Officer Technical Project Officer Functional Analyst User Release Manager Operations Manager Technical Project Officer --Director, DFAS
PQAP
S-PM-054
Quality Assurance Analyst
Director, Systems Integration Director, DCII Engineering
Program Trouble Report Project Training Plan Ranked or Prioritized SCR List Release Guidance Release Instructions
PTR
S-CM-001 S-PM-021 S-PM-009 S-PM-012 S-SE-012
User/Functional Analyst Technical Project Officer Functional Analyst Functional Analyst Software Engineer
---TSO Site Director Systems Manager Systems Manager Technical Project Officer
Release Package Requirements Definition Review Checklist Review Report Risk Management Plan Software Architecture Description Software Configuration Index Record Software Design Description Software Development Plan SAD SCIR SDD SDP
S-PM-014 S-SE-003 S-PM-036 S-SE-028 S-PM-006 S-PM-040 S-SE-023 S-SE-019 S-PM-017
Functional Analyst --Scribe Scribe Functional Analyst Director, DCII Engineering
Systems Manager --Review Chair(s) Review Chair(s) System Manager Chief Technology Officer Technical Project Officer Technical Project Officer Technical Project Officer
----Technical Project Officer Technical Project Officer(s)
--Software Engineer Software Engineer
----Systems Manager
8/3/2013, 6:26 PM
86

Software Interface Design Description Software Process Improvement Plan SIDD S-PM-041 S-PM-060 Software Engineer SPI Coordinator --Technical Project Officer Dir, DCII Engineering Dir, Sys Engineering Support TSO Site Directors Program Director Dir, DCII Applications Architecture Dir, DCII Engineering DCD Technical Project Officer DCW Technical Project Officer Test Director Program Manager/Functional Project Officer Technical Project Officer Acquisitions Support Specialist Technical Project Officer Technical Project Officer TSO Director
Software Requirements Description
SRD
S-PM-039
Functional Manager
SQA Report
S-PM-050
Quality Assurance Analyst
Statement of Work
SOW
S-PM-051
Program Analyst
Program Manager, Functional Project Officer Dir, Acquisitions Support Office
System Architecture and Requirements Allocation Description
SARAD
S-PM-038
Technical Project Officer
Director, DCII Engineering Director, DCII Applications Architecture Chief Technology Officer Technical Project Officer
System Change Request System Requirements Specification System Security Authorization Agreement
SCR SRS SSAA
S-CM-002 S-PM-037 S-PM-035
Functional Analyst
Systems Manager
Certification Authority User Representative
Designated Approving Authority (Director for Information and Technology) Site TSO Director Director, ISO DFAS Chief Technology Officer Program Manager/Functional Project Officer
Technical Acquisition Requirements
S-PM-053
Director, DCII Engineering Director, Systems Integration
TPP
S-PM-027
DCII Technical Project Officer
8/3/2013, 6:26 PM
87
TEMP
S-PM-024
Functional Manager(s) User's Representative Asst Dep Dir for Test, Eval, & LCM Dir, DCII Applications Architecture Enterprise Test Agency Director, Systems Integration Operational Test Agency Chief Information Officer
Dir, OT&E, OSD Dir, Test Sys Eng & Eval (OUSD(A&T))
Test Cases Test Discrepancy Report Test Plan Application Enterprise TDR
S-SE-021 S-SE-011 S-SE-020 Technical Project Officer Enterprise Test Director Application Quality Assurance - ? DCII Test Director DCII Technical Project Officer Dir, DCII Engineering Deputy Director, Test and LCM -----
Technical Project Officer ---
Program Manager Dir, DCII Applications Architecture
Test Report Testing Analysis Report Training Plan
S-SE-022 S-SE-014 S-PM-064 Tester Functional Analyst Technical Project Officer End User Technical Project Officer Systems Manager Program Manager/Functional Project Officer TSO Site Director
Transition Plan
S-PM-062
Functional Analyst
Program Manager/Functional Project Officer Technical Project Officer End User
Unit Test Checklist User Advisory
S-SE-030 S-SE-024 Program Analyst Technical Project Officer Program Manager/Functional Project Officer
8/3/2013, 6:26 PM
88

User's Manual UM S-SE-025 Software Engineer Program Manager/Functional Project Officer Technical Project Officer Functional Manager
8/3/2013, 6:26 PM
89
8/3/2013, 6:26 PM
90
8/3/2013, 6:26 PM
91
8/3/2013, 6:26 PM
92
8/3/2013, 6:26 PM
93
8/3/2013, 6:26 PM
94
8/3/2013, 6:26 PM
95
8/3/2013, 6:26 PM
96
Documentation Standard Review
Status Date Standard Title Acquisition Program Baseline Interim 7/1/00 Final 2/28/01 Date of Comment 4/30/01 Source SESO Comments Coordination/Approval: change DCII Appl Arch to Dir, DCII Appl Arch Paragraph 1.1: Correction of typographical error Coordination/Approval: change DCII TPO to Dir, DCII Eng Adopted Disposition of Comments
7/1/00
2/28/01
4/30/01
SESO
Adopted
Analysis of Alternatives
7/1/00
2/28/01
8/8/00
DFAS AR
8/8/00 8/8/00
DFAS AR DFAS AR
Opening paragraph: Add sentence after " DFAS or DOD programs." "The benefits estimate completed during Pre-Milestone 0 shall be specifically updated for each alternative." Paragraph 2: In the second sentence, add the word "benefits," between "...useful life," and "functionality,". Paragraph 3.n. Summary: Add column at end of table: "Benefits Plus $1M Minus $2M Plus $500K Plus $50K
Adopted
Adopted Adopted
Economic Analysis Infrastructure Requirements Description Life Cycle Cost Estimates
7/1/2000 ####### 7/1/00 2/28/01
7/1/00
2/28/01
4/30/01
SESO
Coordination/Approval: Change DCII Applications Architect to Dir, DCII Applications Architecture Modify as a result of revised DOD 5000.2-R (previously Milestone 0) Modify as a result of revised DOD 5000.2-R (previously Milestone I) Modify as a result of revised DOD 5000.2-R (previously Milestone II)
Adopted
5/4/01
5/1/01
DFAS-AR
Adopted
5/4/01
5/1/01
DFAS-AR
Adopted
5/4/01
5/1/01
DFAS-AR
Adopted
Military Interdepartmental Purchase Request Mission Need Statement
Interim / 7/1/00 7/1/2000 5/4/2001 5/4/2001 DFAS-AR Modify link to CSCSI Adopted
8/3/2013, 6:26 PM
97
7/1/00
2/28/01
7/17/00
JTIC
7/17/00 7/17/00
JTIC JTIC
Recommend that template be prefaced with a descriptive paragraph or two explaining the importance and relevance of the document. (Tie into the LCM training program?) Recommend that each document be labeled "mandatory format" or "recommended format," as appropriate. Paragraph 4: delete next to last sentence: ". Each Key Performance Parameter is also considered a Critical Technical Parameter." After discussion, it was agreed that some KPPs may be operational, rather than technical, in nature and should not be CTPs. This sentence has been removed from the Baseline Performance Parameters, as well as from the TIDR. Paragraph 4a(1): (FFMR compliance) - remove the word "substantially" from the threshold. This was a directive that came down through DFAS-HQ several months ago. The use of this word has been removed from the Baseline Performance Parameters, as well as from the TIDR. Paragraph 4b: (IER) deserves additional text. There is much confusion (even here) with IER, its intent, and who it applies to (SOE? COE? Both?). The direction given on the TIDR (and subsequently in this document) was intended as interim guidance until a clarification by a higher authority was provided. We have the opportunity to correct or expand this section now. Paragraph 5c(2)(b): provides guidance on DIICOE compliance. This is an area that is evolving based on text in the JTA v3 and is no longer totally accurate. This is another part where we have the opportunity to correct or expand this section now. Paragraph 5f (as well as paragraph 4c(1): has a parameter for Help Desk. Though it could possibly fit in either section, for consistency purposes, recommend it be listed in one section only. We feel it better fits in 4c(1) rather than here. Adopted Adopted
7/17/00
JTIC
Adopted
7/17/00
JTIC
7/17/00
JTIC
7/17/00
JTIC
Program Management Plan Program Manager's Charter Software Requirements Description
7/1/2000 ####### 7/1/2000 ####### 7/1/00 5/4/01 4/30/01 SESO Coordination/Approval: change DCII TPO to Dir, DCII Eng Adopted
System Architecture and Requirements Allocation Description
7/1/00
2/28/01
10/4/00
SDS Group
Add Requirements Traceability section
Adopted
8/3/2013, 6:26 PM
98
1/21/01
DFAS-AR
Paragraph 4: new Paragraph 5 (previous paragraph 4): minor modifications Paragraph 6 (previous paragraph 5): rewritten Paragraph 9 (prevous paragraph 8): minor modifications Paragraph 10 (previous paragraph 9): rewritten Coordination/approval: modified
Adopted
System Requirements Specification
7/1/00
2/28/01
8/23/00
"Paragraph 5: According to our meeting on Wednesday, Stds Wkg Group August 9 and our discussion on SRS Standard S-PM-037 Item (G. Pimentel, N.5 Required States and Modes, we agree that the CL) information provided in the standard is unclear and insufficient in definition. Therefore, there is a need to provide an interpretation and understanding of the Concepts: State & Mode, to be used in the Functional Hierarchy Diagram according to the SRS for DDRS-Budgetary. I would like to submit to your consideration, the following definitions that will clarify and help in using such concepts, as well as examples that illustrate their interpretation and application."
Sent back for clarification
Definition Background ., for a deterministic linear continuos system, (c.f. F. Russo and Director et.al) a State is defined as follows, A STATE of a system at time t0 is any amount of information, which together with any possible input function specified for " " " "
Comment: Certainly the definition is very general, it implies the possibility to incorporate Initial and Boundary Conditions in the way to determine the output function or response of any system. Yet it abstracts the main elements of its essence and provides a guide for the interpretation of what is a State of an Object-Oriented Model.
"
"
"
"
8/3/2013, 6:26 PM
99
"Proposed Definitions for SRS S-PM-037 Item 5. A system STATE of an Object-Oriented Model, at specific time ti , can be defined as the set of objects or instances, their attributes and values with their associated methods/ functions at time ti, as defined or determined by the methods/ functions that are executed at t < ti , which uniquely response is characterized by all the attribute values, objects/ instances and methods/functions that meet a specific set of requirements. Therefore, the set of all possible states can be called STATE SPACE." " " " "
A system MODE of an Object-Oriented Model can be defined as a specific set of Objects, their attributes and values and their Methods/Functions that enable; a) A specific capability or functionality, and/or b) The definition of specific boundary conditions and/or c) A set of initial conditions of operation, all of which meet a specific set of requirements, remaining valid and active until a different Mode is invoked. Alternatively, a System MODE can be understood as a STATE SUB-SPACE.
"
"
"
"
8/3/2013, 6:26 PM
100
Comments: For the purposes of immediate objectives SRS/ S-PM-037 Item N.5 these definitions should suffice. However, their implications for Analysis, Design and Management are substantial and powerful. For example, the idea of Observable State Variables and Orthogonality applies to Metrics or to the decomposition of design of Modular Architectures for complex systems, like ours. Some of these ideas and concepts could be helpful and necessary for understanding computerized process-algebraic compositional verification. This approach could be used to describe some advanced but practical ways of using basic techniques on object-oriented modeling and requirements specification. In using a process-algebraic semantic approach the representation is at the semantic and state space level.
"
"
"
"
Therefore, the techniques available should be immediately applicable to a wide range of formalisms that can be given semantics in terms of state spaces and transition representations. The benefits will be immediate to Requirements Analysis, System Design and Management (Control and Measures). These are some ideas of interest where if, time, and resources are allowed, I would be happy to contribute.
"
"
"
"
8/3/2013, 6:26 PM
101
Examples: For the case of the DDRS-CFO application, at the higher level of definition it is possible to identify the following system modes:
That is, the Security, Maintenance and Report Production are examples of specific capabilities or functionality bounded by specific conditions of access and/or purpose. In my opinion a set of modes defined at specific level should be mutually exclusive otherwise its differentiation with respect to STATE might be compromised.
"
"
"
"
Yet it is possible to envision the possibility of EMBEDDED MODES where a MODE could be included in another MODE as a consequence of a specific system state(s). This is an interesting scenario for requirement analysis, since in the process of assessing impact of an SCR in the understanding of a hierarchy of requirements, this definition would empower a Requirements Analyst in correlating, qualifying and quantifying the impact on development or re-engineering efforts.
"
"
"
"
To illustrate the Case of a Embedded Modes -in the context of DDRS-CFO, lets consider the case in which for a Journal Voucher where an APPROVAL MODE could be invoked as part Space State of the System as defined by functional requirements. Note: Examples of system States are trivial, they follow the definition itself, and will not be discussed here, unless is explicitly requested.
"
"
"
"
8/3/2013, 6:26 PM
102

Adopted 7/17/00 SDS Group Paragraph 6.1: second paragraph: Change " "out of bounds" conditions, requirements for error handling, " to " "out of bounds conditions; user roles responsible for performing functions; requirements for error handling; " third paragraph: Change "... contributed to, and business unit associations." to "... contributed to, business unit associations, and user roles which perform the functions." Paragraph 6.3: first paragraph: Change " the system must provide, and the criteria " to " the system must provide, access instructions for user roles, and the criteria " Paragraph 6.6: second paragraph, under bullet "Required characteristics of individual data elements that the system must provide, store, send, access, retrieve, etc., such as:" Add sub-bullet under "Names/identifiers", before "Applicationunique identifiers": "User access requirements to review, monitor, or trigger interface input or output" Paragraph 6.6: The term "entity" is not appropriate in all instances. Need to clarify when it should be changed to another term. Paragraph 6.9: fourth paragraph: Change " transaction volumes, description, and notes." to " transaction volumes, description, user role access requirements, and notes." Paragraph 6.10: delete this paragraph and renumber remaining paragraphs Coordination/Approval: remove DCII TPO - it's a duplicate for Dir, DCII Eng Modify based on revisions to regulations Adopted
7/17/00
SDS Group
7/17/00
SDS Group
Adopted
7/17/00
SDS Group
Adopted
7/17/00
SDS Group
Adopted
7/17/00
SDS Group
Adopted
4/30/01
SESO
Adopted
System Security Authorization Agreement
Interim / 3/1/01
2/20/01
DFAS-AR
Adopted
7/1/2000
5/4/01
11/6/00
SDS Group
Paragraph 3: add: "Briefly describe the functionality being developed by the release.
Adopted
8/3/2013, 6:26 PM
103
Paragraph 4: change to: "Identify management responsibilities, roles, numbers of resources, dependencies, and products. Prepare schedule for performance of the Software Requirements Analysis, Software Architecture Design, Software Detailed Design, and Software Coding and Unit/Module Testing activities of the life cycle. These activities all conclude with reviews whose dates should coincide with the activity completion date. As development begins, the percent completeness of each activity will be recorded and reported bi-weekly for updating of integrated release schedules. 4/27/2001 SESO Coordination/Approval: Changed DCII TPO to Dir, DCII Eng
Adopted
Adopted
7/1/00
5/4/01
7/17/00
JTIC
7/17/00
JTIC
Recommend that template be prefaced with a descriptive paragraph or two explaining the importance and relevance of the document. (Tie into the LCM training program?) Recommend that each document be labeled "mandatory format" or "recommended format," as appropriate.
7/17/00
JTIC
Paragraph 1c: we should make it clear that each documented parameter in the ORD (to include threshold and objective) is brought forward to this section unless it has been identified as a CTP. It would then go into paragraph 1e. It is recommended that a statement to the affect that COIs are listed in paragraph 4b, not part 1c, be inserted. We understand that COIs are here for clarity purposes (to identify which are MOEs and which are MOSs and under which COI they fall) and that is fine. Though duplicative, listing COIs in both places is probably ok. Paragraph 3b2: exit criteria is mentioned. It is recommended that a list of typical exit criteria be inserted. (The OTRR checklist serves as DT&E exit criteria, as well as OT&E entrance criteria. Additionally, a DT&E report, a formal certification by the PM that the system has successfully completed DT and is ready for OT, as well as other possible items, are common DT exit criteria.) Reference: Update link to DOD 5000.2-R
Adopted
7/17/00
JTIC
Adopted
5/1/2001
SESO
Adopted
Test Plan
Interim / 7/1/00
7/17/00
JTIC
7/17/00
JTIC
Recommend that template be prefaced with a descriptive paragraph or two explaining the importance and relevance of the document. (Tie into the LCM training program?) Recommend that each document be labeled "mandatory format" or "recommended format," as appropriate.
8/3/2013, 6:26 PM
104
7/17/00
JTIC
Though many of the areas overlap, for consistency purposes it is recommended that the Test Plan (and Test Report if developed) formats follow those outlined in MIL-STD-498. It is well known that MIL-STD-498 was rescinded on May 27, 1998 and replaced with IEEE 12207. However, as a commercial standard, the IEEE series failed to address planning and reporting in any detail. Therefore the majority of the DoD test community decided to continue to recommend (not mandate) the use of the MIL-STD-498 formats for planning and reporting only. These formats are also recommended in the draft version of the DFAS 8000.1-R, Chapter 3 (Test and Evaluation), which is due to be released shortly.
Test Report not used - Testing Analysis Report used instead
8/3/2013, 6:26 PM
105
Date of Disposition 5/4/01
5/4/2001
2/28/01
2/28/01 2/28/01
5/4/01
5/4/01
5/4/01
5/4/01
5/4/2001
8/3/2013, 6:26 PM
106
2/28/01
2/28/01
2/28/01
5/4/01
2/28/01
8/3/2013, 6:26 PM
107
5/4/01
8/3/2013, 6:26 PM
108
8/3/2013, 6:26 PM
109
8/3/2013, 6:26 PM
110
8/3/2013, 6:26 PM
111
2/28/01
2/28/01
2/28/01
2/28/01
2/28/01
2/28/01
5/4/01
3/1/01
2/28/01
8/3/2013, 6:26 PM
112
2/28/01
5/4/2001
2/28/01
2/28/01
5/4/2001
8/3/2013, 6:26 PM
113
8/3/2013, 6:26 PM
114
Documentation Standards - Status
Interim
Comments Received
Final
Updated
7/1/2000
NO
2/28/2001
5/4/2001
7/1/2000
NO
2/28/2001
5/4/2001
7/1/2000
YES
2/28/2001
Application Release Checklist Baseline/Physical Configuration Audit Business Process Reengineering Report
#######
####### 5/4/01
CI Maintenance Form Clinger-Cohen Act Compliancy Report Command, Control, Communications, Computers, and Intelligence Support Plan
####### 2/28/01
2/28/01
Configuration Audit Report
#######
Configuration Management Plan
#######
Continuity of Operations Plan
#######
Course Evaluation
#######
115
#######
Database Design Description
#######
Decision Review Report
5/4/2001
Documented Risks
#######
Economic Analysis Functional Acquisition Requirements
7/1/2000 2/28/01
NO
2/28/2001
Functional Analysis Functional Configuration Audit Checklist Implementation Readiness Review/ Full Rate Production Decision Brief
####### 2/28/01
5/4/01
Individual Development Plan Infrastructure Requirements Description
####### 7/1/00 NO 2/28/01
Infrastructure Services Request
#######
#######
Installation Plan
#######
Interim Progress Review Brief
5/4/2001
116
Joint Technical Architecture Profile
#######
7/1/2000
NO
2/28/2001
5/4/2001
#######
YES
5/4/2001
#######
YES
5/4/2001
#######
YES
5/4/2001
MIPR
7/1/2000
NO
2/28/2001
Mission Need Statement
7/1/2000
NO
2/28/2001
5/4/2001
Operational Architecture Operational Requirements Document
####### 7/1/00 YES 2/28/01
Operator's Manual
#######
Product Delivery Plan
#######
Program Management Plan
7/1/2000
NO
2/28/2001
Program Manager's Charter
7/1/2000
NO
2/28/2001
#######
Program Trouble Report
#######
Project Staffing Profile
#######
117
Project Training Plan
#######
Ranked or Prioritized SCR List
#######
Release Guidance
#######
Release Instructions
#######
Release Package
#######
Requirements Definition
#######
Review Checklist
#######
Review Report
#######
Risk Management Plan
#######
Schedule
#######
Software Architecture Description Software Configuration Index Record
####### 2/28/01
Software Design Description
#######
Software Development Plan Software Interface Design Description
####### 2/28/01
118
Software Process Improvement Plan
#######
Software Requirements Description
7/1/2000
NO
2/28/2001
5/4/2001
SQA Report
#######
Statement of Work System Architecture and Requirements Allocation Description
####### 7/1/00 YES 2/28/01 5/4/01
System Change Request
#######
System Requirements Specification System Security Authorization Agreement
7/1/2000 7/1/00
YES NO
2/28/2001 2/28/01
5/4/2001
Technical Acquisition Requirements
#######
Technical Design
#######
7/1/2000
YES
2/28/2001
5/4/2001
7/1/2000
YES
2/28/2001
5/4/2001
Test Case
#######
Test Discrepancy Report
#######
Test Plan
7/1/2000
YES
2/28/2001
119
Testing Analysis Report
#######
Training Plan
#######
#######
Transition Plan
#######
Unjit Test Checklist
#######
User Advisory
#######
User's Manual
#######
120

Documentation Traceability Matrix

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Documentation Traceability Matrix

Transféré par

Droits d'auteur :

Formats disponibles

Life Cycle / SDS Documentation Standards

(SDS Release 3.2 (INTERIM))

Phase, Activity, Task Where Originated

Phase, Activity, Task Where Updated

Phase, Activity, Task Where Used

Acquisition Program Baseline

I, Program Planning/Management - Establish/Maintain Acquisition Program Baseline

II, Program Planning/Management - Update Program Documentation

I, Program Planning/Management - Determine Acquisition Strategy

II, Program Planning/Management - Update Program Documentation

Life Cycle / SDS Documentation Standards

Allocated Baseline (SAD, SIDD, DBDD, SDD)

II, Deployment Planning - Issue User Advisory

II, Configuration Management/Quality Assurance - Establish Application Allocated Baseline

II, Configuration Management/Quality Assurance - Manage Changes to Application Allocated Baseline

II, Configuration Management/Quality Assurance - Establish Corporate Allocated Baseline

II, Configuration Management/Quality Assurance - Manage Changes to Corporate Allocated Baseline

Analysis of Alternatives Report

I, Program Planning/Management - Analyze Acquisition and Implementation Alternatives

Application Release Checklist

Approved Changes to Business Data Model

III, Software Requirements Analysis - Approve Business Model Changes

Approved Changes to Business Function Model

III, Software Requirements Analysis - Approve Business Model Changes

Approved Changes to Business Process Model

II, Software Requirements Analysis - Approve Business Model Changes

Life Cycle / SDS Documentation Standards

Architecture Acquisition/ Installation Plan

I, System Architecture Design - Plan Execution Environment Changes

Architecture Improvement Proposals

III, Systems Management - Manage System Operations and Maintenance

Architecture Modeling Tools

I, System Architecture Design - Determine Execution Environment Solution

I, Program Planning/Management - Determine Program Management Plans

Automated Strategic Business Plan

I, II, Program Planning/Management - Estimate Life Cycle Resources

Available Functional Analysis Resources

III, Functional Analysis - Prepare Functional Analysis Schedule

Available Staff Hours by Individual

III, Technical Design - Build Software Development Plan

Available Technical Design Resources

III, Technical Design - Prepare Technical Design Schedule

Available Testing Resources

Life Cycle / SDS Documentation Standards

Baseline/Physical Configuration Audit Checklist Baseline

III, Development - Conduct Baseline Configuration Audit

Budget Preparation Guidance

I, Program Planning/Management - Develop Budget Submissions

Business Data Model

II, Software Requirements Analysis - Update Business Models

Business Function Model

II, Software Requirements Analysis - Update Business Models

Life Cycle / SDS Documentation Standards

Business Process Model

II, Software Requirements Analysis - Update Business Models

Business Process Reengineering Report

0, Business Process Review and Improvement - Review Current Business Process

Life Cycle / SDS Documentation Standards

Capacity Planning Tools

I, System Requirements Analysis - Determine Capacity Requirements

I, II, III, Program Planning/Management - Maintain Customer Relationship

III, Technical Design - Conduct Configuration Control Board Meeting

Chairman of Joint Chiefs of Staff Instruction (CJCSI) 3170.01B)

III, Technical Design - Maintain Configuration Items