Professional Documents
Culture Documents
By 19-SE-53
MUHAMMAD HASHIM
19-se-53@students.uettaxila.edu.pk
Task 8
Study VolBank case study and identify all the use cases, actors, stake holders
and apply use cases and actors’ relationships and associations. Draw the
model in StarUML.
Actor:
An actor is anything with behavior, including the system under discussion (SuD)
itself when it calls upon the services of other systems.[2] Primary and supporting
actors will appear in the action steps of the use case text. Actors are roles played
not only by people, but by organizations, software, and machines.
Volunteer Organization
Voluntary Organization System
Volunteer
Voluntary Organization
Stakeholder:
Stakeholder – someone or something with vested interests in
the behavior of the system under discussion (SUD)
Volunteer Organization
Voluntary Organization System
Volunteer
Voluntary Organization
Use Cases:
Use cases are requirements, primarily functional or behavioral requirements that
indicate what the system will do.
Register Volunteer
Deposit Time
Record volunteer organization
Match volunteer
Record successful match
View statistical Analysis
Produce volunteering Agreement
Update opportunities
Lab Task 9
Extract all the possible use case of your project and write a full detailed
document.
ONLINE FOOD DELIVERY SYSTEM
Fully dressed use cases show more detail and are structured; they are useful order to obtain a deep
understanding of the goals, tasks, and requirements.
- Sales System: Wants to record all the sales and order completed.
- Cashier System: will update all the food deliveries.
- Customer: Wants purchase and fast service of the food.
- Company: Wants to accurately authorized the user and satisfy customer interests. Wants to ensure
that Payment Authorization Service payment receivables are recorded. Wants some fault tolerance to
allow sales capture even if server components (e.g., remote credit validation) are unavailable. Wants
automatic and fast update of accounting and inventory.
- Payment Authorization Service: Wants to receive digital authorization requests in the correct format
and protocol. Wants to accurately account for their payables to the store.
Preconditions: Must have an account to Login and have a secure internet connection.
Success Guarantee (Postconditions): Customer will successfully login to the application and will order
food of his choice.
To support recovery and deliverers, ensure all transaction sensitive state and events can be
recovered from any step of the scenario.
1. User restarts System, logs in, and requests recovery of prior state.
2. System reconstructs prior state.
2a. System detects anomalies preventing recovery:
1. System signals error to the user, records the error, and enters a clean state.
2. System starts interface.
Customer asks system to remove an item from the purchase:
1. System enters item identifier for removal from sale.
2. System displays updated running total.
Customer tells System to cancel order:
1. System will cancel the particular order.
Customer says they are eligible for a discount (e.g., coupons, vouchers):
1 User signals discount request.
2 User enters coupons or voucher number.
3 System presents discount total, based on discount rules.
Customer says they have credit card in their account, to apply to the Discount Offer:
1 User signals credit request.
2 User enters identification.
3 System will verify the users credit card and offer the user discounts deals.
Paying by cash:
1 User enters the cash amount tendered.
2 System presents the balance due, and releases the cash drawer.
3 System deposits cash tendered and returns balance in cash to Customer.
4 System records the cash payment.
Paying by credit:
1 Customer enters their credit account information.
2 System sends payment authorization request to an external Payment
Authorization Service System, and requests payment approval.
2a. System detects failure to collaborate with external system:
3a. System records the credit payment, which includes the payment approval.
3c. Cashier asks Customer for a credit payment signature. Customer enters
signature.
Paying by debit...
Customer presents coupons:
1. Before handling payment, system records each coupon and System reduces price as
appropriate. System records the used coupons for accounting reasons.
Open Issues:
a. Errors in Login
b. Error in fetching the location by the app.
c. Little bit late in delivery
d. Error in card authorization