| Object-oriented Analysis And Design |
Article Index for Object-oriented |
Website Links For Analysis |
Information AboutObject-oriented Analysis And Design |
| CATEGORIES ABOUT OBJECT-ORIENTED ANALYSIS AND DESIGN | |
| object-oriented programming | |
| software development | |
| software engineering | |
|
Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a system. Object-oriented design (OOD) elaborates the analysis models to produce implementation specifications. OOA focuses on ''what'' the system does, OOD on ''how'' the system does it. OBJECT-ORIENTED SYSTEMS An object-oriented system is composed of Object s. The behavior of the system results from the collaboration of those objects. Collaboration between objects involves them sending messages to each other. Sending a message differs from calling a function in that when a target object receives a message, it itself decides what function to carry out to service that message. The same message may be implemented by many different functions, the one selected depending on the state of the target object. The implementation of "message sending" varies depending on the architecture of the system being modeled, and the location of the objects being communicated with. OBJECT-ORIENTED ANALYSIS Object-oriented analysis ('''OOA''') looks at the problem domain, with the aim of producing a conceptual model of the information that exists in the area being analyzed. Analysis models do not consider any implementation constraints that might exist, such as Concurrency , Distribution , Persistence , or how the system is to be built. Implementation constraints are dealt with during object-oriented design (OOD). The sources for the analysis can be a written requirements statement, a formal vision document, interviews with stakeholders or other interested parties. A system may be divided into multiple domains, representing different business, technological, or other areas of interest, each of which are analyzed separately. The result of object-oriented analysis is a description of ''what'' the system is functionally required to do, in the form of a conceptual model. That will typically be presented as a set of Use Cases , one or more UML Class Diagram s, and a number of interaction diagrams. It may also include some kind of User Interface mock-up. OBJECT-ORIENTED DESIGN See Also: Object oriented design Object-oriented design ('''OOD''') transforms the conceptual model produced in object-oriented analysis to take account of the constraints imposed by the chosen architecture and any non-functional—technological or environmental—constraints, such as transaction throughput, response time, run-time platform, development environment, or programming language. The concepts in the analysis model are mapped onto implementation classes and interfaces. The result is a model of the solution domain, a detailed description of ''how'' the system is to be built. LITERATURE
SEE ALSO
EXTERNAL LINKS
|
|
|