GSA 544 Class 9
Terms in this set (11)
Unified Model Language
History of UML
-Introduced in 1997 by the Object Management Group (OMG)
-Developed by Jim Rumbaugh, Ivar Jacobson, and Grady Booch ("The 3 Amigos")
-Fits well with the Object Oriented ("OO") approach for building systems
Basic Object-Oriented (OO) Concepts
OO approach is built on the idea of an object, which contains both data and methods that manipulate data
Data represent the state of the object
-Example: An Account might have...
---A balance (the internal state of the account)
----An owner (another object representing a person)
Methods represent operations that the object can perform
-Example: A Checking Account object might have three operations...
Every object belongs to (is an instance of) a class (a template or "cookie cutter" defining the data and methods of those objects
Class Hierarchies & Inheritance
Object classes are arranged in a hierarchical structure ("upside down tree")
Object classes inherit the data and methods/operations of all "superclasses" above it in the structure
--Like supertypes/types in ER Diagramming
Application of OO Concepts
OO programming languages (C++, Java, Smalltalk, etc.)
OO Analysis & Design methodologies (e.g., Rational Unified Process (RUP)
UML specifies a set of diagrams that describe different aspects of a system.
A Use Case illustrates some unit of functionality of the system
--Helps to visualize the functional requirements of a system, including the "actors" (humans) who will interact with the system.
Shows how the different entities relate to each other
Shows a detailed flow for a specific use case - requests/calls between different objects, in sequence
YOU MIGHT ALSO LIKE...
Academic Word Lists - AWL Sublists
ACCTMIS 4620 Chapter 14
Systems Analysis: Ch. 6 Object Modeling
Systems Analysis and Design Chapter 6
OTHER SETS BY THIS CREATOR
GSA 552 Midterm 1
GSA 544 - Day 6
GSA 544 Day 5
GSA 544 Day 4