Premium
7.6.3 Case Study in Establishing Systems Engineering Principles: One Organization's Experience
Author(s) -
Reutzel Adria Liszka
Publication year - 2007
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2007.tb02943.x
Subject(s) - terminology , computer science , system of systems engineering , process (computing) , requirements engineering , mainstream , organizational architecture , stakeholder , management science , systems design , engineering management , systems engineering , software engineering , engineering , knowledge management , management , philosophy , linguistics , theology , software , programming language , operating system , economics
Even within a well‐established systems engineering organization, formalizing the practice of systems engineering can be an arduous task. This paper describes one organization's effort to start this formalization by defining and documenting the very foundation of its practice: its systems engineering principles. Topics include the process for developing principles (augmenting organizational guidance with industry best practices), the final form of the principles (justifying terminology), and the connection to broader formalization efforts (associating the principles diagram to the systems engineering logo). The principles are divided into four categories that tie mainstream systems engineering definitions together: Stakeholder, Systems Engineer, Problem, and Solution.