The software is a desktop application and has two main
components: the front end and the back end. The main front end
page is the logon page which allows the customer or the
employee to login and is an entry into the user authorized
view. The backend consists of the database.

4.2.1 External
machine interfaces
4.2.2 External system
interfaces
None
4.2.3 Human interface
Interface requirements include ability to view graphics. The
human interface is a design that has all control fields on the
user screen. The interface comprises of simple and easy to use
input mechanisms, where the user will be able to make or input
choices easily and submit the input. The output is then
displayed in a user friendly format to all users. Workstation
requirements include monitor, keyboard and mouse.
5.0 Behavioral Model and Description
The
description of the behavior of the software is given below.
5.1 Description of software behavior
The
software will behave differently in different scenarios for
each user – manager, employee, and customer.
It displays a different interface for each of these
types of users.
5.1.1 Events
An event causes the system to change from one state to
another. There are three actors that can generate an event -
customers, employees and administrator. The following are
events generated:
Customer:
·
Log in/ Log out to/from the system
·
View their profile information
·
Make an order
·
Make a payment
·
View all order information
Employees:
·
Log in/ Log out to/from the system
·
View their profile information
·
View all order
·
View all customer information
·
View all payment information
·
Update customer/order information
·
Delete customer/order information
·
Add new customers
·
View the log file
Manager:
·
Log in/ Log out to/from the system
·
View their profile information
·
View all order
·
View all customer information
·
View all payment information
·
View all employee information
·
Update customer/order information
·
Delete customer/order information
·
Add new customers
·
View the log file
5.1.2 States
A list of
states that is a result of the above events is given below:
|
Event
|
State
|
|
The
application is run
|
The system presents the login screen
|
|
The user
types invalid login data
|
The system stays at the login screen
and an error message is displayed which asks the user
to re-enter login information
|
|
The user
requests
new account
|
The system redirects to a new
account screen, where the user creates an account.
|
|
The user
is an employee
|
The system gives the user- employee
privileges.
|
|
The user
is an manager
|
The system gives the user- manager
privileges
|
|
The user
logs is an existing customer
|
The system gives the user- customer
privileges.
|
|
The user
requests to view orders
|
All/some orders are displayed
depending on the user privileges
|
|
The
customer makes a payment
|
The payment page takes the payment
information and processes it
|
|
An
employee/manager edits an order
|
The system displays the order for
editing and updates the database.
|
Table 4: Event-State
5.2 State chart diagram
This diagram depicts the overall
behavior of the system
6.0 Restrictions, Limitations and Constraints
Following are the evaluated constraints:
1.
Orders can be edited/deleted only by the employee/manager once
they have been placed.
2.
Multiple employees cannot process/edit data simultaneously
3.
Trade-off between system optimization and data processing
speed.
7.0 Validation Criteria
The approach to software validation/verification is described
in the table below along with the expected results and
performance bounds.
7.1 Classes of tests
|
Classes of tests
|
Description
|
Expected software response
|
Performance bounds
|
|
Login
|
Check for
validity of username/password
|
Only correct
username/password combination is allowed access
|
An incorrect
combination of username/password should result in
rejected login.
|
|
Payment
|
Data should
not be processed unless all the required information
is entered.
|
An invoice is
generated to the customer/employee once a transaction
has taken place
|
Information
should not be processed if required fields are
incomplete.
|
|
View Order
|
Verify that
all customer orders are correctly displayed.
|
All orders
placed by
No orders displayed
the
particular
if none exist.
customer
displayed.
|
|
Customer
|
All required
fields are filled in before a customer account is
created.
|
Customer
account created successfully.
|
Account not
created if inadequate information provided.
|
|
Employee
|
All required
fields are filled in before an employee account is
created.
|
Employee
account created successfully.
|
Account not
created if inadequate information provided.
|
|
Order
complete
|
Checks that
all the required information for the order is filled.
|
Customer/employee successfully place order.
|
Order does
not go through if inadequate information provided.
|
Table
5: Test Criteria