SAD

GROUP ASSIGNMENT
Intake : UCD2F0904DIT

Module title & code : SYSTEM ANALYSIS DESIGN

(AAPP007-3-2-SAD)

Lecture : MISS PALVIN

Group Members :
Name
ID
Name
ID
Name
ID
Name
ID

: Amirali Rezaei
: TP016277
: Mohamed Yasau
: TP016225
: Muhammed Zuhair
: TP015838
: Vivick s/o Rajendran
: TP016028
1

Contents
INTRODUCTION........................................................................................................... 4
PROJECT BACKGROUND............................................................................................... 5
PROJECT BACKGROUND............................................................................................ 6
PROBLEM IDENTIFICATION........................................................................................ 7
Recording Information................................................................................................ 7
Dispatching Information.............................................................................................. 7
Assigning Orders....................................................................................................... 7
Problems faced by Customers....................................................................................... 8
PROPOSED SOLUTIONS.............................................................................................. 9
Recording Information................................................................................................ 9
Dispatching Information.............................................................................................. 9
Assigning Orders.................................................................................................. 9
Problems faced by Customers..................................................................................... 10
Methodology................................................................................................................ 11
DATA GATHERING...................................................................................................... 19
I: Questionnaire Customers................................................................................ 20
LOGICAL DESIGN....................................................................................................... 31
Context Diagram........................................................................................................ 32
DFD Level 0............................................................................................................. 33
DFD Level 1........................................................................................................... 34
Process 1 (Order)..................................................................................................... 34
Process 2 (Driver Assigner)........................................................................................ 35
Process 3 (Pick-up).................................................................................................. 36
Process 4 (Payment)................................................................................................. 37
Process 5 (Report)................................................................................................... 38
Data Dictionary.......................................................................................................... 39
FEASIBILITY STUDY................................................................................................... 53
SCHEDULE FEASIBILTY........................................................................................... 54
GANTT CHART..................................................................................................... 54
PERT CHART........................................................................................................ 54
OPERATIONAL FEASIBILITY..................................................................................... 57
2

The PIECES Framework........................................................................................... 57

TECHNICAL FEASIBILITY........................................................................................ 61
Purchase of Computers............................................................................................. 61
CUSTOM TAILORED SOFTWARE FOR WOW............................................................65
ECONOMICAL FEASIBILITY..................................................................................... 66
IMPLEMENTATION...................................................................................................... 69
WEBSITE INTERFACE.............................................................................................. 70
PDA INTERFACE...................................................................................................... 81
DATABASE STRUCTURE WEBSHOTS.........................................................................82
MINUTES OF MEETING............................................................................................... 83
REFERENCES............................................................................................................. 90

INTRODUCTION
In todays world the boom of Information Technology (IT) cannot be overlooked. The computers
are playing an important role in todays dynamic business environment. As a result every
business needs to cope up with the pace of technology to survive the competition & assure the
customers that they are always at their best.
The company which we need to develop is a restaurant delivery system, named as Waiters On
Wheels, which deals with a bunch of restaurants to deliver their meal orders to the respective
customers.
As the operations of this company are purely service based, its of high importance that they
introduce a good information system to value their service quality, and therefore gain loyalty
from their suppliers as well as customers.
Companies use Information as a vital resource in the battle to increase productivity, deliver
quality products and services, maintain customer loyalty and make sound decision. (Gary B.
Shelly, Thomas J. Cashman, Harry J. Rosenblatt, 2001, P.1.1). Information Technology just not
make the operation of information easy and faster but also improve productivity and help
managers to take decisions.
We are a group of students acting as System Analysts and Designers. Our group comprises of
MUHAMMAD ZUHAIR, AMIRALI REZAEI, MOHAMMED YASAU & VIVICK
RAJHENDARAN, who are all equally enthusiastic about this project since the group formation
till the finalization of this project.

PROJECT BACKGROUND
PROBLEM IDENTIFICATION
PROPOSED SOLUTIONS

PROJECT BACKGROUND
Waiters on Wheels is a restaurant meal-delivery service started in 1997 by Sue and Tom
Bickford. The Bickfords both worked for restaurants while in college and always dreamed of
opening their own restaurant. But unfortunately, the initial investment was always out of reach.
The Bickfords noticed that many restaurants offer take out food, and some restaurants, primarily
pizzerias, offer home delivery service. Many people they met, however, seemed to want home
delivery service but with a more complete food selection.
Waiter on Wheels was conceived as the best of both worlds for Sue and Tom a restaurant
service but without the high initial investment. The Bickfords contracted with a variety of wellknown restaurants in town to accept orders from customers and to deliver the complete meals.
After the restaurant prepares the meal to order, it charges Waiters on Wheels a wholesale price,
and the customer pays retail plus a service charge and tip. Waiters on Wheels started modestly,
with only two restaurants and one delivery driver working the dinner shift. Business rapidly
expanded, and the Bickfords realized they needed a customer computer system to support their
business operations. They hired your consultant firm to help them define what sort of a system
they needed.
Sue described the current system as such When a customer calls in wanting to order, I need to
record it and get the information to the right restaurant. I need to know which driver to ask to
pick up the order, so I need drivers to call in and tell me when they are free. Sometimes
customers call back wanting to change their orders, so I need to get my hands on the original
order and notify the restaurant to make the change.
Tom continued, The drivers get the copy of the bill directly from the restaurant when they pick
up the meal, which should agree with our calculations. The drivers collect the amount plus a
service charge. When drivers report in at closing, we add up the money they have and compare it
to the records we have. After all drivers report in, we need to create a deposit slip for the bank for
the days total receipts. At the end of each week, we calculate what we owe each restaurant at the
agreed-to-wholesale price and send them a statement and check.

PROBLEM IDENTIFICATION
This is the first and most important phase of System Development Life Cycle. In order to
produce a successful Information System we should have a deep overview of the underlying
problems. After observing the functionality of the system briefly we came up with some of
the following problems being faced by Waiters on Wheels.

Recording Information

Lot of paperwork is involved as everything is being written on paper.

Whenever a regular customer calls, the operator always asks for his address as no
database system is present.

Dispatching Information

They operator has to calculate the total, taxes & service charge at the same time to tell the
total to the customer.

Almost all customers ask the estimated delivery time and the operator either has to
apologize about not having any idea or gives him wild guess which has high chance of
going wrong.

If the customer changes his order, the company has to worry about informing the delivery
person before he leaves the restaurant.

Assigning Orders

Inability to determine which driver will be free first & company has to wait under the
driver reports back.

There is no efficient system to track the drivers. The company cannot completely trust
them. They may cheat the company in many ways e.g. they can use the transport vehicle
for their personal use after any delivery task and may give the excuse of traffic.
7

Furthermore, lack of tracking system make it difficult for the operators to know where the
driver currently is, in order to tell the estimated time of delivery to the customer.

As all the communication is done using telephone there is a great probability of

communication errors e.g. drivers can note wrong address or telephone number while
they are on their way.

