3.

3 Non-Functional Requirements
3.3.1 Performance
PE.1: Operations such as the production of reports should take less 20 seconds for 90% of
transactions.
PE.2: The system downtime may not exceed 1 minute per day.
PE.3: The system should handle requests of at least 300 users per second at its peak and
respond to requests in less than 10 seconds.
PE.4: Before delivery, packages must be verified by the warehouse employee.
PR.5: Delivery employees will verify the location of delivery using a mobile device and
proceed to the location of the customer.
PR.6: If requested, the customer would pay the delivery person on arrival of the package,
either by in hard money, check, or by credit card.
3.3.2 Availability
A.1: The system should meet or exceed 98% uptime.
A.2: The system should not be unavailable for more than 1 hour per 750 hours of operation.
A.3: The system should take less than 25 seconds to restart after a failure 95% of the time.
3.3.4 Security
S.1: Access to customer accounts shall be restricted to only the customers that have created
an account and have login information, the owner, Bill Wiley, and minimum access for
delivery personnel that have created one and have login information.
S.2: Upon their arrival, employees must check in via company policy.
S.3: System must be password protected with users logging in using a unique ID and
password.
S.4: Four levels of users will be established customers, driver, managers, and administrators.
S.4.a: Customers may be able to create accounts in the system, enter tracking numbers, and
view the status of a package(s).
S.4.b: Drivers are able to enter information such as package information into the system.
S.4.c: Managers are able to do all functions of a clerk, in addition to creating and compiling
reports.
S.4.d: Administrators will have full access to all aspects of the system as well as manage
authentication and authorization of the system.
S.5: All users may change their passwords.
S.6: In a situation where forgotten passwords occur, administrators must change the
passwords for lower authorized users.
S.7: At least 99% of intrusions shall be detected within 15 seconds.

3.4 Design Constraints

DC.1: The system shall use the company standard SQL Server database engine.
DC.2: HTML coding will be based off the HTML5 standard.
DC.3: All scripts should be written in Java.

Software Requirements Specification Template - 1

DC.4: Hardware limitations may include the system running on a Windows desktop computer
with an Intel processor and a minimum of 256MB of RAM.
DC.5: Software limitations include the system working on a Windows platform.
DC.6: Any future development of mobile applications should be written in Java for Android and
Objective-C for iOS.

3.5 Other Requirements

3.5.1 Data Base
DB.1: The system will require a data server and a SQL database.
DB.2: This database will have tables that store customer, employee, payment and package
information.
DB.3: The system will have another database for backup.
3.5.2 Operations
OP.1: Normal hours of operation will be from 7:00am to 9:00pm.
OP.2: Deliveries will be from 7:00am to 7:00pm.
OP.2: Online system will operate at all times including online support.
OP.3: Period of downtime will be every 2 weeks on Sunday from 5am to 5:30pm for maintenance.
OP.4: Incremental backups will be per shift.
3.5.3 Site Adaptation
SA.1: The system will be adapted in phases, as future changes will be made.

Software Requirements Specification Template - 2