On The Spot Courier Services

profiletutu2410
milestone1.docx

ON THE SPOT COURIER SERVICES CASE STUDY

Fred Osei Tutu

Computer Information System, Gwinnett Technical College

CIST 2921: IT Analysis Design & Project Management 24461

Charles Hardnett

November 5, 2020

Table of Contents System Vision Document 3 Problem Description 3 System Capabilities 3 Business Benefits 3 Stakeholders: 3 Functional requirements: 4 Usability requirements: 4 Reliability requirements: 4 Security requirements: 4 Performance requirements: 4 use case diagram: 6 Use case of the most important 7 High Level Security control 8

System Vision Document

Problem Description

Bill Willey which formed his own delivery company has some problems. He began by listing his mobile phone number in yellow pages and also sent letters to all those companies that need the same day delivery service. But after a few months he discovered he needed to have additional services like having online order, checking warehouse by inventory, additional help for delivery and pick up, managing customer accounts.

System Capabilities

The new system should have these capabilities:

· Provide website for customer to look at it.

· Take online order to pick up.

· Schedule and manage warehouse inventory.

· Gathering and manage customer information.

· Have a capability to pick up and delivery on same day.

Business Benefits

The System should provide these benefits:

· Making customer more satisfy which can help to grow business.

· Provide same day delivery that help save time for customer.

· Growing business makes more opportunity for people to having job.

Stakeholders:

· The owner of business

· Customers

· Employee of delivery

· Employee of warehouse

· Employee of managing website

Considering that Bill was the vision bearer for the business and the framework, he will comprehend the requirements of the framework. Be that as it may, since he is letting business clients utilize the framework to plan bundles, it would be a smart thought to shape a center gathering of clients who would help in necessities definition. Both the conveyance people and the stockroom staff will have proposals on the best way to make their positions simpler. They ought to be associated with the necessities definition. Bill's bookkeeper ought to be included to guarantee that the framework has adequate budgetary data and controls.

Functional requirements:

· Enter customer information

· Take a pick-up package

· Pick up package

· Deliver a package

· Enter package information

· Track a Package

· Display a route (print, view)

· Update a route

· Print monthly bills

· Accept payment

Usability requirements:

· The system has to provide a web user interface that provides the required functionality using a maximum of three mouse clicks to navigate to any feature page and sub function.

· The user interface has to be available on devices on a variety of devices like mobile phones, tablets, and laptop and desktop.

· The user interface should be usable to perform all functions to the hearing and visually impaired user community.

Reliability requirements:

· The system web site shall be available with an uptime of 99.9%- with a maximum planned downtime of 8 hours per month between midnight and 8 AM.

· The maximum downtime of any unplanned outage-shall not exceed 5 minutes in normal business hours.

· The accuracy of package tracking shall reflect the current status to within one hour.

Security requirements:

· The system shall maintain confidentiality of all data both while in transit over the internet and while at rest.

· The system shall require user access controls for any user of the system.

· The system shall enforce role-based security for all functions on the web site.

Performance requirements:

· The system website shall provide a response time of all interactive page refreshes to not exceed 2 secs with an average response time of 1 sec.

· Any long running reporting operations on the web site whose elapsed time exceeds 5 secs shall provide a progress indicator to the user.

· The system web site shall support up to one hundred simultaneous users without any performance degradation of other performance requirements.

Questions for Stakeholders

Stakeholders such as Customers who are using courier service "Persons who are delivering the couriers and Employee who is working in warehouse should be interviewed. Here are lists of questions need to be answered:

· Whether the product needs to be delivered by same day?

· Whether the product needs to be delivered by overnight?

· Whether the customer is a ready cash paying customer?

· Whether the customer is paying amount of the product through account?

· Whether the customer is new to this service?

· What location to pick up the package?

· What is the size of the package?

· How much cost it takes to deliver the packet?

· What kind of equipment is required to maintain products in warehouse?

· What information is needed to be tracked?

· Whether the payment is done by ready cash?

· Whether the payment is done through web page?

· Whether the payment is done by monthly account?

