A UML pattern language

Select an Action

Place Hold(s)
Add to My Lists
Email
Print

Title:

Personal Author:

Evitts, Paul

Series:

Software engineering series

Publication Information:

Indianapolis, IN. : Macmillan Tech Pub, 2000

ISBN:

9781578701186

Subject Term:

Computer software -- Development

UML (Computer science)

Available:*

Library	Item Barcode	Call Number	Material Type	Item Category 1	Status
Searching... PSZ KL	30000003612730	QA76.76.D47 E84 2000	Open Access Book	Book	Searching... Unknown
Searching... PSZ KL	30000003409772	QA76.76.D47 E84 2000	Open Access Book	Book	Searching... Unknown

Social scientists, whether earnest graduate students or tenured faculty members, clearly know the rules that govern good writing. But for some reason they choose to ignore those guidelines and churn out turgid, pompous, and obscure prose. Distinguished sociologist Howard S. Becker, true to his calling, looks for an explanation for this bizarre behavior not in the psyches of his colleagues but in the structure of his profession. In this highly personal and inspirational volume he considers academic writing as a social activity.

Both the means and the reasons for writing a thesis or article or book are socially structured by the organization of graduate study, the requirements for publication, and the conditions for promotion, and the pressures arising from these situations create the writing style so often lampooned and lamented. Drawing on his thirty-five years' experience as a researcher, writer, and teacher, Becker exposes the foibles of the academic profession to the light of sociological analysis and gentle humor. He also offers eminently useful suggestions for ways to make social scientists better and more productive writers. Among the topics discussed are how to overcome the paralyzing fears of chaos and ridicule that lead to writer's block; how to rewrite and revise, again and again; how to adopt a persona compatible with lucid prose; how to deal with that academic bugaboo, "the literature." There is also a chapter by Pamela Richards on the personal and professional risks involved in scholarly writing.

In recounting his own trials and errors Becker offers his readers not a model to be slavishly imitated but an example to inspire. Throughout, his focus is on the elusive work habits that contribute to good writing, not the more easily learned rules of grammar and punctuation. Although his examples are drawn from sociological literature, his conclusions apply to all fields of social science, and indeed to all areas of scholarly endeavor. The message is clear: you don't have to write like a social scientist to be one.

Author Notes

Paul Evitts is a systems and management consultant from Toronto, and he is the President of neoLogistiks, Inc. He has more than 20 years of experience in systems integration, technology planning and implementation, and software methodology/lifecycle development. Paul's clients have included dozens of private sector and government organizations across North America, including insurance and manufacturing companies, real estate and retail organizations, educational institutions, and financial sector firms.

Over the last 10 years, Paul has successfully crafted custom use-case driven development approaches for clients, acted as business architect and project manager for individual projects, and provided strategic planning support for clients migrating to new technologies.

His consulting activities have not been limited to traditional applications development and system integration. He has also evaluated business opportunities for systems technology in the Third World (Africa, Latin America, and the Caribbean), acted as technical producer for a commercial CD-ROM published by The Voyager Company, assisted a startup multimedia media company in business planning, and worked as a system architect for one of the significant successes in business re-engineering.

Paul's methodology consulting practice has not been limited to object-oriented development. He spent many years in the 1980s providing clients with Rapid Application Development and event-based development approaches, coaching and mentoring modeling using a variety of CASE tools.

Before getting into Information Technology, Paul was involved in community development and the use of emerging technologies to promote social change. As a socio-economic consultant, he was an early part of the Inuit Land Claims effort in the Canadian Arctic, which recently culminated in the establishment of a new Canadian Territory called Nunavut. Paul helped the Inuit use video and other media in the process of initial consensus-building across the North, and he provided advice on housing and community planning. His first exposure to the ideas of Christopher Alexander came about earlier as a result of work with a legalized squatting community in London, England where he was involved in the cooperative rehabilitation of abandoned neighborhoods.

Paul studied community development, politics, and advanced technology at Rochdale College in Toronto. Rochdale is an experimental educational community that he helped establish. It is an alternative to traditional universities. His experiences at Rochdale were recently made into a very popular television documentary in Canada, which aired a number of times by the Canadian Broadcasting Corporation and is available as a video from the National Film Board of Canada. Please refer to Paul's Web site, http://www.umlpatterns.com, for further materials related to this book.

