R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Definition Language (IDL for short) is defined to provide a uniform access to the server objects. Servers own interfaces used by potential clients to request some services. Still these interfaces define only some messages types. Contracts and interaction protocol languages go a step further. In [26] Wirfs Brock and al. define a contract as a list of services an object can request from another object . Booch has a more dynamic definition and says a contract specifies a (static) set of services together with a (dynamic) specification of the ordering of those services . Interaction protocol ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....ffl Inheritance of common attributes between objects. These basic principles are present in all the object oriented methods, despite their differences. In general, object oriented modeling assumes the identification of specific objects and classes of objects, along with relationships between them [1, 3, 4, 6, 14, 25, 28, 30]. Objectoriented modeling promotes modularity, abstraction and re use [8] The Unified Modeling Language (UML) is an object oriented modeling language that has 1 in the past few years gained significant industry support and has been adopted by the Object Management Group (OMG) as a standard ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice-Hall, Englewood Cliffs, New Jersey, 1990. 11

.... cooperative work [11] This is because these conventional techniques are based on a data model rather than a dynamic behavior model of the whole system and promote such design process as objects are defined prior to their behavior by using various notations of static relationships between objects [1, 5, 17, 18, 20], although there are a few notations for system behavior among objects such as an event trace diagram. 2.2. Research goals A new approach and its support tools have been developed for satisfying the following requirements and are described as facilities of M base in this paper: 1. The target ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....of participants Reading: Selected OO Terms from [14] Unit 2. Introductory Overview of the Basic OO Methods: Top Ten List Contents: Booch [3, 5, 23] OMT [11, 5, 19] Objectory [17] Fusion [8] HOOD [10, 20] ROOM [21] Shlaer Mellor [22] Coad Yourdon [6, 7, 25] MOSES [15, 16] RDD [24]. Unit 3. Object Oriented Requirements Analysis: Fundamental Notions Contents: Naive view Objects as nouns, attributes as adjectives, operations as verbs; Identification of Objects and Classes; Use cases specification of requirements from the external point of view; Results of OOA. Unit ....

R. Wirfs-Brock, B. Wilkerson, L. Wiener, Designing Object-Oriented Software, Prentice Hall, Englewood Cliffs, NJ, 1990

....Nurse Emit Patient Report Pharmacist 3 1 4 2 Medicine Request Emit Patient s Condition Treatment Apply Describe Patient s Symptoms Prescribe Treatment Figure 1: ID for the Hospital System. that is, an interaction diagram (graph) ID) The ID is similar to the collaboration graph [12] and the message diagram [13] The former shows the relationships between collaborators that is, the connections between the various classes. The latter can be seen as a detailed version of the collaboration graph where the arrows represent the actual messages that can be exchanged amongst the ....

Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....Object oriented modeling is a widely adopted technique in the development of large software systems. There exist a plethora of O O notations and methods described in the literature and available to software engineers, including Rumbaugh s OMT [1] Booch [2] Coad Yourdon [3] Wirfs Brock [4]. Most of them have been overcome by the advent of UML, the Unified Modeling Language [5] which has become a de facto standard notation for modeling object oriented systems. UML in itself provides a very rich set of diagram types to describe static and dynamic aspects of the system under ....

R. J. Wirfs-Brock, B. Wilkerson, L. Wiener: "Designing object oriented software", Prentice Hall, Englewood Cliffs N.J., 1990.

....applications seems to remain an open issue. With the existing approaches such as the OMG CORBA, developers can write client objects and server objects, and make them interoperate in a distributed heterogeneous environment. These are mainly simple client server interactions. Contracts [HHG90, WBWW90, Hol92, JBJE95] and interaction protocol languages [AG94b, AG94a, Bok96] provide a way to specify all the legal sequences of messages that can be exchanged. Nevertheless these approaches separate the design of the interactions from the design of the objects behaviors. In [Bon94, BDFS96] we give ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....they can be found in use case descriptions. The entities that form the nature of user system communication will be called Abstract Interface Objects (AIO) They are abstract in the sense that they do not necessarily represent concrete interface objects. Instead, they model responsibilities (see [4]) that can be mapped to one or more real interface objects. The intention is to avoid any design decisions at this stage. Identication of abstract interface objects is achieved by examining all the use cases and the problem domain terminology, and searching for entities that take part in the ....

Wirfs-Brock, R., et al. Designing Object-Oriented Software, Prentice Hall, 1990.

....a few minutes. However, as mentioned above there were subjects who said they would have preferred to have been able to de ne all the classes separately before determining the relationships between them. This is reminiscent of the classic CRC method for determining the roles of classes in a system [Wirfs Brock et al. 1990]. Others had no problems with the top down scheme and actually felt that it helped them, possibly because it forced them to work in a well organised top down fashion. Perhaps both capabilities need to be supported. Certainly some systems may lend themselves better to top down design than others. ....

