Outbrief for BKCASE Workshop VI Part V: Implementation Examples

1. Outbrief for BKCASE Workshop VI Part V: Implementation Examples John Brackett, Aaron Chia, Heidi Davidz, Kevin Forsberg, Richard Freeman, Tom Hilburn, Alex Lee, Alice Squires

2. Purpose • The purpose of SEBoK • Guide to the body of knowledge • Not duplicating the body of knowledge, so not copying over the case studies in their entirety • The purpose of Part V • Illustrate the topics from the other parts • Examples which other part authors reference • Help with the development of SE courses • GRCSE will also use the matrix mapping topics to examples

3. Part V Topic Outline with Authors • Full author team to contribute to each section • Outline • Introduction • Matrix • Case Studies • Description of case study • Relating the example to SEBoK topics via the matrix • Link to the case study material • Vignettes • Description of something that happened • Relating the example to SEBoK topics via the matrix • Link to source material (if applicable) Notional

4. Breakout Meeting Results • Team is targeting 10 case studies for June workshop • Each team member will be responsible for writing the two-page introduction for two cases • Internal team review process so at least two authors view each case • Each author to write two and review two • NEED FULL LIST OF KNOWLEDGE AREAS TO START WRITING • Cases available on Sakai for authors to reference • If authors have additional cases to reference, LET US KNOW

5. Forward Plan • Obtain list of knowledge areas • Assign cases • Populate wiki • Review cases • Close open actions from review matrix • Initial set of links to knowledge areas complete

6. List of Cases and Vignettes

7. Case Study and Vignette Materials • Hyperlink or document loaded in Sakai

8. Terminology • Topics from each part which we reference • Case study • Vignette

9. Primary References • Reference for each case study used • Case study chapter references • Friedman, G., Sage, A. (2004, January). Case Studies of Systems Engineering and Management in Systems Acquisition, Systems Engineering. Vol. 7, No. 1, 84-96. (http://sse.stevens.edu/fileadmin/sse/academics/resources/Developing_an_SE_Case_Study.pdf) • Haskins, C. (Editor) (2009). Systems engineering handbook: A guide for system life cycle processes and activities (version 3.2). International Council on Systems Engineering. • Herreid, C. F. (1997 November). What is a Case? Journal of College Science Teaching, 27, 92-94. (http://ublib.buffalo.edu/libraries/projects/cases/teaching/whatis.html) • Herreid, C. F. (1998 January). What Makes a Good Case? Journal of College Science Teaching, 27, 163-165. (http://ublib.buffalo.edu/libraries/projects/cases/teaching/good-case.html) • Herreid, C. F. (2002 February). The Way of Flesch: The Art of Writing of Readable Cases. Journal of College Science Teaching, 31, 288-291. (http://ublib.buffalo.edu/libraries/projects/cases/teaching/flesch.html) • Kardos, G., Smith, C. O. (1979 March) On Writing Engineering Cases. Proceedings of SEE National Conference on Engineering Case Studies. (http://cee.carleton.ca/ECL/cwrtng.html) • Moody, C., van Voorhees, B. (1997). Metrics and Case Studies for Evaluating Engineering Designs. New Jersey: Prentice Hall. • Air Force Center for System Engineering – Case Study collection (http://www.afit.edu/cse/cases.cfm) • Case of the Killer Robot, Richard G. Epstein, Westchester University of Pennsylvania Mike Melamed, CWRU 2000 (http://www.onlineethics.org/cms/5122.aspx) • INCOSE Code of Ethics (http://www.incose.org/about/ethics.aspx) • National Center for Case Study Teaching in Science (http://ublib.buffalo.edu/libraries/projects/cases/case.html) • National Institute of Engineering Ethics (http://www.niee.org/cases/)

10. Issues for June Meeting • Experts in cases to review summaries • Include more diverse cases • Be sure enterprise, SoS, etc. covered