SWEBOK. The Emerging Consensus on the Software Engineering Body of Knowledge. A. Abran, NSERC Ottawa, February 18, 2002

Transcription

1 SWEBOK The Emerging Consensus on the Software Engineering Body of Knowledge A. Abran, P. Bourque,, R. Dupuis, J. W. Moore, L. Tripp NSERC Ottawa, February 18, 2002 ÉTS 1

2 Corporate Support by: Project managed by: 2

3 Presentation Plan Project background Project objectives, audiences and plan Content of the Guide Next steps Research Issues 3

4 Key Issues Groups and individuals: Universities: Different views of software engineering Offering undergraduate degrees in Software Engineering, outside of traditional Engineering Departments Limited consistency across curriculum Different accreditation groups (Canada:CIPS and CCPE) Increased interest in the establishment of a profession 4

5 Market Trends - Examples Texas Board of Engineers: Decision to license software engineers: a strategy with significant impact on: industry (e.g. mobility of staff & training) universities policy bodies individuals (+ engineering boards in Canada and universities) 5

6 What is Software Engineering? IEEE : (1) The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software. (2) The study of approaches as in (1). 6

7 Key Interrelationships for a Core Body of Knowledge Development of Software Engineering Curricula Influences Consensus on a Core Body of Knowledge Influences Development of Certification / Licensing Criteria and Exams Influences Development of University Program Accreditation Criteria 7

8 Presentation Plan Project background Project objectives, audiences and plan Content of the Guide Next steps Research issues 8

9 Project Objectives Promote a consistent view of software engineering worldwide Clarify the place of, and set the boundary of, software engineering with respect to other disciplines Characterize the contents of the Software Engineering Body of Knowledge - SWEBOK Provide a topical access to the Software Engineering Body of Knowledge Provide a foundation for curriculum development and individual certification and licensing material 9

10 Intended Audiences Public and private organizations Practicing software engineers Makers of public policy Professional societies Software engineering students Educators and trainers 10

11 What Are we Not Trying to Accomplish? Not an all-inclusive description of the sum of knowledge in the field Not all categories of knowledge Not a curriculum development effort 11

12 Categories of Knowledge in the SWEBOK Specialized Generally Accepted Advanced and Research Focus of the SWEBOK Guide 12

13 Generally Accepted «Applies to most projects, most of the time, and widespread consensus validates its value and effectiveness» Project Management Institute Bachelor + 4 years of experience 13

14 IEEE and ACM strategies IEEE-CS: ACM: initial focus on generally accepted strategy with intermediate deliverables contributions to the maturation and consensus building opposition to licensing withdrawal from joint efforts with IEEE-CS concerns: focus on specialized knowledge 14

15 Three Underlying Principles of the Project Transparency: the development process is itself published and fully documented Consensus-building: the development process is designed to build, over time, consensus in industry, among professional societies and standards-setting bodies and in academia Consensus does not equal Unanimity! Available free on the web 15

16 A Three-Phase Approach for Developing the Guide to the SWEBOK Straw Man Straw Man Version Version Stone Man Phase Stone Man Phase (Trial Version) (Trial Version) Iron Man Version Iron Man Version (Sub-phase 1) (Sub-phase 1)

17 Project Team Editorial team Industrial Advisory Board Knowledge Area Specialists A very large international group of Reviewers 17

18 A Three-Phase Approach for Developing the Guide to the SWEBOK Straw Man Straw Man Version Version Stone Man Phase Stone Man Phase (Trial Version) (Trial Version) Iron Man Version Iron Man Version (Sub-phase 1) (Sub-phase 1)

19 Phase 2: Stone Man Review Process Version 0.1 Limited number of domain experts Review Cycle 1 Version 0.5 Selected users Review cycle 2 Version 0.7 Community Review Cycle 3 Version

20 Stone Man Review Process Transparency and consensus-building All intermediate versions of documents are published and archived on All comments are made public as well as the identity of the reviewers Detailed comment disposition reports are produced for Review Cycle 2 and 3 20

