8 - OOA - Object-Oriented Analysis We now have the...

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

View Full Document Right Arrow Icon
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
Background image of page 1

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

View Full DocumentRight Arrow Icon
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
Background image of page 2
Use Case Text Example Scenario: Buy a Product Online The customer browses the catalog and adds desired items to the shopping basket. When the customer wishes to pay, the customer describes the shipping and credit card information and confirms the sale. The system checks the authorization on the credit card and confirms the sale both immediately and with a follow-up message. Additional Scenarios:
Background image of page 3

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

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 12

8 - OOA - Object-Oriented Analysis We now have the...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online