Atjaunināt sīkdatņu piekrišanu

E-grāmata: Requirements Engineering

3.83/5 (12 ratings by Goodreads)
, ,
  • Formāts: PDF+DRM
  • Izdošanas datums: 23-Aug-2017
  • Izdevniecība: Springer International Publishing AG
  • Valoda: eng
  • ISBN-13: 9783319610733
Citas grāmatas par šo tēmu:
  • Formāts - PDF+DRM
  • Cena: 53,52 €*
  • * ši ir gala cena, t.i., netiek piemērotas nekādas papildus atlaides
  • Ielikt grozā
  • Pievienot vēlmju sarakstam
  • Šī e-grāmata paredzēta tikai personīgai lietošanai. E-grāmatas nav iespējams atgriezt un nauda par iegādātajām e-grāmatām netiek atmaksāta.
Requirements EngineeringPalielināt
  • Formāts: PDF+DRM
  • Izdošanas datums: 23-Aug-2017
  • Izdevniecība: Springer International Publishing AG
  • Valoda: eng
  • ISBN-13: 9783319610733
Citas grāmatas par šo tēmu:

DRM restrictions

  • Kopēšana (kopēt/ievietot):

    nav atļauts

  • Drukāšana:

    nav atļauts

  • Lietošana:

    Digitālo tiesību pārvaldība (Digital Rights Management (DRM))
    Izdevējs ir piegādājis šo grāmatu šifrētā veidā, kas nozīmē, ka jums ir jāinstalē bezmaksas programmatūra, lai to atbloķētu un lasītu. Lai lasītu šo e-grāmatu, jums ir jāizveido Adobe ID. Vairāk informācijas šeit. E-grāmatu var lasīt un lejupielādēt līdz 6 ierīcēm (vienam lietotājam ar vienu un to pašu Adobe ID).

    Nepieciešamā programmatūra
    Lai lasītu šo e-grāmatu mobilajā ierīcē (tālrunī vai planšetdatorā), jums būs jāinstalē šī bezmaksas lietotne: PocketBook Reader (iOS / Android)

    Lai lejupielādētu un lasītu šo e-grāmatu datorā vai Mac datorā, jums ir nepieciešamid Adobe Digital Editions (šī ir bezmaksas lietotne, kas īpaši izstrādāta e-grāmatām. Tā nav tas pats, kas Adobe Reader, kas, iespējams, jau ir jūsu datorā.)

    Jūs nevarat lasīt šo e-grāmatu, izmantojot Amazon Kindle.

Using the latest research and driven by practical experience from industry, this book gives useful hints to practitioners on how to write and structure requirements. It will benefit those seeking to develop their knowledge of requirements engineering process.



Written for those who want to develop their knowledge of requirements engineering process, whether practitioners or students.

Using the latest research and driven by practical experience from industry, Requirements Engineering gives useful hints to practitioners on how to write and structure requirements. It explains the importance of Systems Engineering and the creation of effective solutions to problems. It describes the underlying representations used in system modeling and introduces the UML2, and considers the relationship between requirements and modeling. Covering a generic multi-layer requirements process, the book discusses the key elements of effective requirements management. The latest version of DOORS (Version 7) - a software tool which serves as an enabler of a requirements management process - is also introduced to the reader here.

Additional material and links are available at: http://www.requirementsengineering.info

