Domain architectures : models and architectures for UML applications

Select an Action

Place Hold(s)
Add to My Lists
Email
Print

Title:

Personal Author:

Duffy, Daniel J.

Publication Information:

Chichester, West Sussex : John Wiley & Sons, 2004

ISBN:

9780470848333

Subject Term:

Computer software -- Development

Business -- Data processing

UML (Computer science)

Available:*

Library	Item Barcode	Call Number	Material Type	Item Category 1	Status
Searching... PSZ JB	30000010070440	QA76.76.D47 D83 2004	Open Access Book	Book	Searching... Unknown

Domain Architectures is a comprehensive catalog of the domain architectures essential to software developers using object-oriented technology and UML to solve real-life problems. Providing a unique top-down view of systems, the book also provides quick access to landmarks and references to domain architectures. The ability to describe applications, in terms of the properties they share, offers software designers a vast new landscape for implementing software reuse. The ideal professional's handbook. Helps readers reduce trial and error and increase productivity by reusing tried and trusted ideas Models are described and documented using UML (incorporating UML 2.0) models and meta models

Author Notes

Daniel Duffy is founder of Datasim, a company that has provided training and consultancy in object-oriented technology areas since 1987. He is also the author of "From Chaos to Classes". He resides in Amsterdam, Netherlands.

