Analysis of Use Case Descriptions: Customer Membership System Project

This assignment presents a set of use case descriptions for a customer membership system, detailing various processes such as onboarding new customers, processing payments, handling declined credit cards, and issuing membership cards. Each use case includes an ID, importance level, primary actor, stakeholders, brief description, trigger, relationships, normal flow of events, subflows, and alternate/exceptional flows. The 'Process New Customer' use case covers membership requests, discount calculations, and bill generation. 'Process Payment' addresses cash and credit card transactions, including a subflow for declined credit cards. 'Process Declined Credit Card' outlines the steps for handling payment failures. Finally, 'Issue Membership Card' describes the card issuance process. The descriptions provide a comprehensive view of the system's functionalities and user interactions, suitable for system design and analysis.

Use Case Description
Use Case Name: Process New Customer ID: 1 Importance Level: H
Primary Actor: Staff
Stakeholders and Interests:
Customer – Want to join the health club.
Staff – Assists customer with membership.
Brief Description: 12
Trigger: 13
Relationships:
Include: 14
Extend:
Normal Flow of Events:
1. Customer requests membership.
2. 15
3. 16
4. System determines the discount rate.
If desired membership length < 6 months,
then discount rate = 0
Else if desired membership length < 12 months
then discount rate = .10
Else discount rate = .15
5. System calculates payment amount.
6. System generates bill.
7. Staff gets bill and gives to customer.
8. Customer presents accepted form of payment (cash or credit card).
9. Staff executes the Process Payment use case.
SubFlows:
Alternate/Exceptional Flows:
8a. 17
8b. Process New Customer terminates.

Use Case Name: Process Payment ID: 2 Importance Level: M
Primary Actor: Staff
Stakeholders and Interests:
Customer – Person that is paying for new membership.
Staff – Employee receiving payment.
Brief Description: 18.
Trigger: 19
Relationships:
Include: 20
Extend: 21
Normal Flow of Events:
1. Customer presents accepted form of payment to staff.
If payment is with 22, the 23 subflow is performed.
If payment is with 24, the 25 subflow is performed.
2. System generates membership card.
3. Staff executes 26 use case.
SubFlows:
S-1a. Cash Payment
1. Staff records cash payment.
2. Staff puts cash in cash box and gives customer change if necessary.
S-1b. Credit Card Payment.
1. 27
2. 28
Alternate/Exceptional Flows:
S-1b-2a. Staff executes the 29 use case.

Use Case Name: Process Declined Credit Card ID: 3 Importance Level: M
Primary Actor: Staff
Stakeholders and Interests:
Customer – Person requesting a new membership.
Staff – Employee working at the health club.
Brief Description: 30
Trigger: 31
Relationships:
Include: 32
Extend:
Normal Flow of Events:
1. Staff notifies customer that credit card was not approved and returns credit card to customer.
2. Staff asks customer for another form of accepted payment.
3. Customer gives staff another form of payment.
4. 33
SubFlows:
Alternate/Exceptional Flows:
3a. 34
3b. Staff terminates processes.
Use Case Name: Issue Membership Card ID: 4 Importance Level: M
Primary Actor: Staff
Stakeholders and Interests:
Customer – New member receiving membership card.
Staff – Employee issuing membership card.
Brief Description: 35
Trigger: 36
Relationships:
Include:
Extend:
Normal Flow of Events:
1. 37
2. 38
SubFlows:
Alternate/Exceptional Flows: