Revisiting the similar process to engineer the contemporary systems

Abstract

This paper addresses the present-day context of Systems Engineering, revisiting and setting up an updated framework for the SIMILAR process in order to use it to engineer the contemporary systems. The contemporary world is crowded of large interdisciplinary complex systems made of other systems, personnel, hardware, software, information, processes, and facilities. An integrated holistic approach is crucial to develop these systems and take proper account of their multifaceted nature and numerous interrelationships. As the system’s complexity and extent grow, the number of parties involved (stakeholders and shareholders) usually also raises, bringing to the interaction a considerable amount of points of view, skills, responsibilities, and interests. The Systems Engineering approach aims to tackle the complex and interdisciplinary whole of those socio-technical systems, providing the means to enable their successful realization. Its exploitation in our modern world is assuming an increasing relevance noticeable by emergent standards, academic papers, international conferences, and post-graduate programmes in the field. This work aims to provide “the picture” of modern Systems Engineering, and to update the context of the SIMILAR process model in order to use this renewed framework to engineer the challenging contemporary systems. The emerging trends in the field are also pointed-out with particular reference to the Model-Based Systems Engineering approach.

Keywords

SIMILAR process / systems engineering / standards / MBSE

References

[1] Arlow J., Neustadt I.. UML 2 and the Unified Process: Practical Object Oriented Analysis and Design, 2005, 2nd Edition Massachusetts: Pearson Education, Inc

[2] Arnold S.. Where is standardization guiding us?. INSIGHT-INCOSE Journal, 2007, 10(2): 41-43.

[3] Bahill A., Botta R.. Fundamental principles of good system design. Engineering Management Journal, 2008, 20(4): 9-17.

[4] Bahill A., Briggs C.. The systems engineering started in the middle process: a consensus of systems engineers and project managers. Systems Engineering, 2001, 4(2): 156-167.

[5] Bahill A., Gissing B.. Re-evaluating systems engineering concepts using systems thinking. IEEE Transactions on Systems, Man and Cybernetics - Part C: Applications and Reviews, 1998, 28(4): 516-527.

[6] Bahill A., Brown P., Buede D., Martin J.. Systems engineering fundamentals. INSIGHT-INCOSE Journal, 2002, 5(1): 7-10.

[7] Bailey K.. Fifty years of systems science: further reflections. Systems Research and Behavioral Science, 2005, 22(5): 355-361.

[8] Blanchard B., Fabrycky W.. Systems Engineering and Analysis, 2006, 4th Edition New Jersey: Pearson Education, Inc

[9] Boehm B.. Some future trends and implications for systems and software engineering processes. Systems Engineering, 2006, 9(1): 1-19.

[10] Boulding K.. General systems theory: the skeleton of science. Management Science, 1956, 2: 197-208.

[11] Browning T.. The many views of a process: toward a process architecture framework for product development processes. Systems Engineering, 2009, 12(1): 69-90.

[12] Buede D., Forsberg K., Mooz H., Plowman C., Tufts B.. Systems engineering processes. INSIGHT-INCOSE Journal, 2002, 5(1): 11-15.

[13] Buede D.. The Engineering Design of Systems Models and Methods, 2009, 2nd Edition New York: John Wiley & Sons, Inc

[14] Chen P., Clothier J.. Advancing systems engineering for systems of systems challenges. Systems Engineering, 2003, 6(3): 170-183.

[15] Cloutier R., Verma D.. Applying the concept of patterns to systems architecture. Systems Engineering, 2007, 10(2): 138-154.

[16] Davidz H., Nightingale D.. Enabling systems thinking to accelerate the development of senior systems engineers. Systems Engineering, 2008, 11(1): 1-14.

[17] Dori D.. Object Process Methodology: A Holistic Systems Paradigm, 2002, New York: Springer

[18] Eisner H.. Essentials of Project and Systems Engineering Management, 2002, 2nd Edition New York: John Wiley & Sons, Inc.

[19] Friedenthal S., Moore A., Steiner R.. A Practical Guide to SysML, The Systems Modeling Language, 2008, Burlington: Morgan Kaufmann/OMG Press, Elsevier Inc.

[20] Hardman, N., Colombi, J., Jacques, D., Hill, R. & Miller, J. (2009). The challenges of human considerations in the systems engineering technical processes. In: Kalawsky, O’Brien, Goonetilleke (eds.), 7^th Annual Conference on Systems Engineering Research (CSER 2009), Loughborough, April 20–23, 2009, Research School of Systems Engineering

[21] Haskins C.. The state of systems engineering in Norway. INSIGHT-INCOSE Journal, 2007, 10(4): 47-48.

[22] Hitchins D.. Advanced Systems, Thinking, and Management, 2003, Norwood: Artech House, Inc

[23] Hitchins D.. Systems Engineering: A 21st Century Systems Methodology, 2007, London: John Wiley & Sons, Ltd