Preface	p. xv
Part I Background and fundamentals	p. 1
1. Introducing and motivating domain architectures	p. 3
1.1 What is this book?	p. 3
1.2 Why have we written this book?	p. 4
1.3 For whom is this book intended?	p. 5
1.4 Why should I read this book?	p. 5
1.5 What is a domain architecture, really?	p. 5
1.6 The Datasim Development Process (DDP)	p. 8
1.7 The structure of this book	p. 9
1.8 What this book does not cover	p. 10
2. Domain architecture catalogue	p. 11
2.1 Introduction and objectives	p. 11
2.2 Management Information Systems (MIS) (Chapter 5)	p. 13
2.3 Process Control Systems (PCS) (Chapter 6)	p. 16
2.4 Resource Allocation and Tracking (RAT) systems (Chapter 7)	p. 18
2.5 Manufacturing (MAN) systems (Chapter 8)	p. 19
2.6 Access Control Systems (ACS) (Chapter 9)	p. 20
2.7 Lifecycle and composite models (Chapter 10)	p. 21
3. Software lifecycle and Datasim Development Process (DDP)	p. 23
3.1 Introduction and objectives	p. 23
3.2 The Software Lifecycle	p. 24
3.3 Reducing the scope	p. 25
3.4 The requirements/architecture phase in detail	p. 29
3.5 The object-oriented analysis process	p. 30
3.6 Project cultures and DDP	p. 33
3.6.1 Calendar-driven projects	p. 34
3.6.2 Requirements-driven projects	p. 34
3.6.3 Documentation-driven style	p. 35
3.6.4 Quality-driven style	p. 36
3.6.5 Architecture-driven style	p. 36
3.6.6 Process-driven style and the DDP	p. 37
3.7 Summary and conclusions	p. 38
4. Fundamental concepts and documentation issues	p. 41
4.1 Introduction and objectives	p. 41
4.2 How we document domain architectures	p. 43
4.3 Characteristics of ISO 9126 and its relationship with domain architectures	p. 44
4.4 Documenting high-level artefacts	p. 48
4.5 Goals and core processes	p. 48
4.6 System context	p. 50
4.7 Stakeholders and viewpoints	p. 50
4.7.1 Documenting viewpoints	p. 52
4.8 Documenting requirements	p. 54
4.9 Defining and documenting use cases	p. 54
4.10 Summary and conclusions	p. 55
Appendix 4.1 A critical look at use cases	p. 55
Part II Domain architectures (meta models)	p. 57
5. Management Information Systems (MIS)	p. 59
5.1 Introduction and objectives	p. 59
5.2 Background and history	p. 59
5.3 Motivational examples	p. 61
5.3.1 Simple Digital Watch (SDW)	p. 61
5.3.2 Instrumentation and control systems	p. 62
5.4 General applicability	p. 63
5.5 Goals, processes and activities	p. 64
5.6 Context diagram and system decomposition	p. 65
5.7 Stakeholders, viewpoints and requirements	p. 67
5.8 UML classes	p. 69
5.9 Use cases	p. 70
5.10 Specializations of MIS systems	p. 71
5.10.1 Example: Noise control engineering	p. 72
5.11 Using MIS systems with other systems	p. 74
5.12 Summary and conclusions	p. 76
6. Process Control Systems (PCS)	p. 77
6.1 Introduction and objectives	p. 77
6.2 Background and history	p. 78
6.3 Motivational examples	p. 78
6.3.1 Simple water level control	p. 79
6.3.2 Bioreactor	p. 80
6.3.3 Barrier options	p. 81
6.4 Reference models for Process Control Systems	p. 83
6.4.1 Basic components and variables	p. 83
6.4.2 Control engineering fundamentals	p. 86
6.5 General applicability	p. 88
6.6 Goals, processes and activities	p. 89
6.7 Context diagram and system decomposition	p. 90
6.7.1 Decomposition strategies	p. 91
6.8 Stakeholders, viewpoints and requirements	p. 96
6.8.1 Input and output variable completeness	p. 97
6.8.2 Robustness criteria	p. 97
6.8.3 Timing	p. 98
6.8.4 Human--Computer Interface (HCI) criteria	p. 100
6.8.5 State completeness	p. 100
6.8.6 Data age requirement	p. 101
6.9 UML classes	p. 101
6.10 Use cases	p. 102
6.11 Specializations of PCS systems	p. 105
6.11.1 Multi-level architectures	p. 105
6.12 Using PCS systems with other systems	p. 106
6.13 Summary and conclusions	p. 107
Appendix 6.1 Message patterns in Process Control Systems	p. 108
7. Resource Allocation and Tracking (RAT) systems	p. 111
7.1 Introduction and objectives	p. 111
7.2 Background and history	p. 112
7.3 Motivational examples	p. 112
7.3.1 Help Desk System (HDS)	p. 113
7.3.2 Discrete manufacturing	p. 115
7.4 General applicability	p. 117
7.5 Goals, processes and activities	p. 118
7.6 Context diagram and system decomposition	p. 118
7.7 Stakeholders, viewpoints and requirements	p. 120
7.8 UML classes	p. 121
7.9 Use cases	p. 123
7.10 Specializations of RAT systems	p. 124
7.11 Using RAT systems with other systems	p. 125
7.12 Summary and conclusions	p. 126
8. Manufacturing (MAN) systems	p. 127
8.1 Introduction and objectives	p. 127
8.2 Background and history	p. 128
8.3 Motivational examples	p. 130
8.3.1 Compiler theory	p. 130
8.3.2 Graphics applications	p. 132
8.3.3 Human memory models	p. 134
8.4 General applicability	p. 137
8.5 Goals, processes and activities	p. 138
8.6 Context diagram and system decomposition	p. 138
8.7 Stakeholders, viewpoints and requirements	p. 139
8.7.1 Stakeholders and viewpoints	p. 139
8.7.2 Requirements	p. 140
8.8 UML classes	p. 141
8.9 Use cases	p. 142
8.10 Specializations of MAN systems	p. 143
8.11 Using MAN systems with other systems	p. 144
8.12 Summary and conclusions	p. 144
9. Access Control Systems (ACS)	p. 147
9.1 Introduction and objectives	p. 147
9.2 Background and history	p. 148
9.3 Motivational examples	p. 148
9.3.1 The Reference Monitor model	p. 148
9.4 General applicability	p. 152
9.5 Goals, processes and activities	p. 152
9.6 Context diagram and system decomposition	p. 153
9.7 Stakeholders, viewpoints and requirements	p. 154
9.8 UML classes	p. 155
9.9 Use cases	p. 155
9.10 Specializations of ACS	p. 157
9.10.1 Security models for Web-based applications	p. 157
9.10.2 Access control during design: the Proxy pattern	p. 159
9.11 Using ACS with other systems	p. 162
10. Lifecycle and composite models	p. 163
10.1 Introduction and objectives	p. 163
10.2 Background and history	p. 164
10.3 Motivational example: the Rent-a-machine system	p. 164
10.4 General applicability	p. 168
10.5 Goals, processes and activities	p. 170
10.6 Context diagram and system decomposition	p. 171
10.7 Stakeholders, viewpoints and requirements	p. 171
10.8 UML classes	p. 172
10.9 Use cases	p. 173
10.10 Specializations of LCM	p. 174
10.11 Using LCM systems with other systems	p. 174
10.12 Summary and conclusions	p. 175
Part III Applications (models)	p. 177
11. Project resource management system: Manpower Control (MPC) system	p. 179
11.1 Introduction and objectives	p. 179
11.2 Description and scope of problem	p. 180
11.3 Core processing and context diagram	p. 181
11.4 Requirements and use case analysis	p. 183
11.4.1 Functional requirements and use cases	p. 183
11.4.2 Non-functional requirements	p. 186
11.5 Validating use cases	p. 187
11.6 Class architecture	p. 189
11.7 Generalizations	p. 192
11.8 Summary and conclusions	p. 192
12. Home Heating System (HHS)	p. 193
12.1 Introduction and objectives	p. 193
12.2 Background and history	p. 194
12.2.1 Hatley-Pirbhai	p. 194
12.2.2 The Booch approach	p. 197
12.3 Description of problem	p. 197
12.4 Goals, processes and context	p. 197
12.5 System decomposition and PAC model	p. 200
12.6 Viewpoints and requirements analysis	p. 201
12.7 Use cases	p. 202
12.8 Validation efforts	p. 207
12.9 Creating statecharts	p. 209
12.10 Generalization efforts	p. 212
12.11 Summary and conclusions	p. 213
13. Elevator Control System (ELS)	p. 215
13.1 Introduction and objectives	p. 215
13.2 Domain categories and ELS	p. 216
13.3 A traditional object-oriented requirement specification	p. 217
13.4 Re-engineering ELS: goals and processes	p. 220
13.5 Stakeholders and their requirements	p. 223
13.6 Requirements	p. 225
13.7 System decomposition of ELS	p. 227
13.8 PAC decomposition of ELS	p. 230
13.9 Major use cases	p. 232
13.9.1 Normal use cases	p. 232
13.9.2 Exceptional use cases	p. 233
13.10 Summary and conclusions	p. 235
Appendix 13.1 Definitions	p. 235
14. Order Processing Systems (OPS)	p. 237
14.1 Introduction and objectives	p. 237
14.2 Customer Requirements Specification (CRS): the product management vision of OPS	p. 239
14.2.1 Business concerns and stakeholders' viewpoints	p. 239
14.3 OPS as a lifecycle model	p. 240
14.3.1 Order Creation System (OCS)	p. 242
14.3.2 Order Realization System (ORS)	p. 243
14.3.3 Order Management System (OMS)	p. 244
14.4 Behavioural aspects	p. 245
14.4.1 Front Office	p. 246
14.4.2 Back Office	p. 246
14.4.3 Middle Office	p. 247
14.4.4 External groups	p. 247
14.5 Collecting requirements from multiple stakeholder viewpoints	p. 248
14.5.1 Critical use cases	p. 248
14.6 Class architecture	p. 250
14.6.1 Class models and diagrams	p. 250
14.7 Design guidelines for OPS	p. 252
14.7.1 Data patterns	p. 253
14.8 Functional and non-functional requirements and their realization	p. 256
14.8.1 ISO 9126 revisited	p. 257
14.9 Database repository: an architectural style for data-driven systems	p. 258
14.10 Summary and conclusions	p. 259
Appendix 14.1 Documenting use cases	p. 259
Appendix 14.2 Some UML class diagrams	p. 261
15. Drink Vending Machine (DVM)	p. 263
15.1 Introduction and objectives	p. 263
15.2 Description of problem	p. 264
15.2.1 Scope and span of problem	p. 265
15.3 Goals, processes and context	p. 266
15.4 Use cases	p. 268
15.5 Creating an initial PAC model	p. 269
15.6 Class structure	p. 270
15.7 Interaction diagrams and interface discovery	p. 271
15.7.1 Sequence diagrams	p. 271
15.8 Summary and conclusions	p. 278
Appendix 15.1 Collaboration diagrams in a nutshell	p. 278
16. Multi-tasking lifecycle applications	p. 281
16.1 Introduction and objectives	p. 281
16.2 The problem domain	p. 282
16.2.1 General description of problem	p. 282
16.2.2 System stakeholders	p. 285
16.3 System features	p. 285
16.4 System architecture	p. 286
16.4.1 The PAC models	p. 289
16.5 Design issues: overview	p. 291
16.6 The proof of the pudding: enter the ACE library	p. 291
16.7 The challenge: applying the ACE library in the extrusion application	p. 293
16.8 Summary and conclusions	p. 298
Appendix 16.1 An introduction to multi-threading	p. 298
Part IV Domain architecture summary and 'how to use' documentation	p. 307
17. Summary of domain architectures	p. 309
17.1 Introduction and objectives	p. 309
17.2 Object Creational Systems (OCS)	p. 310
17.3 Object Alignment Systems (OAS)	p. 311
17.4 Object Behavioural Systems (OBS)	p. 312
17.4.1 MIS	p. 312
17.4.2 PCS	p. 313
17.4.3 ACS	p. 314
17.5 Keeping the domain architectures distinct and orthogonal	p. 315
17.5.1 MAN versus RAT	p. 316
17.5.2 MAN versus MIS	p. 317
17.5.3 MAN versus PCS	p. 317
17.5.4 MAN versus ACS	p. 317
17.5.5 RAT versus MIS	p. 317
17.5.6 RAT versus PCS	p. 318
17.5.7 RAT versus ACS	p. 318
17.5.8 MIS versus PCS	p. 318
17.5.9 MIS and PCS versus ACS	p. 318
17.6 Summary and conclusions	p. 319
18. Using domain architectures and analogical reasoning	p. 321
18.1 Introduction and objectives	p. 321
18.2 In which domain architecture does my application belong? The bird-watching method	p. 322
18.3 Focusing on essential system features: the framework method	p. 324
18.4 The defining-attribute view	p. 325
18.4.1 Advantages and disadvantages	p. 326
18.5 The prototype view	p. 327
18.5.1 Advantages and disadvantages	p. 328
18.6 The exemplar-based view	p. 329
18.6.1 Advantages and disadvantages	p. 330
18.7 Summary and conclusions	p. 331
Appendix 18.1 Analogical reasoning and learning by analogy	p. 331
Appendix 1. The Inquiry Cycle and related cognitive techniques	p. 335
A1.1 Introduction and objectives	p. 335
A1.2 Background and history	p. 336
A1.3 An introduction to the Inquiry Cycle model	p. 336
A1.3.1 Requirements documentation	p. 336
A1.3.2 Requirements discussion	p. 337
A1.3.3 Requirements evolution	p. 337
A1.4 Using the right questions	p. 338
A1.4.1 General applicability	p. 340
A1.5 The learning loop	p. 341
A1.6 Summary and conclusions	p. 342
Appendix 2. The Presentation-Abstraction-Control (PAC) pattern	p. 345
A2.1 Introduction and objectives	p. 345
A2.2 Motivation and background	p. 346
A2.2.1 A short history of objects	p. 347
A2.2.2 Subsuming object orientation in a broader context	p. 348
A2.3 Decomposition strategies	p. 348
A2.3.1 System decomposition and activity diagrams	p. 350
A2.3.2 System decomposition and context diagrams	p. 350
A2.4 PAC and object-oriented analysis	p. 352
A2.4.1 Entity classes	p. 355
A2.5 The relationship between PAC and UML	p. 355
A2.6 Summary and conclusions	p. 357
Appendix 3. Relationships with other models and methodologies	p. 359
A3.1 Introduction	p. 359
A3.2 Information hiding and the work of David Parnas	p. 360
A3.3 The Rummler-Brache approach	p. 361
A3.4 Michael Jackson's problem frames	p. 363
A3.5 The Hatley-Pirbhai method	p. 364
A3.6 The Garlan and Shaw architectural styles	p. 365
A3.7 System and design patterns	p. 366
A3.8 The Unified Modelling Language (UML)	p. 367
A3.9 Viewpoint-based requirements engineering	p. 367
Appendix 4. The 'Hello World' example: the Simple Digital Watch (SDW)	p. 371
A4.1 Introduction	p. 371
A4.2 Features and description of problem	p. 371
A4.3 Goals and processes	p. 372
A4.4 Stakeholders, viewpoints and requirements	p. 373
A4.5 Context diagram and system decomposition	p. 373
A4.6 Use cases	p. 375
A4.7 UML classes	p. 375
A4.8 Statecharts	p. 375
Appendix 5. Using domain architectures: seven good habits	p. 379
References	p. 383
Index	p. 387

Available:*

On Order

Summary

Summary

Author Notes

Table of Contents