Defense Finance and Accounting Service

1
Defense Finance and Accounting Service
System Acquisition through Milestone C
DFAS-DTC SLC Seminar 2002 2003
MSC-03-1
2
System Developmentand Demonstration

• System Integration
• Program Planning/Management
• Information Assurance/Security
• Technical Project Planning/Management
• System Development (Build or Purchase)
• Test Planning
• Configuration Management / Quality Assurance
• System Demonstration
• Program Planning/Management
• Information Assurance
• Deployment Planning
• Development Test Evaluation
• Operational Test Evaluation
• Milestone C Review

3
System Integration Leads to Interim Progress
Review (IPR)
MS B
System Integration
Interim Progress Review
Program Planning / Management
Program Planning / Management
Continuity of Operations Plan
APB(U)
Information Assurance/ Security
SSAA V2
Technical Project Planning / Management
Software Development Plan4
SW Process Improvement Plan4
System Development (Build or Purchase)

• Development IPT, or
• Purchase/Customize/Integrate Product(s)

Test Planning
QA Audit Reports
Test Plans
Configuration Management / Quality Assurance
SAD4 DBDD4 SDD4
SRD SIDD
Functional Baseline
Allocated Baseline
Release Review
4
System Integration

• Whats Done in this Phase
• Develop continuity of operations plan
• Update Acquisition Program Baseline (APB)
• Verify info assurance design against
  requirements
• (System Security Authorization Agreement)
• Develop and/or procure software product(s)
• Transform data
• Develop test plans
• Control Program Functional Baselines
• Concludes with
• Interim Progress Review

5
Program Planning/Management (1)

• Maintain Customer Relationship
• Establish Development Integrated Product Team
• Develop Continuity of Operations Plan
• Manage Program Acquisition (Update APB)
• Estimate Life Cycle Resources
• Determine Release Content
• Manage Program and Functional Baseline
• Perform Program Management Reviews
• Conduct Interim Progress Review

6
Information Assurance/Security (1)

• Conduct DITSCAP Phase 2, Verification

7
Technical Project Planning/Management

• Support Development Integrated Product Teams
• Coordinate Technical Integration
• Assess Technical Project Risks
• Manage Technology/Services Acquisition
• Manage Software Quality Assurance
• Ensure Configuration Management

repeated for each Release
8
System Development

• Develop OR Purchase/Customize/Integrate(Bu
  ild vs. Buy)

9
Develop
MS B
Interim Progress Review
System Integration
Development IPT
SW Reqts Desc.
Users Manual
SW Interface Design Desc.
Infra. Reqts Desc.
Operators Manual
DB Design Desc.
Test Scripts (I)
Unit Test Report
SW Design Desc
Applic. Release Checklist
SW Arch Description
SW Configuration Index Record
Allocated Baseline
SAD DBDD SDD
SRD SIDD
Functional Baseline
Release Review
IPR Presentation to CIO/BIE Council
Milestone B Presentation to CIO/BIE Council
10
Develop (1)

• Identify Integration Requirements
• Perform Release Impact Analysis
• Prepare Software Development Plan
• Develop Integrated Software Architecture
• Perform Application Development
• Produce Documentation
• Perform Development Cycle Review
• Prepare Application Release Checklist

More...
repeated for each Release
11
Develop (2)

• Obtain Implementation Approval
• Establish Allocated Baseline
• Conduct Release Review
• Perform SQA Audit of Product
• Perform SQA Review of Process

repeated for each Release
12
Purchase/Customize/Integrate
MS B
Interim Progress Review
System Integration
Purchase/Customize/Integrate Product(s)
SW Design Description
SW Interface Design Desc.
COTS Customization Plan
SW Configuration Index Record
SW Reqts Desc.
DB Design Desc.
Users Manual
SW Arch. Desc.
COTS Customized Product Description
Test Scripts (I)
Operators manual
applies to modifications only
Allocated Baseline
SAD3 DBDD3 SDD3
SRD SIDD
Functional Baseline
Release Review
IPR Presentation to CIO/BIE Council
Milestone B Presentation to CIO/BIE Council
13
Purchase/Customize/Integrate (1)

• Identify Integration Requirements
• Perform Release Impact Analysis
• Prepare Software Development Plan
• Develop Integrated Software Architecture
• Determine COTS Customization Requirements
• Determine COTS Modification Requirements
• Perform COTS Customization
• Modify COTS

More...
repeated for each Release
14
Purchase/Customize/Integrate (2)

• Produce Documentation
• Perform Development Cycle Review
• Prepare Application Release Checklist
• Obtain Implementation Approval
• Establish Allocated Baseline
• Conduct Release Review
• Perform SQA Audit of Product
• Perform SQA Review of Process

repeated for each Release
15
Test Planning

• Prepare Test Plans

repeated for each Release
16
Configuration Management/Quality Assurance

• Establish Allocated Baseline

repeated for each Release
17
Interim Progress Review
Pre-Systems
Concept Technology
Production and Deployment
System Development and Demonstration
Acquisition
Development
MS C
Interim Progress
MS B
MS A
Decision
FRP Decision
Review
Review
Review
Low-Rate
Concept
Technology Opportunities
Component Advanced
Full Rate Production
System Demonstration
System Integration
Initial
and User Needs
Exploration
Development
Deployment
Production
Development Test Evaluation
Requirements stability Cost/schedule
status Release strategy Test readiness Risk
management
Configuration Management / Quality Assurance
Allocated
Baseline
Release
PIR
IRR
Review
Milestone A
Decision Rev.
Milestone C
Milestone B
IPR
FRP
Presentation
Presentation
Presentation
Presentation
Presentation
Presentation
to CIO/BIE
to CIO/BIE
to CIO/BIE
to CIO/BIE
to CIO/BIE
to CIO/BIE
Council
Council
Council
Council
Council
Council
18
Interim Progress Review (1)

