2D2 - Special Session on Systems Engineering Case Studies Room: Palm (DEF) Chair: Brian E. White (CAU-SES, USA) Value of Case Studies 1. On the Importance and Brian E. White Brian E. White (CAU-SES) CAU SES Sudbury, MA, USA 2. *Strategic Architecture Approach T o Transforming Defense Acquisition: A Case bewhite71@gmail.com Study in Moving From Formal Bureaucracy to Lateral Hierarchy John S. Jimmy Gandhi Dickmann, Jr. (Sonalysts, Inc.) University of California Northridge, CA, USA 3. **Studying regulatory institutions competition and collaboration dynamics in s jg07646@yahoo.com network industries: Using Agent-based Modeling and Simulation Hamid R. Alex Gorod University of Adelaide Darabi and Mo Mansouri (Stevens Institute of T echnology) Adelaide, South Australia 4. Elaborating a Conceptual Collaborative Framework: A case Study for Wood alex.gorod@adelaide.edu.au Supply Chain in North-Shore Region in Quebec, Canada Vernon Ireland University of Adelaide Kyarash Shahriari (CRIQ, Canada) and Ali G Hessami (Vega Systems & London Adelaide, South Australia City University, United Kingdom) (Chair will present on behalf of authors.) vernon.ireland@adelaide.edu.au 5. Biomedical Diagnostic System for Device Coding Brian Sauser University of North T exas Carlos Alvarez, Destin Smith, and Ankur Agarwal (Florida Atlantic University) ___________ Denton, TX, USA * Full case study planned for forthcoming book, Case Studies in Brian.Sauser@unt.edu System of Systems, Enterprises, and Complex System Engineering ** The above book will contain a full case study related to this paper. The 7 th IEEE International Systems Conference 1 5/22/2014 5-18 April2013, Orlando, FL USA
See Notes Page Brian E. White CAU SES Sudbury, MA, USA bewhite71@gmail.com S. Jimmy Gandhi University of California Northridge, CA, USA s jg07646@yahoo.com Alex Gorod University of Adelaide Adelaide, South Australia alex.gorod@adelaide.edu.au On the Importance and Value of Case Studies Vernon Ireland University of Adelaide B. E. White, Ph.D. Adelaide, South Australia vernon.ireland@adelaide.edu.au 2D2 - Special Session on Systems Engineering Case Studies Brian Sauser 3:30 p.m. – 5:45 p.m. – Tuesday, 16 April 2013 Hyatt Regency Grand Cypress University of North T exas Denton, TX, USA Brian.Sauser@unt.edu The 7 th IEEE International Systems Conference 2 5/22/2014 5-18 April2013, Orlando, FL USA
See Notes Page Introduction Engineering is solving human-made problems. Systems Engineering (SE) evolves as trans-disciplinary [1]. Education usually teaches theory first. T eaching through case studies addresses “wicked” problems [4] at the “messy” frontier [5], in “ mega-system ” [6] SE environments. This paper emphasizes the importance and value of case studies in complex, System of Systems (SoS), and enterprise SE. The 7 th IEEE International Systems Conference 3 5/22/2014 5-18 April2013, Orlando, FL USA
See Notes Page Some Definitions (1/3) System, engineering, and enterprise do not need definition – but “complex” does. Complex means more than complicated. Many use complex and complicated interchangeably – or worse – when they only mean complicated. A complex system is distinguished by including people as part of the system – to better reflect reality. Complex systems evolve through self-organization in response to many internal and environmental interactions. Complex systems engineers are not really in control but can Only influence the system Decide to intervene again (at some point) if the system moves in undesirable directions. The 7 th IEEE International Systems Conference 4 5/22/2014 5-18 April2013, Orlando, FL USA
Virtual Virtual SoSs lack a central management authority and a centrally agreed-upon purpose for the SoS. Large-scale See Notes Page Fig. 1 A Perceived Venn Diagram behavior emerges—and may be desirable—but this type SoS must rely upon relatively invisible mechanisms to maintain it. Collaborative In collaborative SoSs, the component systems interact more or less voluntarily to fulfill agreed-upon Relationship Among Systems (2/3) central purposes. The Internet is a collaborative system. The Internet Engineering Task Force works on standards but has no power to enforce them. The central players collectively decide how to provide or deny service, thereby providing some means of enforcing and maintaining standards. Acknowledged Acknowledged SoSs have recognized objectives, a designated manager, and resources for the SoS; however, the constituent systems retain their independent ownership, objectives, funding, as well as development and Degree of Difficulty Can Because of its homeostasis property, sustainment approaches. Changes in the systems are based on collaboration between the SoS and each member system. an Enterprise might be more difficult Increase in This Direction to engineer than a Complex System. Directed Directed SoSs are those in which the integrated SoS is built and managed to fulfill specific purposes. It is centrally managed during long-term operation to continue to fulfill those purposes as well as any new ones the system owners might wish to address. The component systems maintain an ability to operate independently, but their normal operational mode is subordinated to the central managed purpose. The 7 th IEEE International Systems Conference 5/22/2014 5 5-18 April2013, Orlando, FL USA
See Notes Page Fig. 2 Another Perceived Venn Diagram Relationship Among Systems (3/3) The 7 th IEEE International Systems Conference 5/22/2014 6 5-18 April2013, Orlando, FL USA
See Notes Page Why Do Case Studies? (1/2) Experienced systems engineers have great ideas for engineering difficult systems but often do not think case studies are needed. Stakeholders who have achieved career success want “ proof ” that complex SE ideas “ will work ” . The complex systems engineer says “ This is not a mathematical theorem. People are not predictable, and behaviors are impossible to model. You need to take informed risks by pursuing opportunities for system interventions. ” T o help the systems engineer can experiment with modeling/simulation. Give simple rules of interaction to autonomous agents (representing system constituents). In a large number of iterations, unexpected events occur even when each step is completely deterministic. Case studies are used for initial conditions and actor guidance. The 7 th IEEE International Systems Conference 7 5/22/2014 5-18 April2013, Orlando, FL USA
See Notes Page Why Do Case Studies? (2/2) In case studies theory follows practice but many people believe that applications must follow theory. Case studies can be used to Build upon or enhance a body of knowledge Suggest things to try Highlight errors to avoid Learn from others’ mistakes Compare specific aspects across case studies Show the importance of including people in the system Extract ideas that can become general principles. Some case studies focus success on wonderful technology. But other practitioners want system success in human terms. Case studies make for compelling story telling [13] and SE teaching. The 7 th IEEE International Systems Conference 8 5/22/2014 5-18 April2013, Orlando, FL USA
See Notes Page How to Do Case Studies Focus on complex, SoS, and enterprise engineering. * When starting a complex system project/program Prepare an plan for gathering and recording data. Keep this record ongoing, preserving the issues, decisions, actions, and results of each step. Record interesting developments in essay form. Insights will suggest ways forward and provide valuable case study fodder. Case studies must be written honestly. Obtaining public release can be a challenge but much information can be shared to one’s own advantage [17]. Objectivity is important but emotions are relevant [18]. Compare and contrast case studies using an outline template. ** ____________ * The authors are working on assembling 20+ such case studies for a new book [16]. ** A suggested example outline that the authors are advocating in the forthcoming book [16] is provided in the Appendix. The 7 th IEEE International Systems Conference 9 5/22/2014 5-18 April2013, Orlando, FL USA
See Notes Page Example Case Studies (1/6) The authors of this 1 st Paper of our special session anticipate 20 case studies in their book [16] in commerce, culture, environment, finance, health care, homeland security, military, and transportation. 2 nd Paper. Case Study: SoS Engineering Applied to a Large IT Enterprise – Jeffrey Higginson, Timothy Rudolph, and Jon Salwen.* This discusses the minimum set of Systems of Systems Engineering (SoSE) processes needed to effectively manage an enterprise Information T echnology (IT) SoS and provides an example of how these processes and methods may be applied. ___________ *A full case study is being prepared for our book [16]. Unfortunately, the U.S. Department of Defense froze travel funds (induced by the “sequester” ) and the consequent unavailability of the authors prevents this paper’s presentation. The 7 th IEEE International Systems Conference 10 5/22/2014 5-18 April2013, Orlando, FL USA
Recommend
More recommend