1 Introduction
1(32)
1.1 Introduction to Requirements
1(3)
1.2 Introduction to Systems Engineering
4(3)
1.3 Defining Requirements Engineering
7(3)
1.3.1 Definition of a Requirement
7(1)
1.3.2 Definition of a Stakeholder
8(1)
1.3.3 Definition of Requirements Engineering
9(1)
1.4 Requirements and Quality
10(1)
1.5 Requirements and the Lifecycle
11(3)
1.6 Requirements Tracing
14(4)
1.7 Requirements and Modelling
18(2)
1.8 Requirements and Testing
20(1)
1.9 Requirements in the Problem and Solution Domains
21(2)
1.10 Requirements and Design Agnosticism
23(6)
1.11 Requirements and Interfaces
29(1)
1.12 How to Read this Book
30(3)
2 A Generic Process for Requirements Engineering
33(24)
2.1 Introduction
33(1)
2.2 Developing Systems
33(3)
2.3 Generic Process Context
36(4)
2.3.1 Input Requirements and Derived Requirements
38(1)
2.3.2 Acceptance Criteria and Qualification Strategy
38(2)
2.4 Generic Process Introduction
40(3)
2.4.1 Ideal Development
40(1)
2.4.2 Development in the Context of Change
41(2)
2.5 Generic Process Information Model
43(6)
2.5.1 Information Classes
43(2)
2.5.2 Agreement State
45(1)
2.5.3 Qualification State
46(1)
2.5.4 Satisfaction State
47(1)
2.5.5 Information Model Constraints
48(1)
2.6 Generic Process Details
49(7)
2.6.1 Agree Requirements
49(2)
2.6.2 Analyse and Model
51(1)
2.6.3 Derive Requirements and Qualification Strategy
52(4)
2.7 Summary
56(1)
3 System Modelling for Requirements Engineering
57(36)
3.1 Introduction
57(1)
3.2 Representations for Requirements Engineering
58(10)
3.2.1 Data Flow Diagrams
58(6)
3.2.2 Entity-Relationship Diagrams
64(1)
3.2.3 Statecharts
65(1)
3.2.4 Object-Oriented Approaches
66(2)
3.3 Methods
68(23)
3.3.1 Viewpoint Methods
69(9)
3.3.2 Object-Oriented Methods
78(3)
3.3.3 The UML Notation
81(5)
3.3.4 SysML
86(3)
3.3.5 Formal Methods
89(2)
3.4 Model-Based Systems Engineering
91(1)
3.5 Modelling and Qualification
91(1)
3.6 Summary
92(1)
4 Writing and Reviewing Requirements
93(20)
4.1 Introduction
93(1)
4.2 Requirements for Requirements
94(1)
4.3 Structuring Requirements Documents
94(2)
4.4 Key Requirements
96(1)
4.5 Using Attributes
97(2)
4.5.1 Definition of a Requirement Expression
97(2)
4.6 Ensuring Consistency Across Requirements
99(1)
4.7 Value of a Requirement
100(1)
4.8 The Language of Requirements
101(2)
4.9 Requirement Boilerplates
103(2)
4.10 Granularity of Requirements
105(2)
4.11 Requirements and Modelling
107(1)
4.12 Criteria for Writing Requirements Statements
107(2)
4.13 Guide to Writing Requirements
109(2)
4.14 Summary
111(2)
5 Requirements Engineering in the Problem Domain
113(22)
5.1 What is the Problem Domain?
113(1)
5.2 Instantiating the Generic Process
114(2)
5.3 Agree Requirements with Customer
116(1)
5.4 Analyse & Model
116(6)
5.4.1 Identify Stakeholders
117(1)
5.4.2 Create Usage Model
118(4)
5.4.3 Scoping the System
122(1)
5.5 Derive Requirements
122(12)
5.5.1 Define Structure
122(4)
5.5.2 Capture Requirements
126(7)
5.5.3 Define Acceptance Criteria
133(1)
5.5.4 Define Qualification Strategy
133(1)
5.6 Summary
134(1)
6 Requirements Engineering in the Solution Domain
135(24)
6.1 What is the Solution Domain
135(2)
6.2 Engineering Requirements From Stakeholder Requirements to System Requirements
137(17)
6.2.1 Producing the System Model
137(2)
6.2.2 Creating System Models to Derive System Requirements
139(5)
6.2.3 Banking Example
144(3)
6.2.4 Car Example
147(5)
6.2.5 Deriving Requirements From a System Model
152(1)
6.2.6 Agreeing the System Requirements with the Design Team
153(1)
6.3 Engineering Requirements From System Requirements to Subsystems
154(2)
6.3.1 Creating a System Architecture Model
154(2)
6.3.2 Deriving Requirements From an Architectural Design Model
156(1)
6.4 Other Transformations Using a Design Architecture
156(1)
6.5 Summary
157(2)
7 Advanced Traceability
159(1)
7.1 Introduction
159(1)
7.2 Elementary Traceability
160(2)
7.3 Rationale
162(1)
7.4 Satisfaction Statements
162(1)
7.5 Rich Traceability
163(4)
7.6 Supporting Information and Evidence
167(2)
7.7 Sufficiency and Necessity
169(1)
7.8 Reviewing Traceability
170(1)
7.9 The Language of Satisfaction Statements
170(1)
7.10 Rich Traceability Analysis
170(2)
7.11 Requirements Flow-down
172(1)
7.12 Rich Traceability for Qualification
173(1)
7.13 Implementing Rich Traceability
174(1)
7.13.1 Single-layer Rich Traceability
174(1)
7.13.2 Multi-layer Rich Traceability
174(1)
7.14 Design Documents
175(4)
7.15 Metrics for Traceability
179(6)
7.15.1 Breadth
180(1)
7.15.2 Depth
181(1)
7.15.3 Growth
181(1)
7.15.4 Balance
182(1)
7.15.5 Latent Change
183(2)
7.16 Summary
185(2)
8 DOORS: A Tool to Manage Requirements
187(20)
8.1 Introduction
187(1)
8.2 The Case for Requirements Management
188(1)
8.3 DOORS Information Model
188(1)
8.4 The Project Area
189(2)
8.5 Modules as Documents
191(1)
8.6 Artifacts
192(2)
8.7 Traceability Links
194(2)
8.8 Views
196(5)
8.8.1 Rows in Views
197(2)
8.8.2 Columns in Views
199(2)
8.9 Artifact Types and Attributes
201(4)
8.10 Import and Export
205(1)
8.11 Summary
206(1)
9 Management Aspects of Requirements Engineering
207
9.1 Introduction to Management
207(1)
9.2 Requirements Management Problems
208(2)
9.2.1 Summary of Requirement Management Problems
210(1)
9.3 Managing Requirements in an Acquisition Organisation
210(5)
9.3.1 Planning
210(3)
9.3.2 Monitoring
213(1)
9.3.3 Changes
213(2)
9.4 Supplier Organisations
215(6)
9.4.1 Bid Management
215(4)
9.4.2 Development
219(2)
9.5 Product Organisations
221(6)
9.5.1 Planning
221(4)
9.5.2 Monitoring
225(1)
9.5.3 Changes
226(1)
9.6 Agile Development
227(1)
9.7 Organisational Culture
228(1)
9.8 Summary
229
9.8.1 Planning
229(1)
9.8.2 Monitoring
230(1)
9.8.3 Changes
230(1)
9.8.4 Organisational Culture
230
Erratum to: Requirements Engineering 1(230)
Bibliography 231(4)
Index 235
Jeremy Dick has been consulting in tool-supported requirements processes for over 20 years, across a wide range of sectors in the UK and elsewhere, most recently in the Civil Nuclear and Oil & Gas industries. A past chairman of the INCOSE International Requirements Working Group, he has contributed to the development of the discipline, particularly with regard to traceability.

Elizabeth Hull is Professor Emerita of Computing Science at Ulster University. She has published extensively on software engineering and requirements engineering. She is a Chartered IT Professional and an Honorary Fellow of the BCS, The Chartered Institute for IT. 





Ken Jackson has over 40 years experience in the development of real time systems. For 16 years he worked as a requirements management consultant in a wide set of domains including defence, automotive, aerospace and telecommunications. He has contributed to INCOSE and is a founder member of the IEEEcommittee on ECBS (Engineering of Computer Based Systems).
Biežāk uzdotie jautājumi par e-grāmatām Biežāk uzdotie jautājumi par e-grāmatām
Permanent link: https://www.kriso.lv/db/97833196107332e.html
Keywords: