Académique Documents
Professionnel Documents
Culture Documents
section II Analysis
object-oriented methodology object models use case modeling unified modeling language the data dictionary the cornucopia case portfolio project
Chapter Objectives
When you complete this chapter you will be able to: Differentiate between object-oriented and traditional methodologies Identify objects and construct an elementary object model Identify the elements in a use case model Identify the elements in four of the most common UML models Define, construct, and maintain data dictionaries
Object-Oriented Methodology
Object-oriented systems analysis and design (OOSAD) evolved to accommodate the increasing popularity of object-oriented programming languages If you plan to implement your design with object-oriented development tools, you should seriously consider using OOSAD As the name implies, OOSAD revolves around objects
Object-Oriented Methodology
Information system objects derive their definition from our understanding of realworld objects Just as real-world objects are organized into classifications, enterprise objects are members of a class While a specific object is distinguished by its particulars, it inherits its general makeup from its class
Object-Oriented Methodology
By definition, a class embodies two important information processing concepts:
Data attributes Behaviors
After enterprise objects are created from their class blueprint, their data attributes are assigned values and their behaviors are tailored to fit their specific circumstance Objects interact with one another through a messaging system
Object-Oriented Methodology
The object-oriented methodology involves familiar phases: analysis, design, and implementation
Analysis: Identify the classes from which enterprise objects are created and the interactions between these classes
Design: Refine class definitions and interactions based on the requirements of the new information system Implementation: Create a working information system using object-oriented languages and tools
Object Models
In the OOSAD methodology, the object model serves the same purpose as do the DFD and ERD in the traditional SDLC methodology
The object model is focused on data and software, showing classes and class interactions
Object People Procedures Data Hardware Software Networks Class Attributes Methods
Object Models
Object Identification: Use case modeling is the preferred technique for identifying enterprise objects
Another way to identify classes is to use the DFD and ERD models as a springboard, where each of the DFDs data stores and ERDs entities are potential classes
TECHNOTE 5-1
Anatomy of an Object
Class: a two-part abstraction (attributes and methods) of a real-world person, place, thing, or activity Instance: a specific object created from the class blueprint Encapsulation: describes the enveloping, membrane-like environment in which an object exists Messages: means by which objects communicate with each other Polymorphism: allows a method to behave differently when encapsulated in different classes Inheritance: imprints class definitions on new generations of the class Class relationships: describes the way classes interact with one another
10
This specialization relationship indicates that there are two subsets of the Boat class
12
Object Model
Data Model
13
15
Component Diagram
Deployment Diagram
16
17
18
19
20
ThinkingCritically
What action would you recommend if you discovered that your most talented analyst had consistently inflated the labor hours charged to a project?
21
optional entry
key field data structure composition attribute separator
[]
underline =
22
23
The analysts do not intend to use an objectoriented programming language to implement the new system. Even the objectlike features of 4Gl software do not require object identification or use case modeling.
Cornucopias object model is derived from the ERD.
24
25
26
Objects are characterized by their attributes and behaviors Objects communicate with one another through messaging
27
The data dictionary provides a systematic procedure to keep track of the names, definitions, associates, and existing or proposed uses of data
28