Question

System Analysis and Design

On the Spot Courier Services

As On the Spot Courier Services continues to grow, Bill discovers that he can provide much better services to his customers if he utilizes some of the technology that is currently available. For example, it will allow him to maintain frequent communication with his delivery trucks, which could save transportation and labor costs by making the pickup and delivery operations more efficient. This would allow him to serve his customers better. Of course, a more sophisticated system will be needed, but Bill's development consultant has assured him that a straightforward and not-too complex solution can be developed.

Here is how Bill wants his business to operate. Each truck will have a morning and afternoon delivery and pickup run. Each driver will have a portable digital device with a touch screen. The driver will be able to view his or her scheduled pickups and deliveries for that run. (Note: This process will require a new use case something the Agile development methodology predicted would happen.) However, because the trucks will maintain frequent contact with the home office via telephony Internet access, the pickup/delivery schedule can be updated in real time even during a run. Rather than maintain constant contact, Bill decides that it will be sufficient if the digital device synchronizes with the home office whenever a pickup or delivery is made. At those points in time, the route schedule can be updated with appropriate information.

Previously, customers were able to either call On the Spot and request a package pickup or visit the company's Web site to schedule a pickup. Once customers lugged in, they could go to a Web page that allowed them to enter information about each package, including "deliver to" addresses, size and weight category information, and type of service requested. On the Spot provided "three hour," "same day," and "overnight- services. To facilitate customer self-service, On the Spot didn't require exact weights and sizes, but there were predefined size and weight categories from which the customer could choose.

Once the customer entered the information for all the packages, the system would calculate the cost and then print mailing labels and receipts. Depending on the type of service requested and the proximity of a delivery truck, the system would schedule an immediate pickup or one for later that day. It would display this information so the customer would immediately know when to expect the pickup.

Picking up packages was a fairly straight forward process. But there was some variation in what would happen depending on what information was in the system and whether the packages were already labeled. Upon arriving at the scheduled pickup location, the driver would have the system display any package information available for this customer. If the system already had information on the packages, the driver would simply verify that the correct information was already in the system for the packages. The driver could also make such changes as correcting the address, deleting packages, or adding new packages. If this were a cash customer, the driver would collect any money and enter that into the system. Using a portable printer from the van, the driver could print a receipt for the customer as necessary. If there were new packages that weren't in the system, the driver would enter the required information and also print mailing labels with his portable printer.

One other service that customers required was to be able to track the delivery status of their packages. The system needed to track the status of a package from the first time it "knew" about the package until it was delivered. Such statuses as "ready for pickup," "picked up," "arrived at warehouse," "out for delivery," and "delivered" were important. Usually, a package would follow through all the statuses, but due to the sophistication of the scheduling and delivery algorithm, a package would sometimes be picked up and delivered on the same delivery run. Bill also decided to add a status of "canceled" for those packages that were scheduled to be picked up but ended up not being sent.

a. Draw a Domain Class Diagram of your entire system.
b. For the Use Case Request a Package Pickup:
i.Write a Fully Developed Use Case description.
ii. Draw an Activity Diagram.
iii. Draw an SSD.

Answer 1

Thank you. Please give an upvote. If any queries or changes needed please comment will respond ASAP!!!!!