Muutke küpsiste eelistusi

Requirements Engineering Fundamentals: A Study Guide for the Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant 2nd New edition [Pehme köide]

3.79/5 (140 hinnangut Goodreads-ist)
,
  • Formaat: Paperback / softback, 184 pages, kõrgus x laius x paksus: 234x184x13 mm, kaal: 378 g, 50+
  • Ilmumisaeg: 30-Apr-2015
  • Kirjastus: Rocky Nook
  • ISBN-10: 193753877X
  • ISBN-13: 9781937538774
Teised raamatud teemal:
Requirements Engineering Fundamentals: A Study Guide for the Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant 2nd New editionSuurem pilt
  • Formaat: Paperback / softback, 184 pages, kõrgus x laius x paksus: 234x184x13 mm, kaal: 378 g, 50+
  • Ilmumisaeg: 30-Apr-2015
  • Kirjastus: Rocky Nook
  • ISBN-10: 193753877X
  • ISBN-13: 9781937538774
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9781937538774.html
Märksõnad:

Requirements engineering tasks have become increasingly complex. In order to ensure a high level of knowledge and competency among requirements engineers, the International Requirements Engineering Board (IREB) developed a standardized qualification called the Certified Professional for Requirements Engineering (CPRE). The certification defines the practical skills of a requirements engineer on various training levels.

This book is designed for self-study and covers the curriculum for the Certified Professional for Requirements Engineering Foundation Level exam as defined by the IREB.

The 2nd edition has been thoroughly revised and is aligned with the curriculum Version 2.2 of the IREB. In addition, some minor corrections to the 1st edition have been included.

About IREB:The mission of the IREB is to contribute to the standardization of further education in the fields of business analysis and requirements engineering by providing syllabi and examinations, thereby achieving a higher level of applied requirements engineering.

The IRE Board is comprised of a balanced mix of independent, internationally recognized experts in the fields of economy, consulting, research, and science. The IREB is a non-profit corporation.

For more information visit www.certified-re.com.

Foreword v
With Contributions from vii
1 Introduction and Foundations 1(10)
1.1 Introduction
1(4)
1.1.1 Figures and Facts from Ordinary Projects
1(2)
1.1.2 Requirements Engineering - What Is It?
3(2)
1.1.3 Embedding Requirements Engineering into Process Models
5(1)
1.2 Fundamentals of Communication Theory
5(1)
1.3 Characteristics of a Requirements Engineer
6(2)
1.4 Requirement Types
8(1)
1.5 Importance and Categorization of Quality Requirements
9(1)
1.6 Summary
10(1)
2 System and Context Boundaries 11(8)
2.1 System Context
11(1)
2.2 Defining System and Context Boundaries
12(5)
2.2.1 Defining the System Boundary
13(2)
2.2.2 Defining the Context Boundary
15(2)
2.3 Documenting the System Context
17(1)
2.4 Summary
17(2)
3 Eliciting Requirements 19(14)
3.1 Requirements Sources
19(3)
3.1.1 Stakeholders and Their Significance
19(1)
3.1.2 Handling Stakeholders in the Project
20(2)
3.2 Requirements Categorization According to the Kano Model
22(2)
3.3 Elicitation Techniques
24(7)
3.3.1 Types of Elicitation Techniques
24(1)
3.3.2 Survey Techniques
25(1)
3.3.3 Creativity Techniques
26(2)
3.3.4 Document-centric Techniques
28(1)
3.3.5 Observation Techniques
29(1)
3.3.6 Support Techniques
30(1)
3.4 Summary
31(2)
4 Documenting Requirements 33(16)
4.1 Document Design
33(1)
4.2 Types of Documentation
34(3)
4.2.1 The Three Perspectives of Requirements
34(1)
4.2.2 Requirements Documentation using Natural Language
35(1)
4.2.3 Requirements Documentation using Conceptual Models
35(1)
4.2.4 Hybrid Requirements Documents
36(1)
4.3 Document Structures
37(3)
4.3.1 Standardized Document Structures
37(2)
4.3.2 Customized Standard Contents
39(1)
4.4 Using Requirements Documents
40(1)
4.5 Quality Criteria for Requirements Documents
41(2)
4.5.1 Unambiguity and Consistency
42(1)
4.5.2 Clear Structure
42(1)
4.5.3 Modifiability and Extendibility
42(1)
4.5.4 Completeness
42(1)
4.5.5 Traceability
43(1)
4.6 Quality Criteria for Requirements
43(2)
4.7 Glossary
45(2)
4.8 Summary
47(2)
5 Documenting Requirements in Natural Language 49(10)
5.1 Effects of Natural Language
49(4)
5.1.1 Nominalization
50(1)
5.1.2 Nouns without Reference Index
51(1)
5.1.3 Universal Quantifiers
51(1)
5.1.4 Incompletely Specified Conditions
52(1)
5.1.5 Incompletely Specified Process Verbs
53(1)
5.2 Requirement Construction using Templates
53(4)
5.3 Summary
57(2)
6 Model-Based Requirements Documentation 59(30)
6.1 The Term Model
59(3)
6.1.1 Properties of Models
60(1)
6.1.2 Modeling Languages
60(1)
6.1.3 Requirements Models
61(1)
6.1.4 Advantages of Requirements Models
61(1)
6.1.5 Combined Use of Models and Natural Language
62(1)
6.2 Goal Models
62(2)
6.2.1 Goal Documentation Using AND/OR Trees
63(1)
6.2.2 Example of AND/OR Trees
63(1)
6.3 Use Cases
64(6)
6.3.1 UML Use Case Diagrams
64(3)
6.3.2 Use Case Specifications
67(3)
6.4 Three Perspectives on the Requirements
70(1)
6.5 Requirements Modeling in the Data Perspective
71(5)
6.5.1 Entity-Relationship Diagrams
71(3)
6.5.2 UML Class Diagrams
74(2)
6.6 Requirements Modeling in the Functional Perspective
76(6)
6.6.1 Data Flow Diagrams
76(2)
6.6.2 Models of the Functional Perspective and Control Flow
78(1)
6.6.3 UML Activity Diagrams
79(3)
6.7 Requirements Modeling in the Behavioral Perspective
82(5)
6.7.1 Statecharts
83(1)
6.7.2 UML State Diagrams
84(3)
6.8 Summary
87(2)
7 Requirements Validation and Negotiation 89(22)
7.1 Fundamentals of Requirements Validation
89(1)
7.2 Fundamentals of Requirements Negotiation
90(1)
7.3 Quality Aspects of Requirements
91(3)
7.3.1 Quality Aspect "Content"
91(1)
7.3.2 Quality Aspect "Documentation"
92(1)
7.3.3 Quality Aspect "Agreement"
93(1)
7.4 Principles of Requirements Validation
94(3)
7.4.1 Principle 1: Involvement of the Correct Stakeholders
94(1)
7.4.2 Principle 2: Separating the Identification and the Correction of Errors
95(1)
7.4.3 Principle 3: Validation from Different Views
95(1)
7.4.4 Principle 4: Adequate Change of Documentation Type
96(1)
7.4.5 Principle 5: Construction of Development Artifacts
96(1)
7.4.6 Principle 6: Repeated Validation
96(1)
7.5 Requirements Validation Techniques
97(7)
7.5.1 Commenting
97(1)
7.5.2 Inspection
98(1)
7.5.3 Walk-Through
99(1)
7.5.4 Perspective-Based Reading
100(1)
7.5.5 Validation through Prototypes
101(2)
7.5.6 Using Checklists for Validation
103(1)
7.6 Requirements Negotiation
104(5)
7.6.1 Conflict Identification
105(1)
7.6.2 Conflict Analysis
105(1)
7.6.3 Conflict Resolution
106(2)
7.6.4 Documentation of the Conflict Resolution
108(1)
7.7 Summary
109(2)
8 Requirements Management 111(28)
8.1 Assigning Attributes to Requirements
111(4)
8.1.1 Attributes for Natural Language Requirements and Models
111(1)
8.1.2 Attribute Scheme
112(1)
8.1.3 Attribute Types of Requirements
113(2)
8.2 Views on Requirements
115(3)
8.2.1 Selective Views on the Requirements
115(2)
8.2.2 Condensed Views on the Requirements
117(1)
8.3 Prioritizing Requirements
118(4)
8.3.1 Method for Requirements Prioritization
118(1)
8.3.2 Techniques for Requirements Prioritization
119(3)
8.4 Traceability of Requirements
122(5)
8.4.1 Advantages of Traceable Requirements
122(1)
8.4.2 Purpose-Driven Definition of Traceability
123(1)
8.4.3 Classification of Traceability Relations
124(1)
8.4.4 Representation of Requirements Traceability
125(2)
8.5 Versioning of Requirements
127(4)
8.5.1 Requirements Versions
128(1)
8.5.2 Requirements Configurations
129(1)
8.5.3 Requirements Baselines
130(1)
8.6 Management of Requirements Changes
131(5)
8.6.1 Requirements Changes
131(1)
8.6.2 The Change Control Board
131(2)
8.6.3 The Change Request
133(1)
8.6.4 Classification of Incoming Change Requests
134(1)
8.6.5 Basic Method for Corrective and Adaptive Changes
134(2)
8.7 Measurement of Requirements
136(1)
8.7.1 Product vs. Process Metric
136(1)
8.7.2 Examples of Product and Process Metrics
136(1)
8.8 Summary
137(2)
9 Tool Support 139(10)
9.1 General Tool Support
139(1)
9.2 Modeling Tools
140(1)
9.3 Requirements Management Tools
141(2)
9.3.1 Specialized Tools for Requirements Management
142(1)
9.3.2 Standard Office Applications
142(1)
9.4 Introducing Tools
143(1)
9.5 Evaluating Tools
144(3)
9.5.1 Project View
145(1)
9.5.2 User View
146(1)
9.5.3 Product View
146(1)
9.5.4 Process View
146(1)
9.5.5 Provider View
146(1)
9.5.6 Technical View
147(1)
9.5.7 Economic View
147(1)
9.6 Summary
147(2)
References 149(8)
Index 157
Klaus Pohl holds a full professorship for Software Systems Engineering at the Institute for Computer Science and Business Information Systems (ICB) at University of Duisburg-Essen, Germany and an adjunct-professorship at the University of Limerick, Ireland. From 2005 to 2007 he acted as the funding scientific director of Lero, the Irish Software Engineering Research Centre. He received his Ph.D. and his habilitation in computer science from RWTH Aachen, Germany.

Pohl is author/coauthor of more than 250 peer-reviewed publications as well as several textbooks. As a consultant, assessor, and expert, he supports reputable companies, research institutions, and public funded research programs.

Chris Rupp - SOPHIST-in-chief (formally: founder and executive partner of the SOPHIST GmbH), chief consultant, coach and trainer.

Looking back over 25 years of professional experience, a lot has come up: a company... 6 books... 55 employees... countless articles and presentations... and a whole lot of experience. My passion for project consultation might account for the fact that, until now, I do not "only" manage, but I am still directly involved in projects and remain close to customers. What drives me is the vision to implement good ideas so that developers, contractual partners, and users-both direct and indirect-face an intelligent, sophisticated, and beneficial product. In doing so, I work with a range of methods and approaches in agile and non-agile environments. In order to standardize qualification for requirements engineers/business analysts, I founded the IREB e.V. (International Requirements Engineering Board). You can find further information on www.sophist.de.