[24] Honour E.. Systems engineering and complexity. INSIGHT-INCOSE Journal, 2008, 11(1): 20-21.

[25] Hybertson D., Sheard S.. Integrating and unifying old and new systems engineering elements. INSIGHT-INCOSE Journal, 2008, 11(1): 13-16.

[26] IEEE. (2000). Recommended Practice for Architectural Description of Software Intensive Systems (IEEE Std 1471 2000). Institute of Electrical and Electronics Engineers Standards Association

[27] INCOSE. (2007a). Systems Engineering Handbook - a Guide for System Life Cycle Processes and Activities. International Council on Systems Engineering

[28] INCOSE. (2007b). Systems Engineering Vision 2020. Systems Engineering Vision Working Group of the International Council on Systems Engineering. International Council on Systems Engineering

[29] Jamshidi M.. System of systems engineering - new challenges for the 21st century. IEEE Aerospace and Electronics Systems Magazine, 2008, 23(5): 4-19.

[30] Kalawsky, R. (2009). Grand challenges for systems engineering research. In: Kalawsky, O’Brien, Goonetilleke (eds.), 7^th Annual Conference on Systems Engineering Research (CSER 2009), Loughborough, April 20–23, 2009, Research School of Systems Engineering

[31] Kim C.H., Weston R., Hodgson A., Lee K.H.. The complementary use of IDEF and UML modelling approaches. Computers in Industry, 2003, 50: 35-56.

[32] Kruchten P.. The 4+1 view model of architecture. IEEE Software, 1995, 12(6): 42-50.

[33] Lane J., Boehm B.. System of systems lead system integrators; where do they spend their time and what makes them more or less efficient. Systems Engineering, 2008, 11(1): 81-91.

[34] Maier M., Recthin E.. The Art of Systems Architecting, 2002, 2nd Edition Florida: CRC Press

[35] Maier M.. System and software architecture reconciliation. Systems Engineering, 2006, 9(2): 146-159.

[36] Martin J.. Processes for engineering a system: an overview of the ANSI/EIA 632 standard and its heritage. Systems Engineering, 2000, 3(1): 1-26.

[37] Meadows D.. Thinking in Systems: A Primer, 2008, Vermont: Chelsea Green Publishing Company, part I

[38] Militello L., Dominguez C., Lintern G., Klein G.. The role of cognitive systems engineering in the systems engineering design process. Systems Engineering, 2010, 13(3): 261-273.

[39] Mueller M.. Human systems integration - what’s it all about?. INSIGHT-INCOSE Journal, 2008, 11(2): 7-10.

[40] Murman, E. (2008). Lean enablers for systems engineering. Paper presented at the Lean Advancement Initiative (LAI) Conference, MIT, Boston, April 22–24, 2008

[41] Oppenheim B.. Lean enablers for systems engineering. INSIGHT-INCOSE Journal, 2009, 12(1): 35-36.

[42] Ramo, S. (2004). Systems Engineering Manual. Federal Aviation Agency (FAA)

[43] Ramos, A., Ferreira, J. & Barceló, J. (2008). A framework for intelligent urban environmental traffic management: the data acquisition module’s case. In: Proceedings of the 15th World Congress on Intelligent Transport Systems, New York, November 16–20, 2008

[44] Rhodes, D. (2008). Addressing Systems Engineering Challenges Through Collaborative Research. SEARI-Systems Engineering Advancement Research Initiative. Massachusetts Institute of Technology

[45] Richards, M., Shah, N., Hastings, D. & Rhodes, D. (2007). Managing complexity with the department of defense architecture framework: development of a dynamic system architecture model. Working Paper ESD-WP-2007/09, Engineering Systems Division, MIT

[46] Ross D.. Structured analysis (SA): a language for communicating ideas. IEEE Transactions on Software Engineering, 1977, 3(1): 16-34.

[47] Sheard S., Mostashari A.. Principles of complex systems for systems engineering. Systems Engineering, 2009, 12(4): 295-311.

[48] Sheard, S. (1996). Twelve systems engineering roles. In: Proceedings of the 6th Annual International Symposium of the INCOSE, Boston

[49] Sommerville I.. Software Engineering, 8th Edition, 2007, London: Pearson Education Limited

[50] Tien J., Berg D.. A case for service systems engineering. Journal of Systems Science and Systems Engineering, 2003, 12(1): 13-38.

[51] Valerdi R., Davidz H.. Empirical research in systems engineering: challenges and opportunities of a new frontier. Systems Engineering, 2009, 12(2): 169-181.

[52] Van Daalen C., Thissen W., Verbraeck A.. Sage A., Rouse W.. Methods for the modeling and analysis of alternatives. Handbook of Systems Engineering and Management, 2009, New York: Wiley Interscience 1037-1076.

[53] Wymore A.. Model Based Systems Engineering, 1993, Florida: CRC Press

[54] Zachman J.. A framework for information systems architecture. IBM Systems Journal, 1987, 26(3): 276-292.