Knowledge_Area_Description_for_Software_Requirements_Engineering(version_0_6)英文资料.pdfVIP

SWEBOK: Software Requirements Engineering Knowledge Area Description Version 0.6 Pete Sawyer and Gerald Kotonya Computing Department, Lancaster University United Kingdom {sawyer} {gerald} @comp.lancs.ac.uk 1. INTRODUCTION2 2. REFERENCES USED3 3. OVERVIEW OF REQUIREMENTS ENGINEERING 3 3.1. WHAT IS A REQUIREMENT? 3 3.2. THE CONTEXT OF REQUIREMENTS ENGINEERING 4 3.3. SYSTEM REQUIREMENTS AND PROCESS DRIVERS 4 3.4. REQUIREMENTS ANALYSIS IN OUTLINE 6 3.5. REQUIREMENTS ENGINEERING IN PRACTICE 7 3.6. PRODUCTS AND DELIVERABLES 8 4. SOFTWARE REQUIREMENTS ENGINEERING BREAKDOWN: PROCESSES AND ACTIVITIES 9 4.1 THE REQUIREMENTS ENGINEERING PROCESS 10 4.2 REQUIREMENTS ELICITATION 12 4.3 REQUIREMENTS ANALYSIS 13 4.4 SOFTWARE REQUIREMENTS SPECIFICATION 16 4.5 REQUIREMENTS VALIDATION 17 4.6 REQUIREMENTS MANAGEMENT 18 APPENDIX A - SUMMARY OF REQUIREMENTS ENGINEERING BREAKDOWN20 APPENDIX B BREAKDOWN RATIONALE 21 APPENDIX C MATRIX OF TOPICS AND REFERENCES 23 APPENDIX D - SOFTWARE REQUIREMENTS ENGINEERING AND BLOOMS TAXONOMY 25 APPENDIX D – SOFTWARE REQUIREMENTS ENGINEERING REFERENCES26 1. Introduction This document proposes a breakdown of the SWEBOK Software Requirements Engineering Knowledge Area. The knowledge area was originally proposed as Software Requirements Analysis. However, as a term for the systematic acquisition and handling of software requirements, requirements analysis has been largely superceded by requirements engineering. We therefore use requirements engineering to