BIT301 Systems Design & Development Page 1 of 16 pages Assignment 1 – Systems Design Report Assignment Due Date: Week 8 (Draft due in Week 5)

Report Synopsis:

This assignment requires a report to be submitted documenting the design elements specified in the task list below based on the On the Spot Couriers case study. TASKS 1. Develop a design plan and schedule detailing your plans for the next 4 weeks in

order to deliver the tasks specified. This should cover what design decisions must be made and who should make them; what tasks must be performed and in what order; how the project will be managed and controlled;

2. Specify technical requirements based on inputs, process and outputs. Make a list of the equipment that Bill should purchase to support his new system. Include all

equipment that will be needed for the home office, the drivers, and at Bill's residence. Identify and describe actual equipment that can be purchased today. Estimate the cost of the equipment. 3. Design the environment for the system by drawing a network diagram showing how

all the equipment will be connected. Identify Internet connections, VPNs, and telephony links as appropriate.. 4. For each of the use cases supplied: Design Menu hierarchies, storyboards and

implement a prototype for each of the supplied use cases. i. Design menu hierarchies for each use case ii. Write out the steps of the dialogs for each use case use cases iii. Create storyboards for each use case making a sketch of the

interaction with web pages. iv. Create a prototype for the web pages using a suitable tool. This could be done on a web development package or for example in

word or powerpoint, the idea being not to develop a working prototype but rather to provide a mock-up of the interface. BIT301 Systems Design & Development Page 2 of 16 pages

.Assessment Requirements The report is a TEAM PROJECT, (4 students per group) but students will receive an overall mark based on their individual contribution to the team effort, with some marks being based

on the total report and allocated to the group as a whole, and others being based on peer assessment of an individual's contribution which will account for 20% of the overall mark.

A progress report and draft will be submitted for feedback during week 5

The team must conduct a professional walkthrough of their document lasting a maximum of 15 minutes to be delivered to the tutor during the workshop session in week 8 of the semester.

Your report must include: Assignment Cover Page: (Use the cover sheet provided. Include the Title, Assignment number, Student Names and IDs, Subject) Title page (Name of report who it is prepared for, and authors)

Executive summary (1 paragraph) Table of contents The relevant design documents requested in the task list

References/ Bibliography A footer to include your team's student IDs, and page number. Students in the team should contribute equally and equitably to the team effort..

BIT301 Systems Design & Development

Page 3 of 16 pages Submission of Assignments

The report, as a whole, must be submitted by the team leader. Each student must submit their section separately as specified below.

Prior to submission of your assignment you will be required to check for authenticity and originality using the "Turnitin" facility. The link can be accessed via moodle. All assignments must be submitted as an electronic file with an electronic cover sheet. The assignment cover sheets are available on your subject's Moodle. Under no circumstances must you submit your assignment via email or to your teacher unless otherwise instructed. • Please ensure that all assignments are handed in by the due date and with the

appropriate Assignment Cover Sheet. Assignments handed in past the due date may not be accepted or may incur penalty points. • Please ensure that you abide by Melbourne Polytechnic's Rules and Regulations

Submission of Late Assignments A penalty of 10% of marks received per day will be applied where assignments are submitted after the due date UNLESS a request in writing has been submitted by the due

date together with relevant documentation including a medical certificate where appropriate. Academic and Professional Standards Plagiarism is the inclusion of another person's work within your submission without

acknowledgment or permission. While limited amounts of information and concepts expressed by others may be included as part of your work, each inclusion must be

identified by appropriate referencing and acknowledgement to the original author. Plagiarism is regarded as a form of cheating, The penalties associated with

misconduct are severe, and plagiarism may result in failure or variation of grade in the unit. For more information on the rights and responsibilities of students, grievance and appeal procedures see NMIT/1R/11 Student Discipline

BIT301 Systems Design & Development Page 4 of 16 pages Proposed marking Scheme: Draft Outline week 5

Mark i) Reasonable attempt at some of required document

Marks for the Draft outline may not be awarded to students that do not take part in its preparation Score 5 . Team Project Element