Problems faced by Customers

If several callers are calling at the same time the line is busy. There is no call waiting
system. Inability to deal concurrent orders.

The customer faces trouble in deciding what to order because they cannot view the menu
and their prices.

Many customers prefer to pay though their credit card. There is no way to use it in the
current system.

PROPOSED SOLUTIONS
Recording Information

A database management system is the most suitable to approach to record customer

details. It would only be necessary to record the information of the customers calling for
the first time, as the system can easily retrieve the details of an already registered caller.

Dispatching Information

The database system will have an interactive front-end enabling the operators to
automatically total the meal , taxes, & service charges as soon the meal preference is
entered.

Applications like Google Maps can be easily integrated with applications in order to tell
the distance between to places on the map. Once the distance is known by the system, it
can easily calculate a close estimate of the delivery time.

The delivery personnel can be equipped by a PDA device with internet connectivity
which can be always synchronized by the companys database remotely. They will
instantly know when a customer changes his order.

Assigning Orders

The drivers can easily interact with their PDA application to inform their status in just a
single click.

Furthermore, assigning orders will be far more robust & efficient if the company is able
to see the drivers location on a map displayed on their computer screens. This can be
achieved easily if the PDAs with the delivery personnel has GPS functionality which can
send its coordinates at regular intervals. This way the company can easily determine
which delivery personnel is near to the next orders destination.

Problems faced by Customers

As the companys is maintaining a database, its now easy for the company to reduce their
work load by leaving much of the work to be done by the internet customers. The
company can make a website connected to their database. Therefore, the delivery through
the website directly updates the companys database.

The customer who needs to decide on the meals, can visit the companys website
showing the Menus of the restaurants they deal with.

The customers who like to pay with their credit card can order the meal from the
restaurant and use websites e-payment system. This way much of the cash dependency on
the delivery men is also reduced.

10

Methodology
WaterFall
DSDM
RAD
Selected Methodology

11

Introduction to methodology
Methodology refers to the framework that is used to structure, plan and control the
process of developing an information system. As with any process, one of the most important
steps in carrying out a successful evaluation is choosing the right way to go about doing it. If the
study's design is well suited to the questions being considered, the whole process will be made
considerably easier. A huge variety of framework has evolved over the years, In order to keep on
the track with it, waiters on Wheels requires and efficient methodology. Each and every
methodology has its own strength and weaknesses. One system methodology is not necessary
suitable for all other projects. Each of the available methodologies is best suited to specific kinds
of projects, based on various technical, organization, projects and team consideration. Therefore
we will have the comparisons of three different methodologies, which are Waterfall, Dynamic
System Development Method (DSDM) and rapid Application development (RAD).
Selecting a System Development Methodology

Waterfall/Traditional SDLC
The waterfall model is a chronological system development process, in which progress is seen
as flowing gradually downwards (like a waterfall) through the phases of Conception
Initialize Investigation
Requirements Definition
System design
Coding testing
Implementation

Traditional SDLC
Operation &
The waterfall model is a popular version of the systems development
life cycle
Support

Principles:
1. Divided into phases, with some overlap and acceptable phases.
12

2. Importance on planning, time schedules, target dates, budget and implementation of an

entire system at one time.
3. Tight control is maintained over the life of the project through use of wide written
documentation.

Strengths
1. Methodologies incorporating this approach have been well tried and tested
2. Divides development into distinct phases:
well tried and tested
Makes tasks more manageable
3. Offers opportunity for more control over development process

4. Provides standards for documentation

5. Much better than trial and error
6. Ideal for supporting less experienced project teams and project managers, or project
teams whose composition fluctuates
7. Progress of system development is measurable
8. Conserves resources.
Weaknesses:

1. Inflexible, slow, costly and cumbersome due to significant structure and tight
controls.

2. Project progresses forward, with only slight movement backward.

3. Depend upon early identification and specification of requirements, yet users
may not be able to clearly define what they need early in the project.

4. Problems are often not discovered until system testing.

5. Difficult to respond to changes. Changes that occur later in the life cycle are
more costly and are thus discouraged.

6. Produces excessive documentation and keeping it updated as the project

progresses is time consuming

13

Dynamic System Development Method (DSDM)

DSDM is one of the heavier Agile approaches available. It was originally
developed as an extension to Rapid Application Development (RAD), incorporating
best practices from the business-oriented founders.

Source:
http://www.ifi.uzh.ch/req/courses/seminar_ws03/14_Voigt_DSMD_Ausarbeitung.pdf

Principles:
1.
2.
3.
4.
5.

Active user Involvement is Imperative

Teams Must be Empowered to Make Decisions
Focus on Frequent Delivery
Iterative and Incremental Development is Mandatory.
Using fitness for business purpose as the essential criterion for acceptance of

6.
7.
8.
9.

deliverables.
All Changes During Development Must Be Reversible
Requirements are Baseline at High-Level
Testing is integrated throughout the Lifecycle.
Collaborative and Co-operative Approach

Strengths:
14

1. An emphasis on testing is so strong that at least one tester is expected to

be on each project team.
2. Designed from the ground up by business people, so business value is
identified and expected to be the highest priority deliverable.
3. Has specific approach to determining how important each requirement is
to iteration.
4. Sets stakeholder expectations from the start of the project that not all
requirements will make it into the final deliverable.

Weaknesses
1. Possibly the most heavyweight project
2. Expects nonstop user involvement.
3. Defines several work of arts and work products for each phase of the
project; heavier documentation.
4. Access to material is controlled by a group, and fees may be charged just
to access the reference material.

15

Rapid Application Development (RAD)

RAD (rapid application development) is a concept that products can be developed
faster and of higher quality through (Principles):

1.
2.
3.
4.

Using workshops or focus groups to gather requirements.

Prototyping and user testing of designs.
Re-using software components.
Following a schedule that defers design improvements to the next product

version.
5. Keeping review meetings and other team communication informal.
6. Iteratively produces production software, as opposed to a throwaway
prototype.

Strengths:

1. RAD (rapid application development) proposes that system can be developed

faster and of higher quality
2. Time saving on the system development effort
3. Saving time and human effort
4. Users are seen as gaining more of a sense of ownership of a system, while

developers are seen as gaining more satisfaction from producing successful

systems quickly.
5. Provides the ability to rapidly change system design as demanded by users

Weaknesses:

1. Faster developing of the system

and lower cost may lead to lower overall

system quality
2. Lack of scalability
3. High cost of commitment on the part of key user personnel.

16

The following table is just to show the strength and weakness of some other methodologies.
Table 1. Methodology Strengths and Weaknesses (Rod Coffin & Derek Lane, n.d)
Each methodology has its own unique strengths and weaknesses that make each more
appropriate in certain contexts.
Strengths

Weaknesses

XP

Scru
m

Strong technical
practices.

Requires onsite customer.

Customer ownership of
feature priority,
developer ownership of
estimates.

Documentation primarily through verbal

