R. Fichman and C. Kemerer, "Object-Oriented and Conventional Analysis and Design Methodologies: Comparison and Critique," Computer, Oct. 1992, pp. 22-39.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Modeling Language [3] These description techniques define different views on the application system or the software system. While the particular notations and views have changed over the years adhering to a structured, data oriented or object oriented paradigma (for a comparison see e.g. [7]) the use of views in software development is indespensable in order to concentrate on different system aspects (e.g. static structure, data, behaviour) on different abstraction levels. The former reflect concerns of the different participants (e.g. manager, user, system analyst, software ....

R.G. Fichman and C.F. Kemerer. Object-oriented and conventional analysis and design methodologies. IEEE Computer, pages 22--39, october 1992.

.... Semantic Gap Application Computer Analysis Design Implementation Figure B.4: The semantic gap Object oriented design methods di#er from traditional ones. Two categories of traditional design methods are top down and data driven design [FK92] Top down structured design [BCN92, ACPT99] looks at the problem as a single function that is decomposed into subfunctions in a structured manner to yield small enough function components that can be implemented as a module or software unit. Data driven design focuses on the input and output ....

R.G. Fichman and C.F. Kemmerer. Object-Oriented and Conventional Analysis and Design Methods: Comparison and Critique. IEEE Computer, pages 22--39, October 1992.

....modeling method 1 used for the analysis and design of a system, replacing the structured analysis modeling techniques. The emergence of Object Oriented Analysis and Design (OA D) techniques has been the natural consequence of the central assumptions of data oriented analysis and design methods [8]: 1 What we refer to as methods in this paper are often called methodologies. However, in an academic context, the word methodology should properly be used for the study and comparison of methods. ffl Organizational data provides quite a stable foundation for modeling a system, since as 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 (November 17, 1997) According to what is stated in its specification: UML) ....

R.G. Fichman and C.F. Kemerer. ObjectOriented and Conventional Analysis and Design Methodologies. IEEE Computer, 25(10), October 1992.

....middleware such as graphical user interface builders and object management platforms. However, these successes in object oriented programming(OOP) do not necessarily imply successes in object oriented analysis(OOA) and design(OOD) yet al..though many methodologies of OOA and OOD came out around 1990 [8, 16]. Most of conventional OOA OOD methodologies are suitable for large scale database centered systems such as banking systems, but they are not suitable for application software of such new fields as distributed office information systems with end user computing and cooperative work [11] This is ....

R. G. Fichman and C. F. Kemerer. Object-oriented and conventional analysis and design methodologies. IEEE Trans. Computer, 25(10):22--39, Oct. 1992.

.... There are related studies in the research fields of object oriented technology for software reuse [7, 18, 22] Essential concepts of object oriented technology came out around 1970 and were expanded into programming methodologies through 1980 s and into software analysis design methodologies [5, 19] in 1990 s. Object oriented programming has already been used in practice into various software fields. In particular, distributed object management systems such as CORBA and DCOM become important as middleware for distributed object management with network transparency. As our policy, it is easy ....

Fichman,R.G. and Kemerer,C.F., "Object-Oriented and Conventional Analysis and Design Methodologies, " IEEE Computer, vol.25, no.10, pp.22-39, Oct. 1992.

....analysis consists in detailing a problem space and abstracting the entities of the domain. Object oriented analysis organizes a domain that will be eventually programmed in an object oriented language. Only in the past few years we could see the emergence of object oriented analysis methodologies [9]. Similar to structured analysis, the goal of OOA is to develop a consistent and accurate representation of the problem domain. The difference is that OOA does not separate data from procedures. Among more than twenty technologies that came out in past few years, we find three of them being ....

Fichman, Robert G., Kemerer, Chris F.,"Object-Oriented and Conventional Analysis and Design Methodologies," Computer. USA, v. 25, n. 10, pp. 22-39, Oct. 1992.

....a manufacturing system. These design rationales tell a software engineer with no prior experience in agent development how to make agent related design decisions. To this end, many software design methodologies have been developed, including object oriented and even agentoriented approaches (see [6,9] for an overview) But none of these methodologies is applicable to the design of agent based production control systems; they either provide analysis models that are inappropriate for production control or else they lack comprehensive design rationales. The aim of our research work is therefore ....

R.G. Fichman, C.F. Kemerer: "Object-Oriented and conventional analysis and design methodologies -- comparison and critique". In IEEE Computer , Vol. 25, No. 10, pages 22 -- 39, 1992.

.... System State State Model State Model State Model Tool for State Modelling Harel StateCharts Harel StateCharts Harel StateCharts System Partition Subsystem Module, Subsystem Subsystem Subject 1994, Michael Mattsson Page 7 31 Another comparison made by Fichman and Kemerer [Fic92] compares object oriented methods with conventional analysis and design methods. Here we present the results concerning only the object oriented methods (the Objectory method was not included in the comparison) Table 2. The comparison by Fichman is based on the idea that the steps in the ....

....that the method must support the C object model or be language independent. Each methods in the evaluation was scored against a weighted evaluation matrix that reflects Alcatel s development priorities. The five categories were the static and dy Table 2: Common steps in the reference methods [Fic92] Component Booch OMT Coad Yourdon Identification of classes Class diagram Class diagram Class and Objects diagram layer 1 Identification of attributes Class diagram Class diagram Class and Objects diagram layer 4 Identification of operations Class diagram Class diagram State diagram ....

Fichman R G., Kemerer C F., " Object-oriented and Conventional Analysis and Design Methodologies", IEEE Computer, Oct 1992

....in which reuse is strongly motivated to enhance the productivity and quality of the software components. Further, reuse is no longer restricted to mere code since the object oriented abstraction mechanisms facilitate reuse in the earlier phases of the software life cycle (Korson and McGregor 1990; Fichman and Kemerer 1992). Much research has been invested in design and implementation of reusable classes and class hierarchies (Johnson and Foote 1988) but less research has been invested in reuse of analysis and specification components. However, there is a growing belief in the object oriented software engineering ....

Fichman, R. G. and C. F. Kemerer (1992, October). Object-oriented and conventional analysis and design method. IEEE COMPUTER 25 (10), 22--39.

....Modeling Language [3] These description techniques define different views on the application system or the software system. While the particular notations and views have changed over the years adhering to a structured, data oriented or object oriented paradigma (for a comparison see e.g. [7]) the use of views in software development is indespensable in order to concentrate on different system aspects (e.g. static structure, data, behaviour) on different abstraction levels. The former reflect concerns of the different participants (e.g. manager, user, system analyst, software ....

R.G. Fichman and C.F. Kemerer. Object-oriented and conventional analysis and design methodologies. IEEE Computer, pages 22--39, october 1992.

....the customers requirements and any other constraints imposed by the context in which the task is to be performed. That is, software design produces a mechanism to perform the task, and that mechanism is later realised in a programming language. There are many methodologies for designing software [13, 18, 26, 39, 40, 44, 66, 76, 80, 81]. They chiefly address designing a system from scratch rather than design with reuse. Design is an example of a wicked problem [18, pp.19 21] In particular, the requirements for a system may not be fully understood until the design is complete; there is no right answer to the problem, just a ....

....out reusable components. 2.3 Design Design [18] is the activity to produce a description of how to perform a task in such a way that it satisfies the customers requirements and also satisfies any constraints imposed by the environment in which the system is to be used. Design methodologies [18, 26, 44] typically have three principal components: ffl a representation of the design using one or more notations; ffl a process for developing or transforming the representation; and ffl a set of heuristics maybe guiding the order of steps, or the selection of issues that are to be addressed. ....

R.G. Fichman and C.F. Kemerer, Object-oriented and conventional analysis and design methodologies, IEEE Computer 25, 20 (1992) 22--39.

....are gaining an important role in the practice of systems development. These environments are meant to support many diagrammatic techniques [20] used in the software development process. Although several support environments have been developed for conventional and object oriented methodologies [15], a number of factors are limiting their acceptance by the industry. Two of the major limitations of current CASE environments are: ffl lack of customizability ffl lack of support for specifying methodology knowledge In addition to these limitations, the effort to develop such environments is ....

R.G. Fichman and C.F. Kenerer. Object-Oriented and Conventional Analysis and Design Methodologies: Comparison and Critique. IEEE Computer, vol. 25, no. 10, pp. 22-39, October 1992.

....domain and the implementation domain. The clear relationship between domain and implementation objects facilitate Kant and Newell s [115] insight mechanisms. In addition, the principles behind objectorientation modularity, abstraction, encapsulation, reuse have firm theoretical foundations [71]. Object oriented design provides a vocabulary for communication between designers and users in cooperative design episodes. Booch [15] notes that object diagrams, used extensively in object oriented software design, have also been used independently in fields as diverse as astronomy and banking. ....

Fichman, R.G. and Kemerer, C.F., "Object-oriented and conventional analysis and design methods - comparison and critique," IEEE Computer, 22--39, Oct. 1992.

.... the development process [36] reuse problem domain concepts [31, 33] and provide a common platform for software development activities [23] Unfortunately, many aspects of the paradigm are still immature, especially those related to early development activities, such as analysis and design [18]. Consequently, software development organizations are experiencing various difficulties in switching over to an object orientation, including: scaling up technology for large applications [19] managing the development process [41] achieving expected productivity gains [37, 33] and teaching ....

Fichman, R. G. and C. F. Kemerer, "Object-Oriented and Conventional Analysis and Design Methodologies", Computer, Vol. 25, No. 10, October, 1992, pp. 22-39.

....We are only beginning to address these and other issues concerning support for SIB users, taking as starting point the prototype implementation reported here. Finally, while not claiming to address issues concerning software artifact understanding, along the lines of research efforts such as [FiKe92], we do claim that the SIB offers valuable assistance to software artifact understanding efforts through the representation and organization of software descriptions. The remainder of the paper is organized as follows. Section 2 offers an elaboration on the SIB structure, defined in terms of ....

....The SIB model and system have been evaluated in the context of a specific reuseoriented methodology developed in the project ITHACA. Moreover, we have begun the evaluation of the model with other object oriented analysis and design methodologies [FiKe92] starting with the Booch design methodology [Booc91] An obvious advantage of doing the evaluation using the ITHACA methodology is that there already exist substantial amounts of data, generated by companies participating in the project. After all, it is hard to establish the strengths of the SIB ....

Fichman, R.G., and Kemerer, C.F., "Object-oriented and Conventional Analysis and Design Methodologies", in IEEE Computer, October 1992, pp.22-39.

....to a more global comparison, incorporating the signalling of trends in the development of OO methods. The material is mainly based on a study of relevant books ( 13] 14] 12] 71] 6] 7] 35] 70] 61] 41] 62] 63] 27] 15] and articles in which the methods have been described ([21] [25] 26] 69] 52] 10] 2] 56] 33] Additionally, several articles and books containing comparisons of methods have been studied ( 19] 54] 34] 57] 9] 55] 66] 43] Such a comparison can not be complete; doing justice to all features of all methods is impossible in the ....

