Requirements engineering from system goals to UML models and software specifications
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Chichester
Wiley
2009
|
| Schlagworte: | |
| Online-Zugang: | Inhaltsverzeichnis |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV022585637 | ||
| 003 | DE-604 | ||
| 005 | 20141118 | ||
| 007 | t| | ||
| 008 | 070816s2009 xx |||| 00||| eng d | ||
| 020 | |a 9780470012703 |9 978-0-470-01270-3 | ||
| 035 | |a (OCoLC)634978560 | ||
| 035 | |a (DE-599)BVBBV022585637 | ||
| 040 | |a DE-604 |b ger |e rakwb | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-703 |a DE-91G |a DE-706 |a DE-859 |a DE-861 |a DE-11 |a DE-M347 |a DE-384 |a DE-573 |a DE-1049 |a DE-739 | ||
| 084 | |a ST 230 |0 (DE-625)143617: |2 rvk | ||
| 084 | |a ST 237 |0 (DE-625)143623: |2 rvk | ||
| 084 | |a DAT 335f |2 stub | ||
| 100 | 1 | |a Van Lamsweerde, Axel |e Verfasser |4 aut | |
| 245 | 1 | 0 | |a Requirements engineering |b from system goals to UML models and software specifications |c Axel van Lamsweerde |
| 264 | 1 | |a Chichester |b Wiley |c 2009 | |
| 300 | |a XXIX, 682 S. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 500 | |a Hier auch später erschienene, unveränderte Nachdrucke | ||
| 650 | 0 | 7 | |a Requirements engineering |0 (DE-588)4213997-1 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Requirements engineering |0 (DE-588)4213997-1 |D s |
| 689 | 0 | |5 DE-604 | |
| 856 | 4 | 2 | |m Digitalisierung UB Bayreuth |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=015791827&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-015791827 | |
Datensatz im Suchindex
| DE-BY-TUM_call_number | 0102 DAT 335f 2009 A 1920 0104 DAT 335f 2009 A 1920 0303 DAT 335f 2009 L 254 |
|---|---|
| DE-BY-TUM_katkey | 1665073 |
| DE-BY-TUM_location | 01 03 |
| DE-BY-TUM_media_number | 040010146402 040010146479 040071405357 040071405346 040071405380 040071405368 040071405379 040071299051 040071299062 040071299073 040071299084 040071280210 040071280221 040071280232 040071299095 |
| _version_ | 1820896018368036864 |
| adam_text | Foreword
xvii
Preface
xxi
Part I Fundamentals of Requirements Engineering
1
1
Setting the Scene
3
1.1
What is requirements engineering?
3
1.1.1
The problem world and the machine solution
4
1.1.2
Introducing our running case studies
6
1.1.3
The WHY. WHAT and WHO dimensions of requirements engineering
12
1.1.-4
Types of statements involved in requirements engineering
17
1.1.5
Categories of requirements
23
1.1.6
The requirements lifecycle: Processes, actors and products
30
1.1.
Target qualities and defects to avoid
35
1.1.8
Type·, of software projects
40
1.1.9
Requirements in the software lifecycle
42
1.1.10
The relationship of requirements engineering to other disciplines
45
12
Why engineer requirements?
4
1.2.1
Facts, data and citations about the requirements problem -p
1.2.2
The role and stakes of requirements engineering
51
І.З
Obstacles to good requirements engineering practice
52
1
-i Agile development processes and requirements engineering
53
Summan
55
Xotes
and Further Reading
56
Exercises
58
Contents
Domain
Understanding and Requirements Elicitation 6l
2.1
Identifying stakeholders and interacting with them
62
2.2
Artefact-driven elicitation techniques
64
2.2.1
Background study
64
2.2.2
Data collection
65
2.2.3
Questionnaires
65
2.2.4
Repertory grids and card sorts for concept-driven acquisition
66
2.2.5 Storyboards
and scenarios for problem world exploration
67
2.2.6
Mock-ups and prototypes for early feedback
70
2.2.7
Knowledge reuse
72
2.3
Stakeholder-driven elicitation techniques
76
2.3.1
Interviews
77
2.3.2
Observation and ethnographic studies
79
2.3.3
Group sessions
80
2.4
Conclusion
81
Summary
82
Notes and Further Reading
84
Exercises
85
Requirements Evaluation
87
3· 1
Inconsistency management
88
3.11
Types of inconsistency
88
3.1.2
Handling inconsistencies
89
3.1.3
Managing conflicts: A systematic process
90
$.2
Risk analysis
93
32.1
Types of risk
9-4
3.2.2
Risk management
95
3.2.3
Risk documentation
101
3.2.4
Integrating risk management in the requirements lifecycle
102
33
Evaluating alternative options for decision making
105
3-4
Requirements pnoritization
108
З- 1
Conclusion
112
Summan
) 13
Notes ami Further Raiding II4
Exercises
1
id
Requirements Specification and Documentation
119
4 1
Free documentation in unrestricted natural language
120
4.2
¡Disciplined documentation in structured natural language
121
4.2.1
Local rules on writing statements
121
4.2.2
Global rules on organizing the requirements document
124
Contents ix
4.3
Use of diagrammatic
notations
127
4.3.1
System scope: context, problem and frame diagrams
127
4.3.2
Conceptual structures: entity-relationship diagrams
130
4.3.3
Activities and data: SADT diagrams
133
4.3.4
Information flows: dataflow diagrams
134
4.3.5
System operations: use case diagrams
136
4.3.6
Interaction scenarios: event trace diagrams
136
4.3.7
System behaviours: state machine diagrams
138
4.3.8
Stimuli and responses: R-net diagrams
Ы2
4.3.9
Integrating multiple system views and multiview specification in UML
1ч2
4.3.10
Diagrammatic notations: Strengths and limitations I44
4.4
Formal specification
1-45
4.4.1
Logic as a basis for formalizing statements I46
4.4.2
History-based specification
151
4.4.3
State-based specification
155
4.4.4
Event-based specification
163
4.4.5
Algebraic specification
167
4.4.6
Other specification paradigms
~Ί
4.4.7
Formal specification: strengths and limitations
173
4.5
Conclusion 1~4
Summary
1^6
Notes and Further Reading
179
Exercises
183
Requirements Quality Assurance
187
5.1
Requirements inspections and reviews
188
5.1.1
The requirements inspection process
188
5.1.2
Inspection guidelines
190
5.1.3 Requirements inspection checklists
191
5.1.4
Conclusion
195
5.2
Queries on a requirements database 19d
5.3
Requirements validation by specification animation
198
Ť.3.I
Extracting an executable model from the specification
199
5.3.2
Simulating the model i -w
·!.3
Visualizing the simulation
200
^.3
t
Conclusion
200
5.4
Requirements verification through formal checks
202
5.4.1
Language checks
202
5.4.2
Dedicated consistency and completeness checks
203
5.4.3
Model checking
205
5.4.4
Theorem proving
208
Contents
5.5
Conclusion
211
Summan
213
Notes
and Further Reading
2.1
-і
Exercises
217
6
Requirements Evolution
219
6.1
The time-space dimensions of evolution: Revisions and variants
220
6.2
Change anticipation
223
6.3
Traceability management for evolution support
225
6.3.1
Traceability links
226
6.3-2
The traceability management process, its benefits and cost
233
6-3.3
Traceability management techniques
237
6.3.4
Determining an adequate cost-benefit trade-off for traceability
management
244
6.4
Change control
246
6.4.1
Change initiation
24?
6.4.2
Change evaluation and prioritization
248
6.4.3
Change consolidation
249
6.5
Runtime monitoring of requirements and assumptions for dynamic change
249
6.6
Conclusion
251
Summan
252
Notes and Further Reading
254
Exercises
256
7
Goal Orientation in Requirements Engineering
259
~.l What are goals?
260
~
.2
The granularity of goals and their relationship to requirements and
assumptions
261
.3
Goal types and categories
265
.3.1
Types of goal· behavioural goals vs soft goals
265
.3 2
Goal categories: Functional vs non-functional goals
269
~a The central role of goals in the requirements engineering process 2~2
5
Where are goals coming from?
2
.6
The relationship ot goals to other requirements-related products and
processes
2Гь
.6.1
Goals and scenarios 2~<^
.6.2
Intentional and operational specifications
2
A3
Goals and use cases 2~~
7.6.4
Goals and model-checked properties 2~*7
7.6.5
Goal orientation and agent orientation
278
7.6.6
Goal orientation and object orientation
278
7.6.7
Goal orientation and top-down analysis
2 ľ9
Contents xi
S
Limma
ry
279
Notes
and Further Reading
280
Exercises
283
Part II Building System Models for Requirements Engineering
287
8
Modelling System Objectives with Goal Diagrams
293
8.1
Goal features as model annotations
294
8.2
Goal refinement 297
8.3
Representing conflicts among goals
301
8.4
Connecting the goal model with other system views
302
8.5
Modelling alternative options
303
8.5.1
Alternative goal refinements 30-i
8.5.2
Alternative responsibility assignments
305
8.6
Goal diagrams as AND/OR graphs
ЗСГ
8.7
Documenting goal refinements and assignments with annotations
308
8.8
Building goal models: Heuristic rules and reusable patterns
309
8.8.1
Eliciting preliminary goals
309
8.8.2
Identifying goals along refinement branches
311
8.8.3
Delimiting the scope of the goal model
316
8.8.4
Avoiding common pitfalls
317
8.8.5
Reusing refinement patterns
319
8.8.6
Reusing refinement trees associated with goal categories
326
Summary
328
Notes and Further Reading
329
Exercises
331
9
Anticipating What Could Go Wrong: Risk Analysis on Goal Models
335
9.1
Goal obstaiction by obstacles
336
9.1.1
What are obstacles?
336
9.1.2
Completeness of a set of obstacles 33~
9.1.3
Obstacle categories
338
9.2
Modelling obstacles
339
ιλ2.1
Obstacle diagrams 33l)
9.2.2
Conditions on obstacle refinement
3-łl
9.2.3
Bottom-up propagation ot obstructions in goal AND-refinements
342
9.2.4
Annotating obstacle diagrams
343
9.3
Obstacle analysis for a more robust goal model
344
9.3.1
Identifying obstacles
344
9.3-2
Evaluating obstacles
349
9-3-3
Resolving obstacles in a modified goal model 3-t9
Summan
353
Contents
Xotes
and Further Reading
355
Exercises
356
10
Modelling Conceptual Objects with Class Diagrams
359
10.1
Representing domain concepts by conceptual objects
360
10.1.1
What are conceptual objects?
360
10.1.2
Object instantiation: classes and current instances
361
10.1.3
Types of conceptual object
362
10.1.4
Object models as UML class diagrams
363
10.1.5
Object features as model annotations
364
10.2
Entities
366
10.3
Associations
366
10.4
Attributes 3~1
10.5
Built-in associations for structuring object models
373
10.5.1
Object specialization
373
10.5.2
Object aggregation
376
10.6
More on class diagrams 377
10.6.1
Derived attributes and associations
3^
10.6.2
OR-associations
378
10.6.3
Ordered associations
379
10.6.4
Associations of associations
379
10.
^ Heuristic rules for building object models
380
10.
.I Deriving pertinent and complete class diagrams from goal diagrams
380
10. .2
Object or attribute?
38-4
10.~ 3 Entity, association, agent or event?
384
10Л4
Attribute of a linked object or of the linking association?
385
10. .5
Aggregation or association?
386
10.
Тб
Specializing and generalizing concepts
386
10,
Avoiding common pitfalls
38
tummar.
389
Note- and Further Rtudmg 3C)1
11
Modelling System Agents and Responsibilities
395
11.1
What are agents 30h
11.2
Characterizing system agenb /W~
11.2.1
Basic features
39
11.2.2
Agent capabilities
39
11.2.3
Agent responsibilities and goal realizability
399
11.2.4
Agents as operation performers 4OI
11.2.5
Agent wishes and beliefs
402
11.2.6
Agent dependencies
4ОЗ
Contents
11.3
Representing agent models
405
11.3-1
Agent
diagrams and
instance
declarations t()5
11.3-2
Context diagrams
Ю6
11.3-3
Dependency diagrams 4()~
11.4
Refinement of abstract agents
4O8
11.5
Building agent models til
11.5.1
Heuristics for building agent diagrams from goal models
-tl
1
11.5.2
Generating context diagrams from goal models
1
1
3
Summary
1
15
Notes and Further Reading tf
Kxercises -j
18
12
Modelling System Operations
421
12.1
What are operations? i22
12.2
Characterizing system operations
425
12.2.1
Basic features
425
12.2.2
Operation signature
425
12.2.3
Domain
pre-
and post-conditions +2d
12.2.4
Operation performer t2~
12.3
Goal operationalization
+2
12.3-1
Required
pre-,
post- and trigger conditions for goal satisfaction -il~
12.3-2
Agent commitments
130
12.З.З
Goal operationalization and satisfaction arguments -j32
12.4
Goals, agents, objects and operations: The semantic picture
13
4
12.5
Representing operation models
435
12.5.1
Operationalization diagrams 43s
12.5.2
UML use case diagrams i3^
12.6
Building operation models
ł3~
12.6.1
Heuristics for building operationalization diagrams
43
12.6.2
Generating use case diagrams from operationalization diagrams
ні
Summary tt2
Notes and l- unher Reading
ш
l- el !s<.-n t4^
13
Modelling System Behaviours
13 1
Modelling instance behaviours
-õo
13-1-1
Scenarios as UML sequence diagrams
ł5()
13-1-2
Scenario refinement: Episodes and agent decomposition
i52
13.2
Modelling class behaviours
454
I3.2.I State machines as UML state diagrams
455
13-2.2
State machine refinement: Sequential and concurrent sub-states
-ñy
13.3
Building behaviour models
46З
13-3-1 Elaborating relevant scenarios for good coverage
465
xiv Contents
13.3.2
Decorating scenarios with state conditions
4б.;
13.3.3
From scenarios to state machines
469
13.3.4
From scenarios to goals
4 3
13.3.5
From operationalized goals to state machines 4 5
Summan.· 4^
Notes and Further Reading
^80
Exercises 481
14
Integrating Multiple System Views
485
14.1
A meta-model for view integration -t85
14.1.1
Overall structure of the meta-model
48
14.1.2
The goal meta-model
-188
14.1.3
The object meta-model
489
14.1.4
The agent meta-model
490
14.1.5
The operation meta-model
491
14.1.6
The behaviour meta-model
492
14.2
Inter-view consistency
mies
493
14.3
Grouping related view- fragments into packages
496
Summary
498
Notes and Further Reading
498
Exercises
499
15
A Goal-Oriented Model-Building Method in Action
501
15.1
Modelling the system-as-is
503
15.1.1
Step
1:
Build a preliminary goal model illustrated by scenarios
503
1^.1.2
Step
2:
Derive a preliminary object model
506
15.2
Modelling the system-to-be
50
15.2.1
Step
3:
Update the goal model with new goals illustrated by scenarios
50
1^.2.2
Step
4:
Derive the updated object model
510
15.2.3
Step
5:
Analyse obstacles, threats and conflicts
512
15.2.4
Мер
(v
Analyse responsibilities and build the agent model
515
1^.2.5
Step
■
Make choices among alternative options
51
15.2.(i Step S: Operationalize goab in the operation model Sis
15.2.
Step
9:
Build and analyse the behaviour model
521
15.3
Handling model variants for product
Unes
524
Summan,
52S
Notc^
and Further Reading
524
Fxcravcs
529
Part
ΙΠ
Reasoning About System Models
535
16
Semi-Formal Reasoning for Model Analysis and Exploitation
537
16.1
Query-based analysis of the model database
5З8
Contents xv
16.1.1
Checking the structural consistency and completeness of the model
538
16.1.2 Generation of other views for dedicated analyses
540
16.1.3
Traceability management
540
16.1.4 Analogical model reuse
541
16.2 Semi-formal analysis of goal-oriented models
544
16.2.1 Conflict analysis
5-м
16.2.2 Heuristic identification of obstacles
549
16.2.3
Threat analysis: From goal models to anti-goal models
551
16.3 Reasoning about alternative options 55T
16.3.1 Qualitative reasoning about alternatives
557
16.3.2
Quantitative reasoning about alternatives
560
16.4 Model-driven generation of the requirements document
562
16.5 Beyond RE: From goal-oriented requirements to software architecture
566
16.5.1 Deriving a software data architecture from the object model 567
16.5.2 Deriving an abstract dataflow architecture from the agent and oper¬
ation models
568
16.5.3
Selecting an architectural style from architectural requirements 5~0
16.5.4
Architectural refinement from quality requirements
5~Ί
Summary
574
Notes and Further Reading
576
Exercises
578
17
Formal Specification of System Models
583
17.1
A real-time temporal logic for specifying model annotations
584
17.1.1
State assertions
584
17.1.2
Temporal assertions
585
17.1.3
Real-time temporal constructs
586
17.2
Specifying goals in the goal model
588
17.3
Specifying descriptive properties in the object model
592
I 7.
4
Specifying operationalizations in the operation model
594
I7.
5
Back to the system s semantic picture
^96
Summan
^98
Note-
лпЛ
Further Re.iding ^L>9
18
Formal Reasoning for Specification Construction and Analysis
6ОЗ
18.1
Checking goal refinements
604
18.1.1
Using a theorem
prover 6O4
18.1.2
Formal refinement patterns
6O4
18.1.3
Using bounded SAT solvers
608
18.2
Deriving goal operationalizations
609
18.2.1
Using bounded SAT solvers
610
Contents
18.2.2 Formal operationalization
patterns
610
18.3
Generating obstacles for risk analysis 6l3
18.3-І
Regressing obstructions through domain properties
614
І8.З.2
Using formal obstruction patterns
617
18.4
Generating anti-goals for security analysis 6I8
18.4.1
Specifying security goals 6I8
18.4.2
Identifying security goals and initial anti-goals
620
18.4.3
Refining anti-goals
621
18.5
Formal conflict analysis
622
18.5.1
Deriving boundary conditions for conflict
623
18.5.2
Formal resolution of divergences
625
18.6
Synthesizing behaviour models for animation and model checking
627
18.6.1
Goal-driven model synthesis
628
18.6.2
Scenario-driven model synthesis
628
Summary
635
Notes and Further Reading
636
Exercises
637
Bibliography
641
Index
669
|
| any_adam_object | 1 |
| author | Van Lamsweerde, Axel |
| author_facet | Van Lamsweerde, Axel |
| author_role | aut |
| author_sort | Van Lamsweerde, Axel |
| author_variant | l a v la lav |
| building | Verbundindex |
| bvnumber | BV022585637 |
| classification_rvk | ST 230 ST 237 |
| classification_tum | DAT 335f |
| ctrlnum | (OCoLC)634978560 (DE-599)BVBBV022585637 |
| discipline | Informatik |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01443nam a2200349 c 4500</leader><controlfield tag="001">BV022585637</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20141118 </controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">070816s2009 xx |||| 00||| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780470012703</subfield><subfield code="9">978-0-470-01270-3</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)634978560</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV022585637</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-703</subfield><subfield code="a">DE-91G</subfield><subfield code="a">DE-706</subfield><subfield code="a">DE-859</subfield><subfield code="a">DE-861</subfield><subfield code="a">DE-11</subfield><subfield code="a">DE-M347</subfield><subfield code="a">DE-384</subfield><subfield code="a">DE-573</subfield><subfield code="a">DE-1049</subfield><subfield code="a">DE-739</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 230</subfield><subfield code="0">(DE-625)143617:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 237</subfield><subfield code="0">(DE-625)143623:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">DAT 335f</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Van Lamsweerde, Axel</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Requirements engineering</subfield><subfield code="b">from system goals to UML models and software specifications</subfield><subfield code="c">Axel van Lamsweerde</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Chichester</subfield><subfield code="b">Wiley</subfield><subfield code="c">2009</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXIX, 682 S.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Hier auch später erschienene, unveränderte Nachdrucke</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Requirements engineering</subfield><subfield code="0">(DE-588)4213997-1</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">Digitalisierung UB Bayreuth</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=015791827&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-015791827</subfield></datafield></record></collection> |
| id | DE-604.BV022585637 |
| illustrated | Not Illustrated |
| indexdate | 2024-12-23T20:09:16Z |
| institution | BVB |
| isbn | 9780470012703 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-015791827 |
| oclc_num | 634978560 |
| open_access_boolean | |
| owner | DE-703 DE-91G DE-BY-TUM DE-706 DE-859 DE-861 DE-11 DE-M347 DE-384 DE-573 DE-1049 DE-739 |
| owner_facet | DE-703 DE-91G DE-BY-TUM DE-706 DE-859 DE-861 DE-11 DE-M347 DE-384 DE-573 DE-1049 DE-739 |
| physical | XXIX, 682 S. |
| publishDate | 2009 |
| publishDateSearch | 2009 |
| publishDateSort | 2009 |
| publisher | Wiley |
| record_format | marc |
| spellingShingle | Van Lamsweerde, Axel Requirements engineering from system goals to UML models and software specifications Requirements engineering (DE-588)4213997-1 gnd |
| subject_GND | (DE-588)4213997-1 |
| title | Requirements engineering from system goals to UML models and software specifications |
| title_auth | Requirements engineering from system goals to UML models and software specifications |
| title_exact_search | Requirements engineering from system goals to UML models and software specifications |
| title_full | Requirements engineering from system goals to UML models and software specifications Axel van Lamsweerde |
| title_fullStr | Requirements engineering from system goals to UML models and software specifications Axel van Lamsweerde |
| title_full_unstemmed | Requirements engineering from system goals to UML models and software specifications Axel van Lamsweerde |
| title_short | Requirements engineering |
| title_sort | requirements engineering from system goals to uml models and software specifications |
| title_sub | from system goals to UML models and software specifications |
| topic | Requirements engineering (DE-588)4213997-1 gnd |
| topic_facet | Requirements engineering |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=015791827&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT vanlamsweerdeaxel requirementsengineeringfromsystemgoalstoumlmodelsandsoftwarespecifications |