communication and code. For some teams
these are the only artifacts created, others
create minimal design and user
documentation.

Frequent feedback
opportunities.

Complements existing
practices.

Only provides project management support,

other disciplines are out of scope.

Self organizing teams and

feedback.

Does not specify technical practices.

Customer participation
and steering.

Complements existing
practices.

Does not specify technical practices.

Focuses on project ROI.

Requires constant gathering of metrics which

may be difficult for some environments to
accommodate.

Eliminates all project

waste.

Supports multiple teams

working in parallel.

Promotes individual code ownership as

opposed to shared/team ownership.

Lean

FDD

17

All aspects of a project

tracked by feature

Iterations are not as well defined by the

process as other Agile methodologies.

Robust methodology with

many artifacts and
disciplines to choose
from.

Higher levels of ceremony may be a

hindrance in smaller projects.

Minimal attention to team dynamics.

Expects all team members to be co-located.

May not work well for distributed teams.

Adjustments are required from one project

size/structure to another in order to follow
the prescribed flavor of Crystal for that
project size/criticality

AUP

Cryst
al

Scales up very well.

Family of methodologies
designed to scale by
project size and criticality.

Only methodology that

specifically accounts for
life critical projects.

18

Selected Methodology: Waterfall/Traditional SDLC

Each methodology represents a different approach to evaluation. The fact
that there are so many approaches in common use simply reflects the fact that no
single methodology is 'the best'. Which one will be most appropriate for you
depends on the type of system.

So we will be selecting the traditional SDLC for this tracking delivery system
that is requires us to design and propose the system. The project has a clear
objective and solution that has been given to us by the user. Were not required to
implement the system urgently as were given a time frame for our analysis and
design which is suitable to apply the waterfall methodology.
Project

requirements

are

stable

or

unchanging

during

the

system

development life cycle which will be to create a prototype of the tracking system
within the time frame and is up to the requirements. Another reason why we chose
this methodology is because some of the team members are inexperienced and this
methodology can provide us the guidelines which are the stages in the life cycle.
Team composition may be unstable and expected to fluctuate because some
of the team members are specialized in certain field. As a project manager, which is
not be fully experienced, choosing SDLC will ease the work of managing the project
as the stages of the methodology is straight forward.
Resources can also be conserved because unlike RAD proposes the analysis
and design step by step rather than rushing to create a prototype system which
could be unstable or inconsistent. And the weakness of DSDM is, like with many
other structured approaches, the relatively high barrier to entry (apart from the
licensing costs). Switching to DSDM is neither
cheap nor fast, and requires a significant cultural shift in any organization, because
suddenly deliverables are replaced with tasks. I suppose for many people accepting
the fact that their project will be on time and on budget, but not necessarily
delivering the initially requested functionality will be hard to accept.

19

In conclusion, for the development of this system we will be using the

waterfall methodology.

20

DATA GATHERING
Questionnaire
Interview
Result/Chart

21

Data gathering
We consider that the data gathering or fact finding as one of the best method of
determining the user requirements, we will be using questionnaires which involve technical
information as well, this questioners is also to gather information regarding the requirements and
provide the best solution for the system and to provide better service to the customers. Therefore
we decided to divide the questioners into two parts which will be answered by the customers and
another set for the staffs in Waiters on Wheels. Each set of questionnaire would contain, not
more than 15 questions that will be relevant to gather information because we believe it will be
enough to summarize from the outcome.
We prepared the following questions as given bellow.

While preparing the

questions our main focus was to get the true information. So we passed the
questionnaires to different areas.

I: Questionnaire Customers
We are carrying out this questionnaire and interview in hope to improve the
current food delivery system of Waiters on Wheels. All the information you give will
be kept private and confidential. We would be very happy if you can fill in the
details as truthfully as possible as it would help us to build a system which will meet
the user requirements and to provide a better service for all the customers of
Waiters on Wheel
Thank you for your cooperation. We really appreciate it.

1. What kind of food you normally order from delivery service?

Chinese food
Malay food
India food
Western food

22

2. If Waiters on Wheels provide the following ways to place your order, which one would
you choose?
Telephone
Website
SMS
Other ..
3. What time of the day/week you normally order for food?
Morning
Afternoon
Evening
Night

4. How often do you order food through the delivery service(per month)?
Less than 10 times
10-20 times
20-30 times
30 times and above

5. What is the expected delivery time for your orders?

Less than 15 minutes
15 30 minutes
30 45 minutes
45 60 minutes
6. How do you think about the operator who served you?
Very Good
Good
Average
Bad

23

7. Have you ever facing difficulties while order the food through delivery
service?

Yes
No
8. How would you like to pay your bills? By
Cash
Credit Card
Online Banking
Cheque

9. Are you satisfied with the service provided by Waiters on Wheels? (For existing
customers)
Yes
No. Kindly explain

10. How can we improve our food delivery service to you? Kindly suggest.

24

Summary of Questionnaire

After observing the answers of questionnaires filled by various customers of

Waiters on Wheels and other random people, we used the graphical ways to show
the results of the above questions and also we use that information useful
information to design the computerized system for the company. The main purpose
of targeting the questionnaire to the existing customers of Waiters on Wheels is to
identify and study the current weakness and opportunities to improve the existing
system, which they have been used before. And also we have targeted the
questionnaire to some random people to get their point of view towards a new
computerized delivery system and to identify their expectations of such a system.

As you can see from the graphical column chart of the results of the
questionnaire we have concluded that the current system has many boundaries for
the customers. One of the main points that most of the customers mentioned was
the time spent to give the order, because the current system requires the telephone
operator to write down everything manually. This drawback could be overcome by
the new system, which allows the operator to simply clicking the items based on the
customer requirement. The other thing that we figured out was the delay in
delivering the order. Most of the customers who have answered the questionnaire
expect the food to be delivered within 15 to 30 minutes or less than 15 minutes.
30% of the customers also stated that they would like to make the payment using
their credit card/online payment. So to meet the customer expectation it will be an
added bonus for the system to enable the customers to make online payments.
See the following Observation.

25

Results and Charts

No.

Question

Percentage

of

Customers

who

selected to do the questionnaires

and answers are from (a) to (d)
(a)
1.

2.

3.

(b)

(c)

(d)

What kind of food you 25%

normally order from
delivery service?
If Waiters on Wheels 30%
provide the following
ways to place your
order,
which
one
would you choose?

30%

25

20

30%

What time of the

10%

20%

20%

50%

40%

30%

20%

10%

delivery 80%

19%

1%

35%

45%

15%

5%

order 60%

40%

35%

35%

3%

day/week you
normally order for
food?
4.

How often do you

order food through
the delivery service
(per month)?

5.

Estimate
time

6.

Operators
service attitude

7.

Difficulties
food through

delivery service
8.

Method of payment

27%

26

9.

Satisfaction for

70%

30%

Waiters on Wheels
services

1. Kind of food prefer

35%
30%
25%
20%
15%
10%

Chinese food
Malay food
India food
Western food

