Object-Oriented Analysis: Use Case and Conceptual Class Model, Assignments of Designs and Groups

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

2021/2022

Uploaded on 07/05/2022

gavin_99
gavin_99 🇦🇺

4.3

(73)

998 documents

1 / 12

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Object-Oriented Analysis
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:
1. Use-Case Model
2. Domain Class Model
Both models are expressed in UML
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download Object-Oriented Analysis: Use Case and Conceptual Class Model and more Assignments Designs and Groups in PDF only on Docsity!

Object-Oriented Analysis

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:

  1. Use-Case Model
  2. Domain Class Model

Both models are expressed in UML

Use Case Analysis

Use cases describe sequences of events

  • The user interacting with the product to achieve his/her goal

The goals of use case analysis:

  • Design system from user’s perspective
  • Communicate system behavior in user’s terms
  • Comprehensive insight into the behavior of system

Use cases come in two flavors: Use case texts:

  • a sequence of numbered steps
  • describes a user goal
  • maybe developed from a scenario Use case diagrams:
  • illustrates a use case text as a stylized diagram

Use Case Diagram Example

An elevator use case diagram

Note: use case diagrams should be considered illustrations of use case texts.

Elements of Use Case Diagrams

== major system component/entity, system boundaries

== event, use case

== bidirectional relation

== actor (use role, other systems)

Special Unidirectional Relations

<

< == instead of repeating similar behavior throughout your diagram factor it out and use <> to show dependence on this behavior.

== if the results of one use case/event depend on another, use <>.

UML Class Diagrams: Conceptual Model

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:

  • Conceptual classes (domain objects)
  • Associations between conceptual classes
  • Attributes of conceptual classes

Components of conceptual class diagrams:

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.

Example: Noun Extraction

Consider our online buying use case text:

Use Case Text: Buy a Product Online

  1. Customer browses through catalog and selects items to buy.
  2. Customer goes to checkout.
  3. Customer fills out shipping information.
  4. System presents full pricing information, including shipping information.
  5. Customer fills in credit card information.
  6. System authorizes purchase.
  7. System confirms sale immediately.
  8. System sends confirming email to customer.

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: