Seamless Object-Oriented Software Architecture

Series editor’s preface......Page 5 Preface......Page 7 Part I Introduction......Page 13 1.1 INTRODUCTION......Page 15 Initial difficulties......Page 16 The road to reuse of knowledge......Page 17 1.3 REVERSIBILITY......Page 19 1.4 SOFTWARE CONTRACTING......Page 21 2.1 INTRODUCTION......Page 23 Why not ER modeling?......Page 24 2.3 OTHER METHODS......Page 27 2.4 THE BON POSITION......Page 28 Reversibility......Page 29 Scalability......Page 30 Typed interface descriptions......Page 31 Support for software contracting......Page 32 Simplicity......Page 34 Space economy......Page 35 2.6 STATIC AND DYNAMIC MODELS......Page 36 Part II The model......Page 39 3.1 INTRODUCTION......Page 41 3.2 BON MODELING CHARTS......Page 42 System charts......Page 43 Class charts......Page 44 3.3 SYSTEM STATE INFORMATION......Page 47 Graphical representation......Page 48 3.6 INDEXING CLAUSE......Page 49 Feature names......Page 51 Feature renaming......Page 52 Assertions......Page 53 Example......Page 54 3.9 CLASS INVARIANT......Page 59 3.10 GRAPHICAL AND TEXTUAL SPECIFICATION......Page 60 3.11 THE BON ASSERTION LANGUAGE......Page 61 Basic object expressions......Page 62 Basic boolean expressions......Page 63 3.12 THE BON PREDICATE LOGIC......Page 64 Quantifiers......Page 65 Quantified variables......Page 66 Propositions......Page 67 Range restriction......Page 68 3.13 ASSERTIONS AND PARTIAL FUNCTIONS......Page 69 and and or are also semi- strict in BON, permitting assertions like:......Page 70 3.15 CLASS HEADERS......Page 71 3.16 CLUSTERS......Page 72 Nested clusters......Page 73 Layered clustering— not hierarchical development......Page 74 Local naming......Page 75 Compression of clusters......Page 76 Graphical representation......Page 77 Inheritance involving clusters......Page 78 Static relations between classes......Page 81 Associations and aggregations......Page 82 Graphical representation......Page 83 Bidirectional links......Page 84 Multidirectional links......Page 85 Links involving generic suppliers......Page 86 Compacted generic links......Page 88 Role multiplicity......Page 90 Instance multiplicity......Page 92 Instance sharing......Page 93 Client relations involving clusters......Page 95 Compression of client relations......Page 97 4.3 CLASS VS. OBJECT DEPENDENCIES......Page 98 4.4 INDIRECT CLIENT DEPENDENCIES......Page 100 4.5 SEMANTIC LINKS......Page 101 5.1 INTRODUCTION......Page 102 Object- oriented execution......Page 103 What should be captured by a dynamic model?......Page 104 System events......Page 105 Event charts......Page 106 System scenarios......Page 108 Object creation charts......Page 109 Objects......Page 111 Graphical representation......Page 112 Graphical representation......Page 113 Multidirectional links......Page 114 Object grouping......Page 115 Compression of objects and groups......Page 116 Recursive messages......Page 117 Active and passive objects......Page 118 A more complex example: moving graphical objects......Page 120 The need for two- dimensional object diagrams......Page 122 General scenarios need object grouping......Page 123 A different use of object grouping......Page 126 Use cases......Page 127 Part III The method......Page 129 6.1 INTRODUCTION......Page 131 6.2 SIMULATING AN IDEAL PROCESS......Page 132 6.3 ENTERPRISE MODELING......Page 133 6.4 WHAT IS ANALYSIS AND WHAT IS DESIGN?......Page 134 Multiple language metaphor......Page 135 What is problem and what is solution?......Page 136 Levels of reuse......Page 137 Reuse policy......Page 138 Planned vs. accidental reuse......Page 139 Reuse manager......Page 140 6.6 USER CENTERED DESIGN......Page 141 A reference model for user centered design......Page 142 The conceptual aspect......Page 144 The interface aspect......Page 145 User metaphors......Page 146 6.7 ROLES OF ANALYSIS OBJECTS......Page 147 Systems as objects......Page 148 Front and back ends of systems......Page 149 Several levels of interface......Page 150 No special analysis interface classes......Page 151 6.9 SYSTEM USAGE......Page 152 6.10 A PARADIGM SHIFT......Page 154 7.1 THE BON DELIVERABLES......Page 155 Reversibility......Page 157 Roles of deliverables......Page 158 Risk- driven development strategy......Page 160 Process tasks......Page 162 System borderline......Page 164 Subsystems......Page 165 User considerations......Page 166 External communication......Page 168 Incremental development......Page 169 Establish reuse policy......Page 170 Environmental restrictions......Page 171 Classes vs. objects......Page 172 Glossary of terms......Page 173 High- level class properties......Page 174 Possible system views......Page 175 Gradual evolution of a good model......Page 177 7.6 TASK 4: DEFINE CLASSES......Page 178 Glossary of terms......Page 179 Object creation......Page 180 Finding scenarios......Page 181 Scenarios to guide static modeling......Page 182 7.8 TASK 6: DEFINE PUBLIC FEATURES......Page 183 7.9 TASK 7: REFINE SYSTEM......Page 184 Proceeding into design......Page 185 7.10 TASK 8: GENERALIZE......Page 186 7.11 TASK 9: COMPLETE AND REVIEW SYSTEM......Page 187 Completeness and minimality......Page 188 Requirements traceability......Page 189 8.1 FINDING CLASSES......Page 190 BookmarkTitle:......Page 0 What is an abstract data type?......Page 191 The importance of names......Page 192 Naming classes......Page 193 Tangible objects......Page 194 The dual roles of a designer......Page 195 A world of recursive behavior......Page 197 Encapsulated behavior......Page 198 How many features?......Page 199 Class or operation?......Page 200 8.2 CLASSIFYING......Page 201 Inheritance vs. client usage......Page 202 Facility inheritance......Page 203 Inheritance of secondary properties......Page 204 Beware of reverse modeling......Page 205 8.3 CLUSTERING......Page 206 Client server interfaces......Page 208 Frameworks......Page 209 8.4 DEFINING CLASS FEATURES......Page 210 Distinction from class names and clear word separation......Page 211 Avoid abbreviation— but do not overqualify!......Page 212 How many arguments?......Page 213 Naming consistency......Page 214 8.5 SELECTING AND DESCRIBING OBJECT SCENARIOS......Page 215 8.6 WORKING OUT CONTRACTING CONDITIONS......Page 217 Design by contract......Page 218 Contracting as a mutual benefit......Page 219 Laws of subcontracting......Page 220 Classes as specification elements......Page 221 Run- time monitoring of assertions......Page 222 8.7 ASSESSING REUSE......Page 224 Make the complex parts reusable......Page 225 Encapsulation of non- object- oriented software......Page 226 8.8 INDEXING AND DOCUMENTING......Page 227 Abstract documentation......Page 228 Documenting frameworks......Page 229 Indexing guidelines......Page 230 Style of comments......Page 231 Avoid premature abstraction......Page 232 Strong design means strong dependencies......Page 233 Specialization and generalization......Page 234 Reuse through discovery rather than invention......Page 235 Make regular conceptual summaries......Page 236 Seek polymorphism......Page 237 Consistency......Page 238 Toolkits......Page 239 Part IV Case studies......Page 241 9 A conference management system......Page 243 Users......Page 244 Incoming information......Page 245 Outgoing information......Page 246 9.2 CANDIDATE CLASSES IN THE PROBLEM DOMAIN......Page 247 9.3 CLASS SELECTION AND CLUSTERING......Page 248 Classification......Page 252 Organization......Page 254 Conference program......Page 258 Registration......Page 260 Conference management......Page 262 Events and scenarios......Page 264 What relations to emphasize......Page 265 First scenario......Page 267 Second scenario......Page 269 Third scenario......Page 270 Fourth scenario......Page 271 false). The same is true for very basic numeric types, such as INTEGER and......Page 272 Organization cluster......Page 274 Registration cluster and technical events cluster......Page 278 Internal operation......Page 282 External operation......Page 284 System viewpoint......Page 285 A first attempt......Page 286 10.3 CLASS SELECTION AND CLUSTERING......Page 287 Assessing the architecture......Page 289 A second attempt......Page 290 10.4 CLASS DEFINITION......Page 291 10.5 SYSTEM BEHAVIOR......Page 295 10.6 FORMAL CLASS DESCRIPTION......Page 298 10.7 FINAL STATIC ARCHITECTURE......Page 300 11 Relational and object- oriented coexistence......Page 301 11.1 FROM DATA STORAGE TO OBJECT PERSISTENCE......Page 302 Principle 2......Page 304 11.2 OBJECT MODELS AND RELATIONAL MODELS......Page 305 Integrity constraints......Page 306 Short overview of the relational model......Page 307 Designing a database interface cluster......Page 309 Mapping non- basic object attributes......Page 313 11.4 INTERFACING AN EXISTING RELATIONAL SCHEMA......Page 315 Factors determining the schema......Page 316 A virtual database......Page 317 An example application......Page 318 A virtual database interface......Page 321 Query frames......Page 324 Retrieval by example......Page 325 Retrieval by key......Page 326 11.6 PERSISTENT OBJECT MANAGEMENT......Page 327 Persistent objects......Page 329 Storage managers......Page 331 A full retrieval scenario......Page 333 11.7 AUTOMATIC GENERATION OF SQL STATEMENTS......Page 336 Model queries......Page 337 Attribute mappings......Page 338 Self- joins......Page 340 The generation scheme......Page 341 Updating the database......Page 342 11.8 FULL STATIC ARCHITECTURE......Page 343 12.1 CLUSTERING A PROBLEM DOMAIN......Page 344 12.2 DEFINING CLASS RELATIONSHIPS......Page 346 12.3 ASSERTIONS AND CLASSIFICATION......Page 347 12.4 DYNAMIC BEHAVIOR......Page 348 12.5 PRESCRIPTION AND DESCRIPTION......Page 349 12.6 TRAFFIC- CONTROL SYSTEM......Page 350 12.7 DICE GAME......Page 351 12.8 CAR RENTAL COMPANY......Page 352 12.9 TRUCK FREIGHT......Page 353 12.10 REAL- TIME PROCESS CONTROL......Page 357 Part V Appendices......Page 359 A. 1 INTRODUCTION......Page 361 A. 2 THE SYNTAX NOTATION......Page 362 Repetition......Page 363 A. 4 INFORMAL CHARTS......Page 364 A. 5 STATIC DIAGRAMS......Page 366 A. 6 CLASS INTERFACE DESCRIPTION......Page 367 A. 7 FORMAL ASSERTIONS......Page 369 A. 8 DYNAMIC DIAGRAMS......Page 370 Identifiers......Page 371 Strings......Page 372 Reserved words......Page 373 Conclusion......Page 374 B. 1 BON SPECIFICATION......Page 376 B. 2 INFORMAL CHARTS......Page 377 Inheritance relations......Page 379 Client relations......Page 381 B. 4 DYNAMIC DIAGRAMS......Page 386 BON deliverables: dependencies......Page 393 BON deliverables: description ( indicates the most important ones)......Page 394 BON process: tasks and activities......Page 395 BON notation: charts and interfaces......Page 396 BON notation: static and dynamic diagrams......Page 397 Appendix D: Other approaches......Page 398 ACTOR. Anything that can call a system object from the outside, such as a......Page 400 BOOLEAN See PROPOSITIONAL......Page 401 CLASS An assertion about every object of a certain class. The......Page 402 COLLABORATION. A term used to signify the cooperation of a set of objects......Page 403 COVARIANT A rule stating that argument types of a feature signature......Page 404 DEFERRED A class containing at least one feature which has no......Page 405 DYNAMIC A mechanism permitting different behavior to result from......Page 406 EVENT A graph or table showing a series of events that may occur in a......Page 407 GENERALIZATION. The act of detecting a general pattern in a concrete problem......Page 408 INSTANCE The number of instances of a given class that may......Page 409 METHOD (OF A class feature in Smalltalk terminology.......Page 410 OBJECT- A term signifying that a certain system or method includes......Page 411 OBJECT- A system built using object- oriented techniques.......Page 412 PARTIAL A query or command which is not defined for all possible......Page 413 PROPOSITIONAL A logic whose expressions are built from primitive......Page 414 RESPONSIBILITY. A term used to emphasize the behavior of an object rather......Page 415 ROOT A class of which one instance will be created when an object-......Page 416 SIGNATURE. The type of the return value of a feature, if any, and the number......Page 417 STATIC The act of deciding which version of a routine will be......Page 418 SYSTEM Something to which a system will respond with a certain......Page 419 TYPE. The pattern of behavior of a certain kind of object, specified as a......Page 420 VOID A reference which is not attached to any object.......Page 421 24( 10), New Orleans, LA, Oct. 1989, pp. 1 6.......Page 423 SMC 12( 2), Mar./ Apr. 1982.......Page 424 27( 10), Vancouver, Canada, Oct. 1992, pp. 1 15.......Page 425 34( 9), Sept. 1991, pp. 28 38.......Page 427 25( 10), Oct. 1992, pp. 40 51.......Page 431 Index......Page 437 Contents......Page 451