This document:<\/p>\n
specifies the required processes implemented in the engineering activities that result in requirements for systems and software products (including services) throughout the life cycle;<\/p>\n<\/li>\n
provides guidelines for applying the requirements and requirements-related processes described in ISO\/IEC\/IEEE 15288 and ISO\/IEC\/IEEE 12207;<\/p>\n<\/li>\n
specifies the required information items produced through the implementation of the requirements processes;<\/p>\n<\/li>\n
specifies the required contents of the required information items;<\/p>\n<\/li>\n
provides guidelines for the format of the required and related information items.<\/p>\n<\/li>\n<\/ul>\n
This document is applicable to:<\/p>\n
those who use or plan to use ISO\/IEC\/IEEE 15288 and ISO\/IEC\/IEEE 12207 on projects dealing with man-made systems, software-intensive systems, software and hardware products, and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity;<\/p>\n<\/li>\n
anyone performing requirements engineering activities to aid in ensuring that their application of the requirements engineering processes conforms to ISO\/IEC\/IEEE 15288 and\/or ISO\/IEC\/IEEE12207;<\/p>\n<\/li>\n
those who use or plan to use ISO\/IEC\/IEEE 15289 on projects dealing with man-made systems, software-intensive systems, software and hardware products and services related to those systems and products, regardless of the project scope, product(s), methodology, size or complexity;<\/p>\n<\/li>\n
anyone performing requirements engineering activities to aid in ensuring that the information items developed during the application of requirements engineering processes conforms to ISO\/IEC\/IEEE 15289.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 3.2 Abbreviated terms <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 4 Conformance 4.1 Intended usage 4.2 Full conformance 4.3 Conformance to processes 4.4 Conformance to information item content <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 4.5 Tailored conformance 4.5.1 Processes 4.5.2 Information items 5 Concepts 5.1 General 5.2 Requirements fundamentals 5.2.1 General <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.2.2 Stakeholders 5.2.3 Transformation of needs into requirements 5.2.4 Requirements construct <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 5.2.5 Characteristics of individual requirements <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 5.2.6 Characteristics of a set of requirements <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5.2.7 Requirement language criteria 5.2.8 Requirements attributes <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 5.3 Practical considerations 5.3.1 Application of iteration and recursion <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 5.3.2 Iteration and recursion in requirements engineering <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 5.4 Requirement information items <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 6 Processes 6.1 Requirement processes 6.1.1 Guidelines for processes <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 6.2 Business or mission analysis process 6.2.1 Purpose 6.2.2 Outcomes <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 6.2.3 Activities and tasks <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 6.3 Stakeholder needs and requirements definition process 6.3.1 Purpose <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 6.3.2 Outcomes 6.3.3 Activities and tasks <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 6.4 System [System\/Software] Requirements definition process 6.4.1 Purpose 6.4.2 Outcomes <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 6.4.3 Activities and tasks <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 6.5 Requirements engineering activities in other technical processes 6.5.1 Requirements activities in architecture definition <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 6.5.2 Requirements activities in verification <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 6.5.3 Requirements activities in validation <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 6.6 Requirements management 6.6.1 Management overview 6.6.2 Change management <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 6.6.3 Measurement for requirements <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | 7 Information items <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | 8 Guidelines for information items 8.1 Requirements information item outlines 8.2 Business requirements specification 8.2.1 General <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | 8.2.2 BRS example outline 8.3 Stakeholder requirements specification 8.3.1 General <\/td>\n<\/tr>\n | ||||||
| 62<\/td>\n | 8.3.2 StRS example outline <\/td>\n<\/tr>\n | ||||||
| 63<\/td>\n | 8.4 System requirements specification 8.4.1 General 8.4.2 SyRS example outline <\/td>\n<\/tr>\n | ||||||
| 64<\/td>\n | 8.5 Software requirements specification 8.5.1 General <\/td>\n<\/tr>\n | ||||||
| 65<\/td>\n | 8.5.2 SRS example outline <\/td>\n<\/tr>\n | ||||||
| 66<\/td>\n | 9 Information item content 9.1 General 9.2 General content 9.2.1 Identification 9.2.2 Front matter <\/td>\n<\/tr>\n | ||||||
| 67<\/td>\n | 9.2.3 Definitions 9.2.4 References 9.2.5 Acronyms and abbreviations 9.3 Business requirements specification (BRS) content 9.3.1 BRS overview 9.3.2 Business purpose 9.3.3 Business scope <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | 9.3.4 Business overview 9.3.5 Major Stakeholders 9.3.6 Business environment 9.3.7 Mission, goals and objectives 9.3.8 Business model 9.3.9 Information environment 9.3.10 Business processes <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | 9.3.11 Business operational policies and rules 9.3.12 Business operational constraints 9.3.13 Business operational modes 9.3.14 Business operational quality 9.3.15 Business structure 9.3.16 High-level operational concept 9.3.17 High-level operational scenarios <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | 9.3.18 Other high-level life-cycle concepts 9.3.19 Project constraints 9.4 Stakeholder requirements specification (StRS) content 9.4.1 StRS overview 9.4.2 Stakeholder purpose 9.4.3 Stakeholder scope 9.4.4 Overview 9.4.5 Stakeholders 9.4.6 Business environment <\/td>\n<\/tr>\n | ||||||
| 71<\/td>\n | 9.4.7 Mission, goals and objectives 9.4.8 Business model 9.4.9 Information environment 9.4.10 System processes 9.4.11 System operational policies and rules 9.4.12 Operational constraints 9.4.13 System operational modes and states <\/td>\n<\/tr>\n | ||||||
| 72<\/td>\n | 9.4.14 System operational quality 9.4.15 User requirements 9.4.16 Operational concept 9.4.17 Operational scenarios 9.4.18 Other detailed concepts of proposed system <\/td>\n<\/tr>\n | ||||||
| 73<\/td>\n | 9.4.19 Project constraints 9.5 System requirements specification (SyRS) content 9.5.1 SyRS overview 9.5.2 System purpose 9.5.3 System scope 9.5.4 System overview 9.5.5 Functional requirements 9.5.6 Usability requirements <\/td>\n<\/tr>\n | ||||||
| 74<\/td>\n | 9.5.7 Performance requirements 9.5.8 System interface requirements 9.5.9 System operations <\/td>\n<\/tr>\n | ||||||
| 75<\/td>\n | 9.5.10 System modes and states 9.5.11 Physical characteristics 9.5.12 Environmental conditions 9.5.13 System security requirements 9.5.14 Information management requirements <\/td>\n<\/tr>\n | ||||||
| 76<\/td>\n | 9.5.15 Policy and regulation requirements 9.5.16 System life cycle sustainment requirements 9.5.17 Packaging, handling, shipping and transportation requirements 9.5.18 Verification 9.5.19 Assumptions and dependencies 9.6 Software requirements specification (SRS) content 9.6.1 SRS overview 9.6.2 Purpose 9.6.3 Scope <\/td>\n<\/tr>\n | ||||||
| 77<\/td>\n | 9.6.4 Product perspective <\/td>\n<\/tr>\n | ||||||
| 78<\/td>\n | 9.6.5 Product functions <\/td>\n<\/tr>\n | ||||||
| 79<\/td>\n | 9.6.6 User characteristics 9.6.7 Limitations 9.6.8 Assumptions and dependencies <\/td>\n<\/tr>\n | ||||||
| 80<\/td>\n | 9.6.9 Apportioning of requirements 9.6.10 Specified requirements 9.6.11 External interfaces <\/td>\n<\/tr>\n | ||||||
| 81<\/td>\n | 9.6.12 Functions 9.6.13 Usability requirements 9.6.14 Performance requirements <\/td>\n<\/tr>\n | ||||||
| 82<\/td>\n | 9.6.15 Logical database requirements 9.6.16 Design constraints 9.6.17 Standards compliance 9.6.18 Software system attributes <\/td>\n<\/tr>\n | ||||||
| 83<\/td>\n | 9.6.19 Verification 9.6.20 Supporting information <\/td>\n<\/tr>\n | ||||||
| 84<\/td>\n | Annex A (normative) System operational concept <\/td>\n<\/tr>\n | ||||||
| 96<\/td>\n | Annex B (informative) Concept of operations <\/td>\n<\/tr>\n | ||||||
| 98<\/td>\n | Annex C (normative) Tailoring policies <\/td>\n<\/tr>\n | ||||||
| 100<\/td>\n | Bibliography <\/td>\n<\/tr>\n | ||||||
| 101<\/td>\n | IEEE notices and abstract <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems and software engineering. Life cycle processes. Requirements engineering<\/b><\/p>\n |