{"id":82230,"date":"2024-10-18T03:02:49","date_gmt":"2024-10-18T03:02:49","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/ieee-iso-iec-29148-2011\/"},"modified":"2024-10-24T19:49:31","modified_gmt":"2024-10-24T19:49:31","slug":"ieee-iso-iec-29148-2011","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/ieee\/ieee-iso-iec-29148-2011\/","title":{"rendered":"IEEE ISO IEC 29148 2011"},"content":{"rendered":"
New IEEE Standard – Active. ISO\/IEC\/IEEE 29148:2011 contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. ISO\/IEC\/IEEE 29148:2011 provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO\/IEC 12207 and ISO\/IEC 15288. Information items applicable to the engineering of requirements and their content are defined. The content of ISO\/IEC\/IEEE 29148:2011 can be added to the existing set of requirements-related life cycle processes defined by ISO\/IEC 12207 or ISO\/IEC 15288, or can be used independently. This standard replaces IEEE 830, IEEE 1233, IEEE 1362.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
1<\/td>\n | ISO\/IEC\/IEEE 29148-2011(E) Front cover <\/td>\n<\/tr>\n | ||||||
3<\/td>\n | Contents <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1 Scope 2 Conformance 2.1 Intended Usage <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 2.2 Conformance to processes 2.3 Conformance to information item content 2.4 Full conformance 2.5 Tailored conformance 2.5.1 Processes <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 2.5.2 Information items 3 Normative references 4 Terms, definitions and abbreviated terms 4.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.2 Abbreviated terms 5 Concepts 5.1 Introduction 5.2 Requirements fundamentals 5.2.1 General 5.2.2 Stakeholders <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.2.3 Transformation of needs into requirements 5.2.4 Requirements construct <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5.2.5 Characteristics of individual requirements 5.2.6 Characteristics of a set of requirements <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.2.7 Requirement language criteria 5.2.8 Requirements attributes <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.2.8.1 Examples of requirements attributes 5.2.8.2 Examples of the requirements type attribute <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.3 Practical considerations 5.3.1 Iteration and recursion of processes <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 5.3.1.1 Iterative application of processes 5.3.1.2 Recursive application of processes <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.3.2 Iteration and recursion in requirements engineering <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.4 Requirement information items <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 6 Processes 6.1 Requirement processes <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 6.1.1 Guidelines for Processes 6.2 Stakeholder requirements definition process 6.2.1 Purpose 6.2.2 Outcomes <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 6.2.3 Activities and tasks 6.2.3.1 Elicit stakeholder requirements. <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 6.2.3.2 Define stakeholder requirements. <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 6.2.3.3 Analyze and maintain stakeholder requirements. <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 6.3 Requirements analysis process 6.3.1 Purpose 6.3.2 Outcomes 6.3.3 Activities and tasks <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 6.3.3.1 Define system requirements. <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 6.3.3.2 Analyze and maintain system requirements. <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 6.4 Requirements engineering activities in other technical processes 6.4.1 Requirements in architectural design 6.4.1.1 Define the architecture 6.4.1.2 Analyze and evaluate the architecture <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 6.4.2 Requirements in verification 6.4.2.1 Plan verification <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 6.4.2.2 Perform verification <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | 6.4.3 Requirements in validation 6.4.3.1 Plan validation 6.4.3.2 Perform validation <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 6.5 Requirements management 6.5.1 Management Overview 6.5.2 Change management 6.5.2.1 Configuration management <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 6.5.2.1.1 Plan configuration management 6.5.2.1.2 Perform configuration management <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | 6.5.2.2 Information management 6.5.2.2.1 Plan information management 6.5.2.2.2 Perform information management 6.5.3 Measurement for requirements <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 6.5.3.1 Plan measurement <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | 6.5.3.2 Perform measurement 7 Information items <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 8 Guidelines for information items 8.1 Requirements information item outlines 8.2 Stakeholder requirements specification document 8.2.1 Introduction 8.2.2 StRS example outline <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | 8.3 System requirements specification document 8.3.1 Introduction <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | 8.3.2 SyRS example outline <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | 8.4 Software requirements specification document 8.4.1 Introduction 8.4.2 SRS example outline <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 9 Information item content 9.1 Introduction 9.2 General content 9.2.1 Identification <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | 9.2.2 Front matter 9.2.3 Definitions 9.2.4 References 9.2.5 Acronyms and abbreviations 9.3 Stakeholder requirements specification (StRS) document 9.3.1 Business purpose <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 9.3.2 Business scope 9.3.3 Business overview 9.3.4 Stakeholders 9.3.5 Business environment 9.3.6 Goal and Objective 9.3.7 Business model 9.3.8 Information environment <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | 9.3.9 Business processes 9.3.10 Business operational policies and rules 9.3.11 Business operational constraints 9.3.12 Business operation modes 9.3.13 Business operational quality 9.3.14 Business structure 9.3.15 User requirements <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 9.3.16 Operational concept 9.3.17 Operational scenarios 9.3.18 Project constraints 9.4 System requirements specification (SyRS) document 9.4.1 System purpose 9.4.2 System scope <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 9.4.3 System overview 9.4.3.1 System context 9.4.3.2 System functions 9.4.3.3 User characteristics 9.4.4 Functional requirements 9.4.5 Usability requirements 9.4.6 Performance requirements 9.4.7 System interfaces <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 9.4.8 System Operations 9.4.8.1 Human system integration requirements 9.4.8.2 Maintainability 9.4.8.3 Reliability 9.4.9 System modes and states 9.4.10 Physical characteristics 9.4.10.1 Physical requirements <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | 9.4.10.2 Adaptability requirements 9.4.11 Environmental conditions 9.4.12 System security 9.4.13 Information management 9.4.14 Policies and regulations 9.4.15 System life cycle sustainment 9.4.16 Packaging, handling, shipping and transportation <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | 9.4.17 Verification 9.4.18 Assumptions and dependencies 9.5 Software requirements specification (SRS) document 9.5.1 Purpose 9.5.2 Scope 9.5.3 Product perspective <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 9.5.3.1 System interfaces 9.5.3.2 User interfaces 9.5.3.3 Hardware interfaces 9.5.3.4 Software interfaces <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | 9.5.3.5 Communications interfaces 9.5.3.6 Memory constraints 9.5.3.7 Operations 9.5.3.8 Site adaptation requirements 9.5.4 Product functions <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | 9.5.5 User characteristics 9.5.6 Limitations 9.5.7 Assumptions and dependencies 9.5.8 Apportioning of requirements 9.5.9 Specific requirements <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | 9.5.10 External interfaces 9.5.11 Functions <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | 9.5.12 Usability requirements 9.5.13 Performance requirements 9.5.14 Logical database requirements <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 9.5.15 Design constraints 9.5.16 Standards compliance 9.5.17 Software system attributes <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | 9.5.18 Verification 9.5.19 Supporting information <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Annex A (normative) System operational concept <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Annex B (informative) Concept of operations <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Annex C (informative) Process Mapping from ISO\/IEC 15288 and ISO\/IEC 12207 <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Annex D (normative) Tailoring policies <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Bibliography <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | IEEE Notice to Users <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems and software engineering — Life cycle processes –Requirements engineering<\/b><\/p>\n |