No label defined (Q4393463)

The book presents various concepts related to the analysis and design of object-oriented methodologies, concentrating on the Unified Modeling Language (UML). The book is divided into seven parts, each one with several articles. Part I, ``Structural Issues'', contains five papers. ``Modeling Objects: Using Binary- and Entity-Relationship Approaches'' discusses some of the differences between binary-relationship and entity-relationship models and how these approaches can be applied in an object oriented context. ``Object Types as Objects and Vice Versa'' deals with meta-model concept allowing to define hierarchies of instances as an important aspect of modeling objects and their types. ``Power Types'' discusses a special type of objects whose instances are subtypes of another object type. In ``Specifying Structural Constraints'' are investigated some restrictions that limit the way objects associate each other in order to avoid unclean and ambiguous descriptions in an Object-Oriented analysis. An initial attempt to produce a formalism addressing some structural concepts is presented in ``Toward a formalization of OO Analysis''. Part II, ``Dynamic Issues'', has four papers. In ``What is Object State?'' are presented two ways of defining the state of an object: as a collection of associations of that object, or as a collection of object types of which the object is an instance. ``Dynamic and Multiple Classification'' discusses the ability to change the classification of an object or to consider an object as an instance of many object types. ``Events and their Specification'' discusses the nature of events and describes how to specify their state changes. ``Approaches to Finite-State Machine Modeling'' investigates various ways of representing Object Oriented behaviour using Mealy and Moore model or a combination of these ones; some other notations representing state changes are also mentioned. Part III, ``Business Rules'', contains two articles. ``Business Rules'' discusses rules used to improve other techniques such as entity diagrams, data flow diagrams, state transition diagrams; five specification rules (sometimes called business rules) are identified: stimulus/response rules, operation constraint rules, structure constraint rules, inference rules, computation rules. ``Using Rules with Diagrams'' presents ways in which rules are used together with various diagram notation. Part IV, ``Object Complexity'', contains two papers. ``Managing Object Complexity, Part I: Classification and Generalization'' and ``Managing Object Complexity, Part II: Aggregation''. In order to manage object complexity some mechanisms are proposed: classification which points out some commonalities between objects; generalization which enables to identify all instances of a specific object type as instances of a more general object type; aggregation which allows for an object to be defined with its component parts. Part V, ``Object Aggregation'', contains three papers. ``Six Different Kinds of Aggregation'' examines six ways in which are formed the whole-part associations determined by combinations of three basic properties: configuration, homeomerism, and invariance. In ``A Foundation for Aggregation'' is described a way for expressing the structure of comosite objects; a diagrammatic technique for representing composite objects is provided. ``A User-Level Model for Aggregation'' discusses ways that users think about aggregation, computational services that make sense from an aggregational viewpoint, and development techniques, including a diagrammatic notation reflecting the user viewpoint. Part VI, ``Design Templates'', contains three pages dealing with a number of analysis constructs, describing possible template for each one, suggesting the associated implementation. Part VII, ``The Process of Objects'', contains three papers. ``Method Engineering'' describes how to take the most suitable approach for a particular project. ``User Workshop Techniques'' presents the way for effectively integrating the users in the system development process. In ``Object Oriented Methodologies'' it is provided an overview of how Object Orientation can be used to develop various kinds of systems and what are the differences between traditional and Object Oriented methodologies.