Wirfs-Brock, R., Wilkerson, B., and Wiener, L. (1990). Designing Object-Oriented Software. Prentice-Hall, Englewood Clis, NJ 07632.

....the resulting design against the source code. To assign object responsibilities, use the noun phrases in the requirements as the initial objects and the verb phrases as the initial responsibilities. Derive a design by mapping objects on class hierarchies and responsibilities on operations. See [WIRF 90] for an in depth treatment on responsibility driven design. # Guess Object Roles. The usage scenarios that you get out of INTERVIEW DURING DEMO (p. 117) may serve to define some use cases that in turn help to find out which objects fulfill which roles. See [JACO 92] for use cases and [REEN 96] ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990. (p 124)

....of development were based on those offered by the pre eminent programming paradigm. So, during the era of structured programming, structured analysis and design techniques were proposed [9,17] while object oriented programming has given rise more recently to objectoriented design and analysis [1,15]. For structured development techniques this meant The Tropos project has been partially funded by the Natural Sciences and Engineering Research Council (NSERC) of Canada, and Communications and Information Technology Ontario (CITO) a centre of excellence, funded by the province of Ontario. ....

Wirfs-Brock, R., Wilkerson, B. and Wiener, L., Designing Object-Oriented Software, Englewood Cliffs, Prentice-Hall, 1990.

....of development were based on those o#ered by the pre eminent programming paradigm. So, during the era of structured programming, structured analysis and design techniques were proposed [16,49] while object oriented programming has given rise more recently to object oriented design and analysis [4,45]. For structured development techniques this meant that throughout software development, the developer can conceptualize the system in terms of functions and processes, inputs and outputs. For object oriented development, on the other hand, the developer thinks throughout in terms of objects, ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....in practice. For an example, see the buttons in Fig. 1. Moreover, class models are difficult to decompose. As soon as different objects of a class belong to different parts of a system (which often is the case) hierarchical decomposition does no longer work for class models [14] Wirfs Brock [22] tries to overcome the problems of class modeling by using classes in different roles. However, decomposition remains a problem: what does it mean to decompose a role We therefore decided to use abstract, prototypical objects as the core of an ADORA model (Fig. 1) An equivalent to classes ....

Wirfs-Brock, R., Wilkerson, B., Wiener, L. (1993). Designing Object-Oriented Software. Englewood Cliffs, N. J.: Prentice Hall.

....OBJECT ORIENTED DEVELOPMENT This section provides an overview of the objectoriented development process. To avoid confusion, analysis and design are considered together as the design the bridge between system requirements and the final code implementation. The reader is referred to [1,2,3,4,6,7,10,12] for various definitions of where analysis ends and design begins in the development process. The goal of the design is to provide documentation that can be used to code and maintain an application. Of particular importance is that there be a clear and direct mapping between the design and the ....

....methodologies, most notably Jacobson s [4] designers begin modeling the interface (view) and control objects as well early in development. The initial object analysis is given various degrees of importance in the different object methodologies. In Use case [4] or Responsibility driven approaches [12] designers tend to swiftly identify an initial set of objects, then build up the objects by analyzing functional requirements and assigning services to objects so that those requirements are met. Datacentered approaches [1,6,10] on the other hand, emphasize that objects should be closely ....

Wirfs-Brock, R., Wilkerson, B., and Weiner, L., Designing Object-Oriented Software, Prentice Hall, Englewood Cliffs, New Jersey, 1991.

....UML to specify the external protocol, extended features like and or state decomposition are not supported to ensure that the resulting descriptions are simple enough to allow a seamless embedding into other behavioral specifications. To handle complex cases, the usage of multiple contracts (c.f. [34]) in a style supporting separation of concern as, e.g. role based modeling (see [28] is applied. 3.2. From Protocols to Services When using contracts, for example in a scenario as demonstrated in figure 3, parts of the specified usage protocol can be embedded as needed. In this scenario, an ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....in CATALYSIS [8] The considered media store system (MSS) should support the management of renting medias like books, video tapes and so on. The four layer architecture of the MSS (figure 1) where each layer provides a set of interfaces, emphasizes hierarchical design and separation of concern [32], by separating system wide concerns vertically into layers. Each layer is further decomposed horizontally into different subsystems. The subsystem separation is strengthened using the design by contract idea of [21] It extends each interface to a contract by adding a protocol. These protocols ....

....which are too complex, are not only a matter of expressive hyper graph foldings as provided by the statechart formalism. Such complex protocols indicate a bad design and the interaction and structure should be better decomposed into multiple independent contracts (see separation of concern [32]) as, e.g. provided in role based design methods like [24] Thus, fortunately the scalability of the approach is preserved in practice. The inherent true concurrency of Petri nets allows further to express intra object concurrency by concurrent actions in the resource allocation net and or ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

.... on the basic software engineering ideas of modularization as well as separation and by applying the design by contract idea of Meyer [5] A separation of independent contracts as in role based modeling [6] and thus the support of multiple interfaces for different concerns as outlined in [7] is necessary. The combination of the usual syntactical interface notion with a behavioral protocol builds a basic contract that allows to reduce harmful implementation dependencies to a great extent. These behavioral contracts are also a suitable mechanism to describe architectural aspects using ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener. Designing Object-Oriented Software. Prentice Hall, 1990.

....common phases: 1. Understand user requirements; 2. Identify and classify objects; 3. Define classes; 4. Identify relationships between objects; and 5. Specify behavior of classes and objects. Many object oriented analysis methods has been developed: ffl Responsibility Driven Design [WBWW90] ffl Object Oriented Design [Boo91] ffl Object Oriented Analysis [CY91] ffl Object Modeling Technique [RBP 91] ffl Object Oriented System Analysis [EKW91] ffl Object Oriented Software Engineering [Jac92] ffl Object Oriented Analysis Design [MO92] and many others. Ste93] MP92] and ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener, Designing object-oriented software, Englewood Cliffs: Prentice-Hall, 1990.