21 Data on reviewers Version 0,1: 33 Version 0,5: 195 Version 0,7: ISO reviews from 5 countries 21

22 Geographic Distribution of USA: 55% Europe: 18% 90 reviewers from 25 countries Canada: 10% Australia: 5% Asia: 5% Reviewers Latin America: 4% 22

23 Education of Reviewers 3% 24% 34% Doctorat Master Bachelor Other 39% 23

24 Organizations of Reviewers (no. of employees) 31% 37% more 32% 24

25 Project Overview Presentation Plan Project background Project scope, objectives, audience and plan Contents of the Guide How you can leverage the Guide within your organization Conclusion 25

26 Stone Man Deliverables: Consensus on a list of Knowledge Areas Consensus on a list of topics and relevant reference materials for each Knowledge Area Consensus on a list of Related Disciplines 26

27 Guide to the Software Engineering Body of Knowledge (Version 0.95) Software Requirements Software Design Software Construction Software Testing Software Maintenance Requirement Engineering Process Software Design Basic Concepts Reduction in Complexity Testing Basic Concepts and Definitions Basic Concepts Requirements Elicitation Requirement Analysis Requirements Specification Key Issues in Software Design Software Structure and Architecture Software Design Quality Analysis and Evaluation Anticipation of Diversity Structuring for Validation Use of External Standards Test Levels Test Techniques Test-Related Measures Maintenance Process Key Issues in Software Maintenance Techniques for Maintenance Requirements Validation Software Design Notations Managing the Test Process Requirements Management Software Design Strategies and Methods (a) (b) (c) (d) (e) 27

28 Guide to the Softw are Engineering Body of Knowledge (Version 0.95) Software Configuration Management Software Engineering Management Software Engineering Process Software Engineering Tools and Methods Software Quality Management of the SCM Process Software Configuration Identification Software Configuration Control Software Configuration Status Accounting Software Configuration Auditing Organizational Management Process/Project Management Software Engineering Measurement Software Engineering Process Concepts Process Infrastructure Process Measurement Process Definition Qualitative Process Analysis Process Implementation and Change Software Tools Software Requirements Tools Software Design Tools Software Construction Tools Software Testing Tools Software Maintenance Tools Software Engineering Process Tools Software Quality Tools Software Configuration Management Tools Software Engineering Management Tools Infrastructure Support Tools Software Quality Concepts Definition & Planning for Quality Techniques Requiring Two or More People Support to Other Techniques Testing Special to SQA or V&V Defect Finding Techniques Software Release Management and Delivery Miscellaneous Tool Issues Software Methods Measurement in Software Quality Analysis Heuristic Methods Formal Methods Prototyping Methods Miscellaneous Method Issues (f) (g) (h) (d) (i) (j) 28

29 Software Requirements Software Requirements Requirements Engineering Process Requirements Elicitation Requirements Analysis Requirement Specification Requirements Validation Requirements Management Process Models Requirements Sources Requirements Classification Requirements Definition Document Conduct of Requirements Reviews Change Management Process Actors Elicitation Techniques Conceptual Modeling Software Requirements Specification (SRS) Prototyping Requirements Attributes Process Support and Management Architectural Design and Requirements Allocation Document Structure and Standards Model Validation Requirements Tracing Process Quality and Improvement Requirements Negotiation Document Quality Acceptance tests 29

30 Software Design Software Design I. Software Design Basic Concepts II. Key Issues in Software Design III. Software Structure and Architecture IV. Software Design Quality Analysis and Evaluation V. Design Notations VI. Software Design Strategies and Methods General design concepts The context of software design The software design process Enabling techniques for software design Concurrency Control and handling of events Distribution Exception handling Interactive systems Persistence Architectural structures and viewpoints Architectural styles and patterns (macroarchitecture) Design patterns (micro-architecture) Design of families of programs and frameworks Quality attributes Quality analysis and evaluation tools Software design reviews Static analysis Simulation and prototyping Measures Structural descriptions (static view) Behavior descriptions (dynamic view) General Strategies Function-oriented design Object-oriented design Data-structrure centered design Other methods Function-oriented (structured) design measures Object-oriented design measures 30

31 Knowledge Area Description Classification of Topics Matrix of Topics & References References Topic Descriptions Classification by Vincenti s Taxonomy Classification by Bloom s Taxonomy Not implemented in Stoneman References to Related Disciplines 31

32 Related Disciplines Software Requirements Software Design Software Construction Software Testing Software Maintenance Software Configuration Management Software Eng. Management Software Eng. Tools & Methods Software Engineering Process Software Quality Related Disciplines Computer Science (CC2001) Mathematics (CC2001) Project Management (PMBOK) Computer Engineering Cognitive Sciences and Human Factors Systems Engineering Management and Management Science 32

33 Project Overview Presentation Plan Project background Project scope, objectives, audience and plan Contents of the Guide Next steps Research Issues 33

34 A Three-Phase Approach for Developing the Guide to the SWEBOK Straw Man Straw Man Version Version Stone Man Version Stone Man Version Iron Man Version Iron Man Version (Sub-phase 1) (Sub-phase 1) Iron Man Iron Man Version Version (Subphase 2) (Subphase 2)

35 Collection of feedback from: Education: Curriculum design/evaluation Program accreditation Course design/evaluation Internal training, corporate universities 35

36 Collection of feedback from: Industry & Government job description hiring staffing of projects career planning contracting 36

37 Collection of feedback from: Policy organisations Licensing & Certification licensing exam questions study material in software engineering and other IT fields could be on subsets of Knowledge Areas R & D agencies: strategies for increasing engineering maturity of the domain 37

38 A Three-Phase Approach for Developing the Guide to the SWEBOK Straw Man Straw Man Version Version Stone Man Version Stone Man Version Iron Man Version Iron Man Version (Sub-phase 1) (Sub-phase 1) Iron Man Iron Man Version Version (Subphase 2) (Subphase 2)

39 Project Overview Presentation Plan Project background Project scope, objectives, audience and plan Contents of the Guide Next steps Research Areas 39

40 SWEBOK & Research Issues The Engineering of: Software Requirements Software Design Software Construction Software Testing Software Maintenance Software Quality Software Eng. Management Software Eng. Tools & Methods Software Engineering Process Software Configuration Management 40

41 SWEBOK & R&D Issues How much of Engineering Knowledge types within each of the 10 Knowledge Areas? Fundamental Design Concepts Criteria Specifications Theoretical Tools Quantitative Data Practical Considerations Design Instrumentalities [Vincenti90] W. Vincenti, What Engineers Know and How They Know It: Analytical Studies from Aeronautical History, The Johns Hopkins University Press,

42 Significant progress required from all engineering perspectives Fundamental Design Concepts Criteria Specifications Theoretical Tools Quantitative Data Practical Considerations Design Instrumentalities [Vincenti90] W. Vincenti, What Engineers Know and How They Know It: Analytical Studies from Aeronautical History, The Johns Hopkins University Press,

43 Knowledge Area Description Classification of Topics Matrix of Topics & References References Topic Descriptions Classification by Vincenti s Taxonomy Classification by Bloom s Taxonomy Not implemented in Stoneman References to Related Disciplines 43

44 Comparison of Research Areas R & D Topics in Submission to NSERC Reallocations Committee ref Software Engineering: Software Development Process Software Engineering Environments Modelling and documentation Software patterns, structures and architecture Verification and validation Source: Jointly by Electrical/Computer Engineering and Computer Sciences 44

45 Concluding Remarks Software Engineering: The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is, the application of engineering to software IEEE Strengthening the Engineering Knowledge within this new discipline is required for a rapid maturation, and significant contribution to the Canadian software industry 45

46 swebok.org 46