Introduction	p. 1
Patterns and the UML	p. 2
Levels and Shared Idioms	p. 5
Using This Book	p. 7
Resources, Sources, and References	p. 8
Part I Getting Started	p. 11
1 Pattern Essentials	p. 13
1.1 Patterns and Paradigms	p. 14
1.1.1 The Idea of a Pattern	p. 15
1.2 Elements of Patterns	p. 17
1.2.1 A Simple Example	p. 18
1.3 Interpreting the Patterns in This Book	p. 21
1.3.1 This Book's Pattern Format	p. 22
2 The Unified Modeling Language	p. 25
2.1 The UML, Briefly Put	p. 26
2.2 Roots	p. 27
2.2.1 Key Players	p. 29
2.3 Understanding the UML	p. 33
2.4 Unification: The Methods Wars Are Over	p. 34
2.4.1 Best Practices: In the Eye of the Beholder	p. 35
2.4.2 An Independent-Minded Modeling Language	p. 36
3 UML Essentials, Elements, and Artifacts	p. 39
3.1 Elements, Viewpoints, and Views	p. 40
3.1.1 Models and Model Elements	p. 42
3.1.2 Diagrams	p. 43
3.2 Packages	p. 44
3.2.1 Models: Packages of Views	p. 47
3.2.2 Subsystems: Packages of Behavior and Operations	p. 47
3.2.3 Frameworks: Packages of Patterns	p. 48
3.3 Extensions	p. 49
3.3.1 Tagged Values	p. 50
3.3.2 Constraints	p. 50
3.3.3 Stereotypes	p. 50
3.3.4 Profiles	p. 51
3.4 Symbols	p. 51
3.4.1 Actor	p. 52
3.4.2 Use Case/Collaboration	p. 52
3.4.3 Class/Object/Type/Active Class	p. 53
3.4.4 Interface	p. 54
3.4.5 Component	p. 54
3.4.6 Node	p. 54
3.4.7 Package	p. 55
3.4.8 State	p. 55
3.4.9 Note	p. 56
3.5 Lines	p. 56
3.5.1 Messages	p. 56
3.5.2 Relationships in General	p. 57
3.5.3 Relationships: Some Types of Associations	p. 58
3.5.4 Relationships: Some Uses of Dependency	p. 59
3.5.5 Abstraction: Other Uses of Dependency	p. 60
3.6 Diagrams	p. 61
3.6.1 Class Diagram	p. 61
3.6.2 Use Case Diagram	p. 62
3.6.3 Interaction Diagrams	p. 63
3.6.4 State Diagrams	p. 65
3.6.5 Activity Diagrams	p. 66
3.6.6 Implementation Diagrams	p. 68
3.7 Further Reading	p. 69
Part II The Pattern Language	p. 71
4 Patterns of Style	p. 73
Catalogue	p. 73
Context	p. 74
Common Forces	p. 74
Discussion	p. 75
4.1 Attributes as Compositions to Types	p. 75
4.2 Providing Focus	p. 79
4.3 Explicit Elision	p. 81
4.4 Tree Routing	p. 83
4.5 Tombstone Packages	p. 85
4.6 Inheritance Goes Up	p. 87
4.7 Rotated Text	p. 88
4.8 Dual Associations	p. 89
4.9 Billboard Packages	p. 91
4.10 Text Workarounds	p. 93
4.11 Seven Plus or Minus Two	p. 96
Summary	p. 97
5 Patterns of Substance	p. 99
Catalogue	p. 99
Context	p. 100
Common Forces	p. 100
Discussion	p. 101
5.1 Standard Diagrams	p. 101
5.2 Implementation or Representation	p. 102
5.3 Digestible Chunks	p. 103
5.4 Attach the Actor	p. 104
5.5 Business Rules Invariably Constrain	p. 105
5.6 Dynamic Object Types	p. 107
5.7 Many-to-Many Class Trio	p. 109
5.8 Model the Seams	p. 111
5.9 Packaging Partitions	p. 113
5.10 Let the Tools Do the Work	p. 115
5.11 Opaque Packages	p. 117
Summary	p. 119
6 Domain Patterns	p. 121
Catalogue	p. 121
Context	p. 122
Common Forces	p. 122
Discussion	p. 123
6.1 Domain Model Is Essential	p. 125
6.2 Actors Play Essential Roles	p. 126
6.3 Factor the Actor	p. 127
6.4 Essential Actions	p. 128
6.5 Essential Vocabulary	p. 129
6.6 Objectify Internal Roles	p. 130
6.7 ToBe Model	p. 131
6.8 AsIs Model	p. 132
Summary	p. 134
7 Product Patterns	p. 137
Catalogue	p. 137
Context	p. 138
Forces	p. 138
Discussion	p. 139
7.1 Manageable Product	p. 139
7.2 Product Stakeholders Are Model Clients	p. 141
7.3 Product Events in Context	p. 142
7.4 Use Cases Represent Requirements	p. 144
7.5 Boundary-Control-Entity (BCE)	p. 145
7.6 Product Chunks Digest Easily	p. 148
7.7 Product Traces Support Robustness	p. 149
7.8 Use Cases: Work as Packages	p. 150
7.9 Tests Need Models	p. 151
7.10 Configuration Management Model	p. 152
Summary	p. 154
8 Component Patterns	p. 155
Catalogue	p. 155
Context	p. 156
Discussion	p. 156
8.1 Separation of Concerns	p. 157
8.2 Whole Components	p. 159
8.3 Icons Clarify Components	p. 160
8.4 Icons Identify Nodes	p. 162
8.5 Specification Backplane	p. 164
8.6 Components Manage Change	p. 165
8.7 Configured and Released Packages	p. 166
8.8 Model for Maintenance	p. 167
Summary	p. 169
Part III Another Starting Point	p. 171
9 Patterns in Context	p. 173
9.1 A Little Starting Context	p. 175
9.1.1 Force 1: Structuring Abstraction, Abstracting Structure	p. 175
9.1.2 Force 2: Guiding Creativity, Creative Guidance	p. 176
9.1.3 Force 3: The Search for Quality and Reuse	p. 177
9.1.4 Broader Cultural and Professional Forces	p. 178
9.2 The Pattern Idea	p. 179
9.2.1 First Hints	p. 179
9.2.2 The Early Years	p. 180
9.2.3 The Idea Emerges	p. 181
9.2.4 The Beginnings of PLoP	p. 183
9.2.5 The Gang of Four and After	p. 184
9.3 Patterns as Literature	p. 185
9.4 Types of Software Patterns	p. 188
9.4.1 CoplienForm	p. 190
9.4.2 GammaForm	p. 193
9.5 The Roots: Alexander on Patterns and Pattern Languages	p. 195
9.6 A Note on This Language	p. 198
9.7 The Importance of Patterns	p. 199
9.8 Where Is It All Going?	p. 202
10 The UML in Context	p. 205
10.1 Why Make System Models?	p. 205
10.1.1 What Use Is a Model?	p. 207
10.2 Every Picture Tells a Story: The UML as a Modeling Language	p. 208
10.3 The UML Specification and Metamodel	p. 210
10.4 What Do We Model?	p. 213
10.4.1 Architecture	p. 214
10.4.2 Domains	p. 215
10.4.3 Products	p. 217
10.4.4 Solutions	p. 217
10.5 Abstraction and Architecture Made Simple	p. 219
10.5.1 Abstraction	p. 219
10.5.2 Architecture	p. 222
10.6 Perspectives: A Generic Modeling Framework	p. 225
11 Putting It All Together: Reflecting on the Work of Design	p. 227
11.1 The Work of Design	p. 228
11.1.1 What Is Design?	p. 229
11.1.2 Beyond Patterns and Paradigms	p. 231
11.2 Elements of Reflective Design	p. 232
11.2.1 Problem Setting	p. 234
11.2.2 A Language of Design	p. 235
11.2.3 A Language about Designing	p. 236
11.2.4 Performance	p. 237
11.2.5 Closure	p. 239
11.2.6 Reflective Design and Systems Modeling	p. 239
11.3 To Be Continued	p. 240
References	p. 241
Index	p. 247

Available:*

On Order

Summary

Summary

Author Notes

Table of Contents