Scribd Logo
Upload

Welcome to Scribd!

  • 19 views

    Object Oriented Modeling: Sessions 8 and 9

    Uploaded by

    toabhishekpal
    Object oriented modeling describes a system using objects, classes, and relationships between them. An object has attributes and methods, and similar objects are grouped into classes which can have subclasses. Classes can inherit attributes and methods from parent classes. Use cases represent business processes with actors initiating requests, while class diagrams show class relationships and cardinality. Sequence diagrams illustrate class interactions over time and state transition diagrams show how object states change with events. Activity diagrams depict actions and events as they occur.

    Copyright:

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

    Object Oriented Modeling: Sessions 8 and 9

    Uploaded by

    toabhishekpal
    19 views9 pages
    Object oriented modeling describes a system using objects, classes, and relationships between them. An object has attributes and methods, and similar objects are grouped into classes which can have subclasses. Classes can inherit attributes and methods from parent classes. Use cases represent business processes with actors initiating requests, while class diagrams show class relationships and cardinality. Sequence diagrams illustrate class interactions over time and state transition diagrams show how object states change with events. Activity diagrams depict actions and events as they occur.

    Original Description:

    Session 8,9

    Original Title

    Session 8,9

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Object oriented modeling describes a system using objects, classes, and relationships between them. An object has attributes and methods, and similar objects are grouped into classes which can have subclasses. Classes can inherit attributes and methods from parent classes. Use cases represent business processes with actors initiating requests, while class diagrams show class relationships and cardinality. Sequence diagrams illustrate class interactions over time and state transition diagrams show how object states change with events. Activity diagrams depict actions and events as they occur.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    19 views9 pages

    Object Oriented Modeling: Sessions 8 and 9

    Uploaded by

    toabhishekpal
    Object oriented modeling describes a system using objects, classes, and relationships between them. An object has attributes and methods, and similar objects are grouped into classes which can have subclasses. Classes can inherit attributes and methods from parent classes. Use cases represent business processes with actors initiating requests, while class diagrams show class relationships and cardinality. Sequence diagrams illustrate class interactions over time and state transition diagrams show how object states change with events. Activity diagrams depict actions and events as they occur.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 9

    OBJECT ORIENTED

    MODELING
    Sessions 8 and 9

    OBJECTS
    An object represents a place, event or
    transaction.
    Object oriented analysis describes a system by
    identifying and defining objects.

    Object has
    1.
    Attributes: Characteristics of an object.
    2.
    Methods: Tasks or functions that are performed
    when the object receives some inputs.
    . A group of similar objects is called a class.
    . Class can be divided into subclasses.

    INHERITANCE PROPERTY

    It enables an object (called child) to derive


    various attributes and methods from its parent
    object.

    USE CASES
    A use case represents steps in a business process.
    External entities are called actors.
    Actors initiate the system by sending requests to
    perform certain actions.
    A use case diagram is a visual representation of
    several related use cases within a system.

    CLASS DIAGRAMS
    A class diagram describes a detailed view of
    every use case and depicts the classes that
    participate in the use case.
    Cardinality represents how instances of one class
    relate to the instances of another class.

    SEQUENCE DIAGRAMS

    It shows the interaction among the classes during


    a specified period of time.

    STATE TRANSITION DIAGRAMS

    It shows how an object changes from one state to


    another depending on the events that affect the
    object.

    ACTIVITY DIAGRAMS

    An activity represents a horizontal flowchart that


    shows the actions and events as they take place.

    You might also like