Premium
7.3. Crusader System Engineering Tool Set Continuous Improvement Process
Author(s) -
Eidenschink Bruce,
KeeBowling Bonnie,
Laedtke Patricia,
Sanyal Saumya,
Schweikert Tim,
Zimmermann Roger
Publication year - 1998
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1998.tb00116.x
Subject(s) - suite , process (computing) , traceability , systems engineering , software engineering , set (abstract data type) , computer science , systems development life cycle , process management , engineering , engineering management , software development process , software development , software , operating system , archaeology , history , programming language
Implementation of system engineering tools on large scale development programs require mechanisms that allow for the continued evolution of the selected suite. The initial requirements for a system engineering tool selection will change and evolve as in any system. A program will have changing objectives, champions, and organizations as it progresses through its life cycle. Awareness and use of accepted industry practices for improvement to this type of system have proven vital to its evolution. This paper presents the process and techniques used for evolving one such tool suite within an Integrated Product Development (IPD) organization on Crusader, a major Department of Defense (DOD) development program. This paper documents 4 years of lessons learned during the support, maintenance, and evolution of the Crusader System Engineering (SE) Computer‐Aided Engineering (CAE) tool environment from its initial selection to its current configuration. The tool set, consisting of Requirements and Traceability Management (RTM), Requirements Driven Development (RDD‐100), and Interleaf, has undergone two process improvement cycles. The process, events, and outcomes are described within this paper.