Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “object-oriented analysis”

Object Oriented Analysis

Coad, Peter, Yourdon, Edward · 1990

<p>A step-by-step approach to: defining and communicating system requirements, understanding the application domain in which the user operates, integrating the data and process models, analyzing and specifying systems using self-contained partitioning, gaining leverage through explicit representation of commonality, applying a consistent underlying representation for analysis, and accommodating families of systems.</p>

Cited by 0

Object-Oriented Analysis

2007

Introduction. 1. Improving Analysis with Object-Oriented Techniques. 2. Experiencing an Object Perspective. 3. Identifying Objects. 4. Identifying Structures. 5. Identifying Subjects. 6. Defining Attributes. 7. Defining Services. 8. Moving to Object-Oriented Design.

Cited by 1,636

Object‐Oriented Analysis

Sidney C. Bailin · Encyclopedia of Software Engineering · 2002

Abstract Object‐oriented analysis is a method of formulating a model of a desired software system in terms of objects and their interactions. The discipline was started by practitioners of object‐oriented design who found that conventional process‐oriented analysis methods, such as structured analysis (Gane and Sarsen, 1987; DeMarco, 1979) or SADT (Marca and McGowan, 1987), did not flow well into an object‐oriented design. The difficulties in proceeding from structured analysis to object‐oriented design stem from differences in the criteria for decomposing a system into subsystems and lower level components. Converting a process‐oriented decomposition—the result of a structured analysis—into an object‐oriented decomposition frequently requires a great deal of reorganization. [An early example of this may be found in Section of Seidewitz and Stark 1986]. Object‐oriented analysis seeks to decompose a system into interacting parts that represent the user's requirements as faithfully as conventional analysis methods, but to do so in a way that is compatible with object‐oriented design. Compatibility with object‐oriented design was intended to facilitate the transition from the analysis to the design phase. Whether it really does so is a topic still being debated. At the very least, formulating requirements in terms of objects provides a sound basis for the transition to design. It also simplifies the traceability of requirements throughout the development life cycle, and therefore reduces the disruption involved in iterating over analysis and design (i.e., backtracking to the analysis if the design implications are discovered to be infeasible). Historically, OOA arose for these reasons. Some proponents of the approach argue that the object‐oriented framework provides a more robust and accurate description of user requirements than do the conventional approaches, and is therefore to be preferred intrinsically over process‐oriented analysis.

Cited by 7

Object oriented (domain) analysis

John C. Burnham, Dennis de Champeaux · ACM SIGPLAN OOPS Messenger · 1991

article Free Access Share on Object oriented (domain) analysis Authors: John Burnham View Profile , Dennis de Champeaux View Profile Authors Info & Claims ACM SIGPLAN OOPS MessengerVolume 3Issue 4Oct. 1, 1992 pp 83–90https://doi.org/10.1145/143776.143798Online:01 September 1991Publication History 0citation412DownloadsMetricsTotal Citations0Total Downloads412Last 12 Months3Last 6 weeks1 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Cited by 0

Object Oriented Locational Analysis

Marc P. Armstrong, Paul J. Densham, David A. Bennett · Iowa Research Online (The University of Iowa) · 1989

An object oriented approach to the analysis of spatial data is presented. W6 begin by describing object oriented programming, and then define a structure of spatial and analytical objects within the problem domain of locating facilities. From these objects a set of object classes and inheritance structures is created. The spatial and analytical objects are represented using frames. A Smalltalk implementation of a heuristic location-allocation algorithm is also described.

Cited by 9Open access

TO OBJECT ORIENTED ANALYSIS

Viviana L. Rubinstein, Jorge L. Boria · 1994

According to the Software Engineering Institute (SEI) Capability Maturity Model (CMM), Software Product Engineering is a Key Process Area in Level 3 Organizations. Those companies already doing Software Product Engineering are the ones that could most benefit from Object Oriented techniques. However, few are using it, having invested in development techniques supported in structured analysis and design. Many are reluctant to change because they feel this investment in structured techniques would be lost. This paper shows that it is possible and desirable to use many of the tools in a traditional event-driven approach in analysis to build an object-oriented model of a system under study. Moreover, this approach is fully traceable, and it has the added benefit of allowing the use of CASE tools that are available in today's organizations.

Cited by 2

Object-Oriented Image Analysis

Thomas C. Rearick · Proceedings of SPIE, the International Society for Optical Engineering/Proceedings of SPIE · 1987

An image analysis workstation is described which supports the object-oriented representation and manipulation of grayscale sensed image objects. Segmented grayscale images are transformed automatically into a novel list-oriented representation. Image objects resemble jigsaw puzzle pieces which fit together to form a grayscale image. An image object contains information about its appearance and methods for its manipulation. Image objects are defined within the Flavors object-oriented language and are implemented on a Symbolics LISP machine. Applications include multi-sensor image fusion, data fusion, automated cartography, automated reconnaissance, and image understanding system development.

Cited by 13

Object oriented (domain) analysis

John C. Burnham, Dennis de Champeaux · 1991

article Free Access Share on Object oriented (domain) analysis Authors: John Burnham View Profile , Dennis de Champeaux View Profile Authors Info & Claims ACM SIGPLAN OOPS MessengerVolume 3Issue 4Oct. 1, 1992 pp 83–90https://doi.org/10.1145/143776.143798Online:01 September 1991Publication History 0citation411DownloadsMetricsTotal Citations0Total Downloads411Last 12 Months2Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Cited by 7Open access

Rigorous Object-Oriented Analysis

Ana Maria, Dinis Moreira · 2008

1994 Object-oriented methods for analysis, design and programming are commonly used by software engineers. Formal description techniques, however, are mainly used in a research environment. We have investigated how rigour can be introduced into the analysis phase of the software development process by combining object-oriented analysis (OOA) methods with formal description techniques. The main topics of this investigation are a formal interpretation of the OOA constructs using LOTOS, a mathematical definition of the basic OOA concepts using a simple denotational semantics and a new method for objectoriented analysis that we call the Rigorous Object-Oriented Analysis method (ROOA). The LOTOS interpretation of the OOA concepts is an intrinsic part of the ROOA method. It was designed in such a way that software engineers with no experience in LOTOS, can still use ROOA. The denotational semantics of the concepts of object-oriented analysis illuminates the formal syntactic transformations within ROOA and guarantees that the basic objectoriented

Cited by 0