G. Booch. Object-Oriented Development. IEEE Transaction on Software Engineering, February 1986.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....speaking, the approach described here is an extension of the Control Paradigm developed by Shaw [9] and can be called the Intelligent Control Paradigm of software architecture. Shaw developed the Control Paradigm as one approach to the canonical design problem of the cruise control challenge [10]. She says: This system organisation [feedback control software] is not widely recognised in the software community; nevertheless it seems to quietly appear within designs dominated by other models. Unlike object oriented or functional designs, which are characterised by the kinds of components ....

Booch, G., Object-Oriented Development. IEEE Transactions on Software Engineering, 1986. 2(12): p. 211-221.

....Ei#el, etc. It was also during the 80s that the ideas introduced by OOP languages were generalized into software engineering principles. The term object oriented design was first used by Booch [16, 17] in 1981. In 1986, Booch began to refer to his approach as object oriented development [18]. Object oriented software development advocates the use of objects during the whole software development cycle. The four main activities in software development are analysis, design, implementation and testing. We use objectoriented analysis to define analysis objects that capture the problem ....

G. Booch. Object oriented development. IEEE Transactions on Software Engineering, SE-12(2):211--221, February 1986.

....of object oriented programming, the fundamental features can be beneficial even if these concepts are not applied. Although Fortran 90 was not designed as an object oriented language, we are not the first to develop an object oriented methodology for a language not explicitly object oriented [2, 11]. Our experience indicates that it is possible to use Fortran 90 features to model many aspects of explicitly object oriented languages [5] However, such modeling can be tedious at times since some features, such as sub typing inheritance, must be constructed explicitly in Fortran 90. Efforts to ....

G. Booch, Object-Oriented Development, IEEE Transactions on Software Engineering, SE-12 (1986), pp. 211-221.

....partitioning principle in which data is separated from processing. This partitioning goes against the object oriented partitioning principle that data and processing should be grouped together [32, 57] Second, all the data in a data store is globally accessible to any process that accesses it [4]. This again contrasts with the object oriented encapsulation of data with the processes that access it. Third, data flow diagrams specify the operations that take place during an action, and this tends to have a bias towards implementation [23, 32] To be completely free from any implementation ....

G. Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE-12:211--221, 1986.

....whose data stores correspond to objects, the state of an object is separated from its actions. The state ends up as a record in a data store and an action ends 12 up as a software component that accesses the data store. Another consequence is that the state of an object, in the words of Booch [5], is globally accessible in the DF diagram. Any data transformation that accesses a data store, has access to all records in the data store. This contrasts with the encapsulation of state and behaviour in JSD. In a JSD model of the UoD, an action can only access the local state of the object in ....

G. Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE-12:211-- 221, 1986.

....memory and initiate the execution of the object oriented network. The transformation engine has been developed using EuLisp[9] and, to be more precise, the EuLisp object system known as TE O [3] We decided to apply a well known objectoriented development methodology, that described by Booch [2], to design the new implementation of OPS5, which we have named OOPS5. The ve stages Booch identi es for this process are: 1. Identi cation of objects and attributes; 2. Identi cation of the behaviour of each object; 3. Establishment of the visibility of each object; 4. Establishment of the ....

....wm vector insert wme retrieve wme class retrieve wme wm clock wm clock time retrieve wm time 2. 3 Behaviour of objects The behaviours of objects can be further segregated into static, being the methods de ned on an object, and dynamic, being time or space constraints on an object [2]. In this exposition we describe these two aspects together. Table 1 summarizes these objects and their su ered and required methods. To help present the underlying algorithm that controls the execution of a derived object oriented production system, the behaviour of each of the objects ....

[Article contains additional citation context not shown here]

G. Booch. Object-oriented development. IEEE Transactions On Software Engineering, SE-12(2):211-221, February 1986.

.... industry, largely as the result of the opinions of experts and of market forces despite warnings about relying only on such evidence [10] Its advocates argue that it has a number of benefits compared to conventional technology, for example ffl Designs more suited to real world problems [4,43,44]. ffl Software that is easier to understand [4,41] ffl Software that better facilitates maintenance and enhancement [2,4,43] ffl Software that resists degradation [4,41] ffl Better support for software reuse [2,4,35] ffl Improved programmer productivity[11,4] ffl Reduction in ....