• Are requirements stable? Are changes controlled?
• Is the system architecture solid?
• Are performance measures used? Is performance on
  track?
• Are system interface agreements valid?
• Are original cost estimates still valid?
• Do actual expenditures track with estimates?
• Does actual schedule track with plan?
• Has release strategy changed (what capabilities
  to what customers in what time frames)?
• Is Program compliant with Clinger-Cohen Act?
• Is test strategy sound?

19
Interim Progress Review (2)

• Has transition to new business process system
  been planned?
• Has user training been planned and funded?
• Are risks anticipated and mitigation planning
  done?
• Are there any user or customer issues?
• What problems arose during procurement and/or
  development?
• Is all required documentation prepared and
  approved?
• Is Program ready for testing? (some IPRs serve as
  TRRs)

20
Interim Progress Review Conclusion

• MDA decides whether to
• Continue the project or program,
• Modify the project or program, or
• Terminate the project or program.
• MDA issues the System Decision Memorandum

21
System Demonstration Leads to Milestone C
MS C
Interim Progress Review
System Demonstration
Program Planning / Management
APB (F) Clinger-Cohen Compliance Report
Information Assurance/ Security
SSAA V3 Accred. Memo
Technical Project Planning / Management
Deployment Planning
Installation Plans
Transition Plans
Infrastructure Svcs Request (F)
Training Plans
Test Planning
Development Test Evaluation
Test Plans
Test Scripts (F) Test Discrepancy Reports Test
Reports Compliance Certifications
Operational Test Evaluation
FCA/PCA Checklists
Configuration Management / Quality Assurance
COTS Product Description Technical Documentation
Allocated Baseline
Product Baseline
FCA
PCA
22
System Demonstration

• Whats Done in this Phase
• Finalize the Acquisition Program Baseline (APB)
• Prepare Clinger-Cohen Compliance Report
• Control Program, Functional, and Allocated
  baselines
• Accredit system
• Plan deployment
• Perform DTE
• Plan OTE
• Perform Functional Configuration Audit
• Perform Physical Configuration Audit
• Concludes with
• Milestone C Review

23
Program Planning/Management (2)

• Maintain Customer Relationship
• Finalize Acquisition Program Baseline (APB)
• Prepare Clinger-Cohen Act Compliance Report
• Manage Program, Functional, and Allocated
  Baseline
• Perform Program Management Reviews
• Conduct Milestone C Review

24
Information Assurance/Security (2)

• Conduct DITSCAP Phase 3 Verification to include
  Accreditation Memo

25
Deployment Planning

• Establish Continuity of Operations Capability
• Establish Transition Strategy
• Prepare Product Delivery and Installation Plans
  
• Issue User Advisory
• Prepare User Training Plans
• Produce User Class Materials

repeated for each Release
26
Developmental Test and Evaluation

• Train Test Users
• Prepare Test Schedule
• Develop Test Scripts and Test Data
• Conduct Testing Peer Review
• Build Application Test Environment
• Conduct Test Readiness Review
• Perform Tests
• Approve and Certify Test Results

repeated for each Release
27
Operational Test and Evaluation

• Train Test Users
• Prepare Test Schedule
• Develop Test Scripts and Test Data
• Conduct Testing Peer Review
• Build Application Test Environment
• Conduct Test Readiness Review
• Perform Tests
• Approve and Certify Test Results

repeated for each Release
28
Configuration Management/Quality Assurance

• Establish Product Baseline

repeated for each Release
29
Milestone C
Pre-Systems
Concept Technology
Production and Deployment
System Development and Demonstration
Acquisition
Development
MS C
Interim Progress
MS B
MS A
Decision
FRP Decision
Review
Review
Review
Low-Rate
Concept
Technology Opportunities
Component Advanced
Full Rate Production
System Demonstration
System Integration
Initial
and User Needs
Exploration
Development
Deployment
Production
Measurements
Reqts design stability Transition deployment
planning Test certification completeness User
customer issues
PTR
IOC
FOC
Information Assurance/ Security
Milestone A
Decision Rev.
Milestone C
Milestone B
IPR
FRP
Presentation
Presentation
Presentation
Presentation
Presentation
Presentation
to CIO/BIE
to CIO/BIE
to CIO/BIE
to CIO/BIE
to CIO/BIE
to CIO/BIE
Council
Council
Council
Council
Council
Council
30
Milestone C Briefing
31
Milestone C (1)

• Are requirements stable? Are changes controlled?
• Is the system architecture solid?
• Are performance measures used? Is perf. on
  track?
• Are system interface agreements valid?
• Are approved cost estimates still valid?
• Do actual expenditures track with estimates?
• Does actual schedule track with plan?
• Has release strategy changed (what capabilities
  to what customers in what time frames)?
• Is Program compliant with Clinger-Cohen Act?
• Was development testing successful?

32
Milestone C (2)

• Has transition to new business process system
  been planned?
• Has user training been planned and funded?
• Are risks anticipated and mitigation planning
  done?
• Are there any user or customer issues?
• What problems arose during testing?
• Is all required documentation prepared and
  approved?
• Is Program ready for OTE? (some IPRs serve as
  TRRs)
• Has USD(C) approved system deployment??

33
Milestone C Conclusion

• MDA decides whether to
• Continue the project or program,
• Modify the project or program, or
• Terminate the project or program.
• MDA issues the System Decision Memorandum