Three Actors for the use case:

These are the three actors for the use case:

· Owner

· Customer

· Delivery person

· Warehouse person

The owner (Bill Wiley) is responsible entering the request for pickup, entering of package pickup info into the system, printing out labels, he also has to print out bills for customers, he provides payment and enter payments into the system.

The customer use case here is to sign for delivery.

The delivery person has to provide package pickup info and provide package delivery info.

The warehouse person is the actor of the use case responsible for scanning packages.

use case diagram:

Figure 1: use case diagram

From Figure 1:Use Case diagram , Display label, Display bills, Provide package pickup info, Provide payments, Scan package, Provide package delivery info, and Sign for delivery are the use cases. Bill Wiley, Delivery person, Warehouse person, and Customer are the actors. Bill Wiley communicates with the system to enter a request for pick up, enter Package info, print label, print bills and enter payments. The delivery person who is also an “Actor” communicates with the system by entering package pick up info and enter package delivery info. The customer on the other hand place the order and request for pickup and also sign for delivery. Warehouse person is responsible to track all the packages by scanning each package and helps to avoid the delay or any loss of package. The associate relationship between the actors and the use cases are represented with the lines.

Use case of the most important

Use case name:

Request a package pickup

Scenario:

Web customer request package pickup

Triggering event:

Web customer has package to be picked up and requests pickup

Brief description:

User enters package information (To address, type of service, size/weight). System returns the cost, expected pickup time, and prints label

Actors:

Web customer

Related use cases:

Request package pickup

Enter package info

Stakeholders:

Owner, Customer, Delivery person

Preconditions:

Customer and customer account must exist

Postconditions:

Pickup request is created and associated with customer

Flow of activities

Actor

System

1. For each package

1.1 Enter type of service

1.2 Enter TO information

1.3 Enter package size/weight

1.4 Request label print

1.3.1 Display Cost

1.3.2 Display expected pickup time

1.3.3 Create request record

Create package record

1.3.4 Print label

Exception conditions:

Label cannot print

Table 1: Fully Develop Use Case

“Table 1: Fully Develop Use Case ” is the use case description of how a customer put in a request for a package pickup. From the above use case, the “Use Case Name” will be any name that is simplest possible but descriptive too. Each of the use case contains the internal activities set which are unique and it is represented as “Scenario”, where customers are told to request a package pickup online. “Triggering event” is basically the event that is started by primary actor to start the use case execution. “Brief description” describe the whole use case in a summarize form. “Actor” can be a human user, a hardware device, or any third- party software system that interact with the system for goal accomplishment. Any associated use case is considered as “Related use case” like customers request a package pickup and enter package info, but first a customer create an account. Anybody involved in the successful implementation of the system is considered a “Stakeholder” like owner (Bill Wiley) and the delivery person and the customer as stated in the table above. “Precondition” and “Postcondition” are the conditions that should be met before the use case starts and what should be met after the use case is completed successfully.

The “flow of activities” is the tenth compartment of the use case description. It consists of two columns about the steps performed by the actor and the response of the system. “Exceptions conditions” talks about the details of the other activities.

High Level Security control

Access controls:

· Customers: one of the best controls is using UserID and password for clients so other people cannot access to their account.

· Employee: like delivery person (unauthorized users) their device has to be log off automatically in case of lost it.

· Suppliers are count as Registered users. They are defined depending on what they are authorized to view and update.

· Manager (in this case is Bill) count as Privileged users that access to all the financial records, so access should be controlled like to a bank account with UserID and password.

· Warehouse staffs are count as unauthorized user. So, they aren’t allowed access to any part of account.

All sensitive data would be encrypted.

All information about financial and customer accounts have to be encrypted. Personal information should be encrypted such as credit card number, social security number, bank account numbers.

Encryption is an effective technique for a secure exchange of information between two entities who have appropriate keys. So, unauthorized personal such hackers can’t view them. Hypertext Transfer Protocol Secure (HTTPS) is an Internet Standard for securely transmitting Web pages. It supports several types of encryption, digital signing, and certificate exchange and verification.