.... of experts and of market forces despite warnings about relying only on such evidence [10] Its advocates argue that it has a number of benefits compared to conventional technology, for example ffl Designs more suited to real world problems [4,43,44] ffl Software that is easier to understand [4,41]. ffl Software that better facilitates maintenance and enhancement [2,4,43] ffl Software that resists degradation [4,41] ffl Better support for software reuse [2,4,35] ffl Improved programmer productivity[11,4] ffl Reduction in total life cycle costs [11] ffl Easier testing [43] ....

[Article contains additional citation context not shown here]

G. Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE-12(2):211--221,February 1986. 25

....more humanly accessible constructs to code. Second, the software community is not completely solidified and in agreement on which diagrammatic methods to employ, although the Unified Modeling Language (UML) 51, 46, 15] is gaining considerable momentum since it combines earlier methods from Booch [14, 13] and Rumbaugh [66] Visual formalisms for object oriented software began with the Software Engineering research and is being made manifest today by 2D graphical methods for FSMs such as StateCharts [35] The software engineering community realizes the benefits of modeling, but more progress is ....

Grady Booch. Object-Oriented Development. IEEE Transactions on Software Engineering, 12(2):211 -- 221, February 1986.

.... prototypes directly from functional specifications[6] In this context at the beginning of the 80s, Object Oriented approaches began to emerge among the software community, and this originally was in response, to the needs of the ADA language [3] We recall that the pioneering work of Booch OOD[2] comes from this early period and culminated with the ESA HOOD[15] European Space Agency Hierarchical Object Oriented Design) project. From the beginning it became clear that according to accepted definitions object oriented techniques were more related to design than analysis. In this respect, ....

....definitions object oriented techniques were more related to design than analysis. In this respect, it is worth noting that HOOD proposes the use of classical SADT techniques in order to perform requirement analysis and specifications which can then be transferred into an Object Oriented Design[2, 15] [14] Even now, the issue of what Object Oriented Analysis means, and of what interrelationships there are between Analysis and the other phases of the software life cycle (in particular Design and Prototyping) in an Object Oriented context, has not yet been settled completely. There are ....

G. Booch, Object oriented development, IEEE Transactions on Software Engineering, SE-12, February 1986.

....of an object only if the process has ownership of the object. No single model can describe every aspect of this complex system. A combination of modeling techniques makes high assurance development of secure operating systems possible. 2. 1 Object Oriented Modeling Object oriented development [4] has gained wide acceptance in practice. Objects closely mimic realworld objects, roles, and behavior. Modeling techniques based on object technology are intuitive and easily understood. The transition from object oriented design to object oriented implementation is relatively smooth, because ....

Grady Booch. Object-oriented development. IEEE Transactions on Software Engineering, 12(2):211-- 221, February 1986.

....into object languages and for each functional interface produce a propagation pattern graph, which is a semi class dictionary graph, to describe the code structure. The detail is in [LXSL91] Numerous researchers have proposed object oriented design notations, both graphical and textual (e.g. Boo86, Boo91, RBP 91] Some researchers have noticed that there is a connection between a grammar definition and a class definition: San82] Joh88] Weg88] MN88] etc. The Demeter system takes advantage of the class grammar connection in a sophisticated way 5 CD Graph C D Sentences ....

Grady Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE-12(2), Feb. 1986.

....is that in the level 0 data flow model, the state of an object is separated from its actions, for the state ends up as a record in a data store and an action ends up as a software component that accesses the data store. Another consequence is that the state of an object, in the words of Booch [6], is globally accessible in the DFD. Any data transformation that accesses a data store, has access to all records in the data store. This contrasts with the localisation of state and behaviour in JSD. In a JSD model of the UoD, an action can only access the local state of the object in whose life ....

G. Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE-12:211-- 221, 1986.

....not a bijection between T reeObjects(AorB CorD) and Sentences(AorB CorD) because g print maps the two different AorB CorD objects in Fig. 11a and Fig. 11b to the sentence a . 6 Conclusions Numerous researchers have proposed object oriented design notations, both graphical and textual (e.g. Boo86, Boo91, RBP 91] Some researchers have noticed that there is a connection between a grammar definition and a class structure definition: San82] Joh88] Weg88] MN88] etc. We have described class dictionaries as customizers for an important new kind of software, called adaptive ....

Grady Booch. Object-oriented development. IEEE Transactions on Software Engineering, SE12 (2), Feb. 1986.

.... phase into the implementation [ChF92] An object oriented design method results in an object oriented decomposition defining a model or a set of models that has a notation and a process that support the building of complex systems and consider the logical and the physical aspects of the system [Boo86]. It is seen as a solution centred activity. It involves re examining the problem domain classes, and refining, extending or reorganising those classes. It is a transformation process, mapping declarative descriptions of objects and classes to implementation plans. 40 Object oriented design is ....

