Scribd Logo
Upload

Welcome to Scribd!

  • 186 views

    CT015-3.5-2 Design Methods: Concurrent Object Modeling and

    Uploaded by

    Aiyas Aboobakar
    COMET is a UML-based object-oriented software design method that addresses requirements, analysis, and design modeling. It uses actors and use cases to define requirements in the requirements model. The analysis model describes participating objects and their interactions through use cases. The design model develops the software architecture by mapping the analysis model to an operational environment.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    CT015-3.5-2 Design Methods: Concurrent Object Modeling and

    Uploaded by

    Aiyas Aboobakar
    186 views11 pages
    COMET is a UML-based object-oriented software design method that addresses requirements, analysis, and design modeling. It uses actors and use cases to define requirements in the requirements model. The analysis model describes participating objects and their interactions through use cases. The design model develops the software architecture by mapping the analysis model to an operational environment.

    Original Title

    2.1_COMET.pdf

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    COMET is a UML-based object-oriented software design method that addresses requirements, analysis, and design modeling. It uses actors and use cases to define requirements in the requirements model. The analysis model describes participating objects and their interactions through use cases. The design model develops the software architecture by mapping the analysis model to an operational environment.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    186 views11 pages

    CT015-3.5-2 Design Methods: Concurrent Object Modeling and

    Uploaded by

    Aiyas Aboobakar
    COMET is a UML-based object-oriented software design method that addresses requirements, analysis, and design modeling. It uses actors and use cases to define requirements in the requirements model. The analysis model describes participating objects and their interactions through use cases. The design model develops the software architecture by mapping the analysis model to an operational environment.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 11

    CT015-3.

    5-2 Design Methods


    Concurrent Object Modeling and
    Architectural Design Method
    (COMET)

    Learning Outcome
    After completing this module, you will be
    able to:
    Understand COMET
    Explain each model of COMET

    CT015-3.5-2 Design Methods

    COMET

    Topic & Structure of the Lesson

    COMET
    Requirement Model
    Analysis Model
    Design Model

    CT015-3.5-2 Design Methods

    COMET

    COMET
    A UML-Based Software Design Method for Single
    Systems.
    COMET is a highly iterative object-oriented software
    development method that addresses the requirements,
    analysis, and design modeling phases of the objectoriented development life cycle.
    The functional requirements of the system are defined in
    terms of actors and use cases.
    A use case can be viewed at various levels of detail.

    CT015-3.5-2 Design Methods

    COMET

    COMET (Contd)
    In a requirements model, the functional requirements of the
    system are defined in terms of actors and use cases.
    In an analysis model, the use case is realized to describe
    the objects that participate in the use case, and their
    interactions.
    In the design model, the software architecture is
    developed, addressing issues of distribution, concurrency,
    and information hiding.

    CT015-3.5-2 Design Methods

    COMET

    Requirements Model
    A requirements model is developed in which the functional
    requirements of the system are defined in terms of actors
    and use cases.
    A narrative description of each use case is developed.
    User inputs and active participation are essential to this
    effort.
    If the requirements are not well understood, a throwaway
    prototype can be developed to help clarify the
    requirements.

    CT015-3.5-2 Design Methods

    COMET

    Analysis Model

    Static and dynamic models of the system are developed.

    The static model defines the structural relationships


    among problem domain classes. The classes and their
    relationships are depicted on class diagrams. Objectstructuring criteria are used to determine which objects
    should be considered for the analysis model.
    A dynamic model is then developed in which the use
    cases from the requirements model are realized to show
    the objects that participate in each use case and how they
    interact with each other. Objects and their interactions are
    depicted on either communication diagrams or sequence
    diagrams.
    CT015-3.5-2 Design Methods

    COMET

    Design Model
    The software architecture of the system is designed that is
    that is, the analysis model is mapped to an operational
    environment.
    The analysis model (which emphasizes the problem
    domain) is mapped to the design model (which emphasizes
    the solution domain).
    Subsystem structuring criteria are provided to structure the
    system into subsystems, which are considered as
    aggregate or composite objects.
    Special consideration is given to designing distributed
    subsystems as configurable components that communicate
    with each other using messages.
    CT015-3.5-2 Design Methods

    COMET

    Summary

    COMET
    Requirement Model
    Analysis Model
    Design Model

    CT015-3.5-2 Design Methods

    COMET

    Q&A

    CT015-3.5-2 Design Methods

    COMET

    Next Session
    UML Modeling

    CT015-3.5-2 Design Methods

    COMET

    You might also like