On the Spot Courier Services Running Case Study Michael Dimond System Analysist Problem Description Founder of On The Spot Courier Services, Bill Wiley discovered he had minor issues with his business. He was having trouble getting business. He would advertise to local businesses that needed same day delivery. After that didn’t work he knew he needed to change things. Like build his own website where companies could place shipments online, get software to manage customer accounts, and a database to keep track of inventory. System Capabilities · Be able to have customers place orders online as an alternative to over the phone. · Easily manage inventory · Create customer accounts for easier tracking. · Have delivery drivers be able to scan in packages upon pickup and store that info in warehouse database. Business Benefits · Make ordering pickups and shipments easier for customers. · Easier way to track shipments and know what is in the warehouse at all times to prevent loss of package. · Make tracking packages easy for customers so they will want to continue doing business with you. The stakeholders for On the Spot would be Bill Wiley, the customers, warehouse staff, and delivery personal. The customer should be actively involved in the system definition because they will be placing the orders. As the business grows Human Resources (payroll, accountant) would also be involved. If I were commissioned to build the system I would determine the requirements by: I would first interview the users and stakeholders to understand the business function and need. Then review inputs, outputs, and procedures external to the organization and existing business documents. I would then observe and document the business process to better understand what occurs in the courier business functions. Using the information obtained from the business functions I would then research vender solutions to avoid common mistakes, save time and money. Lastly, I would collect user comments and suggestions to ensure the system is accurate and functioning. Some questions needed answered are as follows: · What are the business operation and process? · How are the operations performed? – how is it done? –what steps are taken? – can they be done another way? · What information is needed to perform the operations? –what information is used? – what inputs are used? –what output is produced? -Use Case actors: · Customer · Employee (Driver) · Bill -Use Cases: · Requesting a package pickup · Picking up a package · Generate Bill · Print Label Fully developed use case for Requesting a package pickup Use case name: Request a package pickup Scenario: Web customer requests package pickup Triggering event: Web customer has package(s) 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: Customer ...

1. On the Spot Courier Services
Running Case Study
Michael Dimond
System Analysist
Problem Description
Founder of On The Spot Courier Services, Bill Wiley
discovered he had minor issues with his business. He was
having trouble getting business. He would advertise to local
businesses that needed same day delivery. After that didn’t
work he knew he needed to change things. Like build his own
website where companies could place shipments online, get
software to manage customer accounts, and a database to keep

2. track of inventory.
System Capabilities
· Be able to have customers place orders online as an alternative
to over the phone.
· Easily manage inventory
· Create customer accounts for easier tracking.
· Have delivery drivers be able to scan in packages upon pickup
and store that info in warehouse database.
Business Benefits
· Make ordering pickups and shipments easier for customers.
· Easier way to track shipments and know what is in the
warehouse at all times to prevent loss of package.
· Make tracking packages easy for customers so they will want
to continue doing business with you.
The stakeholders for On the Spot would be Bill Wiley, the
customers, warehouse staff, and delivery personal. The
customer should be actively involved in the system definition
because they will be placing the orders. As the business grows
Human Resources (payroll, accountant) would also be involved.
If I were commissioned to build the system I would determine
the requirements by:
I would first interview the users and stakeholders to understand
the business function and need. Then review inputs, outputs,
and procedures external to the organization and existing
business documents. I would then observe and document the
business process to better understand what occurs in the courier
business functions. Using the information obtained from the
business functions I would then research vender solutions to
avoid common mistakes, save time and money. Lastly, I would
collect user comments and suggestions to ensure the system is
accurate and functioning.

3. Some questions needed answered are as follows:
· What are the business operation and process?
· How are the operations performed?
– how is it done? –what steps are taken? – can they be done
another way?
· What information is needed to perform the operations?
–what information is used? – what inputs are used? –what
output is produced?
-Use Case actors:
· Customer
· Employee (Driver)
· Bill
-Use Cases:
· Requesting a package pickup
· Picking up a package
· Generate Bill
· Print Label
Fully developed use case for Requesting a package pickup
Use case name:
Request a package pickup
Scenario:
Web customer requests package pickup
Triggering event:

4. Web customer has package(s) 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:
Customer
Related use cases:
Request package pickup (phone in) Enter package info (pickup
package)
Stakeholders:
Bill, Customer, Delivery employee
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. 1.3.1 Display Cost
2. 1.3.2 Display expected pickup time
3. 1.3.3 Create Request record
Create Package record
1.4.1 Print label
Exception conditions:
1.4.1 Label cannot print

5. Use Case Diagram
Access Controls
a. Bill (Owner): Should be given access to all financial records,
as well as payroll, customer info, and shipping info.
b. Customers: A user control for the customer is customerID so
only they have access to their account.
c. Warehouse workers: warehouse workers do not require access
to any controls, therefore have no access controls.
d. Delivery Driver: security locks and safeguards must be
placed on handheld scanners to protect shipping info in case of
loss or theft.
e. Suppliers: Should be given limited access to view weather the
shipment has arrived or not.
All data should be encrypted, especially on handheld devices or
anything that leaves the main office or warehouse. If any of the
encryptions were hacked, then all customer and supplier info
could be at risk of being stolen. Especially billing and payment
info.
Domain Model Classes
· Customer
· Payment
· Customer Account
· Order
· Package