SYSTEM‐LEVEL REQUIREMENTS DEFINITION UNDER A REVISED DoD ACQUISITION PROCESS

A literature search and survey of practicing systems engineers demonstrate that systems engineering processes and roles are not well defined during initial elicitation, capture and analysis of requirements. Changes to DoD acquisition practices that impact this part of systems engineering are outlined and implications drawn. An expanded systems engineering role in requirements definition is identified. Also highlighted are implications regarding: methods that help engineers and those with needs to interact in defining and visualizing requirements, and; capturing and using, throughout the life cycle, the decision rationale that accompanies the requirements definition and system design process.