Design Document has appropriate content (35 marks) • Design plan (5 marks)

• Technical requirements specification based on inputs,

process and outputs. (5 marks) • Equipment Specification & Costing (8 marks) • Network diagram (5 marks) • Design Menu hierarchies, storyboards and prototypes (12

marks) Report Layout (5 marks) Report structure, format, presentation Appropriately referenced

Spelling/Grammar clear Walkthrough (5 marks) Content:

Clear Outline of report and recommendations Covered report contents Demonstrated knowledge of material Delivery

Timing under limit (additional 2-3 minutes question/discussion time)

Pitch - Presented to business audience (professional attire and manner) Quality of vocabulary / professional use of Language Spoke clearly and confidently / regulated pitch and volume i) No significant matches (No reduction) ii) Match score between 15 and 20 (-5 marks)

iii) Match score >= 20 with significant unreferenced matches or large 'matching' sections (-15) iv) Not submitted to Turnitin (-20 marks)

Unauthorised Late submission deduction (10% per day) Peer Assessment (20% of final group mark allocated based on PA)

The presentation and team mark may be reduced if a student does not participate appropriately. The reduction is at the discretion

of the lecturer/tutor. Team Score (40)

Final

Walkthrough 5 Draft 5 Total 50 BIT301 Systems Design & Development Page 5 of 16 pages

On the Spot Courier Services adapted from Saltzinger, J.W., Jackson, R.B, Burd, S.D.: Systems Analysis and Design in a Changing World Editions 6 Course Technology As an employee of a large international courier and shipping service, Bill Wiley met almost every day with many companies that shipped and received packages. He was frequently

asked if his company could deliver local packages on the same day. Over several months, he observed that there appeared to be a substantial need for courier services in the city in which he lived. He decided that he would form his own courier delivery company called On

the Spot to fill this need. Bill began by listing his mobile telephone number in the Yellow Pages. He also sent letters to all those companies that had requested same-day courier service that his prior company

had not been able to serve. He hoped that, through good service and word-of-mouth advertising, his business would grow. He also began other advertising and marketing activities to promote his services.

At first, Bill received delivery requests on his business mobile phone. However, it was not long before his customers were asking if he had a Web site where they could place orders

for shipments. He knew that if he could get a Web presence he could increase his exposure and help his business grow. After he had been in business only a few short months, Bill discovered he needed to have additional help. He hired another person to help with the delivery and pickup of packages. It

was good to see the business grow, but another person added to the complexity of coordinating pickups and deliveries. With the addition of a new person, he could no longer "warehouse" the packages out of his delivery van. He now needed a central warehouse where he could organize and distribute packages for delivery. He thought that if his

business grew enough to add one more delivery person he would also need someone at the warehouse to coordinate the arrival and distribution of all the packages.

. The details of the package pickup and delivery process are described below: When Bill got

an order, at first, only on his phone, he recorded when he received the call and when the shipment would be ready for pickup. Sometimes, customers wanted immediate pickup;

sometimes, they were calling to schedule a later time in the day for pickup. Once he arrived at the pickup location, Bill collected the packages. It was not uncommon for the customer to have several packages for delivery. In addition to the name and address of

the delivery location, he also recorded the time of pickup. He noted the desired delivery time, the location of the delivery, and the weight of the package to determine the courier cost. When he picked up the package, he printed out a label with his portable printer that he

kept in the delivery van. At first, Bill required customers to pay at the time of pickup, but he soon discovered that there were some regular customers who preferred to receive a monthly bill for all their shipments. He wanted to be able to accommodate those customers. Bills were due and payable upon receipt.

BIT301 Systems Design & Development Page 6 of 16 pages To help keep track of all the packages, Bill decided that he needed to scan each package as it was sorted in the warehouse. This would enable him to keep good control of his

packages and avoid loss or delays. The delivery of a package was fairly simple. Upon delivery, he would record information about when the delivery was made and who received it. Because some of the packages

were valuable, it was necessary in those instances to have someone sign for the package. On the Spot courier services grew and changed over the years. At first, Bill received

requests for package pickups on his mobile phone, recorded that information in a log, and would then drive around to retrieve all the packages later in the day. However, he soon discovered that with another driver, it was difficult to coordinate pickups between the two of them from his van. It was not long before he reorganized his business and turned the warehouse employee into a driver. Then, he stayed in. the warehouse

himself, and his two employees made all the pickups and deliveries. This worked well because he could control and coordinate the pickups and deliveries better. It was also easiest for him to receive pickup requests working at a desk rather than trying to

do it while driving a delivery van. As he thought about how his business was growing and the services he provided to his customers, Bill began to itemize the kinds of information he would need to maintain. Of course, he needed to maintain information about his customers. Some of his customers

were businesses; some were individuals. He needed to have basic address and contact information for every customer. Also, for his corporate customers, he needed to identify a primary contact person. It was

mostly his corporate customers who wanted to receive monthly statements listing all their

shipments during the month and the total cost. Bill needed to distinguish which customers paid cash and which wanted monthly statements. In fact, for those that paid monthly, he

needed to keep a running account of such things as when they were last billed, when they paid, and any outstanding balances. Finally, when payments were received, either for individual shipments or from monthly

invoices, he needed to record information about the payment: type of payment, date, and amount. Although this was not a sophisticated billing and payment system, Bill thought it would suffice for his needs.

Next, he started thinking about his packages and shipments. At the time that a request for a pickup came in, he needed to keep track of it as some type of delivery request or delivery

·order. At that point in time, Bill mostly needed' to know who the customer was, where the pickup location was, and what date and time the package(s) would be ready for pickup. He also recorded the date and time that he received the order. A delivery order was considered

"open" until the delivery van arrived at the pickup location and the packages were all retrieved. At that point, the delivery order was satisfied. BIT301 Systems Design & Development Page 7 of 16 pages Once the packages were retrieved, each package needed to be uniquely identified, Bill

needed to know when it was picked up and which delivery person picked it up. Other important information was the "deliver to" entity name and the address. He also needed to identify the type of delivery. Some packages were high priority, requiring same-day delivery. Others were overnight. Of course, the weight and cost were recorded so the customer could either pay or have it added to the monthly invoice. In the courier and delivery business, one of the most important information requirements is the date and time stamp. For each package, it is important to know when it was picked up, when it arrived at the warehouse, when it went back out on the delivery run, and when it was delivered. When possible, it is also important to have names associated with each of

these events. 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 labour 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. 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 logged 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 straightforward process. But there was some variation in what would happen depending on what information was in the system and whether the packages were already labelled. Upon arriving at the scheduled pickup location, the driver BIT301 Systems Design & Development Page 8 of 16 pages 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 "cancelled" for those packages

that were scheduled to be picked up but ended up not being sent. Dialog for Driver and System: System: What do you what to do? Driver: Give me the address of the next stop. System: It is a delivery at this address ---- Driver: How far is that from where I am now?

System: 6.3 miles Driver: Can you show me the best route to get there? System: Here is a map showing the shortest route using primary roads. Do you want printed instructions? Driver: No

Driver: How many pickups do I have left today? System: 14 Driver: How many deliveries do I still have? System: 37

Driver: Show me the next 5 System: Here is a list. Do you want to see a map? Driver: Yes. Show me a map of the next five stops.

System: OK Driver: Do you have any new additions that have come in? System: Yes. There is one new pickup recently received. It will be best to pick it up on the return trip to the warehouse.

BIT301 Systems Design & Development Page 9 of 16 pages USE CASE: BIT301 Systems Design & Development Page 10 of 16 pages

USE CASE DESCRIPTIONS BIT301 Systems Design & Development Page 11 of 16 pages

BIT301 Systems Design & Development Page 12 of 16 pages ACTIVITY DIAGRAMS BIT301 Systems Design & Development Page 13 of 16 pages

BIT301 Systems Design & Development Page 14 of 16 pages SEQUENCE DIAGRAMS BIT301 Systems Design & Development

Page 15 of 16 pages BIT301 Systems Design & Development Page 16 of 16 pages

CLASS DIAGRAM