{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

ISOM221+Lecture+10+-+Introduction+to+Object-Oriented+Modeling+Using+the+UML

ISOM221+Lecture+10+-+Introduction+to+Object-Oriented+Modeling+Using+the+UML

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
ISOM221 Information Systems Analysis and Design Lecture 10: Introduction to Object-Oriented Modeling Using the UML 1 Agenda Introduction to object-oriented modeling and UML Use case modeling 2 Model-Driven Approaches Traditional Approaches Structured Analysis Focuses on the flow of data through processes Key model: data flow diagram Information Engineering Focuses on structure of stored data Key model: entity relationship diagram Object-Oriented Approach Integrates data and process concerns into objects Object –the encapsulation of the data (called properties) that describes a discrete person, object, place, event, or thing, with all the processes (called methods) that are allowed to use or update the data and properties. The only way to access or update the object’s data is to use the object’s predefined processes. 3 A Sample Process Model 4
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
A Sample Data Model 5 A Sample Object Model 6 Unified Modeling Language (UML) Attempt to balance emphasis on data and process Provides a common vocabulary of object-oriented terms and diagramming techniques rich enough to model any systems development project from analysis through implementation The UML does not prescribe a method for developing systems—only a notation that is now widely accepted as a standard for object modeling Major groups of UML 2.0 diagram: Structure diagrams Behavior diagrams 7 UML Structure Diagrams Represent the data and static relationships in an information system Class Object Package Deployment Component Composite structure 8
Background image of page 2
UML Behavior Diagrams Depict the dynamic relationships among the instances or objects that represent the business information system Activity Behavior state Sequence Communication Interaction overview Timing machine Protocol state machine, Use-case diagrams 9 10 Use Case Diagram 11 Class Diagram 12
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Sequence Diagram 13 Behavioral State Machine Diagram 14 Agenda Introduction to object-oriented modeling and UML Use case modeling 15 Use-Case Modeling Use-case modeling –the process of modeling a system’s functions in terms of business events, who initiated the events, and how the system responds to those events Use-case modeling has roots in object-oriented modeling Gaining popularity in non-object development environments because of its usefulness in communicating with users Compliments traditional modeling tools 16
Background image of page 4
Use Cases Use cases are logical models that describe the functions and activities of a system Use cases are the first major model created in the object- oriented software development Use cases are often used in subsequent stages of the object-oriented software development process to validate design, develop test cases, develop user manuals Use cases describe a system from the actors’ perspective A collection of scenarios that describe actors using a system to support a goal
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}