BKCASE Workshop V Day 1 Summary

1. BKCASE Workshop VDay 1 Summary Hilton Garden Inn Phoenix, Arizona January 26-28, 2011

2. Our Partners Under consideration Under consideration Remain as Observers

3. Workshop Objectives • Review and resolve major/global SEBoK 0.25 review comments and issues done • Complete a draft development plan for SEBoK 0.5 started • Review wiki business cases and determine forward strategy for wiki development of BKCASE 0.5 done • Review GRCSE 0.25 release process and resolve residual issues • Determine BKCASE staffing for SEBoK, GRCSE, wiki, and Case Studies • Review specific BKCASE outreach opportunities (conferences, articles, …) and obtain author volunteers for development of papers and presentations • Review status of coordination efforts with IEEE and INCOSE done

4. Wednesday’s Agenda

5. Thursday’s Agenda

6. Friday’s Tentative Agenda PART LEADS/CORE TEAM ALL AUTHORS

7. Overall SEBoK Status • More than 3000 comments from more than 100 reviewers. Wow! Many more than we had expected. Terrific response from the community. • Many really excellent thoughtful comments • All comments captured in an adjudication matrix – Nicole will go over this later today • Core Team spent two days last week understanding the major points raised by the reviewers and preparing recommendations for your consideration today 7

8. Top 10 Issues • SEBoK Structure/Organization isn’t clean; too many independent chapters, no cross-linkages, no graphical “map” to help people navigate addressed • Too much detail for many of the topics – should have less discourse and more references wiki - some • Doesn’t always strike the right balance between prescriptive and descriptive material noted • Chapters 1 to 3 need to be more aligned and consistent wiki • Chapters 6 and 7 need to be more aligned and consistent wiki • Chapters 9 to 12 need to be more aligned and consistent wiki • References are erratic: 2-level system confusing; some stated that there were too many references to be useful; too much BKCASE author work wiki • Methodology for selecting what is in the glossary was unclear and many people were surprised at what was left out wiki • No clear rationale for deciding what should be in Chapter 14 (Cross-Cutting); the term “cross-cutting” was confusing to many wiki • Many style inconsistencies and need for stronger technical editing

9. Part 1 – introduction, foundations Part 1: Beginnings – each part, chapter, topic will have introduction Introduction, introducing System Concepts and Thinking, General Overview of SE and its Value – what and why of SEBoK – introduction and foundations – what and why of SE; SE is not always called SE and has aliases – how to use the SEBoK – distinguish between natural and engineered systems – our scope is engineered systems – top-level material that points to the other Parts where there is more depth – how SEBoK is related to GRCSE and GSwERC – graphical map of whole document – relationship to SWEBOK and PMBOK – why should people care about SEBoK and SE – address misconceptions about SE – introduce principles that are detailed in Part 2 – primary top 10 references for all of SEBoK discussed in Part 1 – use cases for different types of readers – different categories of readers – history of SE and this project – ethical principles of SE and engineering ethics but details in Part 4 – system concept overview in Part 1 WHY 9

10. Part 2 – System Taxonomy WHAT ARE SYSTEMS Product Systems (new), Service Systems, Enterprise Systems. Systems of Systems, Systems Science, SW-intensive systems, Complex Systems – more details of systems thinking and systems science elaborating on what is in Part 1 – systems thinking details in Part 2 – what we are engineering but not how we engineer it – could call this Part “Systems” – system properties and characteristics – recognize the parts of a system such as interfaces without getting into how they are created and engineered – emerging properties – quality attributes which are elaborated in Part 3 – introduces the basic vocabulary and philosophy of systems but not how to build them – systems have stakeholders – systems have entropy – Hitchin’s principles – not too philosophical and academic so we don’t lose the audience – relationships between enterprises, services, and products 10

11. Part 3: Engineering Across the Life Cycles HOW AND WHEN SYSTEMS ARE BUILT Life Cycles, System Definition, System Realization, System Deployment and Use, Life Management, Cross-Cutting, Issues Unique to Pr, S, E, SoS, SE management (how to manage), management outcomes but not who does it How to build the stuff described in Part 2 How you realize enterprise systems – application of SE techniques to realize enterprise objectives; enterprises are continuous; products and services are discrete Explaining the range of techniques that go with how Aspects of SE management Techniques, etc. for specialty engineering Cross-cutting techniques 11

12. Part 4: Who and Where Enabling SE in the Organization, Agreement, Competency, SE in the Global Context/Across Cultures (new) how do you organize to do SE including within an enterprise – designing an organization to do SE – matrix, functional, project, concurrent engineering, IPTs, startups vs. stable companies; how do proper SE in a rapidly evolving company SIZE MATTERS – impacts the way you organize – try to separate thinking about what vs who/where Organizational improvement approaches, cmmi, itil, … Has aspects of SE management; cmmi might help in sorting out organizational vs project levels vs individual level Ethics and roles people play – look at people cmm – how is it relevant – importance to the public – look at IEEE/INCOSE codes of ethics including for IEEE Software Engineering ethics Professionalism (prepatory knowledge, certification, workforce development, role of engineers in society, etc, tied to professional engineers,…) Organizing for specialty engineering 12