Booch, G. Object Oriented Development. IEEE Transactions on Software Engineering, Vol SE-12, No. 2, February 1986.

....and methodology. More details can be found in [14, 17] The OBSERV language combines several paradigms to express the behavior of a system. The object oriented approach provides the basic mechanism for building a system from a collection of objects, with well defined interfaces between them [4]. We use finite state machines to model the behavior of individual objects [10] At a lower level, activities that occur within objects (either upon entry to a state or in transition between states) are described with the logic programming paradigm (Prolog) thus allowing a non procedural ....

G. Booch, Object Oriented Development, IEEE Transactions on Software Engineering, Vol. SE12, No. 2, Feb. 1986, pp. 211--221.

....[8] while active object systems like SAOS [15] have some resemblance to the definitions and protocols in an LSD script. 2.3 Requirements for a Vehicle Cruise Control System: a Case Study 2.3. 1 Overview A vehicle cruise control system has been the focus of several software specification studies [5], 8] 9] The examples in this section are drawn from a vehicle cruise control simulation 8 developed within in our framework and which we regularly use for demonstration purposes. The model was not built primarily as a simulation: it was built to explore our modelling methods. The simulation ....

G. Booch. Object-oriented development. IEEE Transactions in Software Engineering, 12(2):285--292, 1986.

....paper, we are concerned with the reusability of products and in particular with that of the source code. The fundamental question is what can be reused from an existing software system and how easy it is. Modular designs have been proposed [11] as a flexible means to promote reusability. Booch [8] claims that greater gains are obtained from the reuse of archived designs and subsystems than from individual components or objects. This does not occur unless there is some specialization in the problem domain. For example, consider a software factory: although there might be some 18 diversity ....

....that generics offer support for classes. The rest of the properties are not directly or implicitly supported by the Ada rationale. Ada is predominantly an encapsulation language , but as was pointed out, it maintains a certain number of characteristics that enable pragmatic Object Oriented design[8]. In most cases, a set of fundamental system objects that model a problem are identified. Subsequently, their operations, interfaces, interactions and structures are designed. In contrast with the previous two approaches, this methodology tends to be more localized as far as changes are ....

G. Booch. Object--Oriented Development. IEEE Transactions on Software Engineering, 12(2):211--221, February 1986.

....linguistic world and the conceptual world. 7 The idea of identifying these relations is not new. As early as in 1983, Abbot (Abbot, 1983) explained that nouns could be used to derive classes, adjectives to derive attributes, and verbs to define methods, an idea that was subsequently adopted by Booch (Booch, 1986). Burg (Burg, 1997) conducted some of the most rigorous research in this area, seeking to define relations using an intermediate language. However, the above relations are not fully justified and do not account for all the key elements in a conceptual model. Table 1 shows the most important ....

Booch, G., Object Oriented Development, IEEE Transactions on Software Engineering, 12 (2), 211-221 (February 1986).

....on the benefits and shortcomings of the current object oriented methods. The best way to determine these was to apply object oriented techniques to realistic examples in the form of pilot studies. At that time, however, not so many methods were available. We studied Booch s earlier publications [12, 13], and defined our own method. When new methods were introduced [2 11, 14] we updated our method carefully [64] Our intention was to combine what we considered to be the best of these methods. For example, we used Coad and Yourdon s layered approach and their hints for object identification [4, ....

G. Booch, Object-Oriented Development, IEEE Transactions on Software Engineering, Vol. SE-12, No. 2, pp. 211-221, February 1986.

No context found.

G. Booch. Object-Oriented Development. IEEE Transaction on Software Engineering, February 1986.

No context found.

G. Booch, Object Oriented Development, IEEE transactions on Software Engineering, Vol 12, No. 2 (1986) 211-221.

No context found.

G. Booch. Object Oriented Development. IEEE Transactions on Software Engineering, SE-12(2):211--221, 1986.

No context found.

Booch, G., Object-Oriented Development, IEEE Transactions on Software Engineering, February 1986, pp. 211-221.

No context found.

G. Booch, Object oriented development, IEEE Transactions on Software Engineering, SE-12, February 1986

No context found.

Object-Oriented Software Evolution. IEEE Transactions on Software Engineering, 19(4):313--343, April 1993.

First 50 documents

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