Title: Instructor's Perspective - Module 6
Course: CIS2321 Information Systems > Section: Module 6 - Object Modeling

Module 6: Object Modeling

Object modeling is a popular technique that describes a system in terms of
objects. Objects represent things in a system. Unlike structured analysis where
data is separated from the processes, objects include data and processes. The
implementation process transforms objects into program code that can be
optimized, tested, and reused.

Classes make up things that have similar attributes, or characteristics. Individual
members of a class are called objects. Objects within a class can be grouped
into sub classes. Sub classes and super classes exist and extend the
functionality of the model.

Use cases describe a business situation initiated by something interacting with
the system. Case represents a specific transaction, or scenario. A diagram can
be used as a visual summary of related use cases within a system or subsystem.
A diagram of the class is used to represent a detailed view of a single use case.
A sequence diagram is a dynamic model of a use case that shows the interaction
among classes during a specified time period. Sequence diagrams comprise
lifelines, messages, and focuses. To show how an object changes from one state
to another a state transition diagram is used. An activity diagram is a horizontal
flowchart that shows things as they occur in the system.

The final step in the object modeling process is organizing your use cases and
use case diagrams and creating class, sequence, state transition, and activity
diagrams.

Attachments

- Mod6_InstructorPerspective.pdf