Premium
4.6.2 YADSES: Yet Another Darn Systems Engineering Standard
Author(s) -
Walden David D.
Publication year - 2007
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2007.tb02908.x
Subject(s) - process (computing) , set (abstract data type) , computer science , advice (programming) , risk analysis (engineering) , compliance (psychology) , process management , engineering , business , psychology , social psychology , programming language , operating system
It has happened to most everyone – someone releases the “next best” Systems Engineering standard (or method or tool or …) and your organization has decided to use it. How does one incorporate this new standard into the existing set of organizational processes without “breaking” the current processes and negatively impacting compliance to all the “old” standards that do not go away? By the way, expect to repeat this process at least every other year. This paper gives practical advice to help ensure organizations are prepared for these types of situations. Guidance is given on how to establish and maintain organizational processes such that the introduction of Yet Another Darn Systems Engineering Standard (or YADSES as we will refer to it) causes minimal impact.