Difference between revisions of "Case Studies"

From SEBoK
Jump to navigation Jump to search
Line 12: Line 12:
 
==Value of Case Studies==
 
==Value of Case Studies==
  
Case studies have been used for decades in medicine, law, and business to help students learn fundamentals and to help practitioners improve their practice. A [[Matrix of Implementation Examples]] is used to show the alignment of systems engineering case studies to specific areas of the SEBoK. This helps to map each implementation example to discussion of the systems engineering principles illustrated.  The selection of case studies represented here cover a variety of sources, domains, and geographic locations.  Both effective and ineffective use of systems engineering principles are illustrated.
+
Case studies have been used for decades in medicine, law, and business to help students learn fundamentals and to help practitioners improve their practice. A [[Matrix of Implementation Examples]] is used to show the alignment of systems engineering case studies to specific areas of the SEBoK. This is intended helps to provide linkages between each implementation example to the discussion of the systems engineering principles illustrated.  The selection of case studies represented here cover a variety of sources, domains, and geographic locations.  Both effective and ineffective use of systems engineering principles are illustrated.
  
 
The number of publicly available systems engineering case studies is growing.  Case studies which highlight aerospace domain are more prevalent, with a growing number of examples beyond this domain.  
 
The number of publicly available systems engineering case studies is growing.  Case studies which highlight aerospace domain are more prevalent, with a growing number of examples beyond this domain.  

Revision as of 19:22, 30 August 2011

Systems engineering principles described in the Systems Engineering Body of Knowledge (SEBoK) Parts 1-6 are illustrated in Part 7, Systems Engineering Implementation Examples. These examples describe the application of systems engineering practices, principles, and concepts in real settings. These systems engineering examples can be used to improve the practice of systems engineering by illustrating to students and practitioners the benefits of effective practice and the risks of poor practice. The SEBoK systems engineering implementation examples are grouped in two categories, case studies and vignettes . Case studies reference cases which have already been published by external sources in the existing literature. Vignettes are short wiki articles written specifically for the BKCASE project.

Case Studies in the SEBoK

Case study introductions are provided for the following cases:

Value of Case Studies

Case studies have been used for decades in medicine, law, and business to help students learn fundamentals and to help practitioners improve their practice. A Matrix of Implementation Examples is used to show the alignment of systems engineering case studies to specific areas of the SEBoK. This is intended helps to provide linkages between each implementation example to the discussion of the systems engineering principles illustrated. The selection of case studies represented here cover a variety of sources, domains, and geographic locations. Both effective and ineffective use of systems engineering principles are illustrated.

The number of publicly available systems engineering case studies is growing. Case studies which highlight aerospace domain are more prevalent, with a growing number of examples beyond this domain.

The United States Air Force Center for Systems Engineering has developed a set of case studies "to facilitate learning by emphasizing the long-term consequences of the systems engineering/programmatic decisions on cost, schedule, and operational effectiveness" (USAF Center for Systems Engineering). They are using these cases to enhance SE curriculum. The cases are structured using the Friedman-Sage framework (Friedman and Sage 2003; Friedman and Sage 2004, 84-96) which decomposes a case into contractor, government, and shared responsibilities in nine concept areas: Requirements Definition and Management, Systems Architecture Development, System/Subsystem Design, Validation/Verification, Risk Management, Systems Integration and Interfaces, Life Cycle Support, Deployment and Post Deployment, and System and Program Management. This framework forms the basis of the case study analysis carried out by the Air Force Center for System Engineering. Two of these case studies are highlighted in this SEBoK section, the Hubble Space Telescope Case Study and the Global Positioning System Case Study.

The United States National Aeronautics and Space Administration has a catalog of over fifty NASA-related case studies (NASA 2011). These case studies include insights about both program management and systems engineering. Varying in the level of detail, topics addressed, and source organization, these case studies are used to enhance learning at workshops, training, retreats, and conferences. The use of case studies is viewed as important since, "Organizational learning takes place when knowledge is shared in usable ways among organizational members. Knowledge is most usable when it is contextual." Case study teaching is a method for sharing contextual knowledge to enable reapplication of lessons learned. The MSTI Case Study is from this catalog.

References

Citations

United States Air Force (USAF) Center for Systems Engineering. Why Case Studies? Air Force Institute of Technology (AFIT). Wright-Patterson Air Force Base, Ohio, USA. Available at: http://www.afit.edu/cse/cases.cfm (accessed 2011).

Friedman, G., and A. P. Sage. Systems Engineering Concepts: Illustration through Case Studies. January 19, 2003. Available at: http://www.afit.edu/cse/docs/Friedman-Sage%20Framework.pdf (accessed 2011).

Friedman, G., and A. P. Sage. 2004. "Case studies of systems engineering and management in systems acquisition". Systems Engineering 7 (1): 84-96.

NASA. A Catalog of NASA-Related Case Studies. Office of the Chief Knowledge Officer, Goddard Space Flight Center: National Aeronautics and Space Administration (NASA). Updated June 2011. Available at: http://www.nasa.gov/centers/goddard/pdf/450420main_NASA_Case_Study_Catalog.pdf (accessed 2011).

Primary References

United States Air Force (USAF) Center for Systems Engineering. Why Case Studies? Wright-Patterson Air Force Base, OH, USA: Air Force Institute of Technology (AFIT). Available at: http://www.afit.edu/cse/cases.cfm (accessed 2011).

Friedman, G., and A. P. Sage. 2004. "Case studies of systems engineering and management in systems acquisition". Systems Engineering 7 (1): 84-96.

NASA. A Catalog of NASA-Related Case Studies. Office of the Chief Knowledge Officer, Goddard Space Flight Center: National Aeronautics and Space Administration (NASA). Updated June 2011. Available at: http://www.nasa.gov/centers/goddard/pdf/450420main_NASA_Case_Study_Catalog.pdf (accessed 2011).

Additional References

None


Article Discussion

[Go to discussion page]

<- Previous Article | Parent Article | Next Article ->

Signatures

--Hdavidz 23:34, 14 August 2011 (UTC)