A History of Systems Engineering its evolution and devolution
HTML-код
- Опубликовано: 17 окт 2024
- Systems engineering seems to have recognized as an activity in the 20th century. This presentation presents some findings from a limited sample and discusses the changes in systems engineering from its roots in the 1930’s and 1940’ s to 2024 from the following nine perspectives:
1. The introductory phase: the early systems and the start of systems engineering postgraduate education
2. Changes in the definitions of systems engineering: the changes in a sample of definitions of systems engineering between the 1950’s and 2024.
3. Changes in the application of the systems approach in systems engineering: starting with the General Systems Theory, the changes in the meaning of the systems approach.
4. Changes in the systems engineering tools: a look at the tools of systems engineering in the 1950’s and 1960’s and different set of tools in the early 2002’s before Model-based Systems Engineering (MBSE).
5. Changes in the systems engineering roles: a look at how the roles of the systems engineer changed between 1969 and 2024 with samples from1969, 1988, 1994, 1996, 1997, 2000, 2017, 2019 and 2024.
6. The two systems engineering paradigms: a brief overview of the original “A” paradigm and the devolved currently widely-practiced “B” paradigm which seems to have burst on the scene in the 1990’s.
7. The early “Standards” for systems engineering: a brief look at MIL-STD 499, EIA-632, IEEE-1220 and ISO-IEC 15288:2002 showing why they are not actually standards for the performance of systems engineering.
8. Historical sketch of INCOSE: highlights a few milestones from its beginning as the National Council on Systems Engineering to the introduction and singular focus on MBSE.
9. The nine perspectives of systems engineering: shows how the differences in the contents of textbooks, and journal and conference papers were grouped into nine perspectives.
While some of the findings presented have been published previously, there are some new findings which were both expected and unexpected.
Because the sample size is small we couldn’t really make any serious comments, accordingly, the presentation concludes with some semi-serious comments on the findings and questions for future research.
The presentation also shows how perceptions from Temporal Holistic Thinking Perspective go beyond systems thinking and provide information that can be surprising, helpful and perhaps critical in understanding how the undesirable or problematic situation arose.
Great presentation, looking fwd to the next one
Look at some of the others on the Channel while you are waiting :)
I would like to see a presentation on your perspective of UAF, the official successor to DoDAF, MoDAF, NAF, etc. Secondly, technology has made even the simplest system overly complex, especially if there is cybersecurity involved. Lastly, SoS is a reality making good SEM execution nearly impossible. Thanks for your insightful presentation.
Would Dilbert use of the UAF be any different. We don't need Standards and Guideline, we need good people.
POSIWID of SE at the end is a cracker 😅 it’s funny I learnt systems practice through the open university it had a lot to do with perspective, understanding, and determining feasible iterative interventions. Even when working on low level applications or equipment it was always from the perspective of this thing interacting with adjacent things for some purpose of the meta system.
Purpose to me only makes sense when viewed externally from the meta system. This always allowed me to be innovative and also communicate development problems or misunderstandings in terms of the meta system domain language.
So I’d argue even during development I was still doing the understanding the problems of customer and developers and mediating/facilitating feasible and desirable solutions. Sometimes this meant explaining why the customers understanding itself was incorrect, in a hospitable and collaborative manner.
There is very little out there that takes this stance of SE
SE is not generally aught as a problem solving methodology. I do, online in a lifelong learning format.