Waiters on wheels

Introduction

For this project, you will be required to put into practice the tasks associated with the Systems Analysis and Design module. You should work in GROUPS OF FOUR (4) for this project.

It is essential that individual members of the group realize their responsibility to their peers and behave in a professional manner.

OBJECTIVES OF THE PROJECT

1. To identify the framework of activities associated with methodologies and describe how the techniques are used together to develop a system 2. To demonstrate, apply and document, to the appropriate standard, the key techniques of analysis and design for the chosen paradigm 3. To identify the key user interface issues required in a system design

DELIVERABLES

Group Assignment (70%)

Each team should: ← Analyze the existing system carefully as provided in the case study. In areas that lack information, the team may make logical assumptions which need to be documented in their reports. ← Identify the problems in the existing systems and propose a solution. ← Prepare a feasibility report. A schedule feasibility report and an operational feasibility report would suffice o The schedule feasibility report should contain:

▪ Workload matrix ▪ Gantt chart – to be done using an appropriate project management tool o The operational feasibility should be discussed using PIECES framework ← Compare some appropriate / related methodologies and suggest a suitable one for developing the proposed system. Justify the selection ← Identify the breakdown of work associated with the chosen methodology which would be undertaken. (Note: the tasks should be limited to the analysis and design stage, i.e. not including the development / coding and stages thereafter).

← Suggest with justification and apply appropriate techniques of determining user requirements.

Summarize the findings. ← Demonstrate and apply the key techniques of analysis for the chosen methodology based on the findings. ← Develop a prototype of the proposed solution using a proprietary database tool by designing the input, output and dialogue screen that matches with the logical design. ← Document each stage of the analysis and design to the appropriate standards. ← Present the solution

Individual Assignment (15%)

Each team member / individual should prepare a formal documentation of and present the ← physical design which was done by the individual – with the appropriate explanation / description of the design with regards to the finalized logical design ← a critical evaluation of the assignment in terms of problems encountered and how they were overcome, lessons learnt, etc. according to appropriate standards

Individual Presentation (15%)

Each team member / individual should: ← Present his / her contribution of the solution for the Group Assignment Marks awarded here would depend on Project Knowledge / Professionalism and Contribution of the individual.

ADDITIONAL INFORMATION

Contribution

Students are reminded that this is designed to be a group effort. It is not therefore sensible for every group member to be involved in every activity, though overall findings should be discussed and agreed by the group as a whole. Each individual is required to attach to his / her report a signed peer-to-peer evaluation form (to be provided by the module lecturer). This form allows the individual to assess his / her peers’ contribution to the project as well as illustrates the contribution of each team member. It should be remembered that people who do not contribute to the exercise cannot reasonably expect to get any marks from it.

Minutes of meetings

Each group is to regularly submit the minutes of meetings to the module lecturer. The report should among other things contain details such as: ⇨ date, start time, end time and venue of the meeting

⇨ attendees / absentees – with or without apology ⇨ reporting of previous meetings / outcomes / findings ⇨ details of discussion based on agenda / conclusions drawn ⇨ action list for group members Hardcopies of the minutes of meeting need to be attached as appendices in the documentation. Any difficulties / problems faced during the duration of the project – such as non cooperative members, etc, should be pointed out in the minutes.

Documentation Standards

⇨ Project documentation should be complete ⇨ The project documentation should be at least of average standard in terms of language, layout and flow ⇨ The contents of the project documentation should be appropriately structured ⇨ References should be accurate, relevant and up to date ⇨ References should be done using Harvard’s Name Referencing ⇨ Diagrams / tables / graphs which have been used in the documentation should be properly captioned

MARKING CRITERIA

Distinction (75% and above)

This grade will be assigned to work where the documentation is complete and describes in detail, with little or no errors, the following components: introduction, feasibility study, selection of methodologies, selection and application of investigation techniques and analysis / logical design in accordance with excellent documentation standards. To obtain this grade, the candidate’s individual assignment should show all techniques of methodology applied with little or no errors.

All deliverables of the individual component should be coherent with detailed description to explain the diagrams. Overall documentation standards for both the group project as well as the individual assignment should be of excellent quality. In order to obtain a grade at this level, individuals should be able to address all issues with regards to not only their own component of the module but also be those of the other group members. Individual’s contribution to the project, at this level should be more than 75% and overall peer evaluation should indicate excellent standards.

