Premium
3.4.1 Promoting the Real Value of Systems Engineering using an Extended SCARIT Process Model
Author(s) -
Saunders Steven J.
Publication year - 2007
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2007.tb02893.x
Subject(s) - requirements engineering , process (computing) , systems engineering , computer science , traceability , system of systems engineering , system of systems , stakeholder , software engineering , process management , engineering , systems design , public relations , political science , software , programming language , operating system
Systems engineering is the discipline that defines and delivers complex systems to meet the needs of multiple, often conflicting stakeholders. In the past, many books and papers have been published focusing on process areas such as Requirements Engineering, Requirements Quality, Requirements Traceability, and Model Based Systems Engineering. In this paper, the author proposes that by previously focusing on the processes used in Systems Engineering, the real value adding steps of systems engineering; to understand the enterprise needs and to define the problem , has been overlooked. To help overcome this bias, an extended systems engineering process model is presented that strives to elevate the visibility and understanding of key value adding steps in the Systems Engineering process. Six phases are highlighted in the extended systems engineering process model covering the technical phases of systems engineering. These phases are Stakeholder, Concerns, Architecture, Requirements, Implementation and Test (or SCARIT). Process oriented steps are characterized in the final three steps (Requirements, Implementation and Test) and result in definition and deployment of the solution. However, the extended process model precedes these steps with Stakeholders, Concerns and Architecture and postulates these three steps are where the real value of systems engineering is generated. These initial steps focus on defining the problem by looking at the enterprise needs.