2. Table 1 User Account creating
Name ID User Account creating
Use case
diagram
Actors Client
Admin
User stories . Because he is a customer, it is his responsibility to follow the given
directions in order to set up a user account.
Description Customers register for an account by providing card information.
Priority High
Trigger Users must first establish accounts in order to access the system.
Precondition Create user account
Login to the system
Postcondition Store data
Delete data
Update and view data
3. Normal flow
Alternative
flow
User enter incorrect password with 3 attaemps account has locked
Exception Establish user accounts for customers and other parties.
4. Table 2 User payments
Name ID User Reimbursement
Use case
diagram
Actors Customer
Bank
System admin
Application
User stories To complete your transaction as a customer, you will need to enter into the
system and pay using a credit card or a bank account.
Description Customers register for an account by providing card information.
Pay your bills using a credit card.
Priority High
Trigger Customers must first register for an account before they may access the system.
Pay your bills with one of the many online payment methods.
Precondition Login to the system
Take Service
Make payment with in time
5. Postcondition After a week, send a reminder email to customers who haven't paid; •
Always remember to keep track of user information
Not payment for up to two services that have been finished. There is no
activation of the third service.
Normal flow
Alternative
flow
If the payment is not cleared at a given time application send the alterrt from the
system
Exception
6. Table 3 User Payment message system
Name ID User Payment message system
Use case
diagram
Actors Customer
System
Bank
User stories You are required, as a customer, to log into the system.
Send an SMS warning and make payment using either your bank card or cash online.
Description Customers register for an account by providing card information.
Priority High
Trigger Customers must first register for an account before they may access the system.
Please send the verification code to the phone.
7. Precondition Login to the system
Send SMS
Make payment using cash or cards
Postcondition Keep remember user details
Send confirmation code
If not cancellation
Normal flow
Alternative
flow
Login system using login credencial
Payment done by requested services
Finally confirmation message send by the system
Exception
8. Table 4 The system needs to use the Stripe API
Name ID The system needs to use the Stripe API
Use case
diagram
Actors Customer
System
User stories The system needs to use the Stripe API to create customers, add their credit card and to charg
their card for mowing services.
Stripe.NoChange: However, there will be no need to change from using the Stripe API.
Description An API is needed for creating clients and charging them for the mowing services they've
requested using the Stripe API.
Stripe.
However, there will be no need to switch to the Stripe API.
Priority High
Trigger Customers create accounts to login to the system.
Precondition Login to the system
9. create customers
add their credit card
charge their card for mowing services.
Postcondition Keep remember user details
Add, edit, or delete customer details
Normal flow
Alternative
flow
Login to system by admin
He have approved for user management
Exception
Table 5 The system provides discounts
10. Name ID Discounts are available through the system.
Use case
diagram
Actors Customer
Application
Administrator
User stories Those who have paid for 10 services or more in total are eligible for a discount of 15% off
their total bill.
This could change in the future; for instance, we might decide to provide a discount of 20%
to customers who have 15 different services.
Description If a client has paid for ten or more services, they are entitled for a discount that is fifteen
percent more than the standard rate.
This might change; for instance, we could provide a discount of twenty percent to clients
who subscribe to fifteen different services.
Priority High and medium
11. Trigger Customers must first register for an account before they may access the system.
Precondition Check the total number of services • Pay for 10 or more services to receive a
discount; those who have paid for 15 services or more receive the discount.
Postcondition Customers who have paid for 10 services or more are eligible to get a discount of
15% off their total bill.
This could change in the future; for instance, we might decide to provide a discount
of 20% to customers who have 15 different services.
Normal flow
Alternative
flow
If the servive is grteter tha 15 customer gets 20% and more 10 services 15 % discount
Exception
12. Name ID There are not nearly enough properties being serviced to justify developing
schedules similar to calendars.
Use case
diagram
Actors Customer
Application
Admin
User stories We need to keep track of things like how frequently a property has to be mowed,
but there aren't enough properties for calendar-like schedules to be warranted at
this time. Nevertheless, we need to keep track of things like how often a property
needs to be mowed.
Description We need to keep track of things like how often a property has to be mowed, but
there aren't enough properties for us to warrant calendar-like scheduling at this
time. However, we do need to keep track of other items.
Priority High
Trigger Customers must first register for an account before they may access the system.
Request services
There are not enough attributes available at this moment to warrant creating
schedules similar to calendars.
Precondition Login to the system
Check availability
Request services
13. Postcondition There are not nearly enough properties being served to justify developing
schedules in the format of a calendar.
Normal flow
Alternative
flow
If there is not enough properties customer have to schedule till accepet
administrator .
Exception There are enough properties continue the process if not make calender
schedule.
IMPLEMENTATION
