The document outlines requirements for a system that allows customers to create accounts, make payments for mowing services, and receive discounts. It includes 5 use cases: 1) creating user accounts, 2) making payments, 3) sending payment confirmation via SMS, 4) using the Stripe API for payments, and 5) providing discounts for customers who have paid for a certain number of services. Implementation details include user registration/login forms, scheduling services, a mobile interface, and sending confirmation codes by SMS. However, there are currently not enough customer properties to warrant calendar-like scheduling.

1. REQUIREMENTS SPECIFICATION
Table 1 User Account creating
Name ID User Account creating
Use case
diagram
Actors Client
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 create account with card details.
Priority High
Trigger Customers create accounts to login to the system.
Precondition  Create user account
 Login to the system
Postcondition  Keep remember user details

2. Normal flow
Alternative
flow
Exception Create user accounts for clients and others
Table 2 User payments
Name ID User Payment
Use case
diagram

3. Actors Customer
Bank
User stories As customer, you have to login to the system and make payment via online
using bank card
Description Customers create account with card details.
Using card make payments
Priority High
Trigger Customers create accounts to login to the system.
Make payments using online payment method
Precondition  Login to the system
 Take Service
 Make payment
Postcondition  Keep remember user details
 after the 7 days send reminder to the non -payments people
 Not payment completed up to 2 services 3 rd service does not activate
Normal flow

4. Alternative
flow
Exception
Table 3 User Payment message system
Name ID User Payment message system
Use case
diagram
Actors Customer
System
Bank
User stories As customer, you have to login to the system
Send SMS alert
make payment via online using bank card or cash
Description Customers create account with card details.

5. Priority High
Trigger Customers create accounts to login to the system.
Send confirmation code to phone
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
Exception

6. 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
charge 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
 create customers

7.  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
Exception

8. Table 5 The system provides discounts
Name ID The system provides discounts
Use case
diagram
Actors Customer
System
User stories A discount of 15% is applied to those who have paid for 10 services or more.
This may change, for example, we might want to give a 20% discount to those with
15 services.
Description If a customer has paid for ten or more services, they are eligible for a 15% discount.
This might change, for example, we could provide a 20% discount to customers who
have 15 services.
Priority High
Trigger Customers create accounts to login to the system.

9. Precondition  Login to the system
 Check total services
 paid for 10 services or more
 discount to those with 15 services.
Postcondition  A discount of 15% is applied to those who have paid for 10 services or more.
 This may change, for example, we might want to give a 20% discount to those
with 15 services.
Normal flow
Alternative
flow
Exception

10. Name ID Not enough properties are serviced to warrant creating calendar-like schedules.
Use case
diagram
Actors Customer
System
User stories We need to keep track of things like how often a property has to be mow, but there aren't
enough properties for calendar-like schedules to be warranted at this time.
Description We need to keep track of things like how often a property has to be mow, but there
aren't enough properties for calendar-like schedules to be warranted at this time.
Priority High
Trigger Customers create accounts to login to the system.
Request services
Not enough properties for calendar-like schedules to be warranted at this time.

11. Precondition  Login to the system
 Request services
Postcondition  Not enough properties are serviced to warrant creating calendar-like schedules.
Normal flow
Alternative
flow
Exception

12. Figure 1 A class diagram

13. IMPLEMENTATION
Figure 2 User Registration Form

14. Figure 3 User Login
Figure 4 Discount for Services

15. Figure 5 Scheduling
Figure 6 Mobile interface of appointment

16. Figure 7 Confirmation code send to as SMS
Figure 8 Map