Credit (65% – 74%)

This grade will be assigned to work where the documentation is complete and describes briefly, with some errors, the following components: introduction, feasibility study, selection of methodologies, selection and application of investigation techniques and analysis / logical design in accordance with good documentation standards. To obtain this grade, the candidate’s individual assignment should show all techniques of methodology applied but some errors. All deliverables of the individual component should be coherent with detailed description to explain the diagrams.

Overall documentation standards for both the group project as well as the individual assignment should be of excellent quality. In order to obtain a grade at this level, individuals should be able to address most issues with regards to not only their own component of the module but also be those of the other group members. Individual’s contribution to the project, at this level should be more than 65% and overall peer evaluation should indicate excellent standards.

Pass (50% - 64%)

This grade will be assigned to work where, most of the basic requirements of the documentation listed above, such as introduction, feasibility reports, logical process models, data dictionary are of adequate standard which is evident in the hardcopy of the documentation. The physical design of the system in terms of the interactive screen design and report maps adequately against the logical design presented in the documentation.

The documentation should be of adequate standard in terms of language, layout and flow. Some accurate, relevant and up-to-date referencing was visible. Group presentation of the team should have adequate visual aids with relevant information presented and adequate coordination among group members. Individuals should display an adequate level of professionalism and project knowledge. Peer-to-peer evaluation of individual’s contribution should be adequate.

Fail(Below 50%)

This grade will be assigned to work where, most of the basic requirements of the documentation listed above, such as introduction, feasibility reports, logical process models, data dictionary are of poor standard which is evident in the hardcopy of the documentation. The physical design of the system in terms of the interactive screen design and report shows little or no mapping / linking with the logical design presented in the documentation.

The documentation is of poor standard in terms of language, layout and flow. Minimal or no referencing was done. Group presentation of the team has poor visual aids with irrelevant information presented and poor coordination among group members. Individuals display on the average a poor level of professionalism and project knowledge. Peer-to-peer evaluation of individual’s contribution is poor.

WAITERS ON WHEELS : COMPUTERIZED DELIVERY TRACKING SYSTEM

Waiters on Wheels is a restaurant meal-delivery service started in 1997 by Sue and Tom Bickford. The Bickfords both worked for restaurants while in college and always dreamed of opening their own restaurant. But unfortunately, the initial investment was always out of reach. The Bickfords noticed that many restaurants offer take out food, and some restaurants, primarily pizzerias, offer home delivery service. Many people they met, however, seemed to want home delivery service but with a more complete food selection.

Waiter on Wheels was conceived as the best of both worlds for Sue and Tom – a restaurant service but without the high initial investment. The Bickfords contracted with a variety of well-known restaurants in town to accept orders from customers and to deliver the complete meals. After the restaurant prepares the meal to order, it charges Waiters on Wheels a wholesale price, and the customer pays retail plus a service charge and tip. Waiters on Wheels started modestly, with only two restaurants and one delivery driver working the dinner shift.

Business rapidly expanded, and the Bickfords realized they needed a customer computer system to support their business operations. They hired your consultant firm to help them define what sort of a system they needed.

Sue described the current system as such “When a customer calls in wanting to order, I need to record it and get the information to the right restaurant. I need to know which driver to ask to pick up the order, so I need drivers to call in and tell me when they are free. Sometimes customers call back wanting to change their orders, so I need to get my hands on the original order and notify the restaurant to make the change.”

Tom continued, “The drivers get the copy of the bill directly from the restaurant when they pick up the meal, which should agree with our calculations. The drivers collect the amount plus a service charge. When drivers report in at closing, we add up the money they have and compare it to the records we have. After all drivers report in, we need to create a deposit slip for the bank for the day’s total receipts. At the end of each week, we calculate what we owe each restaurant at the agreed-to-wholesale price and send them a statement and check.”

Basic requirements : Design a system which does some processing when events such as these occur : ▪ a customer places an order either via telephone or via the company website. ▪ a driver is finished with a delivery

▪ a driver reports for work

The system should also produce information at some specific points in time – for example, when it is : ▪ time to produce an end-of-day deposit slip ▪ time to produce end-of-week restaurant payments ▪ time to produce weekly sales reports