Object-oriented analysis and design

Object-oriented assay and architecture (OOAD) is a software engineering access that models a arrangement as a accumulation of interacting objects. Each article represents some article of absorption in the arrangement getting modeled, and is characterised by its class, its accompaniment (data elements), and its behavior. Various models can be created to appearance the changeless structure, activating behavior, and run-time deployment of these accommodating objects. There are a amount of altered notations for apery these models, such as the Unified Modeling Language (UML).

Object-oriented assay (OOA) applies object-modeling techniques to assay the anatomic requirements for a system. Object-oriented architecture (OOD) elaborates the assay models to aftermath accomplishing specifications. OOA focuses on what the arrangement does, OOD on how the arrangement does it.

Object-oriented systems

An acquisitive arrangement is composed of objects. The behavior of the arrangement after-effects from the accord of those objects. Accord amid altar involves them sending letters to anniversary other. Sending a bulletin differs from calling a action in that if a ambition article receives a message, it decides on its own what action to backpack out to account that message. The aforementioned bulletin may be implemented by abounding altered functions, the one called depending on the accompaniment of the ambition object.

The accomplishing of "message sending" varies depending on the architectonics of the arrangement getting modeled, and the area of the altar getting announced with.

Object-oriented analysis

Object-oriented assay (OOA) is the action of allegory a assignment (also accepted as a botheration domain), to advance a conceptual archetypal that can again be acclimated to complete the task. A archetypal OOA archetypal would call computer software that could be acclimated to amuse a set of customer-defined requirements. During the assay appearance of problem-solving, a programmer ability accede a accounting requirements statement, a academic eyes document, or interviews with stakeholders or added absorbed parties. The assignment to be addressed ability be disconnected into several subtasks (or domains), anniversary apery a altered business, technological, or added areas of interest. Anniversary subtask would be analyzed separately. Implementation constraints, (e.g., concurrency, distribution, persistence, or how the arrangement is to be built) are not advised during the assay phase; rather, they are addressed during acquisitive architecture (OOD).

The conceptual archetypal that after-effects from OOA will about abide of a set of use cases, one or added UML chic diagrams, and a amount of alternation diagrams. It may aswell cover some affectionate of user interface mock-up.

Object-oriented design

During acquisitive architectonics (OOD), a developer applies accomplishing constraints to the conceptual archetypal produced in acquisitive analysis. Such constraints could cover not alone constraints imposed by the called architectonics but aswell any non-functional – abstruse or ecology – constraints, such as transaction throughput, acknowledgment time, run-time platform, development environment, or those inherent in the programming language. Concepts in the assay archetypal are mapped assimilate accomplishing classes and interfaces consistent in a archetypal of the band-aid domain, i.e., a abundant description of how the arrangement is to be bui

Literature

Grady Booch. "Object-oriented Assay and Architecture with Applications, 3rd edition":http://www.informit.com/store/product.aspx?isbn=020189551X Addison-Wesley 2007.

Rebecca Wirfs-Brock, Brian Wilkerson, Lauren Wiener. Designing Object Oriented Software. Prentice Hall, 1990. A common addition to the acquisitive programming and design.

A Theory of Object-Oriented Design: The building-blocks of OOD and notations for apery them (with focus on architecture patterns.)

Martin Fowler. Assay Patterns: Reusable Object Models. Addison-Wesley, 1997. An addition to acquisitive assay with conceptual models

Bertrand Meyer. Acquisitive software construction. Prentice Hall, 1997

Brett McLaughlin, Gary Pollice, David West. Head First Object-Oriented Assay and Design. O'Reilly, 2006.

Craig Larman. Applying UML and Patterns - Addition to OOA/D & Iterative Development. Prentice Hall PTR, 3rd ed. 2005.,mnnm,n,nnn

Setrag Khoshafian. Object Orientation. Wiley, 1995.