5%
0%

2. Method of ordering

70%
60%
50%

Telephone

40%

Website

30%

Others

SMS

20%
10%
0%

27

3. The time of the day which food is used to order

60%
50%

Morning

40%

Afternoon

30%

Evening

20%

Night

10%
0%

4. Number of ordering times for delivery / permonth

45%
40%
35%
30%
25%
20%
15%
10%
5%
0%

Less than 10
times

10-20 times

20-30 times

30 times and
above

5. Expected delivery time

28

90%
80%
70%
60%
50%
40%
30%
20%
10%
0%

Less than 15
minutes
15 30
minutes
45 60
minutes

6. Operators service attitude

50%

Very Good

40%

Good

30%

Average

20%

Bad

10%
0%

7. Difficulties order food through delivery service

80%
60%

Yes

40%

NO

20%
0%

8. Method of payment

29

40%
35%
30%
25%
20%
15%
10%
5%
0%

Cash

Credit card

Online
Banking

Cheque

9. Satisfaction for Waiters on Wheels services

30

80%

70%

60%

50%

40%

30%

20%

10%

0%
1

31

II: Interview Waiters on Wheels

1. What is the rate of your current system?
1 Bad
2 Average
3 Good
4 Very good
5 Excellent
2. How many staffs are there for current manual system?
Please state with job title
3. Are all of your employees computer literate?
Yes
No
4. Are the requested reports generated on time and accurate?
Yes
No. Kindly Explain []
5. Do the drivers report back to you when they are free?
Yes
No. Kindly Explain []
6. What is the average delivery time spent for a customer?
Please state: ..
7. Do the customers complain regarding the current system?
No
Yes.
Kindly Explain

8. Do you have any suggestions for the new computerized system?

No
Yes.
Kindly Explain

32

Summary of Interview

The main purpose of the above interview is to identify the problems of the current system and
the interview was targeted to Sue and Tom Bickford of Waiters on Wheels. As mention in the
problems of the current system, current system requires 4 telephone operators to record the
orders and 2 deliverymen to work on shift basis. However, Sue and Tom agreed that the working
time for the deliverymen is quite full due to the demand of the customers. So to improve the
service delivery, we recommended Sue and Tom to reduce the telephone operators to 2 (shift
basis) and to employ 2 more deliverymen (total 4 deliverymen). The reason to reduce the
telephone operators is that, the proposed system will be designed to record the orders
electronically which will enable the employ to speed up his/her work and serve more customers
concurrently.
Tom and Sue also stated that its difficult to track the position and status of the deliverymen
because theres no way in the current system to do so. To avoid this issue, our proposed system
can be designed to track the current status of deliverymen and the elapsed time for each delivery.
The system has the application that can track the time it takes to reach the drivers to the
destination. This will enhance the image of the company by gaining the trust of the customers
and also the company staff will strive to maintain their standard of service by delivering the
service within the duration specified.

33

LOGICAL DESIGN
CONTEXT DIAGRAMS
DATA FLOW DIAGRAMS

34

Context Diagram

35

DFD Level 0

36

DFD Level 1
Process 1 (Order)

37

Process 2 (Driver Assigner)

38

Process 3 (Pick-up)

39

Process 4 (Payment)

40

Process 5 (Report)

41

Data Dictionary
Data Flows

Name: Order(s)
Description: Details of the customer and the order items
Source: Entity - Customer
Destination: Proces1.0 - Order
Data

Elements:

Customer-Name,

Phone-Number,

Customer

Address,

ID(PassportNo/IC), Method-of-Payments and Order items

Name: Order Confirmation

Description: Send back the confirmation
Source: Proces1.0 - Order
Destination: Entity Customer
Data Elements: - Customer ID ,Customer-Name, Phone-Number, Customer
Address, ID(PassportNo/IC), Method-of-Payments and Order items

Name: Cook list

Description: Lists of ordered foods and the time of order taken place
Source: Proces1.0 - Order
Destination: Entity- Restaurant
Data Elements: Order items, Order time.

42

Name: Cook list Confirmation

Description: Confirmed Lists of ordered foods and the time of order taken place
Source: Entity- Restaurant
Destination: Proces1.0 - Order
Data Elements: Order Items

Name: Order list

Description: Records of the confirmed order items
Source: Process 1.0- Order
Destination: Data store- Order record
Data Elements: - Customer ID, Order items, Order time, Order date, CustomerName, Customer Address, phone-No and PassportID,

Name: Cook complete

Description: Status that the cooking of foods has been finished
Source: Entity- Restaurant
Destination: Process 2.0- Driver assigner
Data Elements: Order items and status

Name: Restaurant Location

43

Description: Send the information of restaurant along with the location, to the
delivery man
Source: Process 2.0 - Driver assigner
Destination: Entity Delivery man
Data Elements: Name-of-Restaurant, Address-of Restaurants

Name: Delivery man ID

Description: Information of the Driver
Source: Entity Delivery man
Destination: Process 3.0 Pick-up
Data Elements: Driver ID and Driver Name

Name: Cooked item

Description: Pack of foods which has been asked to cook
Source: Entity Restaurant
Destination: Process 3.0 Pick-up
Data Elements: Order Items

Name: Deliver item

Description: Pack of foods which has been confirmed from the order
Source: Process 3.0 Pick-up
Destination: Entity Delivery man
Data Elements: 44

Name: Customer receipt

Description: Details of the foods ordered with price
Source: Entity Restaurant
Destination: Process 3.0 Pick-up
Data Elements: Order Items, Price, order-id

Name: Customer location

Description: Information of the customer who ordered for delivery service
Source: Process 3.0 Pick-up
Destination: Entity Delivery man
Data Elements: Customer ID, Customer-Name, Address, PassportNo, Order time,
Order date

Name: Payment detail

Description: Its the receipt of the order items
Source: Process 3.0 Pick-up
Destination: Entity Delivery man
Data Elements: Customer ID, Customer-Name, Address, PassportNo, Order time,
Order date
Order Items, Price, order-id and method of Payment

45

Name: Ordered Item

Description: Pack of foods which customer ordered
Source: Entity Delivery man
Destination: Process 4.0 Payment
Data Elements: -

Name: receipt
Description: Receipts (price details) of the ordered food items
Source: Entity Delivery man
Destination: Process 4.0 Payment
Data Elements: Customer ID, Customer-Name, Address, PassportNo, Order time,
Order date
Order Items, Price, order-id and method of Payment

Name: Ordered Food

Description: pack of foods which customer ordered
Source: Process 4.0 Payment
Destination: Entity- Customer
Data Elements: -

Name: Bill

46

Description: Send the receipt which has receive from the delivery man along with
money
Source: Process 4.0 Payment
Destination: Entity- Customer
Data Elements: Customer ID, Customer-Name, Address, PassportNo, Order time,
Order date
Order Items, Price, order-id and method of Payment, AmountofMOney

47

Name: Money
Description: payment from the customer
Source: Entity- Customer
Destination: Process 4.0 Payment
Data Elements: -

