3. The system auto-generates a special tracking number to assist in tracking. 4. The system also stores date, time of submission and the expected time of delivery status of payment, total freight and destination office are recorded. 5. The information is then stored and can be used by the receiving office to dispatch the parcel and if unpaid, client can pay then. 6. With tracking number, a client can view other racking details such as real time location
16 126.96.36.199 Adding an office and allocating an officer 1. Only admin can add a new office. 2. Administrator can allocate an office to a new manager. With the developed system, frequent visits to the Smart currier offices will be eliminated and incase a parcel is not delivered to the right destination, the location will be visible to the client only by providing the tracking number to the nearest office manager or do the checking on his comfort zone. 4.3 Requirement specification. A system requirement is a characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users (Rosenblatt, 2011). For this system, the system requirements are functional requirements, non-functional requirements, and hardware requirements. 4.3.1 Functional Requirements Functional requirements are the statements of services the system should provide, how the system should react to particular inputs, and how the system should behave in a particular way. That it essentially specifies something the system should do . Sommerville (2007), The system’s functional requirements or what the system should do to its users are: 1. The system allows for different levels of access that is admin and co-admin logins with various functions. 2. The system will allow admin to create new offices. 3. The system will also allow administrator to create office managers. 4. Administrators will be allowed to view and update courier details. 5. The system will allow courier officers to input parcel details and track status for customers. 6. It will allow customers to for online tracking of real time location of the cargo. 7. Issue tracking code to senders and (or) recipients. 8. Generate reports.
17 4.3.2 Non-functional requirements Non-functional requirements are requirements that are directly concerned with the specific services delivered by the courier management system to its users or rather non-functional requirements describe how the system works that is , they are the attributes of the system . They will simply help the system accomplish the functional requirements (Sommerville, 2007). Non-functional requirements within the system are: 1. The system should be visually attractive, user friendly and simple to use. 2. The system is highly portable with minimal compatibility issues thus can be viewed from any browser.
You've reached the end of your free preview.
Want to read all 49 pages?
- Spring '19
- One Of The Projects Undertaken, ........., Requirements analysis, Smart Courier Services