Scribd Logo
Upload

Welcome to Scribd!

  • 36 views

    YogiNotes OOADi

    Uploaded by

    yogendra sahu
    Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as interacting objects. OOA focuses on analyzing functional requirements, producing a conceptual model of the problem domain. OOD takes the conceptual model and transforms it based on implementation constraints to produce a model of the solution domain describing how the system will be built. The result of OOA is a description of required system functions using use cases, class diagrams, and interaction diagrams.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    YogiNotes OOADi

    Uploaded by

    yogendra sahu
    36 views2 pages
    Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as interacting objects. OOA focuses on analyzing functional requirements, producing a conceptual model of the problem domain. OOD takes the conceptual model and transforms it based on implementation constraints to produce a model of the solution domain describing how the system will be built. The result of OOA is a description of required system functions using use cases, class diagrams, and interaction diagrams.

    Original Title

    YogiNotes.OOADi

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as interacting objects. OOA focuses on analyzing functional requirements, producing a conceptual model of the problem domain. OOD takes the conceptual model and transforms it based on implementation constraints to produce a model of the solution domain describing how the system will be built. The result of OOA is a description of required system functions using use cases, class diagrams, and interaction diagrams.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    36 views2 pages

    YogiNotes OOADi

    Uploaded by

    yogendra sahu
    Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as interacting objects. OOA focuses on analyzing functional requirements, producing a conceptual model of the problem domain. OOD takes the conceptual model and transforms it based on implementation constraints to produce a model of the solution domain describing how the system will be built. The result of OOA is a description of required system functions using use cases, class diagrams, and interaction diagrams.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    1

    Object-oriented analysis and design

    Object-oriented analysis and design (OOAD) is a software


    engineering approach that models a system as a group of interacting objects. Each
    object represents some entity of interest in the system being modelled, and is
    characterised by its class, its state (data elements), and its behavior.

     Various models can be created to show the static structure, dynamic behavior,
    and run-time deployment of these collaborating objects. There are a number
    of different notations for representing these models, such as the Unified
    Modelling Language (UML).
     Object-oriented analysis (OOA) applies object-modelling 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 objects. The behavior of the system results
    from the collaboration of those objects. Collaboration between objects involves those
    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 modelled, 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 during object-oriented design (OOD).
    Analysis is done before the Design.

    YogiNotes.OOADi
    2

    The sources for the analysis can be a written requirements statement, a formal vision
    document, and 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 diagrams, and a number
    of interaction diagrams. It may also include some kind of user interface mock-up.
    The purpose of object oriented analysis is to develop a model that describes
    computer software as it works to satisfy a set of customer defined requirements.

    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.

    Manzil mushkil to kya.... dhundhla saahil to kya..... tanhaa ye dil to kya.......

    YogiNotes.OOADi

    You might also like