Name: Update Driver

Description: Information about the Status of the driver
Source: Process 4.0 Payment
Destination: Data Store- Ordered record
Data Elements: - DriverID, DriverName, DriverStatus

Name: Customer e-receipt

Description: Send the records of the customer receipts including the service
charge to generate report
Source: Entity - Restaurant
Destination: Process 5.0- Reports
Data Elements: - Receipt-Id, Order items, Price, Service-Charge, Order date and
Order time

Name: Retail e-receipt

Description: Send the records of the customer receipts to generate report
Source: Entity - Restaurant
48

Destination: Process 5.0- Reports

Data Elements: - Receipt-Id, Order items, Price, Order date and Order time

Name: Financial Report

Description: Sending the reports to Admin
Source: Process 5.0- Reports
Destination: Entity - Admin
Data Elements: - [Customer e-receipt] and [Retail e-receipt]

Name: All Receipts

Description: Send to store the data
Source: Process 5.0- Reports
Destination: Data store- Financial record
Data Elements: - [Customer e-receipt] and [Retail e-receipt]

Name: Update delivery status

Description: Records information of the status of the delivery
Source: Process 3.0- Pick-up
Destination: Data store- Order record
Data Elements: - Receipt-Id, Order items, Price, Order date, Customer-Name,
Customer Address, phone-No and PassportID, Status-of-Delivery

49

Data Stores
Name: Order record
Description: This record stores customers order information, the status of the
delivery
Input Data Flows Order List, Update delivery status
Output Data Flows: Data Elements: Receipt-Id, Order items, Price, Order date, Customer-Name,
Customer Address, phone-No and PassportID, status of delivery, delivered time,

Name: Financial record

Description: This record stores the information of all receipts
Input Data Flows: All receipts
Output Data Flows: Data Elements: [Customer e-receipt] and [Retail e-receipt]

Name: Driver records

Description: This record stores the information of all receipts
Input Data Flows: Update Driver
Output Data Flows: Data Elements: Status of driver, DriverID, DriverName, Driverlocation
50

Processes
No: 1.0
Name: Order
Description: In this process, system will get the order confirm back the order to
customer and also send the order items to restaurant and get the confirmation from
the restaurant.
Input Data Flow: Order, Cook list confirmation
Output Data Flow: Order confirmation and Cook list confirmation
Process Specification:
BEGIN
GET Order foods,
Confirm the order foods
SEND the Order foods to restaurant
GET confirmation Cook list
STORE the confirmed Order list to Data store order items record
END

No: 2.0
Name: Driver Assigner
Description: In this process, gets that status that order items has been ready and
it send the location of the restaurant to the Delivery man
Input Data Flow: Cook complete

51

Output Data Flow: Restaurant location

Process Specification:
BEGIN
GET Status from the restaurant,
SEND the Location of the restaurant to the driver and ASSIGN
the driver who is nearest to that restaurant

END

No: 3.0
Name: Pick-up
Description: In this process, gets food packs along with the receipt. And check the
Driver ID assigned and give the food pack along with the receipt and customer
location
Input Data Flow: Cooked item, customer receipt and Delivery man ID
Output Data Flow: Delivery item, Receipt, Customer location and Update delivery
status
Process Specification:
BEGIN
GET order items, Customer receipt
AND Check Driver ID
GIVE Order item, customer receipt along with location
STORE Order records and update the driver status
END
52

No: 4.0
Name: Payment
Description: In this process, get the ordered item and receipt from the delivery
man and send the Customer order items to customer along with receipt and get the
money back.
Input Data Flow: Receipt, Ordered item and Money
Output Data Flow: Customer order item, Invoice and free driver
Process Specification:
BEGIN
GET ordered items along with receipt
AND Send the Customer ordered items along with receipt via
driver
GET Money back from Customer through driver
AND update the driver status free
STORE order records

END

No: 5.0
Name: reports

53

Description: In this process, Customer e-receipt and retail e-receipt from the
Restaurant and send the Financial reports to the Admin and records all receipt to
data store Financial record
Input Data Flow: Receipt, Ordered item and Money
Output Data Flow: Customer order item, Invoice and free driver
Process Specification:
BEGIN
GET customer e-receipt & retail e-receipt
SEND financial reports TO admin
STORE Financials records

END

ENTITY

Name: Customer
Description: Customer makes the order from waiters on wheel for food and drinks
Input Data Flow: Order confirmation, ordered food and Bill.
Output Data Flow: Order(s) and Money

Name: Delivery man

Description: Driver in charge of delivery of food and get receipt form WOW
Input Data Flow: restaurant location, deliver item, payment details and customer
location
54

Output Data Flow: receipt, Ordered item, Delivery man ID

Name: Restaurant
Description: Restaurant prepare the customer order to be delivery
Input Data Flow: Cook list
Output Data Flow: Cook list Confirmation, Customer e-receipt, retail e-receipt,
Customer receipt, cooked item and cook complete

Name: Admin
Description: Workers in Waitress On Wheel, such like telephone operator,
accountant
Input Data Flow: Financial report,
Output Data Flow: -

55

FEASIBILITY STUDY
SCHEDULE FEASIBILTY
OPERATIONAL FEASIBILITY
TECHNICAL FEASIBILITY
ECONOMICAL FEASIBILITY

56

SCHEDULE FEASIBILTY
Schedule feasibility means that a project can be implemented in an acceptable time frame.
When assessing schedule feasibility, a system analyst must consider the interaction between time
and cost. (Gary B. Shelly, Thomas J. Cashman, Harry J. Rosenblatt, (2006), Pg. 61).

GANTT CHART
A Gantt chart is a graphical part that shows the duration of tasks. It is a valuable tool for planning
and scheduling projects. A Gantt chart is helpful when you want to see the progress of the
project. It lets you know how long the project should take.
Gantt Charts were developed many years ago by Henry L. Gantt as a production control
technique and still are in common use. A Gantt Chart is a horizontal bar chart that represents a
series of tasks. (Gary B. Shelly, Thomas J. Cashman, Harry J. Rosenblatt, (2006), Pg. 584).

PERT CHART
A PERT (Program Evaluation Review Technique) chart is a graphic representation of a projects
schedule, showing the sequence of tasks, which tasks can be performed simultaneously, and the
critical path of tasks that must be completed on time in order for the project to meet its
completion deadline. The chart allows a team to avoid unrealistic timetables and schedule
expectations, to help identify and shorten tasks that are bottlenecks, and to focus attention on
most critical tasks. Because it is primarily a project-management tool, a PERT chart is most
useful for planning and tracking entire projects or for scheduling and tracking the
implementation phase of a planning or improvement effort.1

1 http://web2.concordia.ca/Quality/tools/20pertchart.pdf)

57

GANTT CHART

58

PERT CHART
Task
A
B
C
D
E
F
G
H
I
J
K

Description
Introduction
Analyze the current system
Problem Identification
Propose a solution
Data Gathering Techniques
Feasibility Report
Selection of Methodology
Process Modeling
Data Modeling
Entity Life Cycle Modeling
Over all Documentation

Length
2
4
3
3
4
7
3
7
6
5
2

Predecessor
--A
B
C
D
E
F
G
G
G
H,I,J

OPERATIONAL FEASIBILITY
A system that has operational feasibility is one that will be used effectively after it
has been developed. if users have difficulty with a new system, it will not produce

59

the expected benefits. Operational feasibility depends on several vital issues. For
example, consider the following questions:

Does management support the project?

Do users support the project?
Is the current system well linked and effectively used?
Do users see the need for change?
Will the new system result in a workforce reduction?
if so what will happen to the affected employees?

In order to measure operational feasibility we use PIECES framework.PIECES is a practical

framework. The pieces framework is significant because it teaches you to always examine
project triggers in terms of their bottom-line impact on the organization(System Analysis
and Design Method, 3rd edition, Jeffrey L. Whitten, pg 98, ISBN 0-256-093601,1994,publication IRWIN,USA)

The PIECES Framework

PERFORMANCE:
Performance means the throughput and response time of the system. Throughput means the
amount of work done by the system in a given time frame. In our case, the throughput will be the
number of orders delivered in a specific time period. In the current system the throughput is less
because all the processes are being done manually. Much time is devoted in noting down the
customer details and order, figuring out the free driver, telling him the address details on his cell
phone, then calling the restaurant and forwarding the order. In the current system for a given time
period fewer orders are delivered. However, in the proposed system all the work is automated
and computerized which results in greater throughput and therefore the system performance is
better.
Response time means the amount of time for the average delay between a transaction or
request and a response to that transaction or request.( Jeffrey L. Whitten, Lonnie D. Bentley,
Victor M. Barlow, (1994), Pg.99). The faster the response time, the better is the performance of
the system. For WOW the response time is the amount of time taken by the system to complete
the delivery of one order. The response time starts from the moment the customer places an order
either via website or telephone till the time the order is delivered a his house. The current system
60

responds slowly compared to the proposed system, as the complete process of the order delivery
takes more time in old one as compared to the new system.

INFORMATION
It refers to the need to improve information and data which means whether the system is
providing important, appropriate, accurate and well timed information to the managers and the
users.
The current system is not at all good when it comes to providing essential information
comes. The customer needs to know about the menus and the prices but they are unable to do so.
Furthermore the existing system provides no details when it is time to make the everyday deposit
slip, weekly sales report or weekly restaurant payment.
On the other hand, the proposed system will be very productive when it comes for
generating data. A companys website will be created where the user can easily view the menu
and its prices. The custom-made companys software will do all the necessary data processing
and calculations at the end of the day.

ECONOMY
Due to its limited initial investment, WOW systems services are limited. Although the
implementation of the new system is expensive but in the long run it is beneficial as it makes the
performance better. Thus the revenue & profit increases.
No we are not prematurely jumping into economic feasibility! The question here is, does the
system offer adequate service level and capacity to reduce the costs of the business or increase
the profits of the increase.(Jeffrey L Whitten, Lonnie D. Bentley, Kevin C. Dittman, (2000),
Pg.368).

Cost Reduction

Less paper cost.

Less telephone bill
Profit Increment

61

 Online ordering eases the customer. More number of orders.

Order delivery will be quick. Thus more time will be available to deliver more orders.
Fast and efficient delivery service will increase reputation.

CONTROL
It refers to the efficient control against fraud and to assure the data is secured.
In the current system, everything is stored on the paper. So its less secure because anyone in the
office has access to the company information such as customer data, their profits records, etc.
In the proposed system, all the things are done automatically and stored digitally. This way its
also possible to make backups and upload it any remote location. For the threats from the
internet, we have antivirus that help protect the server from the virus that come from the internet.

EFFICIENCY
For any business, the efficiency of its system is the root of its success. If the procedures which
are being performed are not efficient then it badly affects the companys profit & reputation even
if they have enough resources. The important part is to have maximum utilization of the
resources.
The Current system of WOW is not efficient at all. The data is recorded on papers, calculations
and making of reports are done manually which is highly susceptible to errors unless they are
very careful.
In the proposed system, data and information is saved in database system and will be processed
automatically whenever important events happens e.g. whenever a registered customer calls his
records will be automatically retrieved & displayed on screen. Similarly, the daily work is being
saved in the database and the computer will be able to sum up the total sale for that particular
day and can generate deposit slips, weekly sales reports and cheque for restaurant payment.

SERVICES
Services is the aspect which is exposed to customers. The delivery time, the accuracy of the
order, avoiding delivery mistakes. These are some of the important phases which determines the
customers view of the organization & their quality.

62

Current system is highly prone for noting down wrong addresses. Manual calculations can also
be done wrongly as the operator is concentrating on dealing with the customer. So more the
paper work, work the chances of suffering from mistakes.
On the other hand constant coordination with the delivery personnel can also be affected, if the
drivers cant be contacted because of signal problems.
On the other hand, the automation & computerization of the system can avoid such problems.
Calculations computerized, coordination via devices with internet accessibility and other overall
speed up of the system results in c customers.

63

TECHNICAL FEASIBILITY
Purchase of Computers
In todays era where computer is widespread, a system without computers is seen as oldfashioned. Because of the technology being common everywhere, the costs are not sky high as
they are for a rare item in the market.
So even though the Bickford brothers have low scale of operation its not a heavy burden for
them to buy a set of good computers, and amongst them one being with an even better
configuration to make it as the server.
Below is some research on the computer & devices with general specification and their prices:
FOR SERVER:
HP ProLiant ML150 G5
Product Specification:

RM

(1) Quad-Core Intel Xeon processor E5430 (3.0 GHz, 4GB

3600

DDR2), 500GB 7200rpm SATA HD, 48x DVD-ROM, Embedded

NC326i Dual Port Gigabit Server NIC, no OS installed.
CLIENT

Because all the data is stored on the server and server will be our main processing computer so
we need a very-low specification for client. We dont even need a hard disk on the client. The
clients job is only to handle the customer call, input the data and send it to server. This is fit with
thin-client concept. Another advantage of thin client concept is it saves the power energy (See
graph below). Based on my research on the internet, there are two vendors who produce thin
client. Its IBM and HP. Because of same specification IBM is more expensive than HP. We
decided HP for our thin client. Our HP specification is HP Compaq t5720 the AMD Geode NX
1500 processor with 512 MB of Flash memory and either 512 MB of DDR RAM standard.

64

Graph 1: Power Usage of Thin Client versus PC

Product Description
HP Compaq t5720 Thin Client with Microsoft Windows XP
Embedded. The t5720 delivers desktop-like features and support
for local applications. This unit is the ideal choice for businesses
featuring the AMD Geode NX 1500 processor with 512 MB of
Flash memory and either 256 MB or 512 MB of DDR RAM
standard.

RM 600