....them with examples. For each category, we discuss strengths and weaknesses of stereotypes and present a preliminary set of stereotype design guidelines. 1 Introduction Since about 1990 a broad variety of object oriented modeling languages have been developed [1] 2] 3] 4] 9] 11] 13] 14][17]. These languages are used to describe the requirements and the design of a software system. Since 1996, various attempts have been made to unify different methods and languages. As a result of this endeavor, two languages have been developed: the Unified Modeling Language UML [12] and the Open ....

Wirfs-Brock, R., Wilkerson, B., Wiener, L. (1993): Designing Object-Oriented Software. Englewood Cliffs, N. J.: Prentice Hall.

....the system when a library is included and rechecking each time a new module which uses the library is added. 4.2 Design in the Object Oriented Paradigm Now we turn to the analysis of an example from the Object Oriented Paradigm. The design we will study (with minimal changes) can be found in [WWW90]. In the Object Oriented Paradigm, we usually have much more information about each class in the design. For example, the list of responsibilities that the class defines, the class type (abstract or concrete) etc. are generally included in the graph. We will show how to handle the extra ....

Wirfs-Brock, R., Wilkerson, B., and Wiener, L. Designing Object-Oriented Software. Prentice Hall, 1990. 21

....16] Currently, these methods presume the existence of a formal description of requirements. But, unfortunately, formal descriptions of requirements for large systems are not easy to obtain. Other approaches to requirements analysis and design include the numerous object oriented 2 techniques [17, 18, 19, 20]. These informal methods enable the rapid construction of a system model using intuitive graphics and user friendly languages. While such techniques have proved to be useful tools, the graphical notations used with these methods are often ambiguous, resulting in diagrams that are easily ....

R. Wirfs-Brock, B. Wilkerson, and L. Wiener, Designing Object-Oriented Software. Englewood, New Jersey: Prentice Hall, 1990.

....The analysis and design of complex software requires the use of well defined methods to ensure consistency, traceability and uniformity. We have evaluated several OO methods [3] to understand their applicability to HEP software problems. We have found that a Responsibility Driven Approach [4], which permits to obtain a model with distributed responsibilities among the various collaborating objects, is the most suited to the problem of HEP event reconstruction. Among the various methods which support such an approach, we have chosen the Booch Method [5] to base our prototype upon ....

R. Wirfs-Brock et al. Designing Object-Oriented Software, (Prentice Hall, Englewood Cliffs, New Jersey, 1990). 7

....[Maughan94, Renouf94] Le rle peut apparatre ds les phases de capture des besoins (Catalysis, D Souza98] et d analyse (OORAM, Reenskaugh92] Dans ces deux dernires, l approche est commune : il s agit de crer et de reprsenter des collaborations d objets. Le rle spcifie alors les responsabilits [Wirfs Brock90] des objets dans les diffrentes collaborations. La modlisation l aide de rles consiste diviser un problme en sous problmes lors de l analyse puis synthtiser ces derniers lors de la conception du systme global. La Figure 1 [D Souza98] montre un objet livre servant de charnire conceptuelle pour les ....

Wirfs-Brock R., Wilkerson B., Wiener L., Designing Object Oriented Software, Prentice-Hall, 1990

No context found.

R. Wirfs-Brock, B. Wilkerson, and L. Wiener, Designing Object-Oriented Software. Englewood Cliffs, NJ: Prentice Hall, 1990.

No context found.

Wirfs-Brock, R., Wilkerson, B. and Wiener, L., Designing Object-Oriented Software, Englewood Cliffs, Prentice-Hall, 1990.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC