This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
bok:eng:sys:intro [2020/09/09 05:20] anwlur [Process] introduces the Seven Samurai overview |
bok:eng:sys:intro [2020/09/10 04:50] (current) anwlur [Performance Qualities] give source for leading indicators |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Introduction to XX ====== | + | ====== Introduction to Systems Engineering ====== |
===== Definition ===== | ===== Definition ===== | ||
==== What it is ==== | ==== What it is ==== | ||
Line 7: | Line 7: | ||
===== Post-condition ===== | ===== Post-condition ===== | ||
===== Performance Qualities ===== | ===== Performance Qualities ===== | ||
+ | |||
+ | Leading source for the performance qualities of the Systems Engineering activities is G. Roedler, D.H. Rhodes, H. Schimmoller & C. Jones, "Systems Engineering Leading Indicators Guide" LAI, INCOSE, PSM and SEAri, INCOSE Technical Product Number: INCOSE-TP-2005-001-03 Version 2.0 (2010). Accessed on September 10th, 2020 [[http://seari.mit.edu/documents/SELI-Guide-Rev2.pdf|here]]. | ||
===== Problem ===== | ===== Problem ===== | ||
===== Methodology ===== | ===== Methodology ===== | ||
==== Method ==== | ==== Method ==== | ||
- | === Heuristics === | + | |
- | ==== Process ==== | + | As with any method there needs to be a clear set of requirements that it needs to address. Below requirements are borrowed from D. Long & Z, Scott “A Primer for Model-Based System Engineering”, Vitech Corporation, 2nd edition (2011). I've only replaced 'process' with 'methodology' to broaden the scope as well as replaced 'must' with 'shall' to make it consistent with standard requirements terminology. Requirement 5, regarding tailoring, is my own addition. |
+ | |||
+ | * Requirement 1: The methodology shall consistently lead to the development of successful systems | ||
+ | * Requirement 2: The methodology shall manage system complexity well | ||
+ | * Requirement 3: The methodology shall lead to effective solutions to a broad range of customer needs | ||
+ | * The methodology shall not be too narrow to deal with any particular domain/sub-domain | ||
+ | * Requirement 4: The methodology shall accommodate three main problem classes (engineering unprecedented systems, reverse engineering, and engineering precedented systems) | ||
+ | * Requirement 5: The methodology shall allow for tailoring to adapt to particular risk profile and project constraints | ||
J. Martin proposed in Martin, J. 2004. "The Seven Samurai of Systems Engineering: Dealing with the Complexity of 7 Interrelated Systems." Proceedings of the International Council on Systems Engineering (INCOSE) International Symposium, 2004, Toulouse, France that there exists seven systems in the design space. | J. Martin proposed in Martin, J. 2004. "The Seven Samurai of Systems Engineering: Dealing with the Complexity of 7 Interrelated Systems." Proceedings of the International Council on Systems Engineering (INCOSE) International Symposium, 2004, Toulouse, France that there exists seven systems in the design space. | ||
+ | |||
+ | {{ :bok:eng:sys:7-samurai.png?600 |}} | ||
+ | |||
+ | Above figure is from a [[http://systemsthinkersanonymous.com/wp-content/uploads/2017/02/US-Government-Non-Defense-The-Seven-Samurai-of-Systems-Engineering-Dealing-with-the-Complexity-of-7-Interrelated-Systems-James-Martin.pdf|presentation]] given by J. Martin in 2012. | ||
These are: | These are: | ||
Line 41: | Line 54: | ||
- Competing System(s) may address the original Problem | - Competing System(s) may address the original Problem | ||
- Competing System(s) compete with Deployed System for resources and for the attention of users and operators | - Competing System(s) compete with Deployed System for resources and for the attention of users and operators | ||
+ | |||
+ | === Heuristics === | ||
+ | ==== Process ==== | ||
=== Systems Engineering for Intervention System === | === Systems Engineering for Intervention System === |