An optional PCI slot allows a broad selection of options. Every

t5720 thin client ships with the Sygate Security Agent pre-installed
and Microsoft Windows XP Embedded SP2.2
MODEM

The thin client specification has come without the modem. The modem that fits with this
hardware is Agile Hi-Speed modem for Thin Client.

Agile Hi-Speed PCI Modem for the thin client

RM 120

ACCESORIES

Standard Keyboard & Mouse for the client.

2 http://h10010.www1.hp.com/wwpc/us/en/sm/WF05a/12454-12454-321959338927-89307-1809592.html
65

Keyboard & Mouse Combo

RM 80

LCD Screens, we need clear, energy efficient, and save-space screen. So we put the HP L1710
17-inch LCD Monitor (GS917A8).

HP L1710 17-inch LCD Monitor (GS917A8)

RM 580

Headset for the operators to receive calls and talk to the customer directly from the client.

Panasonic KX-TCA86

RM 50

NETWORK DEVICES
To connect to the network, we need a fast and reliable switch. We decided to use Cisco Network
Switch. Cisco is well known for its reliability and fast network in networking devices. Cisco 24
10/100 is perfect for this situation.
Linksys 24-Port 10/100 Switch SR224 - Switch - 24 ports
EN,

RM 575

Fast EN - 10Base-T, 100Base-TX

PRINTING DEVICES
We need printer for creating companys report, bank statements and generate bills. Brother Laser
printer has fast printing, Monochrome output, and it is a network printer.

66

Brother Laser Printer

Monochrome laser printer prints up to 23 ppm, perfect for
home or office use
High-quality 2400 x 600 dpi resolution
Features network connectivity via wireless/wired interfaces
250-sheet capacity tray

RM 280

DATA BACKUP SYSTEM

The important part from the server is the hard disk which stores all the companys vital
information. This information needs to be protected from disaster, hardware failure and another
kind of problems related to the data.

Iomega External Harddrive 1 TB

RM 800

SERVER OPERATING SYSTEM

In using windows-based operating system for the server, users are guaranteed for support from
the Microsoft for automatic update, and easy user interface. And Microsoft Windows Server
2003 is well known as stable operating system for server. Even though its old but it has been the
choice of many professionals in the industry. The hardware requirement also matches with the
HP Proliant server.
Designed for departmental and standard
workloads, Windows Server 2003, Standard
Edition, delivers intelligent file and printer
sharing, more secure Internet connectivity,
centralized desktop policy management, and
Web solutions that connect employees.3

RM 1565

3 http://technet.microsoft.com/en-us/windowsserver/bb404900.aspx
67

SERVER SECURITY
Security is the most important things nowadays.Almost every minutes there are new viruses and
threats. For that reason we choose Symantec Antivirus corporate edition to handle the security
problems.

Symantec Norton Antivirus

2010

RM 200

CUSTOM TAILORED SOFTWARE FOR WOW

SOFTWARE REQUIREMENT & COST
In order to handle the processing of Waiters on Wheels business system we need a custom
tailored software which will be made according to the needs and requirements of WOW food
delivery system. The application shown in the prototype is built in Flash which is well known for
its easy integration on websites. Thus providing ability to easily troubleshoot it from remote sites
as well.
The custom tailored software must be able to do the following processes:
Add/modify/delete customer information.
Add/modify/ delete restaurant information.
Place Orders & calculate totals
Assign the nearest Drivers through integrates usage of map applications like Google Maps.
Manage and Generate all the bills and monthly reports.
Generate deposit slip for the bank.
Generate customers bills.
Add/modify Driver profile.
Tracking driver location using their GPS Device.

68

We are assuming the price for this software is around 5000 RM. Its one time investment giving
life long advantages.

ECONOMICAL FEASIBILITY
HARDWARE COST
NO

ITEMS

Quantity

Unit Price RM

Total price RM

Server

$3,600.00

$3,600.00

ACER Travel Mate 3270-6637

$2,285.00

$2,285.00

Hp Thin client (t5720)

$1,600.00

$3,200.00

Hp 17-inch LCD Monitor (L1710)

$580.00

$1,740.00

PCI Modem for thin client

$120.00

$240.00

Keyboard & mouse combo

$80.00

$240.00

Headset Panasonic KX-TCA86

$50.00

$100.00

Memory 2GB

$150.00

$300.00

10

Linksys 10/100 switch 24 ports

$575.00

$575.00

11

Brother printer

$280.00

$280.00

13

External HDD 500GB (Data backup)

$300.00

$300.00

15

Western digital 500GB HDD (server)

$320.00

$320.00

16

Ethernet Cable (20 meter)

$40.00

$200.00

Total

$13,380.
00

69

SOFTWARE COST

NO

ITEMS

Quantity

Unit Price RM

Total price RM

Microsoft windows server 2003

$3,565.00

$1,565.00

Symantec anti-virus 9.0 (3 users)

$585.00

$200.00

Custom tailored software for WOW

$5,000.00

$5,000.00

$6,765.00

Total

DEVELOPMENT COST

No.

Development cost

COST

Total hardware cost

$13,380.
00

Total software cost

$6,765.00

Service of the analyst

$4,000.00

Technician for hardware installation

$1,000.00

Total

$25,145.00

70

PAYBACK ANALYSIS
This graph shows us the payback amount of the invested money.
Cost of Project
= Payback Period
Annual Cash Inflow

$450,000.00
$400,000.00
$350,000.00
$300,000.00
$250,000.00

Cumulative cost

$200,000.00

Cumulative Benefits

$150,000.00
$100,000.00
$50,000.00
$0.00
Year 0

Year 1

Year 2

Year 3

Year 4

Year 5

To calculate payback anaylsis:

Cost of Project (25415.00 RM)
= Payback Period (568 Days)
Annual Cash Inflow (44730.00 RM)

71

72

IMPLEMENTATION
PROTOTYPES

73

WEBSITE INTERFACE
Main Page
This page provides access to all links including registration, menus, delivery coverage, and staff
login, contact us and feedback pages. User login section allows user to login to their profile and
order their food.

74

Registration page

Allows users to register and create their own profile.

New Order page

Allows customers to place an order and makes them able to see the prices as well.

75

Order Verification

Customer can check their details and correct their information if there is any. Method of payment
is available is provided in this page.

Menu page
This page provides links to different menus.

76

Indian Cuisine

Indian foods and price are listed in this page.

Malay Cuisine

Malay foods and price are listed in this page.

77

Chinese Cuisine

Chinese foods and price are listed in this page.

Delivery coverage

This page provides information the locations that delivery is available for.

78

Contact us page

This page provides WOW contact information.

Feed Back page

Thos page allows customers to send their feed backs regarding WOW performance.

79

Staff Login page

Staff of WOW can access to the application via this page.

Staff main page

This page provides access to different part of the application.

80

Order page

This page shows the orders status and operator is able to place a new order via this page.

New Order page

This page allows operator to place the customers order that ordering via phone.

81

Driver page

