Recommendations for Revision of SWEBOK Annette Reilly SWEBOK Virtual Town Hall, 25 August 2016

Annette Reilly IEEE-CS Society Representative to ISO/IEC JTC 1 SC7, Systems and Software Engineering IEEE-CS Standards Activity Board member ISO/IEC/IEEE 12207:2017 co-editor (Systems and software engineering, Software life cycle processes) SWEBOK v3 associate editor annette.reilly@computer.org After three editions and over twenty years in development, the basic methodology of SWEBOK needs to adapt to a more dynamic concept of knowledge and more rapid pace of change in engineering methods.

SWEBOK Opportunities Role of SWEBOK Development and maintenance Knowledge areas Enhancing content and enabling technologies

Context of SWEBOK as a Guide to the BOK SWEBOK: Book or Database? Rate of change in the core sources Rate of change in the practice of SW Engr Changes in the problems of interest ISO/IEC TR 19759 Certifications Curricula Standards SWEBOK Core Sources Advanced Research Core Sources SEVOCAB Core Sources Core Sources Related BOK Working SWE SEBOK, IEEE EIT BOK, Japanese IT knowledge base, ITIL®, PMBOK ® Guide, Wikipedia

SWEBOK Development and Maintenance Is the SWEBOK a unified structured model or an open-ended source of reference? Big-Bang block releases have not worked for SWEBOK Development and maintenance of the BoK need to be performed as one continuous process Types of maintenance needed: Updates due to revisions of core sources and standards Revisions of Knowledge Areas (KA) Additions/restructuring of KA with changes in core sources Requires a SWEBOK change control board Agree on the KA Agree on the core references—may be electronic as well as published books and articles Consider coverage in competing BoK Review each KA for topics to retire, revise, add

SWEBOK Changes in KA Focus on KA that require engineering thought and effort, rather than being built in to today’s tools The KA do not necessarily align with the ISO/IEC/IEEE 12207 life-cycle processes Add information assurance Consider impact of automated tools and methods on SWE, in CM, Release Management, Software Integration, Transition Treat open source and agile as mainstream practices Unified performance of software development, test, and maintenance (DevOps) Reconsider interrelationship of software in systems engineering, System of systems The SE hierarchical analytical view is often not helpful to software design and construction Identify relatively stable KA such as requirements engineering, risk management

SWEBOK Changes in Foundational Areas Omit Mathematical Foundations Expand topics from Computing Foundations to treat the primary and particular concerns of software architects and engineers Key principles, algorithms, patterns Information modeling Databases and data management, Big Data considerations Human-computer interfaces and design factors Very large SoS (software-defined networks, cloud systems, smart cities, internet of things)

Enhancing content and enabling technologies Use a content management system for topics and references Electronic content development, review, and approval Output is internet accessible and searchable Links to related SWEBOK topics, core sources, and standards Links to IEEE Xplore® Digital Library for advanced presentations Continuous public input for potential changes Defined coordination with owners of related IEEE-CS educational products, curricula recommendations