13. Part 5: Case Studies Case Studies in Different Domains and Applications Contrast and compare 3 different applications in SE across domains, different size projects Domain-specific concerns Case study matrix – the criteria Case studies themselves – about 3 – have to be available but not physically included in SEBoK Used as examples of how SE was applied as opposed to trying to cover every domain Shape the development of new case studies – strengths and weaknesses of use of SE principles and techniques – criteria for “good” case studies Take existing case studies rather than write them ourselves Table + analysis ala GPS Motivate new case studies that could be written – by students, by companies for internal training 13

14. Issue #1: Proposed Part Lead Authors and Core Team Members Part 1: Beginnings – Barry Boehm and Art Pyster Part 2: System Taxonomy – Rick Adcock and Nicole Hutchison Part 3: Engineering Across the Life Cycle – Bud Lawson and Dave Olwell Part 4: Engineering In and Across Organizations – Garry Roedler and Alice Squires Part 5: Domain Specific Examples – Heidi Davidz and Alice Squires Chapter leader and chapter author assignments still to be decided – people can stay with assignments from 0.25 or move elsewhere 14

15. Issue #9: Cross-Cutting • Purpose of what was Chapter 14 in SEBoK 0.25 is to capture “specialty” engineering that permeates across all other chapters • Often called “non-functional” topics, such as reliability, security, and safety • For SEBoK 0.5, will pick top TBD topics to include • For 0.5, will provide a template for all included topics to provide for common structure, style, content, and length • Will try to include only non-functional topics that are common across multiple domains • Other chapters should address non-functional topics lightly and point to cross-cutting chapter; conversely, cross-cutting chapter should point to other chapters • Well-suited for wiki structure • Name “cross-cutting” not well-accepted. Need another name 15

16. Wiki

17. Systems Engineering Body of Knowledge (SEBoK) Part 1 Related Topics Topic 1 Topic 2 Topic 3 Topic 4 . . . . Part 2 Guidance Materials Citations, Glossary, and primary references – Generated from 0.5 materials Related Primary References and Related topics: New efforts unique to Wiki discussion Part 1 KA 1 Topic 2 (Article Title) Loremipsum dolor sit amet[1], consectetueradipiscingelit, seddiamnonummynibheuismodtinciduntutlaoreetdolore magna aliquameratvolutpat. Utwisienim ad minim veniam, quisnostrudexercitationullamcorpersuscipitlobortisnislutaliquip ex ea commodoconsequat. Duisautemveleumiriuredolor[2]in hendrerit in vulputatevelitessemolestieconsequat, velillumdolor eufeugiat SEBoK Map: Generated from TOC KA 2 Topic 1 nullafacilisis at veroeros et accumsan et iustoodiodignissim qui blanditpraesentluptatumzzrildelenitaugueduisdoloretefeugaitnullafacilisi. Lorem ipsum[3] dolor sit amet, consectetueradipiscingelit, seddiamnonummynibheuismodtinciduntutlaoreetdolore Topic 2 KA 3 Citations Citation 1 • Citation 2 • Citation 3 • Citation 4 . . . . Part 4 Body – Generated from 0.5 Materials Part 5 Figure Caption magna aliquameratvolutpat. Utwisienim ad minim veniam, quisnostrudexercitationullamcorpersuscipitlobortisnislutaliquip ex ea commodoconsequat. [4] Related Primary References Reference 1 • Reference 2 . . . . Discussion Thread Please provide any comments on Topic 2 below. Comment Entry Area (access controls TBD) Comment 1: User XXXXX Body of Comment Comment 2: User XXXX Body of Comment . . . . CommunityInvolvement& Conversation: Specific aspect of wiki development Glossary Term 1 • Term 2 • Term 3 • Term 4 . . . .

18. Way Ahead • Workshop V—Determine approach for version 0.5 • Wiki team: • Review cost data to verify selection is appropriate • Determine appropriate technology/server options • Draft framework for 0.5 (based on author team work) • Work with Core Team to develop a technical review/editing plan for version 0.5 • Milestones (subject to change): • Workshop VI: Draft Architecture • May: Initial 0.5 materials imported to Wiki environment (Static) • June: Authors begin working in Wiki environment (Evolving) • Workshop VII: Any issues with Wiki use are discussed addressed • August: Final drafts of materials in Wiki (Static—by author team) Draft of additional SEBoK Views (author team and wiki team) • August-Sept: Technical editing; Core Team coordination with Part Leads to close gaps, correct redundancies, etc. • Sept: 0.5 Open for review (Static with comment feature enabled)

19. Adjudication / review

20. Expectations for adjudication • Each chapter allocated to a part. Each part lead/team to complete adjudication for its chapters by April Workshop. • Core and part leads to meet to discuss common/cross cutting issues. Emerging issues can be floated up at any time. • Part teams to decide work plan on Friday. • Teams to begin addressing the ‘accept’ and ‘modify’ items for W6 (April).

21. ASEE article • Rubric for classifying compliance with GRCSE is the principal new contribution • Intended uses • Unintended uses • GSWeRC may follow this approach.

22. IEEE/INCOSE • IEEE systems council has no capability to be steward, while computer society does • Put it under educational activities board with CS executing. But CS is not in Sys council • Proposal is to put a committee together between INCOSE (2), IEEE (2), plus two from BKCASE to write stewardship agreements • How co-governed • Agreement to be signed by all three parties • Step towards tighter relationship between INCOSE / IEEE • Don’t freeze out other organizations for revisions • Clean transition by 2012 is goal • Use GSWeRC as example

23. More fun….