This page provides the overview of drivers status and operator can assign a new job to driver.

Sales Report page

This page provides a sales report in any date.

82

Order record page

A provides a list of all sales and its relevant information.

New Customer registration page

Allows operator to registers customer via phone.

83

Customer Detail page

Allows operator to update customers details as well as resetting their password.

84

PDA INTERFACE

Loading Screen for the PDA Application

Refreshing Status to get new Orders

Driver Updating His Status after Completion of a Delivery

85

DATABASE STRUCTURE WEBSHOTS

Customer Table

Driver Table

Open Record

Order Record

Sales Report

86

MINUTES OF MEETING
Minutes of meeting 1
Date: 15.10.2009
Start time: 3:00 pm.
End time: 7:30 pm.
Hours: 4
Venue: Zuhairs House.
Attendees: Zuhair, Amirali, Vivick, Yasau
Activities:
Discuss about the Current System.
Identify Problem and Objective.
Outcomes:
The group came up with some solution regarding current problem.
Next meetings aim
Problem and requirement specification

87

Minutes of meeting 2
Date: 18.10.2009
Start time: 5:00 pm.
End time: 8:00 pm.
Hours: 3
Venue: Amiralis House
Attendees: Zuhair, Amirali, Vivick, Yasau
Previous Activities:
Discuss about the Current System And Identify Problem and Objective. The task was completed
50%.
Activities:
1. Discussed about Current System.
2. Problems and Objective of the system are identified and listed.
3. Assumptions were made and solutions were proposed.
Outcomes:
The problems and requirements of the system are listed and documented. Some systems
requirements are specified and documented.
Next meetings aim:
Feasibility Report

88

Minutes of meeting 3
Date: 20.10.2009
Start time: 4:00 pm.
End time: 7:30 pm.
Hours: 3
Venue: Yasaus house.
Attendees: Zuhair, Amirali, Vivick, Yasau
Previews Activities:
The problems, requirements of the system and current system are listed and documented.
The task is completed.
Activities:
1. Discuss about the Feasibility Report.
Outcomes:
Start the Technical Feasibility and Discuses about it and divide each part of feasibility
reports to the member of group.
Next meetings aim:
Further discussion on Feasibility Report

89

Minutes of meeting 4
Date: 23.10.2009
Start time: 5:00 pm.
End time: 7:30 pm.
Hours: 2
Venue: Vivicks House
Attendees Zuhair, Amirali, Vivick, Yasau.
Previews Activities:
Discuss about feasibility reports and members start each part of their responsibility. The
task was done.
Activities:
1. Done Feasibility Report.
2. Start methodology and discuses about it.
Outcomes:
The group has discussed about the feasibility report and found solution for methodology.
Next meetings aim:
Discuss about technical feasibility.

90

Minutes of meeting 5
Date: 10.11.2009
Start time: 11:00 am.
End time: 11:30 am.
Hours:
Venue: Apiit.
Attendees: Zuhair, Amirali, Vivick, Yasau
Previous Activity:
The Group have discussed about feasibility report and methodology. The task was done
50%.
Activities:
Discuss about the Technical feasibility.
Outcomes:
Decision about hardware
Next meetings aim:
Discuss methodology and start process modeling.

91

Minutes of meeting 6
Date: 30.11.2009
Start time: 12:00 pm.
End time: 5:30 pm.
Hours: 5
Venue: Apiit.
Attendees: Saira Zuhair, Amirali, Vivick, Yasau.
Previous activity:
Completed technical feasibility, the task was done.
Activities:
1. Discuss about the Methodology.
2. Complete the Operation feasibility.
3. Started process modeling.
Outcomes:
The Group decides to choose which kind of methodology to use. Completed operational
feasibility and discuss about process modeling.
Next meetings aim:
Discuss about the context diagram.

92

Minutes of meeting 7
Date: 06.12.2009
Start time: 3:00 pm.
End time: 5:00 pm.
Hours: 2
Venue: Apiit.
Attendees: Saira Zuhair, Amirali, Vivick, Yasau
Previous activity:
Completed operational feasibility, methodology and discuss about context diagram. The
task completed.
Activities:
1. Discuss about the Context diagram and complete it and start DFD level 0.
Outcomes:
The Group starts DFD. First we decide about context diagram and complete it after that
we start the level 0 and discuss about it.
Next meetings aim:
Complete level 0, level 1 & start ERD.

93

REFERENCES
Gary B. Shelly, Thomas J. Cashman, Harry J. Rosenblatt,(2001) Systems Analysis and Design, 4th
Edition, United States of America, Course Technology.

Kenneth E. Kendall and Julie E. Kendall, (1999) SYSTEMS ANALYSIS AND DESIGN,4th Edition,
USA, Prentice Hall.

Penny A. Kendall, (1996) Introduction to System Analysis & Design: A Structured Approach, 3rd
Edition, USA, IRWIN
Valacich Joseph S. George Joey F. Hoffer Jeffrey A. (2001). Essentials of Systems Analysis &
Design, New Jersey, Prentice Hall, Inc.
Jeffrey L. Whitten, Lonnie D. Bentley, Victor M. Barlow,(1994) System Analysis and Design
Methods, 3rd edition, USA, IRWIN.

Jeffrey L Whitten, Lonnie D. Bentley, Kevin C. Dittman, (2000), System Analysis and Design
Methods 5th edition, New York ,Mc Graw Hill.

Gary B. Shelly, Thomas J. Cashman, Harry J. Rosenblatt,(2006) Systems Analysis and Design, 6th
Edition, United States of America, Course Technology.

David Avison & Guy Fitzgerald, (2006) information systems development methodologies,
techniques & tools, USA, McGraw Hill
Rosenblatt, Shelly, (1998). 3rd ed., USA, Operational Feasibility, System Analysis and Design,
Course Technology (Page 2.14)
Greenberg, Stephen, Christa Anderson dan Jennifer Mitchell-Jackson. (2001) Power to the
People:Comparing Power Usage for PCs and Thin Clients in an Office Network Environtment.
Scottdale, AZ.
94

Shinder, Debra Littlejohn (2001) Computer Networking Essentials, Cisco Press.

(Rod Coffin & Derek Lane, n.d) A Practical Guide to Seven Agile Methodologies [Online]
Availabel at: http://www.devx.com/architect/Article/32836/0/page/4
[Accessed on 30th November 2009]

Benjamin J. J. Voigt, 2005. Dynamic System Development Method [Online]

Available

at:

http://www.ifi.uzh.ch/req/courses/seminar_ws03/14_Voigt_DSMD_Ausarbeitung.pdf
[Accessed on 30th November 2009]
http://www.mariosalexandrou.com/methodologies/dynamic-systems-development-model.asp
[Accessed on 5th December 2009]
Martin Oliver & Grainne Conole , 1999. Selecting a Methodology [Online]
Available at: http://www.icbl.hw.ac.uk/ltdi/cookbook/preparation/selecting.html
[Accessed on 6th December 2009]

95