R. G. Fichman and C. F. Kemerer. Object-oriented and conventional analysis and design methodologies. IEEE-Computer, 25, oct 1993.

.... the current custom development process into one characterized by assembly of previously developed components (Cox 1990) Nevertheless, OOPLs are widely viewed as being particularly difficult to adopt and assimilate, chiefly because of the radical changes they impose on would be adopters (Fichman and Kemerer 1992; Booch 1994) As one recent commentator recently put it: object oriented technology is so radically different that we must break and reset programmers coding hands before they can write object oriented rather than procedural programs (Lewis 1994) A set of four mini case studies of OOPL ....

.... Prescott and Conger 1995) Although a recent meta analysis suggests that some these criticisms may have been overstated (Damanpour 1991) it is nevertheless true that studies with strong results have been comparatively rare, especially when the focal innovation has been information technology (Fichman 1992). One of the more plausible explanations for a lack of strong and consistent results is that researchers, in pursuing the worthy goal of establishing a more general theory of innovation diffusion, may have been working at a theoretical level too far abstracted from particular innovations and ....

Fichman, R. G. and Kemerer, C. F., "Object-Oriented and Conventional Analysis and Design Methodologies: Comparison and Critique," IEEE Computer, October (1992), 22-39.

.... OO principles, must learn how to use commercial implementations of OO languages and various supporting technologies, and must determine how to reconfigure team roles, structures, procedures, and incentives in light of the radical differences between object oriented and conventional development [5]. Prior work has shown that in the case of highly complex technologies such as OO, the difficulty of organizational learning can be the primary barrier to successful adoption [6, 7] Further contributing to the difficulty of transitioning to OO is the need for an extended period of ....

Fichman, R.G. and Kemerer, C.F., "Object-Oriented and Conventional Analysis and Design Methodologies: Comparison and Critique," IEEE Computer, Vol. 23, No. 10, 1992, pp. 2239.

No context found.

R. Fichman and C. Kemerer, "Object-Oriented and Conventional Analysis and Design Methodologies: Comparison and Critique," Computer, Oct. 1992, pp. 22-39.

No context found.

Fichman, R., C. Kemerer. 1992. Object-oriented and conventional analysis and design methodologies. Computer. October, 22-39.

No context found.

Fichman, Robert G. and Chris F. Kemerer. "Object-Oriented and Conventional Analysis and Design Methodologies," IEEE Computer p. 22-39 (October 1992).

No context found.

Fichman, R. G. and Kemerer, C. F., "Object-oriented and conventional analysis and design methodologies, " IEEE Computer, pp. 22--39, October 1992.

No context found.

Fichman, R. G. and Kemerer, C. F., "Object-oriented and conventional analysis and design methodologies, " IEEE Computer, pp. 22--39, October 1992.

No context found.

Fichman, R.G.; Kemerer, C.F.: Object-Oriented and Conventional Analysis and Development Methodologies: Comparison and Critique Boston, Ma. 1991

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