2022 Early Hearing Detection & Intervention Virtual Conference
March 13 - 15, 2022
9/27/2017 | 1:05 PM - 1:50 PM | Owning the Technical Requirements Baseline using IBM DOORS | Track 2 - Systems Engineering
Owning the Technical Requirements Baseline using IBM DOORS
Abstract for Owning the Technical Requirements Baseline using IBM DOORS
In the Department of Defense, Owning the Technical Baseline is critical to implementing robust and rigorous systems engineering (SE) processes and delivering the needed capabilities to the warfighter. The technical baseline is defined as “Data and information that provides the program office knowledge to establish, trade-off, verify, change, accept, and sustain functional capabilities, design characteristics, affordability, schedule, and quantified performance parameters at the chosen level of the system hierarchy”. Owning the technical baseline requires that “Air Force program managers and personnel have sufficient technical knowledge of their engineering development programs to ensure program success by making informed, timely, and independent decisions to manage cost, schedule, and performance risk while ensuring disciplined program execution.”
When a government organization develops requirements that are included in a Request for Proposal (RFP), the selected offeror uses the government’s requirements (shall statements in the RFP) to develop their lower-level specifications. However, the government’s ability to effectively and efficiently trace and analyze the decomposition of their requirements is not easily accomplished. Consequently, the government cannot own the technical requirements baseline.
IBM’s requirements management product, Dynamic Object Oriented Requirements System (DOORS) can be used in lieu of requirements documents for government review and analysis of the derived requirements, but only if the DOORS project schema was properly constructed and linked. Reviewing requirements within DOORS significantly reduces the effort for the government’s analysis and the contractor’s efforts in preparing the submittal.
The MITRE Corporation has developed two approaches to use inherent capabilities of DOORS and associated contract language that will ensure a useful and productive DOORS schema that results in an effective requirements management process with submittals in a form the government can use to maintain the technical baseline.
These approaches have been successfully implemented on several Air Force programs and are currently being implemented on several more programs. The presentation will focus on the DOORS schema, using DOORS partitioning and archive/restore for integration between the government and development contractors, and the contracting language to support these approaches.
Distribution Statement A: Approved for public release; distribution is unlimited
Approved for Public Release; Distribution Unlimited. Case Number 17-1341
NOTICE
This technical data was produced for the U. S. Government
under Contract No. FA8702-17-C-0001, and is
subject to the Rights in Technical Data-Noncommercial
Items Clause DFARS 252.227-7013 (JUN 2013)
? 2017 The MITRE Corporation. All Rights Reserved.
Presentation:
This presentation has not yet been uploaded.
Handouts:
Handout is not Available
Transcripts:
CART transcripts are NOT YET available, but will be posted shortly after the conference
Presenters/Authors
William Fetech
(), The MITRE Corporation, wfetech@mitre.org;
Mr. William Fetech retired from the Air Force in 1998 and joined MITRE in 2003. He is a Lead Systems Engineer located in San Antonio where he provides systems engineering processes/tools implementation guidance to programs with sponsors from the Air Force, DoD, and Federal agencies.
He has over 30 year of experience in systems engineering and process/tool standardization and implementation. He has implemented IBM’s DOORS product on multiple programs over the past 7 years. In addition, Bill has provided DOORS training at MITRE. In 2011 and in 2014, Bill provided presentations at the IBM – Rational Users Conference.
ASHA DISCLOSURE:
Financial -
Nonfinancial -