






Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
An introduction to Object-Oriented Analysis (OOA), focusing on the Use-Case Model and Conceptual Class Model. OOA is a process used to identify objects for software realization. the Use-Case Model, which describes sequences of events from a user's perspective, and the Domain Class Model, which represents objects from a user's perspective. Both models are expressed in UML. use case texts and diagrams, the differences between them, and their goals.
Typology: Assignments
1 / 12
This page cannot be seen from the preview
Don't miss anything!







We now have the requirements, but we need objects for a software realization.
We need to examine the requirements for blocks of functionality that can become prototypes for objects.
During OOA we develop two different perspectives of a system:
Both models are expressed in UML
Use cases describe sequences of events
The goals of use case analysis:
Use cases come in two flavors: Use case texts:
An elevator use case diagram
Note: use case diagrams should be considered illustrations of use case texts.
== major system component/entity, system boundaries
== event, use case
== bidirectional relation
== actor (use role, other systems)
<
<
== if the results of one use case/event depend on another, use <
A conceptual model is a visual representation of conceptual classes or real-world objects in a domain of interest (not software components!).
A conceptual model represents objects/classes from a user’s perspective.
A conceptual class model has:
Components of conceptual class diagrams:
The following is a typical conceptual class diagram in UML.
Notice that the classes do not have any operations and the associations are bidirectional. Multiplicities are necessary.
Consider our online buying use case text:
Use Case Text: Buy a Product Online
Here: common noun, doing verb, adjective phrase
Now we can extract the entities we are interested in:
Common noun ≈≈≈≈ class : Customer Catalog Item System ≈ Checkout Purchase Sale
Adjective phrase ≈≈≈≈ attribute : here we also have to decide where to place the attributes, due to step 4 in the use case text we decide to make the attributes part of the System. Shipping info Pricing info Credit card info Confirming email
Doing verb ≈≈≈≈ association: