Systems Analysis and Design
Waiters on Wheels
SYSTEM ANALYSIS AND DESIGN CE00300-1 PALVINDERJIT KAUR A/P HARNEK SINGH WAITERS ON WHEELS
DUE DATE: 6 JULY 2007 GROUP NUMBER: FOUR
GROUP MEMBERS: YERNUR ZHOLDYBAYEV
TP013704
MUHAMMAD BUTT
TP014063
PRAKASH A/L ARICHNAM
TP014245
LAW WERN SIANG
TP014146
Page |0 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Table of Contents No. 1
Topic Introduction
Page 3-7
1.1
Background
4
1.2
Assumptions
5
1.3
Problems
6
1.4
Solutions
7
2
Feasibility report
8-27
2.1
Schedule feasibility
8
2.2
Technical feasibility
12
2.3
Operational feasibility
19
2.4
Economical feasibility
24
3
Selection of methodology
28-35
3.1
Comparison of methodologies
28
3.2
Justification of selected methodology
34
3.3
Breakdown of work associated to selected methodology
35
4
Selection/Application of Investigation Techniques
36-42
4.1
Questionnaires
36
4.2
Interview
41
4.3
Summary
42
Analysis/Logical Design
43-56
5 5.1
Context diagram
43
5.2
Data flow diagram
45
5.3
Entity relationship diagram
48
5.4
Entity life history diagram
51
5.5
Use case diagram
54
5.6
Class diagram
56
Page |1 Asia Pacific Institute of Information Technology
6 Physical design Systems Analysis and Design 6.1 WebPages 6.2 7
Database
Appendix
57-58 Waiters on Wheels 57 58 59-86
7.1
Technical specifications
59
7.2
Interview pictures
65
7.3
Minutes Meetings
66
8
References
87
9
Workload matrix
88
10
Individual reports
90-103
10.1
Yernur Zholdybayev
90
10.2
Muhammad Butt
93
10.3
Prakash A/L Arichnam
96
10.4
Law Wern Siang
100
Page |2 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Introduction This paper investigates the viability and possible ramifications of a proposed automation system for the Waiters on Wheels delivery system. After examining the criteria that the new system is supposed to attain, this paper reveals some of the issues and possibilities inherent in such a system. It presents some of the decisions to be taken with the new updated system and then compares the new system with the current existing one. At the time of writing this report Sue and Tom‟s business concern has experienced and continues to experience rapid growth. An ever increasing customer base has necessitated expansion in operational scale yet the fundamental modus operandi remains unchanged from its original inception. Hampered by budget constraints and minimal operation size, the Brickford‟s original structural and operational system was and is at best, very basic. The manual paper and pen tallies and calling up after drivers may have sufficed back when Waiters on Wheels was a two restaurant, single driver operating concern. At the time the dictates of minimal size and a paucity of resources may have deemed this archaic system the sole plausible option.
Ten years on and Waiters on Wheels now deals with over ten restaurants, a whole team of operators and drivers and employs people in a new accounts section. Given the current scale of operations the existing system is no longer a feasible option. Riddled with inaccuracies and bureaucracies that are the bane of all systems, the current system is nigh on the brink of total collapse. Its inefficiencies are severely hampering growth, consuming unnecessary resources and damaging company credibility with consumer and supplier all the while.
The existing system from start to finish is entirely manual and is as such highly inefficient and susceptible to error. Further the records are temporary, one sided and cannot be cross referenced. The business is very dependent on the telephone for all its business. This is neither cost effective nor is it conducive to handling the larger business inflow that Waiters on Wheels is beginning to see.
An automated computerized system will result in a considerably faster far more fluid and flexible system with enormous headway for further growth. It will allow Waiters on Wheels an opportunity to provide additional services to its customer base thus aiding them to build on brand loyalty. In the long term, an automated system may help slash overheads while increasing market size thereby paving the way to Page |3 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Economies of Scale. To this end we propose a new system with far greater information technology involvement. This paper will outline some of the issues considered in the design process and will highlight and describe some of the features of the new system.
Background Prior to discussing the new system it is important that we fully comprehend Waiter on Wheel’s existing system. Waiters on Wheels was started out by Tom and Sue Brickford, 2 college students in 1997. Waiters on Wheels was envisaged by its founders as being the next best thing to their dream of owning their own restaurant. Waiters on Wheels was to be a restaurant service without the initial capital requirement usually associated with such a venture.
Waiters on Wheels managed to tap into what proved to be a flourishing niche market. It capitalized on the forever growing segment of young and middle-aged professionals whose hectic and chaotic lifestyles do not allow for the luxuries of a home cooked meal. Waiters on Wheels came up with what was a one stop solution for those who wished to eat at home. A myriad variety of cuisines, from different restaurants was now only a single phone number away from the home of a potential customer.
Waiters on Wheels takes orders from customers then forward them to the concerned restaurants with whom they had contractual agreements with. The restaurant prepares the food and a bill that matches Waiters on Wheels selling price. Waiters on Wheels would then pick the food and the bill and deliver to their customers, who would pay regular retail price plus a service charge and a tip. At days‟ end the drivers turn in all cash collected from deliveries during the day leaving owners Tom & Sue with the job of adding all the money and comparing the figures with their own records. (We assume that at this stage the owners also enlist the aid of their accounts staff) Waiters on Wheels would deliver a statement and pay an agreed wholesale price to each restaurant at the end of the week.
Page |4 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Assumptions Existing company setup 1. System verifies delivery range (radius from restaurant and delivery centre to customer‟s location/delivery address 2. Takes order(s) and customers details (name, phone number, address, etc) 3. Passes order(s) to restaurant 4. Restaurant receives and processes order 5. Delivery centre verifies and contacts any available driver; passes product details and specific pickup time 6. Driver pickups prepared food along with the bill from restaurant 7. Driver delivers the meal and collects payment from customer 8. Driver reports delivery status to company 9. At closing, delivery centre calculates total money collected and compares them to received records. A deposit slip is created 10. At the end of the week, money owed to each restaurant is calculated. A statement and check is then sent to them
Other assumptions 1. Growth in operations means that Waiter on Wheels now has contractual agreements with 11 restaurants. 2. The current system hasn‟t been modified since company inception. 3. They currently have 10 telephone operators, 7 drivers and 5 people handling cash flow finances. 4. All restaurants with whom Waiters on Wheels have agreements with have computers with internet connections.
5. We assume, given the current systems overly heavy dependency on the telephone that Waiters on Wheels telephone system is already up-to-scratch features a full switchboard design and is sufficiently capable of handling current and future call volume requirements. 6. Drivers all use mopeds.
Page |5 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Problems
1. The current system being as it is over taxed means that a staff member may be required to do more than his job function leading to a generally disgruntled and unhappy staff. 2. Employee turnover is high as are its subsequent inefficiencies; new staff members have to be taken in, trained and adjusted to the system. 3. New operators frequently accept orders from beyond their delivery range resulting in canceled orders and angry customers and restaurant staff. 4. Inefficiencies in the current order process coupled with growth have resulted in far greater mixed orders and late deliveries then are acceptable. 5. With no real monitoring system to control them the drivers generally tend to loiter and are not always available at hand further exacerbating delivery problems. Resources are continually wasted on calling up drivers. 6. Time consuming manual system wastes a lot of producing deposit slips and reports. Since staffs involved are for the most part new recruits, errors are high not only costing the company financially but also compromising and tarnishing their image with the restaurants. Relations with the restaurants are getting increasingly strained. 7. Poor communication methods with the restaurants result in orders having to be canceled. Many times an order is already taken before Waiter on Wheels is informed that the desired food is no longer available. 8. On numerous occasions, particularly on busy days, the restaurants do make the error of putting the wrong prices on the invoice causing much difficulty and confusion with the customers.
Page |6 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Solutions Design Criteria An ideal system would be able to fluidly manage large amounts of data from multiple sources. As a minimum it should be able to take in data from the Telephone as well as net. It should be able to maintain all data in databases while automatically generating reports at specific times without having to be commanded. It should also effectively be able to keep tabs on company drivers. For safety reasons the system should be able to generate and print reports in real time listing those who are currently in the building so that in the eventuality of a fire or some other mishap all staff can be accounted for. Finally, and perhaps most importantly, all systems need to be cost effective in the long term to be viable.
In an ideal world a system would be extremely powerful yet cost nothing to maintain but this is nigh impossible! Specifically the system will have to strike a balance between being cost effective to procure and maintain while maintaining stability, functionality and expandability. It should function with minimal human interference so that human error and overheads are minimized Implementation Details Determining the best solution for Waiters on Wheels is no easy task and will require assessing our potential solutions‟ viability from different angles. Only after having scrutinize the systems in terms of different feasibility factors will be able to decide with any certainty what the best way forward is. It is for this reason that we will now proceed to examine the system from Technical, Economical and Operational viewpoints. Each type of examination brings with itself its own very specific requirements quite different from other. The ideal system should excel in all these requirements, or at the very least, prove superior to all competition and alternatives.
Page |7 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Feasibility Report 1.
Schedule Feasibility
Page |8 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Page |9 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
P a g e | 10 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
P a g e | 11 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
2. Technical Feasibility For a system to be doable a system must be within the limits of: a. The consultant company‟s field of expertise b. What the end user, i.e. the people of Waiters on Wheels can comprehend and utilize It is important that the process by which our intended system will function is known and understood. To this end we will now outline the Hardware and Software involved in the System. The system will consist of a server, the owner‟s workstation, a Biometric System, a network printer, a dot matrix printer and 12 low end workstations. The biometric scanner and dot matrix printer will be attached to the owner‟s workstation. All staff entering and exiting the Waiters on Wheels office premises will be required to submit themselves to a fingerprint scan. The data will be processed in real time and will result in several actions taking place:
Continuously updated database record showing all the people entering and leaving the building with their exact times.
Time card reports displaying each workers working hours and subsequent due salary at the end of a specified period
A Fire report. This is a hard copy of the aforementioned personnel database.
A “live” onscreen presentation of all drivers that are currently available onsite.
The biometric system will provide real time information about the presence/availability of drivers and the exact working hours of staff by monitoring precise times of entry and exit of all staff. Waiters on Wheels will therefore not only be afforded a method to monitor driver availability but also provide a means of keeping tabs on the exact work hours of all staff and their due wages. The database record showing all peoples entry and exit into a company is for the owners‟ convenience only. It will provide clear information on the working trends and reliability of each staff member. If a member of staff is not coming to work on time or leaving early it will become more then obvious here. This will provide grounds for the owners to warn, reprimand or in exceptional cases dismiss poorly performing staff. The time cards will be generated on and saved on the owners system with a copy being forwarded to the accounts section. They will be filed for the purposes of staff maintaining staff remuneration records. The additional copy on the owners system will function as backup. P a g e | 12 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
In this instance, this employee was due to work 08.00 to 17.00 with a 1 hour lunch, that would be deducted if not clocked for. If more than 3 minutes late their time would be rounded forward to the next 15 minute increment. Overtime would be paid at rate 1 after 39 standard hours worked Monday to Friday. Saturday would be paid at rate 2 overtime but not until 39 hours at standard hours and at least 30 minutes overtime at rate 1 had been achieved. Sunday would be paid at overtime at rate 3 but not until 5 hours at rate 2 (Saturday) had been achieved. (Time Systems Ltd. 2007) The biometric system offers a “live” onscreen presentation of all staff that are currently available onsite. The system constantly updates itself showing who is available and who is not. Further, the names of people that are displayed on the screen are completely customizable, enabling Waiters on Wheels the option of restricting the live display to drivers only. The display will show which driver came when. This is important as it assures that drivers will work on a turn basis. This will also guarantee that the drivers are selected in order and not at a random basis, insuring that all drivers are given equal opportunity to deliver. This is extremely important given that drivers will be paid a base salary plus a commission based on number of deliveries made. This is intended to maximize productivity and extract the full possible potential of all available drivers. The biometric system also allows for data to be polled over the internet thus allowing all restaurants the ability to view this display as well. P a g e | 13 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
(Time Systems Ltd. 2007) Amongst the features of the biometric system will be a safety function called the Fire Report function. With staff going in and out of the office with such frequency it would be hard to keep track of all those in the office at the time of an emergency. The Fire Report is an "as it happens" listing of the employee's/drivers time transactions sent to hard copy. The report lists in real time the names and status of the employees along with the date and time of each transaction. The printer is to be strategically placed at the exit to enable a headcount in the event of sudden forced evacuation
(Time Systems Ltd. 2007) Each operator will be given one workstation. The operators will key in data which will be sent to the server and automatically be added and stored in its database. When a customer calls the caller switchboard system it will automatically rout the call and the callers‟ number to a free operator. The operator will enter the number into the server which will check for the number in its database. If the number is identified it will enter the operators directly into the customer‟s account. If the number isn‟t identified the operator will ask the caller whether or not he/she has used Waiters on Wheels’ service before. If he/she has he/she will be asked to provide the contact number he/she provided previously. The operator will then key in the number and the caller details will be searched in the servers‟ database and his/her account will be entered into. If this P a g e | 14 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
is the customers first time he/she will first provide his/her zip code. If it is within the delivery distance the operator will then proceed to take down the customer full address, contact numbers and email. If not the operator apologizes and the order stops there. Once keyed into the system database the system will generate an account. Once a customer‟s contact particulars are confirmed and saved an email will be auto-generated and sent by the server giving him/her an account that he/she may use should he/she choose to order online. Once a user is added to the database the operator will enter his/her account and place an order for him from there. The customer can therefore proceed to state his/her order. If the customer knows what he/she requires he/she can state their order directly. If the customer is unaware of his choices the operator will guide them through the menu telling them what types of restaurants and foods are available. The customer will be given two payment options; credit card or cash on delivery. As the customer makes his/her selections the operators will enter the data. The software allows for data selection/order recording via drop down menus reducing the chances of any errors. Once the order is complete the server will generate a confirmation page fully stating/displaying the customer‟s order and its cost. The operator will confirm to the customer the order made and its cost. If the customer acknowledges and confirms the order, the order will sent for further processing. On confirmation the order will be added to the respective tables in the database. The server will now generate a temporary order table in its database with all the aforementioned data. The server uses the data in the table to generate an email which will be sent to the customers email account and to the restaurant. On starting to process the order the restaurant will confirm commencement of the order processes by updating to the temporary order table. Updating the temporary order table will result in the server generating an invoice that will be sent to the restaurant as well as the driver‟s workstation. The invoice will show up on the drivers screen alerting the driver whose turn it is next to be ready to move to pick up a delivery from that specific restaurant. The invoice will list: 1. Name of Restaurant producing meal 2. Meal details 3. Customer details 4. Customer order time 5. Payment method The restaurant will use Skype software to communicate to the driver workstation. The restaurant will inform the driver to arrive at the restaurant before a specific time to pick up the order within a specified period. An example of the invoice is shown below P a g e | 15 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
When the driver arrives at the restaurant his ID will be entered into the invoice. The invoice will now be printed out. The driver will be handed order plus the three invoices. He will sign one and return it. This is the restaurant‟s proof of having dispensed their responsibility in full. The driver will now take the food and the two remaining invoices. The driver will now go to the customer ask him to sign on an invoice and drop off his food. The driver will also leave the blank invoice with the customer. The driver will now take the invoice (and money, if any and drop it off) at the accounts department. The accountant will file away the invoice and will mark the order in the database as having being delivered. The server system will also grant each restaurant limited access into the details of its menu. In the eventuality that a food item listed on the menu runs out, the concerned restaurant will be allowed to update the database, allowing all those accessing the restaurant menu that the particular food item is currently no longer available. This will help prevent the inconvenience, lost time and resources associated with having to rectify an unavailable order.
Owners Workstation: It should be noted that the Owner‟s workstation, unlike those of the rest of the staff will function on the Windows Operating System. This has been done primarily because the biometric system is dependent on the Windows platform. Further, giving the owners windows will give them greater flexibility to install and use any other software that they might want to use. A perk earned by virtue of them being company owners! MYSQL will be installed on the owners system so that a backup of all database P a g e | 16 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
entries can be made. We will need to install Panda Internet Security on the owner‟s workstation as Windows is very susceptible to viruses and other intrusive software. Skype is freeware software that will be installed on all workstations. It will help minimize the company‟s dependence on the telephone. It will be used to maintain contact with the restaurants.
Staff Workstations: Staff systems, though originally bundled with MS Windows Vista, will be formatted to run on Linux Mandriva system. This step has been taken in the interests of ultimate system stability. Linux is far more reliable then Windows and is not susceptible to viruses. Another benefit to running Linux software is that it minimizes software used to the bare required minimum. Staff will not be able to sidetrack from their intended purpose with frivolous distractions.
Server: The server will function both as the webhosting entity as well as company database. Additionally all data sent and received from owners, restaurants, customers and company staff will be routed via the server. The server therefore forms the very backbone of the new system. This in mind we direly needed the most stable, no frills, most bloatware-free Operating System possible. This is why FreeBSD was selected as the OS of choice. It is based on the highly regarded, very stable Unix Operating System. Some measure of just how reliable Unix-based operating systems are can be gleaned from the fact that Microsoft uses it for its highly critical Hotmail mail services even though Microsoft has its own server Operating Systems! Yahoo, another huge service provider also functions on the FreeBSD operating system. For the purposes of webhosting we selected Apache, again for the same attributes that made FreeBSD an attractive choice; minimal size and exceptional stability. Some 80% of the worlds web servers function on this software. Apache is a module based software, meaning that features can be chosen and added strictly on a per need basis. Its small size means that it is also extremely fast. PHP will also be used, both for its scripting abilities and its capacity to support the dynamic web pages required by Waiters on Wheels’ ordering system. Finally, also required to support the servers webhosting capabilities is Mambo, a software that will aid in web design and data management. MYSQL will be the Database software of choice. Just like the other software used on the server, MYSQL is an open-source software. As such it offers all the same benefits, unmatched stability, minimal size and zero procurement cost!
P a g e | 17 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Services Utilized For the purposes of credit cards deductions we will enlist the service of Merchant Account system instead of the more commonly used pay pal system. We chose Merchant Accounts services over that of PayPal for several reasons. The main reasons were: 1. Security of having money transferred into own account rather than PayPal accounts 2. That PayPal isn‟t a banking institution and doesn‟t adhere to banking regulations. PayPal can and has frozen its customers accounts without valid reason 3. PayPal is well known for its malpractices. The San Francisco Chronicle once printed an article in which it quoted the number of formally lodged complaints by PayPal customers as having exceeded 100,000. Many lawsuits have been filed, several are pending and some have already been dealt with. Several internet sites maintain detailed records of PayPal‟s many malpractices. One of the more famous ones is www.paypalsucks.com 4. Merchant Account offers far better rates then PayPal and has received accolades for the quality of its service. It should be understood that the new system will be highly intuitive and will only require minimal computer knowledge to accomplish. Most of the work will actually be done by computers leaving very little for the staff to worry about. Operators will be expected to perform little, other then take calls and fill out forms. The accountant for the most part will only have to confirm orders delivered to the server database and receive incoming cash from the drivers. All information pertaining to staff wages and overheads owned will automatically be calculated and auto generated/printed by the system at preset intervals. Drivers will no longer waste time in between jobs. With a base salary plus bonus salary in place the drivers will aspire to perform the most they can in the least possible time. The owners involvement in the company has now been restricted to that of simple management. They will from time to time keep tabs on the staff to make sure that the staffs are doing what is expected of them. They will also be able to double check any accounts to make sure that company finances are not being mismanaged.
P a g e | 18 Asia Pacific Institute of Information Technology
Systems Analysis and Design
3.
Waiters on Wheels
Operational feasibility
An important test required as part of a viability study for any business initiative is the assessment of how successfully a proposed system solves the business‟s problems or takes advantage of available business opportunities. This test is known as an operational feasibility study. To help us asses our system we will use an operational feasibility approach known as the PIECES Framework. The PIECES Framework might be described as being a best practice development initiative that allows us a way to understand and enhance a system. P.I.E.C.E.S. provides a systematic diagnostic approach and offers a practical tool towards team problem solving. In short it is a checklist for identifying problems for both existing and intended systems. P
- Performance
I
- Information
E
- Economy
C
- Control
E
- Efficiency
S
- Services
Performance
Throughput: In terms of data processing capability the existing system is far, far behind. Its‟ entire processing system being manual and dependant on novice inexperienced staff, the current system is highly limited in its processing capabilities. Orders are mismanaged, deposit slips are only calculated at the end of the day, and restaurant payments are not calculated more than once a week. The new system on the other hand will assure that information can and is processed rapidly in real time allowing for reports to be compiled and displayed at the press of a button. Printout orders can be given at anytime and at any stage all information displayed/printed will be current up to that moment. Finally the server will auto-generate end of day deposit slips, weekly restaurant payments due and weekly sales statistics at prespecified intervals.
Response: The existing systems response time is severely hindered by its unstructured, entirely manual processing and largely novice staff. Responses to issues are slow if at all and are more often than not P a g e | 19
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
prone to error. The new system will be able to give real time responses; the only bottleneck involved is human related and that is very limited indeed. Information (and Data)
Output: In terms of information output the current system is very ineffective. It is not even able to maintain tabs and provide up-to-date information on the status its drivers who perform the core function of the Waiters on Wheels delivery service. Additionally because contact between restaurant and Waiters on Wheels is not as fluid as should be, information/data output is not updated to the operators as and when required leading to orders that cannot be processed. The proposed system will address all these issues and then some. Not only will driver availability be monitored but that of the remaining staff as well. The system will introduce new measures to insure that drivers deliver with minimal time delay. All information gathered on staff will be automatically processed to calculate employee wages due. Reports as to status of all staff will be monitored and be made available as hardcopy in real time for safety reasons.
The database will provide output resulting in customers being greeted by operators by their name (if the customer calls from a number previously provided). Customers issued preferred customer cards on the basis of repeat buying encouraging loyalty. Item availability will now be updated in real time. Finally, most importantly perhaps is that errors in output will all but be done away with.
Input: The old system is unable to differentiate an old customer from a new one leading to lengthy recapture again and again. Not only is this redundant data capture a waste of time but it also causes needless frustration to the customer. Also currently there is no real filtration system to sift those whom we can serve to those whose location makes service prohibitive. The proposed system will save all information on a database and will bring up all information to the operators screen when required. Operators will not longer have to take down information repeatedly. The switchboard system will send data to the server and if the number is an existing one the relevant customer account will automatically be opened.
Stored Data: Currently the existing data is stored in ledgers for temporary reference and are discarded once the ledgers fill up. Due to disorganization data is therefore neither available for long nor easily accessible for later use even if available! Using the new system data will be set into databases and will be able to be brought up with zero time delay. Additionally data can now be saved for later reference. It is P a g e | 20
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
quite conceivable that data stored from a couple years prior be brought back up with a couple of keystrokes! Economics
Costs: While our existing system may have cost very little to setup it has since more then made up by generating large overheads in form of labour intensiveness and inefficiencies. Interestingly enough, while labour intensiveness is quite easily measured, the main source of company overheads, inefficiencies in the system are not quite as easily measured. With the new system in place we expect to see a reduction in overheads by a decrease in the size of staff required. We also expect significant changes in costs as a consequence of significant inefficiency reduction. This reduction might come about as a result of error reduction, increased activity speeds, better company flexibility and manageability. Only one person will have to handle accounts down from the current of five.
Profits: With the current system stretched to its absolute limit increased revenue from greater sales volume is pretty much out the window. The system as is cannot adequately handle the current load being placed on it so greater market share is not going to increase profits. The law of diminishing marginal returns has solidly set in. The proposed system on the other hand offers scope for massive sales volume expansion. With the more efficient system in place Waiters on Wheels can now look forward to increasing sales revenues while cutting down on costs all the while. Further marketing might even be considered to aid Waiters on Wheels make use of its new found capacity! All this will be attained in the face of reduced cost thereby increasing profitability. Control
Waiters on Wheels like most other business concerns is a profit making endeavour. For it to function it is necessary that crimes such as embezzlement not be allowed to happen. The existing system is very lax in terms of maintaining records. Currently it would be very easy for staff particularly those working in the accounts to siphon off an amount for there own benefit. The new system maintains a very close watch on all concerned making any such activity very difficult if not near nigh impossible. All data is being backed up on the owner‟s workstation allowing them to keep a sharp eye on company finances. Also invoices clearly state whether orders are card based or COD minimizing risks of drivers mishandling cash.
P a g e | 21 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
To prevent customer data being sold off to third party companies Waiters on Wheels intended database capabilities will not be left open to the entire staff. Staff will be given limited control over how much they can access the database. Only the owners will have complete access rights. Currently it is conceivable that a member of staff might gather and sell off customer information to another company.
Since the entire process is very controlled from start to finish the chances of decision making errors in the new system are pretty non existent compared to the preceding system. The old system stretched as it was to it‟s limits meant that staff had to improvise to manage orders, effectively taking orders into their own hands Efficiency
Time wastage: Under the current scheme of things a whole of data is redundantly inputted again and again because there is no way to quickly look up and renew existing customer information logs. Time is further wasted looking for available drivers. A lot of time is wasted training new employees. The workload, being as it is over and above what the current system can manage results in a great deal of time wastage as some staff might be called in to help other staff members thereby causing them to neglect their own original job duties. The work process is completely unsynchronized and works more on improvised basis rather than any structured, orderly format. With the onset of the new system we expect all this to change. Driver availability, indeed the whereabouts of all staff and their work hours will be noted. Drivers will be provided incentive to minimize time delay. Data will be able to be called up repeatedly with minimal time delay allowing for faster order taking and processing. The new system will enable Waiters on Wheels to select one of two options. To cut back on overheads by reducing now redundant staff or to expand operations and sales volume even further.
Material wastage: In today‟s fast paced cut throat world of business cutting down on even the most mundane of expenses can result in greater profit margins. This being the case, the new system should see space, time, and money currently devoted to filling in and managing ledgers cut down greatly if not entirely. This should result in less money wasted on procuring bulky ledgers that will be filed away, eat away at precious office square footage without being utilized and then finally be discarded for a new wave of ledgers!
P a g e | 22 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Service Waiters on Wheels current system, as repeatedly emphasized earlier, is in utter shambles making for disastrous consequences. The system as is consistently results in wrong, displaced and delayed deliveries. There is currently no sequence for deliveries meaning that a customer might get his order within a half hour or maybe after three depending on his luck that day! All in all this bodes poorly for Waiters on Wheels brand image and clientele loyalty. The problems do not unfortunately end here. Given the very high staff turnover, at any time there is always someone of the old staff who is training a raw recruit how to handle the ropes in the company. Given inefficiencies staff might be required to master handling more then one job at one time. This leads to two major problems. A dissatisfied, poorly functioning, highly strained staff in general or experienced staff that are being prevented from handling their duties cause they are too busy teaching new recruits how to handle their jobs. Further complicating matters is the current lack of structure with current operations. How can staff be expected to provide their fullest if the job they are doing is in itself not clearly defined?! A synchronized, smoothly operating service is currently far, far away and this, as well might be expected, has serious consequences on the quality of services rendered. The new system was designed with the aim of rectifying all of the fore mentioned. We foresee the new system as being the one stop solution for repairing most if not all of the current systems‟ pitfalls. All calculations and data management will now be taken over by machines thus reducing human interference. Reduced human involvement will result in far more faster data processing with no errors (pending input data accuracy). As much as possible human involvement has now been done away with, reducing employment overheads and freeing human involvement for utilization in other processes. Benefits of the new system will also make their appearance with the presence of a more motivated, better functioning, harder working staff. Staff will now work harder for several reasons. Greater job satisfaction, better knowledge of what exactly is expected of them and the knowledge that they will either be held accountable or be rewarded depending on the efforts they put in. We expect far less staff turnover, and jobs that will be far more intuitive, easier to accomplish and require less training.
P a g e | 23 Asia Pacific Institute of Information Technology
Systems Analysis and Design
4.
Waiters on Wheels
Economic Feasibility
The analysis and justification of any venture or project from its economic viewpoint is known as economic feasibility. For any venture to be prove itself economically viable, its aggregate costs must be superseded by its aggregate benefits. It is not possible for the economic feasibility to contain all costs and benefits. There will always be hidden costs and benefits that will not show until the system is functioning and in place. However, a consecrated effort must be made to weigh all positives and negatives so as to attain an approximate outcome that will enable us to decide whether or not a system is doable or not. Costs: There are several main types of costs that we will have to account for. This may include but is not restricted to: 1. Fixed Costs 2. Variable Costs 3. Tangible Costs 4. Intangible Costs 5. Direct Costs 6. Indirect Costs Benefits: Benefits from a new project may include many things. Almost all things will have a direct or indirect bearing in increasing company profitability. Potentials benefits of the new system include slashed overheads, cost avoidance and reduction, error reduction, increased flexibility, superior control and manageability and finally new markets and sales opportunities. There may also be social benefits and reduction of social costs. This though directly not responsible for bringing in benefits will benefit society as a whole, plus the company can use the reduction in social costs as a marketing tool to increase and cement ties with potential clientele. To access the benefits gained from this new system we will be using three different types of Benefit Analysis; Namely: 1. Payback Analysis: Used to access how long it will take to earn back the money you'll spend on the project P a g e | 24 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
2. Present Value Analysis: This might be described as being the return of the original investment plus a commensurate profit 3. Return on Investment (ROI) Analysis: Monetary benefits derived from having spent money on developing or revising a system Breakdown of estimated costs: Development costs Personnel We estimate the project to run a length of one month. The fees payable to each member of the working staff for the one month tenure of the project is shown below: Project Manager System Analyst Programmer Total Chargeable
$7500 $5500 $4500 $17,500
Hardware: Server Owners Workstation Staff Workstations $500(x 12) Biometric System Network Laser Printer Dot Matrix Printer Operator Headsets (x11) Microphone (x2) Driver Room Speakers Total Charge
$7974 $1140 $6000 $820 $625 $700 $110 $30 $5 $17,404
Software FreeBSD Apache PHP Mambo MYSQL Mandriva Windows Vista
$0 $0 $0 $0 $0 $0 System OS $0 P a g e | 25
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Panda Internet Security Payroll Software Skype Total Charge
Waiters on Wheels
$70 $0 $0 $70
One time Staff Training
$3000
Annual Operating Costs: Credit Card debit facility Maintenance and Help Line Total
$300 $6000 $6300
Development Cost: $37,974 Annual Operational Cost: $6300 Projected System Life: 10 years Year Development Cost 1 $37,974 2 3 4 5 6 7 8 9 10
Operational Costs $0 $6,300 $6,300 $6,300 $6,300 $6,300 $6,300 $6,300 $6,300
Cumulative Cost
Benefits
$37,974 $44,274 $50,574 $56,874 $63,174 $69,474 $75,774 $82,074 $88,374 $94,674
$0 $20,000 $25,000 $30,000 $35,000 $40,000 $45,000 $50,000 $55,000 $60,000
Cumulative Benefits $0 $20,000 $45,000 $75,000 $110,000 $150,000 $195,000 $245,000 $300,000 $360,000
Year four highlighted in Blue is the anticipated break-even year.
Payback Analysis: Cumulative Benefit – Cumulative Cost Therefore
360,000
-
94,674
=
$265,326
Return on Investment (ROI): {(Total Benefit – Total Cost) / Total Cost} x 100 Therefore:
265,326/94,674 x 100 = 280.25%
P a g e | 26 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Break Even Diagram
Present Value Analysis: Year 1 Benefit $0 Present Value 10% 1 Present $0 Value Costs $37,974 Present Value 10% 1 Present $37,974 Value
Year 2 Year 3 Year 4 Year 5 Year 6 Year 7 Year 8 Year 9 Year 10 $20,000 $45,000 $75,000 $110,000 $150,000 $195,000 $245,000 $300,000 $360,000
0.826 0.751 0.683 0.621 0.564 0.513 0.467 0.424 0.386 $16,520 $33,795 $51,225 $68,310 $84,600 $100,035 $114,415 $127,200 $138,960 $44,274 $50,574 $56,874 $63,174
$69,474
$75,774
$82,074
$88,374
$94,674
0.826 0.751 0.683 0.621 $36,570 $37,981 $38,845 $39,231
0.564 $39,183
0.513 $38,872
0.467 $38,329
0.424 $37,471
0.386 $36,544
P a g e | 27 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Selection of methodologies Comparison of methodologies Many organizations find that it is useful to use a standard set of steps, called a system development methodology to conduct all the procedures necessary to analyze, design, implement, and maintain information systems. The main focus is to develop and support their information system. Among the methodologies that will be discussed in this report are:
a. System Development Life Cycle (SDLC) b. Object-Oriented Analysis and Design (OOAD) c. Structured System Analysis and Design ( SSADM) d. Rapid Application Development (RAD)
A. System Development Life Cycle (SDLC) The most common methodology used in system development is System Development Life Cycle (SDLC), featuring several phases from progress of the system analysis and design effort. These phases of SDLC are:
i.
Project identification and selection The first phase of the SDLC in which an organization's information system needs are identified, analyzed, prioritized, and arranged.
ii.
Project initiation and planning The second phase of the SDLC in which a potential information systems project is explained and an argument for continuing with the project is presented ; a detailed conducting the remaining phases of the SDLC for the proposed system.
P a g e | 28 Asia Pacific Institute of Information Technology
Systems Analysis and Design
iii.
Waiters on Wheels
Analysis The third phase of the SDLC in which the current system is studied and an alternative replacement system is proposed.
iv.
Logical design The fourth phase of the SDLC in which all functional features of the system chosen for development in the analysis stage are described independently of any computer platform.
v.
Physical design The fifth phase of the SDLC in which the logical specifications of the system from logical design are transformed into technology-specific details from which all programming and system construction can be accomplished.
vi.
Implementation The sixth phase of the SDLC in which the information system is coded, tested, installed, and supported in the organization.
vii.
Maintenance The final phase of the SDLC in which an information system is systematically repaired and improved.
B.
OBJECT-ORIENTED ANALYSIS AND DESIGN (OOAD) Object-oriented analysis and design (OOAD) is a system development methodologies and techniques based on objects rather than data or process. It combines both data and processes (call method) into single entities called object.
i.
Object A structure that encapsulates (or packages) attributes and methods that operate on those attributes. An object is an abstraction of a real-world thing in which data and processes are placed together to model the structure and behavior of the real-world object.
P a g e | 29 Asia Pacific Institute of Information Technology
Systems Analysis and Design
ii.
Waiters on Wheels
Inheritance The property that occurs when entity types or object classes are arranged in a hierarchy and each entity types or object class assumes the attributes and method on its ancestors ; that is, those higher up in the hierarchy. Inheritance allows new but related classes to be derived from existing classes.
iii.
Object class A logical grouping of objects that have the same (or similar) attributes and behaviors (methods).
C.
STRUCTED SYSTEM ANALYSIS AND DESIGN ( SSADM) The methodologies are mainly from the SDLC (System Development Life Cycle). There are two parts which we going to focus on. First is SSADM (Structured System Analysis and Design) and RAD (Rapid Application Development). SSADM and RAD are methodologies which are widely used in this system analysis and design.
SSADM is a methodology which is part of SDLC . It is procedural and documentations standards for systems development. Systematic approach to the analysis and design of IT (Information Technology) applications. This methodology is commonly used in the UK (United Kingdom).SSADM covers system analysis and design which is not include or does not cover project management or quality assurance. SSADM does not attempt to cover information strategy planning or Construction, testing and implementation of the eventual system . SSADM Is a kind of technique used to meet the needs of the practitioner which defines functional and information requirements. The fundamental principle of SSADM is that the system belongs to users and hence their participation in the development process is essential.
SSADM has its own characteristic. It used for requirement specification, system design and structures a project into smaller well defined activities. It also used diagrams and other modeling techniques. Specifies the sequence and interaction of these activities. SSADM can easily be understood by both users and developers.
SSADM has many different components. Structures is a component which define the framework of activities, steps and stages and their input and outputs. Technique is to define how the activities are P a g e | 30 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
performed and documentation is where it define how the products of the activities, steps and stages are presented.
SSADM is Structured in 5 main part: i.
Feasibility study
ii.
Requirement analysis
iii.
Requirement specification
iv.
Logical system specification
v.
Physical design
SSADM revolves around the use of three key techniques:
i.
Logical data modeling - process of identifying, modeling and documenting the data requirements of a business information system.
ii.
Data flow diagram - process on how data flow around a business information system.
iii.
Entity Event Modeling - process in the business events which affect each entity and the sequence in which these events occur.
D.
Rapid Application Development (RAD) Rapid application Development is a methodology used in developing information system which promises better and cheaper and more rapid deployment by having systems developers and end users work together to develop system. RAD was invented by James Martin and has 4 phases of RAD SDLC. As the RAD life cycle is shown on top, it‟s a part of SDLC which have shrunk into four phases. Originally Planning Formed by project identification and selection + Project initiation and planning. P a g e | 31
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Design is from combining Analysis and logical design. Development falls under Physical Design while Cutover Is implementation and Maintenance.
Components of RAD
System development methodologies are invented to radically minimize the time needed to design and implement information systems radically.
Five Key Factors: i.
Extensive user involvement
ii.
Joint Application design sessions (JAD)
iii.
Prototyping
iv.
Integrated CASE Tools
v.
Code generators.
RAD is a general strategy rather than a single Methodologies. RAD has its goals: i.
To analyze a business process rapidly
ii.
To design a viable solution through intense cooperation between users and developers
iii.
To get the complete application into the hands of the user quickly.
Traditional SDLC steps are followed, but phases are combined . Iteration is limited to design and development phases.
Components of RAD includes user involvement is the key to success. Prototyping is managed in sessions similar to Joint Application Design (JAD). Prototyping screens become screens within the production system. CASE tools are implemented to design the prototypes.
P a g e | 32 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Methodologies Applied Our project is currently following the SDLC (system development life cycle) which follows the SSADM (Structured System Analysis & Design). We are applying our project according to the 5 main listing of the of the methodologies:
i.
Feasibility study
ii.
Requirement analysis
iii.
Requirement specification
iv.
Logical system specification
v.
Physical design
RAD methodology was not applied because the methodologies is not efficient don't have the ability to make the correct decision. RAD can be created with radically decreases the time needed, but it will lower the overall quality of the system. The fast pace of RAD can result of missing information due to the growing business. RAD also lack of attention to later systems administration built into system. Overall, RAD is useful in a small and limit scope projects, not to a bigger and wider scope business.
Object-oriented is considered mainly involved 3 phases which is analysis, design and implementationsimilar to the SDLC. The model is created is abstract, focusing on the external qualities of the application system. This methodologies involved more to system architecture, data structure, and algorithm. Basically the system developer must generates the code and database access routine is defined by Hoffer, George, Valacich(1999) . OOAD techniques is based on objects rather than data and processes. So this makes the point where the OOAD is actually not a good methodologies to apply in creating a system.
So the conclusion of selection of methodologies is that SSADM is a better choice rather then RAD and OOAD. SDLC is main life cycle and can be applied for our project, but the SSADM meets what Waiters And Wheels demand. SSADM techniques are based on data and processes. In waiters on wheels, the main part is that they wanted to actually created a system to store data and show the processes clearly. This means SSADM is the right methodologies to select.
P a g e | 33 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Justification of selected methodology We have chosen the Structured System Analysis and Design (SSADM) as our system approach in our project progression due to several reasons. The primary reason for its selection is the fact that more emphasis are made toward the analysis of the user needs and the logical design proposal of the required system rather than to actually construct and maintain the eventual physical design of the system. This suits our project requirement as we are being progressively introduced to the elements of System Analysis and Design. Through this, one does not need to be an expert to produce the results of equal or yet better quality as that of other methods. SSADM is one of the simplest yet effective methods to learn and execute. As mentioned in the previous finding, SSADM revolves around the 3 key techniques which are Logical Data Modelling, Data Flow Diagram, and Entity Event Modelling. These techniques that were used in our project analysis stage gave a foundation to build our system on. It gives us a clear layout all the variables that is in the required system and how they are would interact with one another. This also enables us to identify what exactly the users want and suggest a design proposal before proceeding in developing the actual system and its specifications. Thus unwanted errors and unnecessary process halts due to mistakes can be avoided. Any chances or improvements that have to be made can be conveniently made here in the planning stage in order to satisfy the user‟s requirement. SSADM follows a systematic step-by-step procedure where every phase needs to be completed and analyzed carefully in detailed before proceeding to the next step of the project. This provides us with a strategic guideline on the proceedings of the project while ensuring each phase is done progressively without leaving any modules incomplete. It is required that every progress of the project be documented in an orderly fashion. This allows us to conveniently retrace our steps and make references if ever the need arises. By this, time and effort can also be conserved simply because there is no need for preparation of extra documentation for records. It is therefore safe to say SSADM is a self-documenting methodology that effectively saves the developer from doing additional paperwork.
P a g e | 34 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Breakdown of work associated with SSADM 1. Feasibility Study
thorough analysis of a business area to determine whether a system can cost effectively support the business requirement
includes :
Schedule analysis
Economic analysis
Technical analysis
Operational analysis
2. Requirement Analysis
identify the system requirement
model the current business environment
determine the processes and data structures in the system
3. Requirement Specification
identify detailed functional and non-functional requirements
develop new techniques to identify require processes and data structures
4. Logical System Specification
determine the selection of the technical system specifications
demonstrate the layout and functionality of the system
5. Physical Design
create physical database design and program specifications based on logical systems specifications and technical system specification
P a g e | 35 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Selection / Application of Investigation Techniques Questionnaires Personal Details Please place a tick ( √ ) where appropriate
Questionnaire Please circle or mark your selection
1. How often do you order out? a. b. c. d. e.
Less than once a month Once a month Every 2 weeks Every week Everyday
2. What variety of food do you normally order? (multiple selections are allowed) a. b. c. d. e.
Chinese food Indian food Japanese food Western food Other (please specify) __________________
P a g e | 36 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
3. If you plan to eat out, which service do u normally use to order your meals? (multiple selections are allowed)
a. b. c. d. e.
Eat in Take out Restaurant's delivery hotline Online ordering Other (please specify) _______________________
4. By which means is more convenient? a. b. c. d. e.
Eat in Take out Restaurant's delivery hotline Online ordering Other (please specify) _______________________
5. At which venue you like best to have your ordered meals? a. In the restaurant b. At home c. Other (please specify) _____________________________
6. What time of day do you order out? (multiple selections are allowed)
a. b. c. d. e.
Before 11am Between 11am and 2pm Between 2pm and 6pm Between 6pm and 10pm After 10pm
7. How many people do you normally order for? a. b. c. d.
Just 1 Less than 5 Less than 10 More than 10
8. What is your preferred mode of payment for the food delivered? a. b. c. d.
Cash Cheque Credit card Other (please specify)______________________________________ P a g e | 37
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
9. How would you rate the ordering system of your local restaurant when putting down your order? a. b. c. d.
Excellent Good Fair Poor
10. How far do you live from your local restaurant? a. Within 1km b. 1km to 5km c. 5km to 10km d. Over 10km
11. How long does it normally take for your meals to be delivered? a. b. c. d.
Within 15 minutes Within 30 minutes Within an hour More than an hour
12. How much extra does your local restaurant charge u for its delivery service? a. b. c. d.
RM3 and below RM5 and below RM10 and below Above RM10
13. Are you satisfied with the meals that are delivered to you by your local restaurant? a. Yes b. No (please state reason below) _____________________________________________________ 14. How would you rate the delivery service of your local restaurant? a. b. c. d.
Excellent Good Fair Poor
P a g e | 38 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
15. What major improvement(s) would you want to see in the delivery service? (multiple selections are allowed) a. b. c. d. e. f.
Quicker delivery Better quality food Better ordering system More reasonable delivery charges None. The delivery service is perfect Other (please specify) __________________________________________________________
16. Extra comments: ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Signature: __________________________ ( )
P a g e | 39 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Interview Interviewee: Mishantan (Manager[All star] of Pizza hut Megamall pacific, Penang) Interviewer: Prakash a/l Arichnam Date: 1st May 2007 Time: 11.30am
1. What are the rules & regulations of your restaurant's delivery process? It's simple. We follow our normal routine of handling customer via telephone. Basically we don't have tighter rules or regulations. We just follow standard rules of delivery process 2. How do you cope with the busy schedule of peak hours? We have 3 drivers and standby operators ( maybe 3 or 4). The calls are handled by them and drivers will reached their destination within the time limits. 3. Do your drivers deliver multiple orders on a single trip? Depending on the quantity of the orders. If there are customers from the same city area order in small quantities at the same time, we would have a driver deliver the food to them in a single trip. Otherwise, we would just send one order at a time. 4. Does your restaurant uses any system that allocates delivery task to any available drivers? We do not have a system which allocates these task or checks drivers‟ availability. We just receive the orders from the customer, pack them and send them to any available drivers. There is no schedule to check available drivers, we just send to whoever is available. 5. How orders are made? If possible show how the process works? Our main orders are taken via telephone. We do have our online webpage for Pizza hut which is www.pizzahut.com.my but it just explain briefly on what are the available foods. There's no online food ordering. In other ways is by drive thru, but it's not part of the delivery system. 5. If orders are too many thru telephone, how do you manage it? We have operators to manage it. Sometimes there will be only 1 or 2 operators, depends on the peak & of peak hours. 6. What will be the next step after customer made an order? The staff will prepare the food customer orders. Then they packed and sealed in a airtight box. On top of it, got a labeled with the customers identification, telephone number and also customer's ordered details. As soon as the staffs packed, it will then send to the drivers. They will then delivered the orders to the customer and collect the money. 7. The delivery amount & range is counted or not? We follow the standard of delivery amount which is above RM3. The range are stated in our delivery chart range. It‟s a chart which explains the furthest range they can go. If it‟s out of range, the operator will inform the customer or will suggest the other nearest Pizza hut shop. P a g e | 40 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
8. How do you handle prank calls and how does the system recognize it? Currently we don't have a system that recognizes prank calls but we do have our own solutions to handle the problem. Our callers will have their phone line id appeared in our system, if we get calls from outside the range, we just block the call. 9. If orders are late to delivered, any privileged given? We will give our special rebate or discount on the next order. The discount only will be available for dine-out only. 10. Any due time set for each order? We set a time range of 30 minute. If not we will give our discount or rebate coupon 11. If they orders are more than rm100 or greater, how is this kind of delivery take place We have a van to handle large orders. Mainly they ordered during reunion party, office staff retirement and so on. 12. How does online orders being processed? Currently we don't have any orders taken via online. Our main focus is mainly by telephone 13. How about the discounts, promotion hour or any free gift? Are they also being delivered? Discount or promotions are given under the term & conditions applied. 14. Any weekly or daily target fixed that need to achieve? Daily is about RM2000, weekly is ranged between RM10000-RM12000 15. How does the day-end collections are counted? As soon as the drivers collected the money, they will give the money to the person in charge of the delivery orders and receipt. They will counted and make a day -end collections at the end of the day together with the day-end collections for the dine-in. 16. If the system currently operating has a default or system jammed, how do you overcome the problem? We managed to use other nearby Pizza hut to help with our problems. But until now only once we had this system problem due to the phone connection failure. But it was functioning well in 1/2 hour.
~Questions carried out to the Area Manager and All star of Pizza hut~
P a g e | 41 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Summary of findings Based on the findings using questionnaires, we found out that many people still disagree or not satisfied with the delivery system and the restaurant's delivery hotline. When we make this random questions handout to several people, we get to gather some valuable information about the system. Some of them comment on the late delivery and the restaurant delivery hotline is always busy or unattended. Some even comment about the food, where when it is delivered it is not hot and fresh.
The take-away and dine in is the most preferred. This is because the service is good and the food is served hot and fresh. They don't prefer delivery service because the drivers are normally late and rude. The distance of one randomly selected people home from the restaurant is within 1 km but the driver takes about 30-40 minutes to reach the customer home. This does make sense that the delivery service is poor and need to upgrade to even fast and quicker delivery. There is a minor group who complains that they can‟t order thru online because of limited restaurant have the access to make online ordering. They also have hassle to have two or more item order because they need to call and list their order in different restaurant. This is actually making the people waiting for so long plus need to make many calls to different restaurant. This minority also prefer to have online ordering that can make orders to many restaurant in just 1 click. This makes them hassle-free and can order different types of food at once.
So we can conclude that people prefers to have a better quality food, better ordering system, quicker delivery and also more reasonable delivery charges. The public opinion we receive is under our project to create a better system. This makes our findings relevant with what our project aim is.
P a g e | 42 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Logical Design
P a g e | 43 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
CONTEXT DIAGRAM •
A data flow diagram (DFD) of the scope of an organizational system that shows the system boundaries, external entities that interact with the system and the major information flows between the entities and the system.
•
is a top-level view of the information system
•
has one process symbol representing the entire information system
•
has the external entities around the perimeter of the page
•
use data flow to connect the external entities with the process
•
do not show data store
GOAL Context diagram is shown to view a simple and top level view of information system and entities. It is easy to understand and not so complicated.
Process Flow The process is mainly the Food delivery management system where customer, drivers, restaurant, accounts department are the entities. Firstly customer give in registration details, login-password and makes order to the food delivery system. In other hand, the system will produce receipt to the customer in return. Second entity is the restaurant, where it receives the food order from the system and will send an order status to the system. Third entity is the drivers, which they will receive the delivery request from the system and they will sent a delivery status back to the system. The last entity is the accounting department where the system will sent a financial report to the accounts department.
P a g e | 44 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
P a g e | 45 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
P a g e | 46 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
DATA FLOW DIAGRAM LEVEL 0 & 1 (DFD L0 & L1) Data flow diagram is a versatile diagramming tool. With four symbols, we can use data flow diagram to represent the both physical and logical event. DFD Lo is also known as child diagram which is exploded from parent diagram, DFD L1 GOAL DFD is a basically shows the connection between inside and outside the business unit. The whole data flow diagram are drawn to ease the user and others to see how each process is done and what are the input and outputs involved. The diagram is levelled and well balanced throughout the diagram. Process Flow We begin the process with the child diagram or the DFD L0. The customer begins as a source by login and password. Then the process 1 starts to check the customer‟s account by referring the customer table which is P a g e | 47 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
a data store. If customer registers for the fist time, then the registration details is then sent to customer table via update customer master process. Process 3 start when customer orders food by telephone or thru the net. The item is then refers to the food table which is a data store. Later the list of ordered items then refers to the order table (data store). Process 4, generates order send formatted food orders to the restaurant (source). Process 5 update order status in order table and after order completed is then proceed to the process 6 which is informing the driver. Driver id is done by the drivers table (data store) and the driver is the source. The driver takes the receipt and the food delivered to the customers and report, where process 7 begins. Financial report plus the invoices are then sent to the accounting department. DFD L1- is actually the explode part of the DFD L0. There is 3 different process is being explode. Process 3.0 is 1 part that explode where orders, customers ID, item id is sent to process3.1 which is select food item from menu. The selected item is then progressed to process 3.2 which is Add food item to list. In this process, list of ordered item is then sent to the restaurant, if not there is add more selection option which is sent to process 3.1. Process 6 is exploded in into process 6.1 and process 6.2. The drivers ID is sent to the process 6.1 which is identify free driver. When a free driver is available and is alerted, process 6.2 begins which is Generate delivery request. In this process, complete order information is receive and delivery request will take place. Process 7 is then exploded in to process 7.1, 7.2 and 7.3. Process 7.1 which is generates receipt actually receive order details and generates receipt to the customer. The driver then returns the receipt in process 7.2 which is generates financial report. After receiving the receipt and match the order details, it is then sent to the financial report. Process 7.3 is move temporary order table, which has a temporary order list or table stored in an order history database.
P a g e | 48 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
DATA FLOW DIAGRAM LEVEL 0 & 1 (DFD L0 & L1) Data flow diagram is a versatile diagramming tool. With four symbols, we can use data flow diagram to represent the both physical and logical event. DFD Lo is also known as child diagram which is exploded from parent diagram, DFD L1 GOAL DFD is a basically shows the connection between inside and outside the business unit. The whole data flow diagram are drawn to ease the user and others to see how each process is done and what are the input and outputs involved. The diagram is levelled and well balanced throughout the diagram. Process Flow We begin the process with the child diagram or the DFD L0. The customer begins as a source by login and password. Then the process 1 starts to check the customers account by referring the customer table which is a data store. If customer registers for the fist time, then the registration details is then sent to customer table via update customer master process. Process 3 start when customer orders food by telephone or thru the net. The item is then refers to the food table which is a data store. Later the list of ordered items then refers to the order table (data store). Process 4, generates order send formatted food orders to the restaurant (source). P a g e | 49 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Process 5 update order status in order table and after order completed is then proceed to the process 6 which is informing the driver. Driver id is done by the drivers table (data store) and the driver is the source. The driver takes the receipt and the food delivered to the customers and report, where process 7 begins. Financial report plus the invoices are then sent to the accounting department. DFD L1- is actually the explode part of the DFD L0. There is 3 different process is being explode. Process 3.0 is 1 part that explode where orders, customers ID, item id is sent to process3.1 which is select food item from menu. The selected item is then progressed to process 3.2 which is Add food item to list. In this process, list of ordered item is then sent to the restaurant, if not there is add more selection option which is sent to process 3.1. Process 6 is exploded in into process 6.1 and process 6.2. The drivers ID is sent to the process 6.1 which is identify free driver. When a free driver is available and is alerted, process 6.2 begins which is Generate delivery request. In this process, complete order information is receive and delivery request will take place. Process 7 is then exploded in to process 7.1, 7.2 and 7.3. Process 7.1 which is generates receipt actually receive order details and generates receipt to the customer. The driver then returns the receipt in process 7.2 which is generates financial report. After receiving the receipt and match the order details, it is then sent to the financial report. Process 7.3 is move temporary order table, which has a temporary order list or table stored in an order history database.
P a g e | 50 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
P a g e | 51 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
ENTITY LIFE HISTORY (ELH)
ELH is a diagrammatic technique that provides of all possible biographies for any occurrence of a particular entity in the system. An entity is created-amended-deleted. This 3 process is involved in this whole Entity Life History. GOAL To create an Entity which can be clearly viewed the diagram. The process will have and complete flow form the entity creation, entity modification till entity deletion. This data wil much easily understood by user.
Process Flow Initial identification of events, Constructing the Event / Entity Matrix, Drawing initial Entity Life Histories for all entities, Completion of the Entity Life Histories, Addition of operations, Addition of state indicators. This 6 process is what involved in this ELH. Firstly the events need to be identified. For example like customer‟s event is to log on, placing orders and so on. Secondly is to construct the event and entity. This is the part where we start to list out the entity and also the event. Thirdly, draw initial ELH for all entities. Now the process of drawing the flow chart begins. Completion of the entity comes in next where all the lines are placed or arranged in a proper way. Addition of operation plus the addition of state indicators and the last step involved in this ELH where the process is completed with the symbol of (“0” “*” “1”). The process begins with customers. Customer is the entity involved and the events are Log on, new account registration, order, customer can modify these events by changing the food item and the registration part. Events are then deleted at the end of the event, such as account deletion and food orders are canceled. Second entity involved is the driver and the events are delivery request, receipt, amount and extra charges, delivery status report. Third entity involved is Restaurant and the events are orders request, food preparation, invoices issued. The second event which is the food preparation can take place 0 or many times.
P a g e | 52 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
USE CASE DIAGRAM (UCD) UCD is a process of modelling a system‟s functions from the perspective of external users using a tool called use cases. GOAL The main thing is to help identify objects and their high-level relationships and responsibilities. It is also an effective communication tool and as a basic for a test plan or user‟s manual. P a g e | 53 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Process Flow To begin with the Use Case Diagram, firstly need to identify any additional actors and Use Cases. This can be reviewed in the context model diagram. Secondly construct a Use Case Model. This model is consists of two symbols- the actor and the Use Case symbols (oval shape). Thirdly Document the Use Case Course of event. This is a basic documentation where requirement Use Case is applied. Fourthly define the analysis Use case. Once the requirement is complete, the analyze process begin in which will specify how or implementation specified. The actors are Customers, Telephone operator, Restaurant worker, Driver, Manager. The customer begins with the online order food and then generates food orders to the restaurant worker. The person then inform driver to pick up the order. The driver will then deliver the food to the customer with receipt. Drivers report back to produce management reports, they hand in the day end receipt. Customers can also orders thru the Telephone Operator. The operator then order food via online and generates food orders to the restaurant worker and the process goes on.
P a g e | 54 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
CLASS DIAGRAM Class diagram depict the system‟s object structure. They show object classes that the system is composed of as well as the relationship between those object class as defined by Whitten (2001). GOAL The object the class is said to be persistent if it outlives the execution of the program. This means the object the class describe will be stored in a database. It also shows what classes of objects are required without P a g e | 55 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
showing how the objects might be implemented or how the user might interact with them. This means that user will get a clearer view by looking at the diagram on how the system related together. Process Flow The process of class diagram consists of 3 steps- identify associations and Multiplicity, Identify Generalization relationship and aggregation relationship. Each class has 3 parts; name, attributes, Operations. The numbers and symbols representing cardinality/ multiplicity include a “1” for one and asterisk (*) for many. The process starts with customer where they can attribute and the operation will proceed. This class link to another class where many customers can make many orders. Orders can be made only 1 and that 1 order can have many food items. In that same time, another class is connected which is order and restaurant. Many orders can be taken but only 1 and only 1 restaurant can process at time. The restaurant which is 1 and only 1 can issue many invoices. Invoices are then send to 1 and only 1 driver the drivers can deliver many food but report at 1 and only 1. This is how the process flows.
P a g e | 56 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Physical design Webpage
The picture above is a screenshot of our proposed website. This is where customers are able to log in to make an online order. Specifically, the customers will be directed to this main menu of Waiters on Wheels the site address is entered. A more detailed explanation of the layout and functionality of each webpage in the site is described in the individual report of each member. (refer to „Individual Reports‟)
Database P a g e | 57 Asia Pacific Institute of Information Technology
Systems Analysis and Design
ORDER.table Order ITEM _ID _ID 007F2 99RE 4
Quant ity 1
CUSTOMER.table Customer_ID Name 070707C4
Mike
FOOD_ITEMS.table ITEM_ID 99RE 70FW
Amo unt 13
Tot al 13
Password
Custome r_ID 070707C 4
DESCRIPTION Baklava Mack_Burger
NAME Farzan
Addr ess addre ss
Teleph one 777777 7
Preparation_ Status Ready
Full_Name Last_Name Email
JKL90mike Mike
RESTAURANTS.table RESTAURANT_ID ADDRESS R90TR Address
DRIVERS.table DRIVER_ID DR9001
Waiters on Wheels
TEL_1 77432477
SURNAME Seri
REPORTS.table REPORT_ID ORDER_ID INVOICE_ID Date R9932123 007F24 IN555BN32 4.07.07
Romanson
Tim e 17: 04
Date 4.07. 07
Delivry Address Address
RESTAURANT_ID R90TR BR2M
SKYPE Arzu
EMAIL SCHEDULE
[email protected] 9:00-23:00
Home_ADDRESS HOME_TEL Address 77878237
Time 17:38
Tel_2
[email protected] 897732
PRICE 13 9
TEL_2 77432577
Tel_1
Delivery_S tatus Done
Mob_TEL 43253567
DRIVER_ID ITEMS_ID Quantity DR9001 99RE 1
CUSTOMER_ID 070707C4
The above diagram shows the proposed database table that would be used in the required system. The staff will be given access to view this database that will be updated constantly every minute. Every changes and updates will therefore be synchronised instantly and all staff members would be continuously notified. When an order is placed by a customer, the Order tab would be filled with the summary of the customers‟ order and particular details. The Customer, Food Items, Restaurant, and Drivers tab would then be automatically filled with the specific details from the Order tab. Once an order and delivery has been successfully made, the Reports tab would than summarize the status of the order and delivery.
P a g e | 58 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Appendix Technical Specifications HARDWARE LIST
SPECIFICATIONS Company Server PowerEdge 2900 • Quad Core Intel® Xeon® X5355, 2x4MB Cache, 2.66GHz, 1333MHz FSB Additional Processor: • Quad Core Intel® Xeon® X5355, 2x4MB Cache, 2.66GHz, 1333MHz FSB Memory: • 24GB 667MHz (12x2GB), Dual Ranked DIMMS Primary Controller: • PERC 5/i, Integrated Controller Card Hard Drive Configuration: • Integrated SAS/SATA RAID 1, PERC 5/i Integrated • 750GB 7200 RPM SATA II Hard Drive, Universal Carrier • 750GB 7200 RPM SATA II Hard Drive, Universal Carrier Non-Redundant Power Supply Network Adapter: • Dual Embedded Broadcom® NetXtreme II 5708 Gigabit Ethernet NIC Documentation: • Electronic Documentation and OpenManage CD Kit CD/DVD Drive: • 48X IDE CD-ROM Keyboard: • Keyboard, USB Monitor: • Dell 15 Inch Analog Flat Panel Mouse: • Mouse Option Hardware Support Services: • 3Yr BASIC SUPPORT: 5x10 HW-Only, 5x10 NBD Onsite
Cost RM7974
P a g e | 59 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Staff Workstation (12 pcs) Dimension C521 AMD Sempron™ 3400+ Operating System: • Genuine Windows Vista™ Home Basic Monitors: • 15 inch E157FP Analog Flat Panel Memory: • 512MB Single Channel DDR2 SDRAM at 667MHz Hard Drives: • 160GB Serial ATA Hard Drive (7200RPM) w/DataBurst Cache™ CD or DVD Drive: • 48X CD-RW/ DVD Combo Drive Video Cards: • NVIDIA GeForce 6150 LE Integrated Graphics GPU Sound Cards: • Integrated 7.1 Channel Audio Keyboard and Mouse Bundles: • Dell USB Keyboard and Dell 2-button Scroll Mouse Modem: • 56K PCI Data Fax Modem Mouse Network Interface: • Integrated 10/100 Ethernet Miscellaneous: • Award Winning Service and Support Labels: • Windows Vista™ Basic Warranty and Service: • 1Yr In-Home Service, Parts + Labor - Next Business Day Price per Workstation: $500 (x 12 systems)
Total Cost RM6000 Operator Headsets (10 pcs) Speaker size:40mm Frequency range:20-20,000Hz Speaker impedance:32 Ohm¡À15% Speaker sensitivity:105dB¡À3dB Microphone impedance:2200 Ohm Microphone sensitivity:-58dB¡À2dB Maximum power:100mw Standard operating voltage:4.5V Wire length:2.2 metres Cost $11 P a g e | 60 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Total Cost RM110 Microphone Altec Lansing • ABM-200 Noise Rejecting Desktop Computer • Microphone with Mute Switch https://secure.bhphotovideo.com/bnh/controller/home?O=cart&A=c art&Q=update Cost $15 (2 pcs)
Total Cost RM30 Driver System Speakers Juster SP693 2-piece Multimedia Speakers General Features: Beige color Output power (RMS): • 1W + 1WDriver: 2.25-inch full range cone, 8 Ohms • Frequency Range: 20 Hz ~ 20 KHz • P.M.P.O.: 300 • Watts Signal to Noise Ratio: 62 dB • Input Power: 110V 50 Hz • Power supply: AC, Integrated into casing Volume control • Knob Power On/Off button • Power LED Headphone jack Magnetically Shielded • Dimensions:3.38 x 2.68 x 6.54-inches (D x W x H) http://www.amazon.com/Juster-SP-693-2-Piece-MultimediaSpeakers/dp/B000QD11CM/ref=sr_1_12/103-67886644173469?ie=UTF8&s=pc&qid=1182600424&sr=1-12
Cost RM5 Network Printer HP LaserJet 4240n Printer •Black (best): Up to 40 ppm •Resolution: Up to 1200 x 1200 dpi •Recommended monthly print volume: 3000 to 12000 pages •Monthly duty cycle: Up to 175000 pages •Paper trays: 5 •Paper input capacity: Up to 3100 sheets Workgroup printer with versatile paper-handling and stapler/stacker options for creating a variety of everyday documents
P a g e | 61 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Cost : RM700 Owner’s Workstation Intel® Core™ 2 E6420 Duo Processor(4MB L2 cache,2.13GHZ,1066FSB) Genuine Windows Vista™ Home Premium 17 inch E177FP Analog Flat Panel 2GB Dual Channel DDR2 SDRAM at 667MHz- 2DIMMs 500GB Serial ATA 3Gb/s Hard Drive (7200RPM) w/DataBurst Cache™ 16x DVD+/-RW Drive Intel® Graphics Media Accelerator X3000 Integrated 7.1 Channel Audio Dell USB Keyboard and Dell Optical USB Mouse 13 in 1 Media Card Reader 56K PCI Data Fax Modem Dell A525 30 Watt 2.1 Stereo Speakers with Subwoofer Mouse included in Wireless, Laser or Bluetooth Package Integrated 10/100 Ethernet Award Winning Service and Support Windows Vista™ Premium
Cost RM1140 Fire Report-Dot Matrix Printer Fujitsu DL3750+ Parallel & USB Dot Matrix Printer - 80 column - Auto Tear off - Auto Load - Print Head Protection - Barcode Printing - USB interface - LAN interface - Auto Switching between interface on multiple I/F versions -The printer has nineteen resident fonts: Ten bitmap fonts – Courier 10, Pica 10, Prestige Elite 12, Boldface PS, OCR-B, OCR-A, Correspondence, Compressed, Draft, and High-speed Draft and nine outline fonts –Timeless, Nimbus Sans, and Courier, each in upright, italic, and bold. -Large print buffer.
Cost RM625 Biometric Attendance System
Stops employees clocking for others Monitors Staff presence and availability Overtime by time band, day, week or targeted. P a g e | 62
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Links to P.C. Up to 999 shift patterns Real time fire report Integrates with popular payroll programs Key Personnel display Plugs into a USB port Prints full time card activity Desk mount Calculates hours worked CE approved and complies with all major approvals Standard and three rates of overtime Unlimited targeted overtime rules Highlights/Deducts for lateness
Cost RM820
SOFTWARE LIST Server Operating System Cost RM 0 Web hosting Server Software
Cost RM 0 Database Program Cost RM 0 Scripting Language Cost RM0 Mambo Cost RM 0
P a g e | 63 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Workstations OS
Cost RM 0 Owner’s Workstation OS Windows Vista Premium Provided with system. Owner’s Workstations Virus protection
Pay Roll Software!!!!!!!!!!!!! Skype Cost RM 0
Credit Card Services Merchant Account (property of CardService International) http://www.merchantinc.com/index.html
P a g e | 64 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Interview pictures This is a snapshot of the Interview with Pizza Hut‟s Megamall Pacific, Penang area manager. A sample comment slip available in pizza hut shop to get customers comments about the system they are carrying out. More detailed explanation was given. The background is actually a house situated behind the mall, where all the riders‟ bikes are parked.
The area manager giving the comments slips. According to the manager, any customers are always free to drop by their comments. In this way, they will try to improve the current system. Basically he said customers prefer food served hot and fast. So for a better service, we give some importance to the delivery process also.
Another snapshot of the interview with the all-star manager. He is in charge in managing the Pizza Hut‟s Megamall branch. According to him, the current customers are satisfied with the restaurant dine-in experience and the restaurant is constantly trying to improve its delivery service.
P a g e | 65 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Minutes Meetings 18.04.2007 Meeting Details
Date: 18.04.2007
Time: 4.00pm - 6.00pm
Location: APIIT, L3-1 TPM
Agenda: o
Assigning specific roles in the group and allocating each group members‟ specific responsibility
o
Identifying current system used by Waiters on Wheels
o
To identifying current resources available
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Action List
Yernur Zholdybayev
Taken contact details of all group members
Identified and voiced out the various stages of the existing system
Noted down the existing system progressively
Muhammad Imran Butt
Prakash a/l Arichnam
Identified and voiced out the various stages of the existing system
Identified and voiced out the various stages of the existing system
Law Wern Siang
Identified and voiced out the various stages of the existing system P a g e | 66
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Summary of Discussion First agenda item: Each member present gives a brief background about the abilities and knowledge of each one has. The following are the roles assigned to each member through mutual agreement: Project Manager: Yernur Zholdybayev System Analysis: Muhammad Imran Butt Designer: Prakash a/l Arichnam User/tester: Law Wern Siang
Second agenda item: Procedures of the existing company setup of Waiters on Wheels were progressively listed down.
Third agenda item: The current resources available by Waiters on Wheels such as budgets, drivers, staffs, and databases were also identified.
Next Meeting
Date: 24.04.2007
Time: 5.30pm
Location: APIIT, L2-4 TPM
Agenda: Identifying problems and inconvenience in current system running
Minutes recorded by,
(Law Wern Siang) 18 April 2007
P a g e | 67 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
24.04.2007 Meeting Details
Date: 24.04.2007
Time: 5.30pm - 6.00pm
Location: APIIT, L2-4 TPM
Agenda:
To identifying flaws and problems in current system used by Waiters on Wheels
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Not Present
-
Action List o
o
Yernur Zholdybayev
Identified problems with the current system
Noted down the problems
Muhammad Imran Butt
o
Prakash a/l Arichnam
o
Identified problems with the current system
Identified problems with the current system
Law Wern Siang
Identified problems with the current system
Summary of Discussion Another meeting discussion was held to identify the major loopholes in the current system. Among them that were swiftly identified: i.
Inability to receive and attend to multiple phone orders simultaneously P a g e | 68
Asia Pacific Institute of Information Technology
Systems Analysis and Design
ii.
Waiters on Wheels
Inconvenience when dealing with producing and storing a large number of records such as invoices,
receipts, and bills. iii.
The need of hiring extra personnel to cope with company's hectic processes , increasing company's expenditure
iv.
The risk of human errors such as hold-ups, miscalculations, unattended and undelivered orders
Next Meeting
Date: 25.4.2007
Time: 4.00pm
Location: APIIT, L3-1 TPM
Agenda: Suggesting new ideas to improve the currents system or developing a new system entirely
Minutes recorded by,
(Law Wern Siang) 24 April 2007
P a g e | 69 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
25.04.2007 Meeting Details
Date: 25.04.2007
Time: 4.00pm - 6.00pm
Location: APIIT, L3-1 TPM
Agenda:
Suggesting new ideas to improve the current system
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Not Present
-
Action List o
Yernur Zholdybayev
o
o
Muhammad Imran Butt
Suggested new ideas to improve the currents system
Listed down all agreed suggestions
Prakash a/l Arichnam
o
Suggested new ideas to improve the currents system
Suggested new ideas to improve the currents system
Law Wern Siang
Suggested new ideas to improve the currents system
Summary of Discussion
P a g e | 70 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Group members gathered together to provide ideas on ways to improve the current system. Among the proposed changes that were highlighted were:
1. Automated web based system design to enable faster more accurate data entry and order notification between operating concerns at lower costs 2. Web based interface to allow customers to choose their own meal options 3. Database system to allow owners access to full records 4. Loyalty based card system for regular customers 5. Drivers will be paid a base salary plus commission and bonus based on the number of successful deliveries each individual driver had made to maximize productivity while cutting costs
Next Meeting o
Date : 25.04.2007
o
Time: 11.00am
o
Location: APIIT, Syndicate Room 1
o
Agenda: To discuss ways to improve the newly proposed system
Minutes recorded by,
(Law Wern Siang) 25 April 2007
P a g e | 71 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
26.04.2007 Meeting Details
Date: 26.04.2007
Time: 11.00am - 11.30am
Location: APIIT, Syndicate Room 1
Agenda:
Distribution of task
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Not Present
-
Action List o
Yernur Zholdybayev
Distributed task to each group member
Summary of Discussion A group meeting was called by the project manager to allocate task that was required for the completion of the assignment. The following was the summary of the allocation:
Yernur Zholdybayev
Muhammad Imran Butt
Prepares all diagrams to illustrate the functionality of the required system
Prepares feasibility reports
Prakash a/l Arichnam P a g e | 72
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Prepares reports on methodology selection
Prepares reports on fact findings
Waiters on Wheels
Law Wern Siang
Records all meeting minutes
Prepares a Gantt Chart
Assist on methodology selection and fact finding reports
Next Meeting o
Date : 16.05.2007
o
Time: 11.30am
o
Location: APIIT, Syndicate Room 1
o
Agenda: To discuss ways to improve the newly proposed system
Minutes recorded by,
(Law Wern Siang) 25 April 2007
P a g e | 73 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
16.05.2007 Meeting Details
Date: 16.05.2007
Time: 11.30am - 1.00pm
Location: APIIT, Syndicate Room 1
Agenda: To discuss ways to improve the newly proposed system
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Law Wern Siang
Not Present
Prakash a/l Arichnam (with reason)
Action List
Yernur Zholdybayev o
Gave suggestions to improve the newly proposed system
o
Voiced out the idea that a server be placed within the system of Waiters On Wheels
Muhammad Imran Butt o
Gave suggestions to improve the newly proposed system
o
Sketched the progressive chart of the required system
o
Sketched the progressive chart of the newly required system
Law Wern Siang o
Gave suggestions to improve the newly proposed system
Summary of Discussion The progressive chart of the required system was sketch out. It was later found to be slightly ineffective. According to the new system, the operator takes in the customer's orders and send 2 copies of the order slip to the intended restaurant and Waiters on Wheels respectively via e-mail.
P a g e | 74 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
If ever the case of which these emails failed to be send to either the restaurant or the delivery centre or both without the awareness if any of the parties for what so ever reason, the progressive chain of the system would be broken and synchronization would be greatly disrupted . Immediate troubleshooting between the restaurants and the delivery centre via e-mail to would be a hassle and time consuming. The chances of this situation to occur are very low, but it was taken into consideration as this would seriously upset the whole system if it would ever occur. All group members present mutually agreed to set up a server within Waiters on Wheels to avoid these complication. The server would be the backbone of the entire system as it ensure all orders and data would be synchronized to all parties. Troubleshooting would then be easier as all incoming and outgoing processes can be conveniently crossed check directly through the server. A progressive chart was then drawn to represent the newly required system.
Next Meeting
Date: 21.05.2007
Time: 11.00am
Location: APIIT, Syndicate Room 1
Agenda: To spot any other possible flaws in the system and suggesting solutions to fix them before finalizing the new system.
Minutes recorded by,
(Law Wern Siang) 16 May 2007
P a g e | 75 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
21.05.2007 Meeting Details
Date: 21.05.2007
Time: 11.00am - 1.00pm
Location: APIIT, Syndicate Room 1
Agenda:
Finalizing the draft of the required system
Building a logical design of the required system
Constructing a potential time frame and completion of dates
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Not Present
-
Action List
Yernur Zholdybayev
Prepared a project timeline
Surveyed available servers on the Internet
Muhammad Imran Butt
Surveyed available servers on the Internet
Law Wern Siang
Updated the Gantt chart based on the timeline drawn
Summary of Discussion First Agenda Item: The draft of the newly proposed system was finalized. It was confirm that there were no major loopholes in the new system and any minor inconveniences could be easily diagnosed through the server. P a g e | 76 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Second Agenda Item: The availability of different kinds of servers in the market today was firstly considered, primarily because it would be central of all processes involved in the delivery system. The server type, brand, operating system, specifications, and cost were surveyed online according to the suitability of the business of Waiters on Wheel. A few suitable customizable server models were narrowed down and listed for future final selection.
Third Agenda Item: An estimated time frame of the project was drawn. The progress of the project could be easily tracked and it ensures that all processes within it could be completed before the deadline agreed with Waiters on Wheels. All procedures were allocated fairly within the timeline according to project progression and importance in a form of a Gantt chart.
Next Meeting
Date: 11.06.2007
Time: 10.30pm
Location: APIIT, Syndicate Room 1
Agenda: To finalize the selection of server that would be used
Minutes recorded by,
(Law Wern Siang) 21 May 2007
P a g e | 77 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
11.06.2007 Meeting Detail
Date: 11.06.2007
Time: 10.30am -12.00pm
Location: APIIT, Syndicate Room 1
Agenda:
Server model and specifications finalization
Owner's (Waiters on Wheels) and the operator's computer system customization and finalization
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Not Present
-
Action List
Yernur Zholdybayev
Chose the server type and customized its specifications
Chose and customized the owner's and operator's desktop computer system
Muhammad Imran Butt
Chose the server type and customized its specifications
Chose and customized the owner's and operator's desktop computer system
Law Wern Siang
Noted down the specifications and estimated price of both server and desktop computer system
Summary of Discussion First Agenda Item: A server is chosen among the shortlisted ones from previous meeting. The Dell PowerEdge 1900 Tower Server was chosen because of it had the perfect balance in terms of speed, storage, availability, expandability,
P a g e | 78 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
and affordability. Not to mention it uses the latest technology to date. Among the few specifications that were highlighted were:
a. Brand Dell was the server brand that was brand mainly because it had the best and most convenient online customizing and ordering service to date. b. Operating system No operating system was selected. This was basically to save cost as there were other server based operating system that is available for free which works just as effective as purchasable ones. c. Installation service No installation service were selected. Just as above, to minimize expenditure. Installation could easily be setup by our own company's technician that will also setup the server operating system. Besides the mentioned specifications, other customization included server processor, memory, hard drive, and uninterrupted power supply (UPS). The complete specification of the fully customize server was printed and documented together with the estimated cost.
Second Agenda Item: The owner's and the operator's desktop computer system was also considered and customize during this meeting. Among the highlights were:
a. Brand Dell computer system was chosen for the same reasons as the server's. b. Processor The AMD Athlon 64 X2 Dual-Core processor was chosen over the standard Intel Core 2 Duo processor because the former was more affordable compared to the latter that produces almost the same processing power. c. Operating system Windows XP Home Edition was chosen over the recommended Windows Vista because the former required less system resources, thus boosting performance and lowering processing time. The customized Dell Dimension(TM) E521 desktop was chosen as both the owner's and the operator's computer system. However the owner's system were customized to have an higher specification. Both system settings were printed and documented together with the estimated costs.
P a g e | 79 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Next Meeting
Date: 13.06.2007
Time: 4.00pm
Location: APIIT, L2-5
Agenda:
Reviewing current progress of project
Consulting course lecturer for advice and improvements
Minutes recorded by,
(Law Wern Siang) 11 June 2007
P a g e | 80 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
13.06.2007 Meeting Detail
Date: 13.06.2007
Time: 4.00pm -6.00pm
Location: APIIT, L2-5
Agenda:
Reviewing current progress of project
Consulting course lecturer for advice and improvements
Distribution of new task to group members
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Action List
Yernur Zholdybayev
Re-examine all drafts, findings, and reports
Ran through the objectives and requirements of the assignment
Consulted the lecturer
Distributed new task to group members
Muhammad Butt
Re-examine all drafts, findings, and reports
Ran through the objectives and requirements of the assignment
Consulted the lecturer
Prakash a/l Arichnam
Re-examine all drafts, findings, and reports
Ran through the objectives and requirements of the assignment
Consulted the lecturer
Law Wern Siang
Re-examine all drafts, findings, and reports P a g e | 81
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Ran through the objectives and requirements of the assignment
Consulted the lecturer
Waiters on Wheels
Summary of Discussion First Agenda Item: The current status of the project was once again re-examine. Drafts, findings, and reports were all compiled to be inspected. The objectives and mandatory requirements of the assignment was ran through again to avoid missing crucial elements in the project.
Second Agenda Item: The course lecturer was consulted. Specifically, the technique of producing suitable yet accurate diagrams of the required system and its progress were enquired. Other query include information that was needed yet missing, amount of substance required by the assignment, and the necessary documentation essential for each progress made.
Third Agenda Item: After reviewing the progress of the project together with the consultation of the course lecturer, several new tasked that has not been covered in the project. Among them are:
producing more comprehensive feasibility reports
illustrating clearer and more accurate system diagrams
construct more detailed project time line
identifying the breakdown of work associated with the chosen methodology
suggesting techniques of determining user requirements
These 5 task were distributed fairly among all group members by (and including) the project manager.
Next Meeting
Date: 27.06.2007
Time: 10.00am
Location: APIIT, Syndicate room 1
Agenda: Planning and developing the system's physical design
Minutes recorded by,
(Law Wern Siang) 13 June 2007 P a g e | 82 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
27.06.2007 Meeting Detail
Date: 27.06.2007
Time: 10.00am -11.00am
Location: APIIT, Syndicate room 1
Agenda: Developing the physical design of the required system
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Summary of Discussion The logical design of the newly developed system was ran through. Each ordering and delivering procedure was explained thoroughly to ensure all group members understood the mechanics of the required system. The software needed to developed the physical design was then considered and it was agreed that Adobe Dreamweaver CS2 was the most suitable. The design would be coded in HTML format as it is the simplest.
Action List
Yernur Zholdybayev
Gave procedural explanation of how the required system would work
Suggested the software needed for developing the physical design of the system
Gave a brief tutorial of the functionality of Adobe Dreamweaver CS2
Muhammad Butt
Clarified the mechanics of the required system
P a g e | 83 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Next Meeting
Date: 04.07.2007
Time: 5.00pm
Location: APIIT, L2-5
Agenda: Compiling and editing all documents for handing in
Minutes recorded by,
(Law Wern Siang) 27 June 2007
P a g e | 84 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
04.07.2007 Meeting Detail
Date: 04.07.2007
Time: 5.00pm
Location: APIIT, L2-5
Agenda: Compiling and editing all documents for handing in
Attendees
Present
Yernur Zholdybayev
Muhammad Imran Butt
Prakash a/l Arichnam
Law Wern Siang
Summary of Discussion All findings and reports from all group members were gathered and compiled. Minor editing were made
Action List
Yernur Zholdybayev
Handed in diagrams of the logical design
Presented and edited physical design
Muhammad Butt
Handed in feasibility reports
Presented and edit physical design
Assist in document editing
Prakash a/l Arichnam
Handed in reports on fact finding, comparison of methodologies, and PERT chart
Presented and edited physical design
Law Wern Siang
Handed in reports on minute meetings, justification of chosen methodology, workload matrix, and Gantt chart
Presented and edited physical design P a g e | 85
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Compiled and edited all document
Minutes recorded by,
(Law Wern Siang) 4 July 2007
P a g e | 86 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
References Whitten, Jeffery L., Lonnie D. Bentley, Kevin C. Dittman-2001-System Analysis and Design Method-5th edition- New York-McGraw-Hill publisher. Jeffery A. Hoffer, Joey F. George, Joseph S. Valacich-1999-Modern System Analysis & Design.-2nd editionUnited State of America-Addison Wesley Longman, Inc. Feasibility Report References JOSEPH S. VALACICH, JOEY F.GEORGE – 2004 - ESSENTIALS OF SYSTEMS ANALYSIS AND DESIGN (3RD EDITION) JEFFREY HOFFER , MODERN SYSTEMS ANALYSIS AND DESIGN (4TH EDITION) The Mayfield Handbook of Technical & Scientific Writing http://www.imoat.net/handbook/feasibil.htm
Iowa State University Feasibility Study Outline http://www.extension.iastate.edu/agdm/wholefarm/html/c5-66.html
Online Technical Writing http://www.io.com/~hcexres/textbook/feas.html
P a g e | 87 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Workload Matrix Name Task
Yernur
Muhammad
Prakash a/l
Law Wern
Zholdybayev
Imran Butt
Arichnam
Siang
Cover Page
X
Table of Content
X
Introduction
Problems
X
Solutions
X
Assumptions
X
Project Identification and Selection
Identify current system
Identify current resources
X
Identify flaws in current system
X
X
X
X
X
X
Project initiation and planning
Establishing project initiation plan
Describing project scope, alternatives, and feasibility
X X
Fact Finding
Questionnaires
X
Interview
X
Summary of findings
X
Selection of Methodology
Methodology comparison
Justification of selected
X X
methodology Feasibility Studies
Technical Feasibility
X
Operational Feasibility
X
Economical Feasibility
X P a g e | 88
Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Schedule Feasibility o Gantt Chart
X
o PERT Chart
X
o Workload matrix
X
Logical Design
Context Diagram
X
X
Data flow Diagram
X
X
Entity relationship Diagram
X
X
Entity life history Diagram
X
X
Use case diagram
X
X
Class diagram
X
X
Physical Design
WebPages
X
Database
X
Appendix
Minutes Meetings
X
Documentation
X
Other
X
Compiling and editing
Signature:
___________________________
____________________________
(Yernur Zholdybayev)
(Muhammad Butt)
___________________________
____________________________
(Law Wern Siang)
(Prakash a/l Arichnam)
Individual reports P a g e | 89 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Yernur Zholdybayev
The Waiters on Wheels assignment might not have been my first foray into the field of System Analysis and Design but it most certainly was the first time that I was given the responsibility of being group Project Manager. I did not have opportunity to experience a project from the unique vantage point of group leader prior to this so this proved to be a very novel, very educational experience. All my experiences previous to this centered round smaller, single person individual assignments. As part of my assignment I assumed responsibility for leading my team members into developing a new system for a fictional company called Waiters on Wheels or WOW. As might be expected, our first steps into uncharted territory where hardly what might be termed as smooth sailing. I use the collective term “our” here because the concept of being subordinate to a fellow classmate was an alien an idea to my colleagues as my being a leader to them was to me! We all faced our own set of difficulties, each group members‟ dilemmas being more or less specific to the position that he had been assigned to. My problems, though typical of what a Project Manager must face on a daily basis, were entirely foreign to me. This was the first time I had to take on the job of chairing meetings and I must confess that like most other responsibilities I shouldered as Project Manager, I found it a sobering experience. It turned out to be a far cry from the preposterous notion that I once held; that all managers were a lazy, self centered bunch, who bide their time sitting around, barking orders and acting officious! As manager I now needed to schedule meetings at times convenient to all group members so that they all might be able to attend. I also had to come to a meeting prepared with an agenda of all things that had to be discussed and covered. I needed to prioritize tasks in order of importance so that the most important task could be tackled and done away with first. P a g e | 90 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
I found myself in the most unenviable position of being both a manager and a classmate at the very same time! As manager I realized that I bore the responsibility of distributing tasks to each member in such a way that would make best use of each group members own unique set of talents. At the same time I realized the destructive potential that delegating tasks to people who in no way perceived me as a superior could bring to overall group functionality. I therefore treaded a very fine line between a group leader and classmate at the same time. At times I coaxed, at times I would concede and at all times I sugar coated my words far more than I cared; all in the interests of extracting the best I possibly could from my group members. While I cannot claim complete success in my endeavors, I don‟t believe I can be blamed for lack of making a consecrated effort. Partially a consequence of the unconventional position that I was in and partially a result of my own admitted inexperience, I found myself struggling to maintain the requisite standards that are the hallmark of any accomplished Project Manager. I erred on several occasions but I always tried to rectify my mistakes. It is my unshakable opinion that time and experience together make for peerless instructors! We chose SSADM as our methodology of choice. While our assignment should make it more than evident why we eventually chose SSADM over all others I thought that as Project Manager I might recap in the very briefest of terms, the main reasons behind me and my group-mates decision. Our experience in the field of System design is at best basic. This understood, it should be easy to follow that because SSADM, unlike its contingency solutions, has a highly structured design, that it should prove most conducive to minimizing potential errors. Further it is our belief that SSADM, by virtue of its‟ limiting itself to the system development life cycle, best covers the scope of our project without delving into material superfluous to the scope of our study. Working as Project Manager has ingrained in me certain qualities which I might not have found in much depth preceding this. These qualities are: a) b) c) d) e)
Time Management capabilities Managing the project work flow process Coordinating and managing data team efforts Rapidly selecting the most appropriate solutions Learning to follow the required standards of System Analysis and Design
As manager I was not aloof of involving myself with my team members. I did not restrict myself purely to managing the group but also, I am quite happy to add, worked whole heartedly as a regular team member might. My struggles have taught me quite a bit about diagramming (I took responsibility for all the diagrams in the logical design), using management tools (MS OneNote 2007) and made me quite fluent with the SSADM methodology. I also assumed full responsibility for the development and creation of our logical design. In doing so I ended using several different types of software quite extensively. Of note are: A) Macromedia Flash B) Macromedia Dreamweaver P a g e | 91 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
C) Adobe Photoshop D) ACDSee E) Adobe Image Ready The logical design entailed quite a bit of research and groundwork which I attained primarily from the internet Finally, I wish to conclude my saying that I feel fully responsible for my project and my team members. My team mates have all put considerable time and effort into this project. At no stage have they ever neglected or refused to fulfill that which has been expected of them. It is my honest opinion that they all worked and attempted all that they were given to top of their abilities. I wish to thank them for their hard placed efforts, without which this whole assignment would not have been possible. I am indebted to their non-too-insignificant labor and wish to offer them my most heart felt thanks.
P a g e | 92 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Muhammad Butt
This reflects the first time that I have ever worked on a System Analysis and Design Project. It must be said that the subject has proved itself to be something of an eye opener. In concept, the idea behind System Analysis could hardly be any simpler. Take a flawed system; identify all its major grievances, than give it a thorough rework so that anything not up to scratch is replaced by something shiny and new! Simple, not too difficult is it?! Well, no not quite as simple or so I‟ve recently learnt! System Analysis and Design does look like simple arithmetic from afar, something akin to 2+2. Approach it more closely however and things start looking far more disturbing. More complex algorithm than base arithmetic! Time constraints, financial limitations and ever more demanding environments are just some of the variables that play against each other in this increasingly volatile equation. Finding a solution that can remedy these maladies, all in limited time is not exactly cake walk. As part of our assignment we were to propose changes to the design of a fictitious company by the name of Waiters on Wheels. I and three other classmates were joined together to form a group that would work as a consulting concern for the said company. This was a unique experience for me. I have never before been put in a position where the outcome of an assignment with my work in it was to decided by the work of others along with me. This is something of some concern to me as I have no prior knowledge of my group-mates capabilities. At the same time I can also appreciate the fact that they probably feel the same way about me too! P a g e | 93 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
As a group we were given certain positions/titles and as such we each theoretically carried our own specific job functions. In practice however, little could have been further away from reality. We all had a free hand to do what we want. We all made selections and decisions based on what we thought best at an individual level. The only problem with this course of action was that every now and then you‟d end up in conflict with another team member whose decision ran in direct conflict with your own! This free-for–allattitude may have also been one of the major promoting causes of laziness in some of our members during the initial stages! Part of the issue here was that we were all raw recruits with little or no experience in the field that we were attempting. We had very little idea about how it was to function as a cohesive unit. Not surprisingly perhaps some members might have initially sought out to simplify their side of the project without so much as giving a second thought to the repercussions that might follow for the rest of their team mates! At times things got really frustrating but we‟ve all managed to remain amicable and open to one other all the way from project inception to this point in time, now, as I write this report. This I believe is our groups‟ greatest strength (second only to our innate predilection to laziness)! Towards the end, it must be stated that everyone did finally put in a great deal of honest effort. Some people just tend to function best under stress! My designation in the group was that of System Analyst. I would like to think that the scope of work I completed exceeded that which was required by my job function! Still, given the dictates of human nature this type of opinion is to be expected and is best taken with a pinch of salt. It is entirely common for a person to get overly generous when it comes to self appraisal! Adjudication of my work would most certainly be better left to an impartial third party rather to a person with vested interest such as me! When it comes to work done I would first like to point out that I was a late entry into the current group. When I joined the current group the groups‟ total input on the project was little more than a couple of points partially detailing the workings of the existing Waiters on Wheels order system. I was responsible for completing the description of the current as well as suggesting the new potential system designs. Ultimately, the group selected one of the systems which subsequently became the focus of my new system design. Since the group mate assigned was unable to turn up with anything satisfactory in terms of fact finding I took the liberty of completing the systems planning with my own assumptions and whatever little knowledge I had with regards to delivery service. Wherever I fell short, I found that the web could provide answers. P a g e | 94 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
The feasibility report was a completely new experience to me. With absolutely no prior information of the subject I had to do quite a bit of research on the subject. I used the internet as my primary source and reference. I also found the two books “Modern System Analysis & Design” and “ESSENTIALS OF SYSTEMS ANALYSIS AND DESIGN” to be particularly invaluable in their content they provided. I made extensive use of both books throughout the project. Progress made on the feasibility report was slow for several reasons: 1.
There were several revisions to the final details of the system that necessitated re-writing parts of the report again. This part was particularly frustrating to me because at times a certain colleague (whose abilities I very greatly respect) would decide without warning that he wanted changes made to the system so that it would aid make his side of the project simpler! I was only informed after I consulted him regarding a certain issue I had with the project that, “Oh, by the way, we‟ve decided to scrap such and such part of the project!” or “I think we will change this. We don‟t need this. Let‟s replace it with this!” (In defense of this person I will also admit that he was always more than ready to avail himself for any help I needed on the project. Simply put, his actions, quite like our own, were more the result of a lack of experience then as a consequence of any intended callousness)
2.
I had initially undertaken to write about more than one new system. I had planned that I would evaluate each system from each of the angles of the feasibility report and then select the system best suitable to the job. All work done on this had to be discarded after it was discovered that incorporating the report as is would result in us greatly overshooting our preset page limit. I therefore wiped out all mention and evaluation made of the secondary system and restricted myself to the more conventional core system evaluation.
Amongst other things I also sourced out data for the rest of the group members. This may have also included sourcing former A-grade projects. The underlying intention was not so that they copy, indeed that would not have been an option since many, if not all the assignments were quite different from our own in terms of what they dealt with. The idea behind this was to aid my partners in as much as I could with their part of their assignments. The primary motivational factor here is the fact that their performance would have a direct bearing on my own result! Secondly, I realized the difficulty involved and possibility of error in attempting something for the first time. This in mind I wanted to share whatever help I could with my team mates even if I couldn‟t be directly involved in the process due to other responsibilities of my own. P a g e | 95 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
This System Analysis Project has taught me quite a lot in terms of: 1. Working as a team 2. Learning to overlook peoples shortcomings in favor of their positive strengths 3. Learning to follow steps instead of opting for the short/quicker way out. The quicker the route the proportionally greater the risk of creating a disaster! 4. The importance of proper time management Group work is not without its ups and downs and while things might not always been easy cruising I can quite honestly claim that overall I have enjoyed my time with my group members. I would be more than happy to be assigned to the same group again. Offered an opportunity to work to with the group again I would definitely seize the chance. Having all hopefully learnt from previous mistakes I think we will be able to manage far better than what we currently did. To conclude I would like to state the age old adage saying “All is well that ends well”. Whatever difficulties we faced, we faced together as a group. We might not have been the most cohesive, smoothly functional units around but I would like to think that we‟ve done a pretty darned good job considering our inexperience and distinct lack of exposure. I wish to make perfectly clear the importance of each group member and role that each member eventually played. Without our combined consecrated effort there was no way that this assignment would have been possible. Many things may have been left unsaid but what seems more important to me at this point more than anything else are the words of an old Arabic proverb: “He does not thank man does not thank God” I wish to express my sincerest heart-felt gratitude to all my group members for all the work that they have done.
P a g e | 96 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Prakash A/L Arichnam PHYSICAL DESIGN
SCREENSHOT OF THE HOMEPAGE OF WAITERS ON WHEELS.
Physical design is actually layout or designing homepage for the user and customer to interact with. Normally it is designed for the customer to easy to surf thru online. Basically this homepage layout was designed by our project manager and rest of us have their own part in as helping hands to the project manager. Our physical design is mainly done using a standard tool of designing homepage which is the Dreamweaver 8. This software is a useful and user friendly. This is because it is easy to create and design with all the standard tools. Firstly the layout which is a yellow and white background is use to make the customers get this feel of western style of homepage. It is basically design to have an italic style of background. The header is design such way to give a better and easily understood by customer who surf our webpage. It contains the picture of a chef carrying food and delivered straight from the kitchen. The picture itself describes how our delivery system will be and guaranteed it is served hot. We also have our telephone hotline which is 1-707P a g e | 97 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
707-707, where customer can also call and make their orders. We upgrade our system not only by online ordering but also via telephone order. Our header has the waiters on wheel with the logo of fork, plate and knife. On the top right of the page, we have an order list, which all your selected orders will be list down in the box plus it will also show you the amount of the food according to the order list. There is also a shopping cart which describe of how much food you have ordered so far. The header also has a slogan which describe about or service, our wheels your deal. We provide the delivery, you make your deal or orders and we give the express food delivery. There is a column with login and password for the registered customer. This is to ease regular customer to just order and wait for their food to deliver rather to enter customer‟s address, telephone number, credit card number and the main information that is collected from the customer for delivery purpose. For the new customer, they just have to click on the “register” and it will link to the customer registration page. Any problem or need some assistance, customer can click at the “help”. On the left of the homepage, we have a column name navigator. Navigator is a column where u can find the link such as, Menu, How to guides, order terms, feedback, and contact us. This are the basic link found in all the other websites. In the centre, there is a latest news board, where you can get to know about the latest news of our updated database, such as new restaurant added. Below that we also have hot offer, which gives customer the new deals or discounts. Customer will love with the hot deals, which is quite useful for the customer to order. For example “order more than 10 items and get discount about 30%”. We have discussed and come up with a finalized design. This homepage will be user friendly and easy to surf. We think the customer will love the page and will frequently visit our page. Critical Evaluation I am thankful to our lecturer; Ms. Palvin to gives me the assignment. This group work really teaches me on how a system is created. Firstly as I was divided into groups of four members, I was uncomfortable in the beginning because I don‟t really know about the other members. As our group work goes in progress, I get to know that my team members actually a very good person to work with. Each of us has a different approach to the project, different ideas, and moreover they really help me with my works. Working with them is like a pleasure to be with together. In terms of problem, firstly I was not used with the methodologies techniques and how to compare it. I was completely confused of how to deal with this problem. Luckily with the help of my lecturer and also with the module slides and also books in library, I have learned how to make the comparison between methodologies and the right selection of methodologies. P a g e | 98 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Secondly I have the problem of making findings such as questionnaires and interviews. As I am new to this place, I was shy to approach with the restaurant manager. So later on when my teammate gives me the boost to go and make interview, I finally managed to interview. The interview I carried out was not in Kuala Lumpur, but in Penang. My friend was manager in that place, so this makes me easy to get interview. After this I was not shy to ask question to anymore. Thirdly, I had problems with the diagrams and pert charts. The diagrams give me headache in the beginning. It was complicated to actually draw. Thanks to Microsoft Visio 2007, it makes drawing easy. The description about the diagram is another tough situation I have encountered. The explanations of each diagram are different and some are inter related, such as Context diagram and Data flow diagram level 0 and level 1. It takes me 2 days to actually sit down and focused on how each diagrams works and what are the main points to use in the description. With the help of the library facilities such as System analysis and Design book and some module has describe about the diagrams, gives me a clear view of how each diagrams works. This makes me easier to explain each diagram and actually I managed to complete the description of each diagrams on time. Finally I would like to express my thanks to the other members of my team which have helped me with my project. Rather being stressful with our assignment to finish on time, my team member was always looks relaxed but they worked hard day and night to finish the project. I then realized that rather being a sleeping partner in this team; I wanted to be an active member. So this teaches me how to be a hardworking by looking at others.
P a g e | 99 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Law Wern Siang Physical design Personally, I was given the task to design the registration webpage of the required system of Waiters on Wheels. The registration page would be loaded and shown on the customers screen when the „Register‟ hyperlink is selected and clicked upon from the main webpage. The primary function of this page is to allow new customers to become a registered member of Waiters on Wheels. Every customer is required to sign in as a registered member if he or she has the intention to make an online order. If the customer is new and desires to register before making an order, this is the page where the customer would be directed. Just as shown in the screenshot, the customer will be clearly shown important notices on the very top of the page. Some of the fonts were bolded to ensure it catches the attention of the page visitor and would actually take note of these notices. There notices on the top alongside the ones besides each text field acts as guides and examples for the customer as they fill in his or her particulars into each text field. The asterisk (*) symbol is placed beside each form item to highlight to the customer that those fields are compulsory and it must be filled by the customer in order to have an valid registration. Some of the text fields such as the password, IC number, and telephone number were modified to allow only a certain amount of characters. The username and password field was limited mainly for the reason of convenience. If the particulars are too long, the customer is more prone to make mistakes when reinserting these particulars when logging in. From the company‟s point of view, it helps manage the customers‟ database better by referring to shorter more convenient username. The password text field in particular was modified to show „hidden‟ characters for security purposes. It ensures that characters filled in by the customer could not be directly seen by other individuals. An extra P a g e | 100 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
password text field was also prepared for the customer to type in. The customer has to type same password in both the first and second field in order to have a valid registration. This is to prevent the case where the customer accidently created an account with a mistyped password. This problem could easily be avoided by having these two text fields where the customer has to confirm the entered password by entering it again in the second field. Once both characters entered matches, the customer will be able to submit a valid registration together with the other customer‟s particulars. The two buttons at the bottom of the page has its own functions. When the „Reset‟ button is clicked upon by the user, it clears all particulars and selection the user has filled in. This is again for the matter of convenience of the customer. Last but not least, the „Submit‟ button sends all particulars that were filled in each text field to be stored in the website‟s customer database. Once the customer is shown the message that their registration is valid and complete, he or she can make orders online. This registration webpage was designed and edited fully in HTML format using Adobe Dreamweaver CS3 software. Evaluation of assignment As a member of group 4, I can personally say I‟m satisfied with the overall progress, task distribution, and peer to peer communication of the entire course of this assignment. Not all was a smooth sail as we progressively moved deeper into the project but it is fair to say that everything went well and the project was managed to be completed by the deadline given because of good planning, excellent management, and effective understanding between group members. The project was managed well primarily because there was a definite layout of steps that guided us from the initial planning stage to the very end of compiling our project together. As mentioned in the previous report (see „Justification of selected Methodology‟), the SSADM methodology provided us with a basic foundation to build our project on. We followed precisely the modules of this methodology without overlooking any particular details. The feasibility studies was one of the most crucial elements as it allowed us to plan and determine the whole outline of our project and thus giving us another lead based upon the foundation of our selected methodology especially in terms of judging the time and workload needed to complete this assignment successfully. My main role in the group assignment as a user or tester of the group was to ensure the quality of our findings and reports were up to par to the standards that were set by the assignment requirements. It was also P a g e | 101 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
my duty to record and document the overall progress of the project as it is progressive being completed. In this way, the development of the project could be closely monitored to ensure it would be completed on time. However, my responsibility was not confined to this task alone. I was also assigned to assist choosing, justifying, and writing reports on available methodologies and investigation techniques. A few minor problems did occur along the course of the entire project timeline. One of which was the synchronizing of files, findings, and reports of each individual member to one another. It was rather inconvenient to gather all these materials as there was the constant need to update and modify these materials to three other group members and vice versa. One solution that was proposed was the idea of synchronizing all updates on materials to one particular member particularly the project manager. The downside to the idea was that these materials then couldn‟t be viewed and analysed by other group members. For the project manager to send these materials back with the updates would then be looping back to the same problem we were facing in the first place. It was time consuming and a hassle. However, an effective solution was eventually found with two simple but great innovation of technology. The first was by setting up a wireless ad hoc (computer-to-computer) network between the notebooks of each group member. Through this, synchronizing of material updates from each group member could be done almost automatically if not instantly when a group meeting was held. The second solution that was implemented was by using Microsoft Office OneNote. This project management software that was used by all members allowed us to conveniently view, exchange, and update all reports in the most organized fashion. Apart from attaining knowledge about the fundamentals of System Analysis and Design, there were certainly as few learning experiences that I have personally caught along the way. The one I consider the most crucial is the lesson of teamwork and communication. All members were complete strangers to one another and all from different backgrounds if not origins. Getting to know these new group members of mine that I will be working alongside side with for the next 3 months or so was the first step toward learning to adapt in a working environment which I will eventually be placed. I am truly honoured to be selected to work with these collages as they have proven to be excellent workmates. They have acted in the most professional of manner and yet managed to have a really sociable personality. Even though there were a few disagreements during discussions, they were all constructive disagreements as they provided us with various outlook of how a problem can be solved. This event occurred at the system requirement stage where lots of ideas were suggested by group members. In the end however, we made sure all parties would agree with the solutions that would be implemented. We had all practiced personal respect and have highly done so toward all group members. P a g e | 102 Asia Pacific Institute of Information Technology
Systems Analysis and Design
Waiters on Wheels
Other than that, I‟ve also gained experience in using a variety of latest software available for professional use. Among them are Microsoft OneNote, Microsoft Project, Microsoft Word, Microsoft Visio, Adobe Dreamweaver, and Adobe Photoshop. Most of this software are relatively new to me personally and have no experience in what so ever in using them. However, the requirement of preparing this assignment has driven me to learn to master the use of these applications. These softwares were used in producing the reports and designing the proposed physical design that I was assigned to complete. In conclusion, this assignment indeed moulded me in terms of professionalism. The invaluable experiences I have gained through the course of this assignment has definitely taken me another step closer to prepare me to cope with the working environment that I would encounter in the near future.
P a g e | 103 Asia Pacific Institute of Information Technology
