system engineering documentation presentation for incose orlando chapter meeting on 17 sep 09 dave...
TRANSCRIPT
System Engineering DocumentationPresentation for
INCOSE Orlando Chapter Meeting on 17 Sep 09
Dave Krigelman, President Krigelman and Associates, Inc
813 Cebu PlaceMelbourne, FL 32940
Voice/Fax: (321)242-7598Mobile: (321)544-1862
E-mail: [email protected]
LSI TECHNICAL AND MANAGEMENT
INTERFACE
PROGRAM ORGANIZATION CHART
CHIEF ENGINEER/SYSTEM ENGINEER
VMRE IPT LEAD
INTEG VERIF & TEST LEAD
SW DEVEL LEAD
HW ENG LEAD
PROGRAM MANAGER
PM OFFICE:• PROGRAM CONTROL• CONFIG & DATA MGMT• FINANCE & CONTRACTS
OPERATIONS:• SUBCONTRACTS• PURCHASING• MANUFACTURING• QA/QC & TEST• LOGISTICS SUPPORT
TECHNICAL AND MANAGEMENT
ADVISORS
AAR IPT LEAD
INTEGLOGISTICS
LEAD
SUBJECT MATTER/DOMAIN
EXPERTS
PROGRAM MANAGEMENT PROCESS FLOW
CONTRACTTECHNICAL AND
MANGEMENT REQUIREMENTS
PROGRAM DIRECTIVES
PROGRAM TEAM ORGANIZATION
PROGRAM MANAGEMENT
PLAN
POLICIES, INSTRUCTIONS,
AND OPERATING PROCEDURES
WORKING LEVEL INTEGRATION
DAILY STAND-UP MEETINGS
WEEKLY PROGRAM MEETINGS
MONTHLY MANAGEMENT REVIEWS
STATUS/PROBLEM CORRECTIVE ACTION IDENTIFICATION AND RESOLUTION
ACTION ITEM LIST ACTION ITEM FOLLOW-UP ACTION ITEM CLOSEOUT
PROGRAM TEAM INTEGRATION,
MONITORING, AND CONTROL
SYSTEM ENGINEERING PROCESS FLOW
System Analysis and Control
(Balance)
Process Input
Process Output
Requirements Loop
Design Loop
System Level Tradeoffs
Equipment Level
TradeoffsModeling
Simulation
TestingVerification
Reference: MIL-HDBK-502, Acquisition Logistics
The Analysis Loop and the Synthesis (Design) Loop are Key Elements of the System Engineering Process.
The Analysis Loop and the Synthesis (Design) Loop are Key Elements of the System Engineering Process.
Requirements Analysis
Functional Analysis/Allocation
Synthesis
Introduction
• The objective of this presentation is to review the purpose and scope of SE documents prepared on a program.
• SE documents that will be discussed include the following:– System Documentation Tree– System Engineering Management Plan (SEMP)– Integrated Master Plan (IMP)– Integrated Master Schedule (IMS)– System Performance Specification (PS)– System Design Description (SDD)– System Interface Specification (IS)– Interface Design Description (IDD)– Requirements Traceability Matrix (RTM)– Requirements Verification Matrix (RVM)– Detail Specifications (DS)– Software Documents– System Integration Documents– System Verification Documents– System Test Documents– System Support Documents
System Documentation Tree
• The System Documentation Tree describes:– the program-required System Engineering (SE)–oriented
documents and – their relationships in a top-down structured format.
• The tree is prepared by the System Engineer during the proposal phase based on the Statement of Work (SOW) and Contract Data Requirements List (CDRL) in order to identify required documentation tasks for subsequent costing and scheduling.
• It should be approved by the Program Manager (PM) and maintained current for the life of the program.
SYSTEM PERFORMANCE SPECIFICATION
SYSTEM ENGINEERING
MANAGEMENT PLAN
REQUIREMENTS TRACEABILTY
MATRIX
SYSTEM DESIGN DESCRIPTION
SYSTEM INTERFACE
SPECIFICATION
INTERFACE DESIGN
DESCRIPTIONINTEGRATED MASTER PLAN
REQUIREMENTS VERIFICATION
MATRIX
DETAIL (HW) SPECIFICATIONS
SOFTWARE DOCUMENTS
SYSTEM INTEGRATION DOCUMENTS
SYSTEM VERIFICATION DOCUMENTS
SYSTEM TEST DOCUMENTS
SYSTEM SUPPORT DOCUMENTS
INTEGRATED MASTER
SCHEDULE
SYSTEM DOCUMENTATION TREE
CONTRACT DATA REQUIREMENTS
LIST
CONTRACT PERFORMANCE
WORK STATEMENT
SYSTEM REQUIREMENTS
DOCUMENT
System Engineering Management Plan (SEMP)
• The System Engineering Management Plan (SEMP) describes:– the program SE task and schedule requirements and – how they will be managed and implemented.
• The plan is prepared by the System Engineer based on the SOW and CDRL during the proposal to describe the SE process and how the SE requirements will be planned, organized, integrated, monitored, controlled, and measured.
• It should be approved by the PM and maintained current for the life of the program.
SYSTEM ENGINEERING MANAGEMENT PLAN IAW DI-MGMT-81024
PART I – SYSTEM ENGINEERINGa.FUNCTIONAL ALLOCATIONb.TRADE STUDIESc.DESIGN OPTIMIZATION AND EFFECTIVE ANALYSISd.SYNTHESISe.TECHNICAL INTERFACE COMPATIBILITYf.LOGISTIC SUPPORT ANALYSISg.PRODUCIBILITY ANALYSISh.TRAINING PROGRAMS FOR USERSi.REQUIREMENTS ALLOCATIONj.GENERATION OF SPECIFICATIONSk.OTHER SYSTEM ENGINEERING TASKS
PART II – TECHNICAL PROGRAM PLANNING AND CONTROL
a. PROGRAM RISK ANALYSISb. ENGINEERING PROGRAM INTEGRATIONc. CONTRACT WORK BREAKDOWN
STRUCTURE AND SPECIFICATION TREEd. ASSIGNMENT OF RESPONSIBILITY AND
AUTHORITYe. PROGRAM REVIEWSf. DESIGN REVIEWSg. INTERFACE CONTROLh. DOCUMENTATION CONTROLi. ENGINEERING TESTINGj. TRADEOFF STUDIESk. TECHNICAL PERFORMANCE
MEASUREMENTl. OTHER TECHNICAL PROGRAM TASKSPART III – ENGINEERING INTEGRATION
Integrated Master Plan (IMP)
• The Integrated Master Plan (IMP) describes the program major milestones, the entrance criteria for each milestone, and the exit criteria for each milestone.– Entrance criteria are those requirements that must be
met prior to initiation of the milestone.– Exit criteria are those requirements that must be met
upon completion of the milestone.• The IMP is prepared by the Program Manager during the
proposal based on inputs from the SE and others in accordance with the CDRL.
IMP ITEMNO.
ENTRANCE CRITERIA FOR EACH MILESTONE
MILESTONE EVENT/ACCOMPLISHMENT
EXIT CRITERIA FOR EACH MILESTONE
WBS ITEM NO.SDRL DATA
ITEM NO.1. Meeting agenda and
data package submitted on time to the LSI.
Kickoff meeting complete Presentation, meeting minutes, and action items approved by the LSI.
3.3.1
2. Meeting agenda and data package submitted on time to the LSI.
AAR System Requirements Review (SRR) complete
Presentation, meeting minutes, and action items approved by the LSI.
3.3.1
3. Meeting agenda and data package submitted on time to the LSI.
VMRE System Requirements Review (SRR) complete
Presentation, meeting minutes, and action items approved by the LSI.
3.3.1
4. Meeting agenda and data package submitted on time to the LSI.
Initial baseline review complete
Presentation, meeting minutes, and action items approved by the LSI.
3.3.1
4.1 Data item submitted on time IAW the SDRL.
Monthly AAR TCG and VMRE TCG program cost reports complete
SDRL data item approved by the LSI.
3.3.1 SA007
4.2 Data item submitted on time IAW the SDRL.
Quarterly Contract Funds Status Report (CFSR) complete
SDRL data item approved by the LSI.
3.3.1 SA020
5. Meeting agenda and data package submitted on time to the LSI.
AAR TCG System Design Review (SDR) complete
Presentation, meeting minutes, and action items approved by the LSI.
3.3.1
5.1 Baseline system design recommended to the LSI.
AAR TCG system design complete
System design baseline approved by the LSI.
3.3.1.1
5.2 Data item submitted on time IAW the SDRL.
AAR TCG preliminary Requirements Traceability Matrix (RTM) complete
SDRL data item approved by the LSI.
3.3.2.1.1 SA001A
5.3 Data item submitted on time IAW the SDRL.
AAR TCG preliminary subsystem specification complete
SDRL data item approved by the LSI.
3.3.2.1.2 SA002A
INTEGRATED MASTER PLAN
Integrated Master Schedule (IMS)
• The Integrated Master Schedule (IMS) describes:– the responsible organization and/or individual,– start dates, durations, stop dates, and – network interdependencies for each task listed on the
Work Breakdown Structure (WBS).• The IMS is prepared by the Program Manager during the
proposal based on inputs from the SE and others in accordance with the CDRL.
INTEGRATED MASTER SCHEDULE IAW DI-MGMT-81650
ID Task Name Duration Start Finish
1 Develop Project Specification 14 wks Fri 4/4/08 Thu 7/10/08
2 Selection of EPC Contractor 12 wks Thu 7/10/08 Wed 10/1/08
3 Funding Awarded 1 day Wed 10/1/08 Wed 10/1/08
4 Phase 1: Project Preliminary Design 120 days Wed 10/1/08 Tue 3/17/09
5 Front End Engineering 120 days Wed 10/1/08 Tue 3/17/09
6 Basic Plant Design 12 wks Wed 10/1/08 Tue 12/23/08
7 Procurement of long lead time items 12 wks Wed 12/24/08 Tue 3/17/09
8
9 Environmental/Construction Permitting 40 wks Fri 12/26/08 Thu 10/1/09
10
11 Phase 2: Detailed Design and Construction 538 days Fri 1/9/09 Tue 2/1/11
12 Detailed Engineering 38 wks Fri 1/9/09 Thu 10/1/09
13 Procurement 38 wks Fri 1/9/09 Thu 10/1/09
14 Permit Approvals 1 day Thu 10/1/09 Thu 10/1/09
15 Construction 52 wks Fri 10/2/09 Thu 9/30/10
16 Mechanical Completion 1 day Mon 10/4/10 Mon 10/4/10
17 Commissioning & Start-up Tests 16 wks Tue 10/5/10 Mon 1/24/11
18 Commercial Operation Date 1 day Tue 2/1/11 Tue 2/1/11
10/1
10/4
2/1
Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 22008 2009 2010 2011 2012
ID Task Name
1 FCEC Available for Commerical Operation
2 Siemens - Development and Basic Design
3 Design and Testing of Technologies/Concepts
4 Selection of Go Forw ard technologies
5 Continued Design/Testing of Selected technologies
6
7 Siemens - Introduction for Commerical Use
8 Validation/support of technolgies for commercial use
9 Florida Executive Order 07-127 - emissions to 2000 levels by 2017
2/1
11/2
1/2
2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020
System Performance Specification (PS)
• The System Performance Specification describes:– the system functional performance, – design and construction constraints, – external and internal interfaces, – environmental design criteria, – physical requirements, and – their allocation to lower levels of design.
• The specification is prepared by the System Engineer prior to the System Requirements Review (SRR) and the System Design Review (SDR) in accordance with the CDRL based on the System Requirements Document (SRD), the System Requirements Analysis (SRA), and trade-off study reports.
SYSTEM PERFORMANCE SPECIFICATION IAW DI-SDMP-81465A/MIL-STD-961E
1. SCOPE2. APPLICABLE DOCUMENTS3. REQUIREMENTS3.1MISSIONS3.2 THREAT3.3REQUIRED STATES AND MODES3.4ENTITY CAPABILITY REQUIREMENTS3.5RELIABILITY3.6MAINTAINABILITY3.7DEPLOYABILITY3.8AVAILABILITY3.9ENVIRONMENTAL CONDITIONS3.10 TRANSPORTABILITY3.11 MATERIALS AND PROCESSES3.12 ELECTROMAGNETIC RADIATION3.13 NAMEPLATES OR PRODUCT MARKINGS3.14 PRODUCIBILITY3.15 INTERCHANGEABILITY3.16 SAFETY3.17 HUMAN FACTORS ENGINEERING
3.18 SECURITY AND PRIVACY3.19 COMPUTER RESOURCE REQUIREMENTS3.20 LOGISTICS3.21 INTERFACE REQUIREMENTS3.22 COMPUTER HARDWARE REQUIREMENTS3.23 COMPUTER COMMUNICATIONS
REQUIREMENTS3.24 COMPUTER SOFTWARE REQUIREMENTS3.25 CSCI INTERNAL INTERFACES3.26 CSCI INTERNAL DATA REQUIREMENTS3.27 DESIGN AND CONSTRUCTION3.28 SOFTWARE DESIGN3.29 WORKMANSHIP3.30 PRODUCT CHARACTERISTICS3.31 CHEMICAL, ELECTRICAL AND
MECHANICAL PROPERTIES3.32 STABILITY4. VERIFICATION5. PACKAGING 6. NOTES
System Design Description (SDD)
• The System Design Description (SDD) describes:– the system hardware and software configuration and – the degree to which the requirements described in the
System Performance Specification have been met.• The document is prepared by the System Engineer prior to
the Preliminary Design Review (PDR) and the Critical Design Review (CDR) in accordance with the CDRL based on inputs from the hardware engineers and software developers.
SYSTEM DESIGN DESCRIPTION IAW DI-IPSC-81432A
1. SCOPE1.1 IDENTIFICATION1.2 SYSTEM OVERVIEW1.3 DOCUMENT OVERVIEW2. REFERENCED DOCUMENTS3. SYSTEM-WIDE DESIGN DECISIONS4. SYSTEM ARCHITECTURAL DESIGN4.1 SYSTEM COMPONENTS4.2 CONCEPT OF EXECUTION4.3 INTERFACE DESIGN4.3.1 INTERFACE IDENTIFICATION AND
DIAGRAMS4.3.2 (PROJECT-UNIQUE IDENTIFIER OF
INTERFACE)5. REQUIREMENTS TRACEABILITY6. NOTESA. APPENDICES
System Interface Specification (IS)
• The System Interface Specification describes:– the system external interface allocation and internal
interfaces at lower levels of design.– Interfaces may be hardware-to-hardware, hardware-to-
software, software-to-hardware, and software-to-software.
• The specification is prepared by the System Engineer prior to the SRR and the SDR in accordance with the CDRL based on the System Requirements Document (SRD), the System Requirements Analysis (SRA), and trade-off studies.
SYSTEM INTERFACE SPECIFICATION IAW DI-SESS-81632
1. INTRODUCTION1.1 OVERVIEW1.2 RELATED DOCUMENTS AND DATA1.3 INTERFACE SCOPE1.3.1 SYSTEM SUMMARY1.3.2 INTERFACE BOUNDARIES1.3.3 LAYERED INTERFACE DEFINITION (LID)1.3.4 CONFIGURATION ITEM (CI) RELATIONSHIPS1.4 SECURITY2. REFERENCED DOCUMENTS2.1 GOVERNMENT DOCUMENTS2.2 NON-GOVERNMENT DOCUMENTS3. INTERFACE REQUIREMENTS AND DESIGN3.1 INFO INTERFACES (CHARACTERISTICS REQUIRED TO
TRANSFER INFORMATION ELECTRONICALLY)3.2 NON-INFO INTERFACES (CHARACTERISTICS NECESSARY TO
SUPPORT THE INFORMATION TRANSFER)4. QUALITY ASSURANCE PROVISIONS4.1 SUMMARY4.2 VERIFICATION CROSS-REFERENCE MATRIX (VCRM)5. NOTES5.1 DEFINITIONS AND ACRONYMS/ABBREVIATIONS5.1.1 DEFINITIONS5.1.2 ACRONYMS/ABBREVIATIONS5.2 TUTORIALS AND EXPLANATIONSA. APPENDICESB. APPENDIX-REQUIREMENTS TRACEABILITY MATRIX (RTM)
Interface Design Description (IDD)
• The Interface Design Description (IDD) describes:– the system hardware and software interfaces and – the degree to which the requirements described in the
System Interface Specification have been met.• The document is prepared by the System Engineer prior to
the PDR and the CDR in accordance with the CDRL based on inputs from the hardware engineers and software developers.
INTERFACE DESIGN DESCRIPTION IAW DI-IPSC-81436A
1. SCOPE1.1 IDENTIFICATION1.2 SYSTEM OVERVIEW1.3 DOCUMENT OVERVIEW2. REFERENCED DOCUMENTS3. INTERFACE DESIGN3.1 INTERFACE IDENTIFICATION AND
DIAGRAMS3.2 (PROJECT-UNIQUE IDENTIFIER OF
INTERFACE)3.3 ETC.3.4 ETC.3.5 ETC.4. REQUIREMENTS TRACEABILITY5. NOTESA. APPENDICES
Requirements Traceability Matrix (RTM)
• The Requirements Traceability Matrix (RTM) describes:– the allocation of system requirements to lower levels
within the system, including hardware and software. – Normally, it is prepared as a stand-alone document or as
part of the System Performance Specification.– The RTM should be prepared bi-directional, which shows
“from-to” traceability as well as “to-from” traceability.• The matrix is prepared by the System Engineer in accordance
with the CDRL prior to the SRR and the SDR based on the System Requirements Document (SRD), the System Requirements Analysis (SRA), and trade-off study reports.
ID Object Number
Requirement Text Type TCG_Acq
NTCOIS5 3 REQUIREMENTS N/A
NTCOIS1297 3.2 NTC-OIS Performance Requirements N/A
NTCOIS1298 3.2.1 General N/A
NTCOIS1317 3.2.1.0-18 The NTC-OIS shall collect both "Ground" truth and "Player" truth Training Performance Data.
Spec Digital Tact MonitoringVideo Mon, Rec, EditVoice Tact MonitoringPortable Comp ResourcesWeather
NTCOIS1468 3.2.1.0-18.0-2 Video Monitoring, Recording, Editing shall monitor and record selected areas of the battlefield.
Derived Video Mon, Rec, Edit
NTCOIS1321 3.2.1.0-22 The NTC-OIS shall provide the NTC O/C-TAF team with Player truth and Ground truth to include OPFOR data as required to support EXCON and Training Feedback.
Spec Video Mon, Rec, EditSys Comp ResourcesPortable Comp Resources
NTCOIS1479 3.2.1.0-22.0-1 Video Monitoring, Recording, and Editing shall provide tools to play back video.
Derived Video Mon, Rec, Edit
NTCOIS1331 3.2.3 AAR Theaters N/A
NTCOIS1334 3.2.3.0-3 The NTC-OIS shall provide all equipment required to capture and record NTC AARs to include Theater, Mobile, and Field AARs.
Spec AAR TheatersVideo Mon, Rec, Edit
NTCOIS1510 3.2.3.0-3.0-2 Video Monitoring, Recording, and Editing shall provide all equipment required to capture and record Field AARs.
Derived Video Mon, Rec, Edit
NTCOIS1353 3.2.6 Digital Video and Audio N/A
NTCOIS1354 3.2.6.0-1 The NTC-OIS shall provide the digital video and audio capabilities for NTC Mobile Video Units.
Spec Video Mon, Rec, Edit
NTCOIS2894 3.2.6.0-1.0-1 The Video Monitoring, Recording and Editing Subsystem shall provide the digital video and audio capabilities for NTC Mobile Video Units.
Derived Video Mon, Rec, Edit
REQUIREMENTS TRACEABILITY MATRIX
Requirements Verification Matrix (RVM)
• The Requirements Verification Matrix describes: – how the requirements within Section 3 of a
specification are verified by the means described in Section 4.
– Normally, it is prepared as part of the specification to which it applies.
– The verification may include the methods of analysis, demonstration, inspection, and test.
• The matrix is prepared by the System Engineer or Responsible Design Engineer in accordance with the CDRL prior to SRR and the SDR based on information in the system and lower-tier specifications.
ID Object Number Requirement Text Type TCG_Acq Verification MethodNTCOIS5 3 REQUIREMENTS N/A
NTCOIS1297 3.2 NTC-OIS Performance Requirements N/A
NTCOIS1298 3.2.1 General N/A
NTCOIS1315 3.2.1.0-16 The NTC-OIS shall be able to produce THPs that contain multimedia AARs and training performance data and feedback as provided by NTC to the rotational unit.
Spec AAR TheatersSys Comp Resources
Demonstration
NTCOIS1461 3.2.1.0-16.0-2 The AAR Theaters shall provide resources to record AARs.
Derived AAR Theaters Demonstration
NTCOIS1331 3.2.3 AAR Theaters N/A
NTCOIS1332 3.2.3.0-1 The NTC-OIS shall be capable of supporting simultaneous Theater, Mobile, and field AARs, as required to support NTC scenario OPTEMPO.
Spec AAR TheatersCC TV SystemComms - ArchSys Comp ResourcesPortable Comp Resources
AnalysisDemonstration
NTCOIS1502 3.2.3.0-1.0-1 The AAR Theaters shall provide the peripherals to present simultaneous Fixed, Mobile, and field AARs, as required to support NTC scenario OPTEMPO.
Derived AAR Theaters AnalysisDemonstration
NTCOIS1333 3.2.3.0-2 The NTC-OIS shall consist of a minimum of 4 fixed site AAR theaters and 4 overflow theaters.
Spec AAR TheatersCC TV System
Inspection
NTCOIS1507 3.2.3.0-2.0-1 AAR Theaters shall provide a minimum of 2 fixed site AAR theaters at IOC.
Derived AAR Theaters Inspection
NTCOIS1334 3.2.3.0-3 The NTC-OIS shall provide all equipment required to capture and record NTC AARs to include Theater, Mobile, and Field AARs.
Spec AAR TheatersVideo Mon, Rec, Edit
Inspection
NTCOIS1509 3.2.3.0-3.0-1 AAR Theaters shall provide all equipment required to capture and record NTC AARs to include Fixed and Mobile AARs.
Derived AAR Theaters Inspection
REQUIREMENTS VERIFICATION MATRIX
Detail Specifications (DS)
• Item Detail Specifications describe:– the requirements that have been allocated from a System
Performance Specification. – These may include functional performance, design and
construction constraints, external and internal interfaces, environmental design criteria, and physical requirements.
• The specification is prepared by the Responsible Design Engineer prior to the PDR and the CDR based on the System Performance Specification, the System Requirements Analysis (SRA), and trade-off studies.
DETAIL SPECIFICATION IAW DI-SDMP-81464A/MIL-STD-961E
1. SCOPE2. APPLICABLE DOCUMENTS3. REQUIREMENTS3.1 MISSIONS3.2 THREAT3.3 REQUIRED STATES AND MODES3.4 ENTITY CAPABILITY REQUIREMENTS3.5 RELIABILITY3.6 MAINTAINABILITY3.7 DEPLOYABILITY3.8 AVAILABILITY3.9 ENVIRONMENTAL CONDITIONS3.10 TRANSPORTABILITY3.11 MATERIALS AND PROCESSES3.12 ELECTROMAGNETIC RADIATION3.13 NAMEPLATES OR PRODUCT MARKINGS3.14 PRODUCIBILITY3.15 INTERCHANGEABILITY3.16 SAFETY3.17 HUMAN FACTORS ENGINEERING3.18 SECURITY AND PRIVACY3.19 COMPUTER RESOURCE REQUIREMENTS3.20 LOGISTICS3.21 INTERFACE REQUIREMENTS3.22 COMPUTER HARDWARE REQUIREMENTS3.23 COMPUTER COMMUNICATIONS REQUIREMENTS3.24 COMPUTER SOFTWARE REQUIREMENTS3.25 CSCI INTERNAL INTERFACES3.26 CSCI INTERNAL DATA REQUIREMENTS3.27 DESIGN AND CONSTRUCTION3.28 SOFTWARE DESIGN3.29 WORKMANSHIP3.30 PRODUCT CHARACTERISTICS3.31 CHEMICAL, ELECTRICAL AND MECHANICAL PROPERTIES3.32 STABILITY4. VERIFICATION5. PACKAGING 6. NOTES
SELECT, AS APPLICABLE
Software Documents
• Software Documents include plans, specifications, and description documents described as follows:– The Software Development Plan (SDP) describes the requirements for software
development and how they will be implemented.– The Software Requirements Specification (SRS) describes the software technical
performance requirements derived from the System Performance Specification.– The Interface Requirements Specification (IRS) describes the software technical
interface requirements derived from the System Performance Specification.– The Software Design Description (SDD) describes the degree to which the SRS
requirements have been met.– The Interface Design Description (IDD) describes the degree to which the IRS
requirements have been met.• The documents are prepared by the organization and/or lead individual that is
responsible for software development in accordance with the CDRL.
SOFTWARE DEVELOPMENT PLAN IAW DI-IPSC-81427ASOFTWARE REQUIREMENTS SPECIFICATION IAW DI-IPSC-81433AINTERFACE REQUIREMENTS SPECIFICATION IAW DI-IPSC-81434A
SOFTWARE DESIGN DESCRIPTION IAW DI-IPSC-81435AINTERFACE DESIGN DESCRIPTION IAW DI-IPSC-81436A
SOFTWARE REQUIREMENTSSPECIFICATION
REQUIREMENTS TRACEABILTY
MATRIX
SOFTWARE DESIGN
DESCRIPTION
INTERFACE REQUIREMENTS SPECIFICATION
INTERFACE DESIGN
DESCRIPTION
REQUIREMENTS VERIFICATION
MATRIX
DETAIL (SW) SPECIFICATIONS
CONTRACT DATA REQUIREMENTS
LIST
CONTRACT PERFORMANCE
WORK STATEMENT
SYSTEM PERFORMANCE SPECIFICATION/
SYSTEM INTERFACE SPECIFICATION
SOFTWARE DEVELOPMENT
PLAN
INTEGRATED MASTER PLAN
INTEGRATED MASTER
SCHEDULE
SOFTWARE INTEGRATION DOCUMENTS
SOFTWARE VERIFICATION DOCUMENTS
SOFTWARE TEST DOCUMENTS
SOFTWARE SUPPORT
DOCUMENTS
System Integration Documents
• System Integration Documents include plans, procedures, and reports described as follows:– The System Integration Plan describes the requirements for
integrating the system during development. These may include the following levels of integration: hardware-to-hardware, hardware-to-software, software-to-hardware, and software-to-software.
– The System Integration Procedures describe how the requirements of the plan will be implemented.
– The System Integration Report describes the results of the integration that has been performed.
• The documents are prepared by the organization and/or lead individual that is responsible for integration in accordance with the CDRL.
SYSTEM INTEGRATION PLANSYSTEM INTEGRATION PROCEDURES
SYSTEM INTEGRATION REPORT
SYSTEM INTEGRATION PLAN1. SCOPE2. APPLICABLE DOCUMENTS3. REQUIREMENTS3.1 FLOW DIAGRAM3.2 SCHEDULE4. MANAGEMENT4.1 PLANNING4.2 ORGANIZATION4.3 MONITOR AND CONTROL4.4 REPORTING5. INTEGRATION PLANS5.1 HW TO HW PLANS5.2 HW TO SW PLANS5.3 SW TO HW PLANS5.4 SW TO SW PLANS
SYSTEM INTEGRATION PROCEDURES
1. INTEGRATION PROCEDURES1.1 HW TO HW PROCEDURES1.2 HW TO SW PROCEDURES1.3 SW TO HW PROCEDURES1.4 SW TO SW PROCEDURES
SYSTEM INTEGRATION REPORT
1. SCOPE2. APPLICABLE DOCUMENTS3. REQUIREMENTS4. MANAGEMENT5. INTEGRATION REPORTS5.1 HW TO HW REPORTS5.2 HW TO SW REPORTS5.3 SW TO HW REPORTS5.4 SW TO SW REPORTS
System Verification Documents
• System Verification Documents include plans, procedures, and reports described as follows:– The System Verification Plan describes the requirements
for verifying the system have been met. These may include verification by analysis, demonstration, examination, and test at various stages of the program.
– The System Verification Procedures describe how the requirements of the plan will be implemented.
– The System Verification Report describes the results of the verification that has been performed.
• The documents are prepared by the organization and/or lead individual that is responsible for verification in accordance with the CDRL.
SYSTEM VERIFICATION PLANSYSTEM VERIFICATION PROCEDURES
SYSTEM VERIFICATION REPORT
SYSTEM VERIFICATION PLAN1. SCOPE2. APPLICABLE DOCUMENTS3. REQUIREMENTS3.1 FLOW DIAGRAM3.2 SCHEDULE4. MANAGEMENT4.1 PLANNING4.2 ORGANIZATION4.3 MONITOR AND CONTROL4.4 REPORTING5. VERIFICATION PLANS5.1 ANALYSIS PLANS5.2 DEMONSTRATION PLANS5.3 EXAMINATION PLANS5.4 TEST PLANS
SYSTEM VERIFICATION PROCEDURES1. VERIFICATION PROCEDURES1.1 ANALYSIS PROCEDURES1.2 DEMONSTRATION PROCEDURES1.3 EXAMINATION PROCEDURES1.4 TEST PROCEDURES
SYSTEM VERIFICATION REPORT1. SCOPE2. APPLICABLE DOCUMENTS3. REQUIREMENTS4. MANAGEMENT5. VERIFICATION REPORTS5.1 ANALYSIS REPORTS5.2 DEMONSTRATION REPORTS5.3 EXAMINATION REPORTS5.4 TEST REPORTS
System Test Documents
• System Test Documents include plans, procedures, and reports described as follows:– The System Test Plan describes the requirements for testing
the system. These may include development , qualification, and acceptance tests at various stages of the program.
– The System Test Procedures describe how the requirements of the plan will be implemented.
– The System Test Report describes the results of the testing that has been performed.
• The documents are prepared by the organization and/or lead individual that is responsible for testing in accordance with the CDRL.
SYSTEM TEST PLAN AND PROCEDURES IAW DI-SESS-81704SYSTEM TEST REPORT IAW MIL-HDBK-831
SYSTEM TEST PLAN AND PROCEDURES1. TEST OBJECTIVES2. TEST ITEM CONFIGURATION AND SUCCESS CRITERIA3. MISSION PROFILES4. TEST SCHEDULES5. INSTRUMENTATION REQUIREMENTS AND CALIBRATION INSTRUCTIONS6. DATA PROCESSING AND REPORTING PROCEDURES7. INTERFACE IDENTIFICATIONS8. SAFETY9. FLOW DIAGRAM10. TEST SUPPORT REQUIREMENTS10.1 TEST LOGISTICS10.2 PERSONNEL PLANNING INFORMATION10.3 PERSONNEL SUPPORT REQUIREMENTS10.4 TEST INFORMATION SHEETS (TIS)10.4.1 PLANNING INFORMATION10.4.2 PROCEDURAL INFORMATION10.4.3 TIS SUMMARY
SYSTEM TEST REPORT1. SUMMARY2. REASON FOR THE TEST3. DESCRIPTION OF TEST SAMPLES4. DISPOSITION OF TEST SAMPLES5. NARRATIVE ABSTRACT, CONCLUSIONS AND RECOMMENDATIONS6. REFERENCES7. FACTUAL DATA7.1 DESCRIPTION OF TEST 7.2 APPARATUS7.3 TEST PROCEDURE7.4 RESULTS OF TEST, SUMMATIONS AND ANALYSIS7.5 TEST DATAA. APPENDICES
System Support Documents
• System Support Documents include:– Configuration and Data Management (C&DM), Quality
Assurance (QA), and Integrated Logistic Support (ILS) plans, procedures, and reports, which describe the requirements in the SOW and how they will be implemented.
• The documents are prepared and maintained by the organizations and/or lead individuals that are responsible for C&DM, QA, and ILS in accordance with the CDRL.
SYSTEM SUPPORT PLANSSYSTEM SUPPORT PROCEDURES
SYSTEM SUPPORT REPORTSIAW THE STATEMENT OF WORK AND THE CDRL/DIDs
SYSTEM SUPPORT PLANS
•CONFIGURATION MANAGEMENT PLAN•DATA MANAGEMENT PLAN•QUALITY ASSURANCE PLAN•INTEGRATED LOGISTIC SUPPORT PLAN
SYSTEM SUPPORT PROCEDURES•CONFIGURATION MANAGEMENT PROCEDURES•DATA MANAGEMENT PROCEDURES•QUALITY ASSURANCE PROCEDURES•INTEGRATED LOGISTIC SUPPORT PROCEDURES
SYSTEM SUPPORT REPORTS•CONFIGURATION MANAGEMENT REPORTS•DATA MANAGEMENT REPORTS•QUALITY ASSURANCE REPORTS•INTEGRATED LOGISTIC SUPPORT REPORTS
Questions?