BS ISO/IEC/IEEE 29148:2011
$215.11
Systems and software engineering. Life cycle processes. Requirements engineering
Published By | Publication Date | Number of Pages |
BSI | 2011 | 98 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
11 | 1 Scope 2 Conformance 2.1 Intended Usage |
12 | 2.2 Conformance to processes 2.3 Conformance to information item content 2.4 Full conformance 2.5 Tailored conformance 2.5.1 Processes |
13 | 2.5.2 Information items 3 Normative references 4 Terms, definitions and abbreviated terms 4.1 Terms and definitions |
18 | 4.2 Abbreviated terms 5 Concepts 5.1 Introduction 5.2 Requirements fundamentals 5.2.1 General 5.2.2 Stakeholders |
19 | 5.2.3 Transformation of needs into requirements 5.2.4 Requirements construct |
21 | 5.2.5 Characteristics of individual requirements 5.2.6 Characteristics of a set of requirements |
22 | 5.2.7 Requirement language criteria 5.2.8 Requirements attributes |
23 | 5.2.8.1 Examples of requirements attributes 5.2.8.2 Examples of the requirements type attribute |
24 | 5.3 Practical considerations 5.3.1 Iteration and recursion of processes |
25 | 5.3.1.1 Iterative application of processes 5.3.1.2 Recursive application of processes |
26 | 5.3.2 Iteration and recursion in requirements engineering |
27 | 5.4 Requirement information items |
28 | 6 Processes 6.1 Requirement processes |
29 | 6.1.1 Guidelines for Processes 6.2 Stakeholder requirements definition process 6.2.1 Purpose 6.2.2 Outcomes |
30 | 6.2.3 Activities and tasks 6.2.3.1 Elicit stakeholder requirements. |
32 | 6.2.3.2 Define stakeholder requirements. |
35 | 6.2.3.3 Analyze and maintain stakeholder requirements. |
37 | 6.3 Requirements analysis process 6.3.1 Purpose 6.3.2 Outcomes 6.3.3 Activities and tasks |
38 | 6.3.3.1 Define system requirements. |
40 | 6.3.3.2 Analyze and maintain system requirements. |
43 | 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 |
44 | 6.4.2 Requirements in verification 6.4.2.1 Plan verification |
45 | 6.4.2.2 Perform verification |
46 | 6.4.3 Requirements in validation 6.4.3.1 Plan validation 6.4.3.2 Perform validation |
47 | 6.5 Requirements management 6.5.1 Management Overview 6.5.2 Change management 6.5.2.1 Configuration management |
48 | 6.5.2.1.1 Plan configuration management 6.5.2.1.2 Perform configuration management |
49 | 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 |
50 | 6.5.3.1 Plan measurement |
51 | 6.5.3.2 Perform measurement 7 Information items |
52 | 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 |
53 | 8.3 System requirements specification document 8.3.1 Introduction |
54 | 8.3.2 SyRS example outline |
55 | 8.4 Software requirements specification document 8.4.1 Introduction 8.4.2 SRS example outline |
56 | 9 Information item content 9.1 Introduction 9.2 General content 9.2.1 Identification |
57 | 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 |
58 | 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 |
59 | 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 |
60 | 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 |
61 | 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 |
62 | 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 |
63 | 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 |
64 | 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 |
65 | 9.5.3.1 System interfaces 9.5.3.2 User interfaces 9.5.3.3 Hardware interfaces 9.5.3.4 Software interfaces |
66 | 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 |
67 | 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 |
68 | 9.5.10 External interfaces 9.5.11 Functions |
69 | 9.5.12 Usability requirements 9.5.13 Performance requirements 9.5.14 Logical database requirements |
70 | 9.5.15 Design constraints 9.5.16 Standards compliance 9.5.17 Software system attributes |
71 | 9.5.18 Verification 9.5.19 Supporting information |