A UML pattern language / (Record no. 11441)

MARC details
000 -LEADER
fixed length control field 06540nam a22002294a 4500
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
ISBN 9781578701186
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
ISBN 157870118X
082 00 - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 005.1
Item number EVI
100 1# - MAIN ENTRY--AUTHOR NAME
Personal name Evitts, Paul.
245 12 - TITLE STATEMENT
Title A UML pattern language /
250 ## - EDITION STATEMENT
Edition statement Indian Edition
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT)
Place of publication New Delhi :
Name of publisher Techmedia,
Year of publication 2000.
300 ## - PHYSICAL DESCRIPTION
Number of Pages xii, 257 p. ;
490 1# - SERIES STATEMENT
Series statement Software engineering series
500 ## - GENERAL NOTE
General note Originally Published in Indianapolis, IN : by Macmillan Pub., 1999. ISBN is 157870118X
505 ## - FORMATTED CONTENTS NOTE
Formatted contents note Patterns and the UML 2 --<br/>Levels and Shared Idioms 5 --<br/>1 Pattern Essentials 13 --<br/>1.1 Patterns and Paradigms 14 --<br/>1.1.1 Idea of a Pattern 15 --<br/>1.2 Elements of Patterns 17 --<br/>1.2.1 A Simple Example 18 --<br/>1.3 Interpreting the Patterns in This Book 21 --<br/>1.3.1 This Book's Pattern Format 22 --<br/>2 Unified Modeling Language 25 --<br/>2.1 UML, Briefly Put 26 --<br/>2.2 Roots 27 --<br/>2.2.1 Key Players 29 --<br/>2.3 Understanding the UML 33 --<br/>2.4 Unification: The Methods Wars Are Over 34 --<br/>2.4.1 Best Practices: In the Eye of the Beholder 35 --<br/>2.4.2 An Independent-Minded Modeling Language 36 --<br/>3 UML Essentials, Elements, and Artifacts 39 --<br/>3.1 Elements, Viewpoints, and Views 40 --<br/>3.1.1 Models and Model Elements 42 --<br/>3.1.2 Diagrams 43 --<br/>3.2 Packages 44 --<br/>3.2.1 Models: Packages of Views 47 --<br/>3.2.2 Subsystems: Packages of Behavior and Operations 47 --<br/>3.2.3 Frameworks: Packages of Patterns 48 --<br/>3.3 Extensions 49 --<br/>3.3.1 Tagged Values 50 --<br/>3.3.2 Constraints 50 --<br/>3.3.3 Stereotypes 50 --<br/>3.3.4 Profiles 51 --<br/>3.4 Symbols 51 --<br/>3.4.1 Actor 52 --<br/>3.4.2 Use Case/Collaboration 52 --<br/>3.4.3 Class/Object/Type/Active Class 53 --<br/>3.4.4 Interface 54 --<br/>3.4.5 Component 54 --<br/>3.4.6 Node 54 --<br/>3.4.7 Package 55 --<br/>3.4.8 State 55 --<br/>3.5 Lines 56 --<br/>3.5.1 Messages 56 --<br/>3.5.2 Relationships in General 57 --<br/>3.5.3 Relationships: Some Types of Associations 58 --<br/>3.5.4 Relationships: Some Uses of Dependency 59 --<br/>3.5.5 Abstraction: Other Uses of Dependency 60 --<br/>3.6 Diagrams 61 --<br/>3.6.1 Class Diagram 61 --<br/>3.6.2 Use Case Diagram 62 --<br/>3.6.3 Interaction Diagrams 63 --<br/>3.6.4 State Diagrams 65 --<br/>3.6.5 Activity Diagrams 66 --<br/>3.6.6 Implementation Diagrams 68 --<br/>Part II Pattern Language 71 --<br/>4 Patterns of Style 73 --<br/>Catalogue 73 --<br/>Common Forces 74 --<br/>4.1 Attributes as Compositions to Types 75 --<br/>4.2 Providing Focus 79 --<br/>4.3 Explicit Elision 81 --<br/>4.4 Tree Routing 83 --<br/>4.5 Tombstone Packages 85 --<br/>4.6 Inheritance Goes Up 87 --<br/>4.7 Rotated Text 88 --<br/>4.8 Dual Associations 89 --<br/>4.9 Billboard Packages 91 --<br/>4.10 Text Workarounds 93 --<br/>4.11 Seven Plus or Minus Two 96 --<br/>5 Patterns of Substance 99 --<br/>5.1 Standard Diagrams 101 --<br/>5.2 Implementation or Representation 102 --<br/>5.3 Digestible Chunks 103 --<br/>5.4 Attach the Actor 104 --<br/>5.5 Business Rules Invariably Constrain 105 --<br/>5.6 Dynamic Object Types 107 --<br/>5.7 Many-to-Many Class Trio 109 --<br/>5.8 Model the Seams 111 --<br/>5.9 Packaging Partitions 113 --<br/>5.10 Let the Tools Do the Work 115 --<br/>5.11 Opaque Packages 117 --<br/>6 Domain Patterns 121 --<br/>6.1 Domain Model Is Essential 125 --<br/>6.2 Actors Play Essential Roles 126 --<br/>6.3 Factor the Actor 127 --<br/>6.4 Essential Actions 128 --<br/>6.5 Essential Vocabulary 129 --<br/>6.6 Objectify Internal Roles 130 --<br/>6.7 ToBe Model 131 --<br/>6.8 AsIs Model 132 --<br/>7 Product Patterns 137 --<br/>7.1 Manageable Product 139 --<br/>7.2 Product Stakeholders Are Model Clients 141 --<br/>7.3 Product Events in Context 142 --<br/>7.4 Use Cases Represent Requirements 144 --<br/>7.5 Boundary-Control-Entity (BCE) 145 --<br/>7.6 Product Chunks Digest Easily 148 --<br/>7.7 Product Traces Support Robustness 149 --<br/>7.8 Use Cases: Work as Packages 150 --<br/>7.9 Tests Need Models 151 --<br/>7.10 Configuration Management Model 152 --<br/>8 Component Patterns 155 --<br/>8.1 Separation of Concerns 157 --<br/>8.2 Whole Components 159 --<br/>8.3 Icons Clarify Components 160 --<br/>8.4 Icons Identify Nodes 162 --<br/>8.5 Specification Backplane 164 --<br/>8.6 Components Manage Change 165 --<br/>8.7 Configured and Released Packages 166 --<br/>8.8 Model for Maintenance 167 --<br/>Part III Another Starting Point 171 --<br/>9 Patterns in Context 173 --<br/>9.1 A Little Starting Context 175 --<br/>9.1.1 Force 1: Structuring Abstraction, Abstracting Structure 175 --<br/>9.1.2 Force 2: Guiding Creativity, Creative Guidance 176 --<br/>9.1.3 Force 3: The Search for Quality and Reuse 177 --<br/>9.1.4 Broader Cultural and Professional Forces 178 --<br/>9.2 Pattern Idea 179 --<br/>9.2.1 First Hints 179 --<br/>9.2.2 Early Years 180 --<br/>9.2.3 Idea Emerges 181 --<br/>9.2.4 Beginnings of PLoP 183 --<br/>9.2.5 Gang of Four and After 184 --<br/>9.3 Patterns as Literature 185 --<br/>9.4 Types of Software Patterns 188 --<br/>9.4.1 CoplienForm 190 --<br/>9.4.2 GammaForm 193 --<br/>9.5 Roots: Alexander on Patterns and Pattern Languages 195 --<br/>9.6 A Note on This Language 198 --<br/>9.7 Importance of Patterns 199 --<br/>9.8 Where Is It All Going? 202 --<br/>10 UML in Context 205 --<br/>10.1 Why Make System Models? 205 --<br/>10.1.1 What Use Is a Model? 207 --<br/>10.2 Every Picture Tells a Story: The UML as a Modeling Language 208 --<br/>10.3 UML Specification and Metamodel 210 --<br/>10.4 What Do We Model? 213 --<br/>10.4.1 Architecture 214 --<br/>10.4.2 Domains 215 --<br/>10.4.3 Products 217 --<br/>10.4.4 Solutions 217 --<br/>10.5 Abstraction and Architecture Made Simple 219 --<br/>10.6 Perspectives: A Generic Modeling Framework 225 --<br/>11 Putting It All Together: Reflecting on the Work of Design 227 --<br/>11.1 Work of Design 228 --<br/>11.1.1 What Is Design? 229 --<br/>11.1.2 Beyond Patterns and Paradigms 231 --<br/>11.2 Elements of Reflective Design 232 --<br/>11.2.1 Problem Setting 234 --<br/>11.2.2 A Language of Design 235 --<br/>11.2.3 A Language about Designing 236 --<br/>11.2.4 Performance 237 --<br/>11.2.5 Closure 239 --<br/>11.2.6 Reflective Design and Systems Modeling 239.
520 ## - SUMMARY, ETC.
Summary, etc "A UML Pattern Language pairs the software design pattern concept with the Unified Modeling Language (UML) to offer a tool set for software professionals practicing both system modeling and software development. This book provides a collection of patterns in the domain of system modeling, including those that are useful to management, operations, and deployment teams, as well as to software developers; a survey of the development of patterns and the UML; a discussion of the underlying theory of the patterns and instructions for using the language; and a thorough exploration of the design process and model-driven development."
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical Term Computer software
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical Term UML (Computer science)
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical Term Softwareentwicklung.
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Koha item type Lending Books
Holdings
Collection code Home library Current library Shelving location Date acquired Source of acquisition Cost, normal purchase price Full call number Accession Number Koha item type
Reference Main Library Main Library Stacks 23/04/2004 Purchased 375.00 005.1 EVI 008869 Lending Books

© University of Vavuniya

---