CmpE 296P ? Advanced Object-Oriented Analysis and Design

CmpE 202 - Software System Engineering Design Session (06) Exercises
Examine the following use cases (three groups) and list all the major
problems with them. State why? Group #1: Use Case 1
Use Case No.: 1.1.1
Use Case Title: Find Product
Actors: Customer
Roles: Searcher (Customer)
Corresponding Attributes: Product Name, Product description, Price range
Corresponding Interfaces: Fill search request form, Submit search request,
Print the search result list
Corresponding Classes: DataManager, SearchEngine
Description of the Use Case:
1. Customer enters information about the products she wants into the
search engine.
2. The search engine transfers the search request into formal search
request and sends it to the DataManager.
3. The DataManager determines the list of the products based on the
customer's request passed in by the search engine and returns it to
the customer.
Use Case 2
Use Case No.: 1.1.2
Use Case Title: Place Product into Shopping Cart
Actors: Customer
Roles: Regular Customer (Customer)
Corresponding Attributes: Product Quantity
Corresponding Interfaces: Add the product, remove the product, Empty the
cart, Check out
Corresponding Classes: OnlineCart
Description of the Use Case:
1. Customer chooses the product she wants and adds it into the online
shopping cart.
2. Customer specifies the quantity of each product she wants to buy and
check out.
3. Alternatively customer can remove the product item from or add more
product into the online shopping cart or totally empty the online
shopping cart if she decides not to buy anything now.
Use Case 3
Use Case No.: 1.1.3
Use Case Title: Register in
Actors: Customer
Roles: Register (Customer)
Corresponding Attributes: Customer ID, Password
Corresponding Interfaces: Login
Corresponding Classes: AccountManager, CustomerAccount
Description of the Use Case:
1. After check out, Customer can login as a member and type in the user
name and password.
2. The AccountManager checks and verifies the username through the member
list and the password against the customer account profile.
3. Once the username and password are verified, the Account Manager fills
the OnlineOrder with the information it knows from the customer
account profile.
4. Alternatively if the customer doesn't have an account, the Account
Manager lets the customer to choose continue check out or create a new
account.
Group #2:
Use Case Id : 1.0 Use Case Title: Appointment |Actors |Roles |
|Patient |Problem_descriptor |
| |Take Appointment |
|Classes |Attributes |Interfaces |
|Patient |Ssn_number |State_problem( ) |
| |Patient_Name |Appointment ( ) |
| |Prob_Statement | | Use Case Description:
- Patient logs on to the system through ssn
- Describes problem
- Enters suitable Appointment time
- Confirm Appointment
- Patient logs out Use Case Id : 2.0 Use Case Title: Doctors Availability
|Actors |Roles |
|Medical Staff |Retrive problems of patients |
| |Match concerned Doctor |
| |Retrive appointment time |
| |Finalize appointment |
|Classes |Attributes |Interfaces |
|Doctor |Doc_name |Doc_schedule( ) |
| |App_time |Treatment( ) |
|Patient |Patient_name |Retrive_problem( ) |
| |Ssn |Appointment( ) | Use Case Description:
- retrieves problems of different patients
- looks for concerned doctor
- Retrieves appointment time of different patients
- fits the appointment time of different patients in doctors schedule Use Case Id : 3.0
Use Case Title: Doctors appointment Schedule |Actors |Roles |
|Medical Staff |Retrieves doctors working hours |
| |Lists appointments of doctors |
| |Confirm doctors appointment |
|Classes |Attributes |Interfaces |
|Doctors |Working hours |Retrieves_workinghours|
| | |( ) |
| |Patients_name |Appointment ( ) |
| |Appointment_time | | Use Case Description:
- Doctors working hours are retrieved
- appointments are fixed in doctors working schedule
- doctors appointment schedule is confirmed
Group #3: |Use Case No.: |1 |
|Use Case Title: |Adult without disabilities learning to speak a|
| |language. |
|Actors/Roles: |Actors |
| |Roles |
| | |
| |LanguageStudent |
| |Speaker, Listener, Reader |
| | |
|Classes | |
|Attributes/Interfaces | |
|Classes |
|Attributes |
|Interfaces |
| |
|LanguageStudent |
|Age, |
|Development stage (pre- or post-puberty) |
|Read, listen, speak, take tests |
| |
|SpokenLanguage |
|Type of language(tonal vs. non-tonal), |
|Range of sounds |
|Create/present/analyze audible information |
| |
|LangStructure |
|Word relationship; |
| |
|Create relationships between words; |
|Enforce rules of word order and form |
| |
|Grammar |
|Tense |
|Case |
|Declension |
|Mood |
|Number |
|Voice |
|Analyze/Classify language structure; |
|Name components of language; |
|Explain relationships between parts of speech |
| |
|Textbook |
|Price, |
|Availability, |
|Teaching method, |
|Presentation style |
|Present grammatical information of a language |
|Develop/present a method of learning a language |
|Guide the learning process |
| |
|Vocabulary |
|Part of speech, |
|PronunciationRule, |
|SpellingRule |
|Classify words by parts of speech; |
|Relate spelling to pronunciation |
| |
|Dictionary |
|Price,