Create ONE Use Case diagram using VP based on theactivityand theUse Case descriptions. Keep it in native vpp format and upload the file

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:

Customer requests membership.

15

16

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

System calculates payment amount.

System generates bill.

Staff gets bill and gives to customer.

Customer presents accepted form of payment (cash or credit card).

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:

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.

System generates membership card.

Staff executes 26 use case.

SubFlows:

S-1a. Cash Payment

Staff records cash payment.

Staff puts cash in cash box and gives customer change if necessary.

S-1b. Credit Card Payment.

27

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:

Staff notifies customer that credit card was not approved and returns credit card to customer.

Staff asks customer for another form of accepted payment.

Customer gives staff another form of payment.

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:

37

38

SubFlows:

Alternate/Exceptional Flows: