System Analysis and Design

AAPP007-3-2
1

Contents
Introduction .................................................................................................................... 3
Chapter 1 Planning ....................................................................................................... 4
1.1 Initial evaluation .............................................................................................. 4
1.1.1 Problem identification .............................................................................. 4
1.1.2 System Development Methodologies ...................................................... 5
1.2 Feasibility study ............................................................................................ 11
1.2.1 Operational Feasibility ........................................................................... 11
1.2.2 Economic Feasibility ............................................................................. 13
1.2.3 Technical Feasibility .............................................................................. 17
Chapter 2 Analysis ..................................................................................................... 19
2.1 Questionnaires ............................................................................................... 19
2.1.1 Questionnaires analysis .......................................................................... 23
2.1.2 Sample answer from staff ...................................................................... 24
2.1.3 Sample answer from customer ............................................................... 26
2.2 Observation ................................................................................................... 28
2.3 Process Modeling .......................................................................................... 29
2.3.1 Data Flow Diagram ................................................................................ 29
2.4 Logical Model ............................................................................................... 31
2.5 Model conceptual data .................................................................................. 31
Chapter 3 Design ........................................................................................................ 33
3.1 Logical Design or Logical Data Modeling .................................................... 34
3.1.1 Data Dictionary ...................................................................................... 34
3.2 Input & Output .............................................................................................. 35
3.2.1 OFFLINE SYSTEM .............................................................................. 35
3.2.2 ONLINE SYSTEM ................................................................................ 46
Chapter 4 Implementation .......................................................................................... 50
Chapter 5 Maintenance ............................................................................................... 51
Chapter 6 Project Management .................................................................................. 52
6.1 Gantt Chart .................................................................................................... 52
6.2 Pert Chart....................................................................................................... 53
System Analysis and Design
AAPP007-3-2
2

6.3 Workload Breakdown Matrix........................................................................ 54
Reference ..................................................................................................................... 57
Appendix A. Minutes of meetings ............................................................................... 58
Appendix B: Hardware and Software .......................................................................... 63
Appendix C: Individual Evaluation ............................................................................. 68
Appendix D: Peer to Peer Evaluation .......................................................................... 70
Appendix E: Storyboard .............................................................................................. 72



System Analysis and Design
AAPP007-3-2
3

Introduction

System analysis and design has assigned a project in which have to design a
new computer system for a restaurant to provide a systematic and effective solution.
The organization assigned for this study is a restaurant called Waiters on Wheels.
The restaurant was established in 1997 by Sue and Tom Bickford. It is a privately
owned business which rapidly gained many customers and eventually majored in the
field of delivery .The restaurant is fairly large, and it provides several types of dishes
from several well known restaurants in town. The main vision of the establishment is
to satisfy their customers and to ensure that the best quality food is given at the lowest
price. Furthermore, to give our best service to our customers and to be the best and
fastest food delivery company of choice.

In this project we analyzed the whole system of this restaurant. The
observations was that the current system is been done manually and lately. Their are
struggling to run the restaurant smoothly and systematic. In our research, we found
that the restaurant was having problems because the system was outdated and
unreliable. Due to these problems we recommended implementing a new system for
the restaurant, based on a software running platform.

Our Vision
To give our best service to our customers.
To be the best and fastest food delivery company of choice.
Usability to customer
To educate the community for a better future.
To expand our service around the world.
To give more employment.

System Analysis and Design
AAPP007-3-2
4

Chapter 1 Planning
1.1 Initial evaluation
1.1.1 Problem identification
Waiters on Wheels are a restaurant meal-delivery service started in 1997 by
Sue and Tom Bickford. The Bickfords noticed that many restaurants offer takeout
food, and some restaurants, primarily pizzerias, offer home delivery service. So the
company hire a candidate to consultant them to define what sort of a system they
needed.
Alvis is the project manager that company hires to be a consultant and define
the problem that face to the company and their system need.
Waiters on Wheels Company are facing the problem on no computerization
system to support their business. Besides that, the companies services that provide are
perform poorly. The timing that customer order or change meal after the phone call
services and the time to delivery meal to customer.
The cost of wholesale price that needed to pay by the company first then only
can get back from customer. For the cost, the wholesale price needed to store in the
computer for lately report use. The computerized report needed to support their
company business for the daily report, weekly report, and monthly report to avoid
company staffs to do it by manually. The deposit slips of the day sale need to get it
end of the day. In the case, they also need the computer system to help them to do
calculation of the sale with deposit. This also to avoid their company staff forgets to
get the deposit slips.
Problem solving:
- Organization need computerization system
- Improve the delivery system
- Staff training needed
- Computerize report
- Online ordering system added

System Analysis and Design
AAPP007-3-2
5

1.1.2 System Development Methodologies
SDLC RAD Prototyping
Introduction System
Development
Life Cycle
Waterfall Model
Systematic
approach (step
by step) that
completes all
the phases in a
system
development
Rapid
Application
Development
Collection of
process
models,
tools,
techniques
and
technologies,
with the
purpose to
reduce the
development
time of a
particular
system
Evolution
Model
Some phases
conducted
simultaneous
ly, the
product/
prototype
will undergo
continuous
improvement
until it
matures
before
delivery to
customers
Advantage Step by step
Slow but steady
System can
be developed
rapidly
Requirement
specification
is well
refined and
accurate in
accordance
with users
requirement
Development
time reduced
and reduction
in cost
Disadvantage Time
consuming
Might not
meeting long
Software
quality is
System Analysis and Design
AAPP007-3-2
6

term strategy
but fulfilling
short term
fulfilling
Little
emphasis on
quality or
consistency
of the
software
often
overlooked
or not
emphasized
Sufficient
tools must be
made
available
Report
generators/
code
Experience
required
Phase Planning
Analysis
Design
Implementation
Maintenance
No phases
list
Identify
problem
Develop
prototype
Implement &
use prototype
Revise &
enhance
prototype
Convert to
operational
system
(Table 1: The System Development Methodologies.)

According to the 3 type of system development methodologies, the method
SDLC (System Development Life Cycle) is the method that using the waterfall model
method. This method like the water fall model with step by step and systematic to run
the process and completes all the phases in a system development.
System Analysis and Design
AAPP007-3-2
7

For the RAD (Rapid Application Development) is the method that can develop
rapidly but is little emphasis on quality or consistency of the system that develop. The
prototyping method is the evolution model method with skilful and experience
developer. This method have the strong emphasis on quality of the software by build
the product or prototype to make improvement continuous until the system perfect
before handout the product or system.
Prototyping method has reduced and the reduction in cost of developer, but the
cost of the product or prototype will add into the budget that builds the system.
In conclusion, the best system development methodology is SDLC. SDLC
method is suitable to developer to develop a new system. It follows step by step to
complete the process of phases in the method of planning, analysis, design,
implementation and maintenance. With the steps, the project will run smoothly to
complete with all the method.

(Figure 1: System Development Life Cycle, Step by step.)
System Development Life Cycle
SDLC phases that use in this project.
Planning phase
Initial evaluation
Steering committee receives a project-request
Review and approve the project request
System Analysis and Design
AAPP007-3-2
8

Problem identification
Defining project scope and constraints
Report to management
Allocate resources to approved projects
Form a project development team for each approved project

Feasibility study
Operational
o A system that has operational feasibility is one that will be used
effectively after it has been developed
Economical
o A system request has economy feasibility if the project benefits of
the proposed system outweigh the estimated costs involved in
acquiring, installing and operating it
Technical
o A system request has technical feasibility if the organization has
the resources to develop or purchase, install and operate the system
Outcomes: Baseline Project Plan (BPP) or Preliminary investigation report.
Analysis phase
Determination of users requirements
Interview
Observation
Questionnaires
Study or review documents
Analyzing procedures
Structuring of system requirements
Process modeling
o Outcome: Data Flow Diagram
Logical model
o Outcome: Structured English or Decision Table
Model conceptual data
System Analysis and Design
AAPP007-3-2
9

Outcome: Entity-Relationship Diagram

Design phase
Logical Design or Logical Data Modeling
Outcome: Each data element is a raw data either kept in the systems
database or can be derived from data in the database
Physical Design or Designing Physical Files
Outcome: A set of specifications of physical file and database design
and referential integrity
Program Structure Design or Program and System structure design using
structure charts
Outcome: A set of structure charts
Designing Forms and Reports
Designing Interfaces and Dialogues
Designing Inputs and Outputs
Outcome: A set of physical design specifications for each separate part
of the system

Implementation phase
I. Coding
II. Testing
III. Evaluation
IV. Installation
V. Documenting the System
VI. Training Users
VII. Supporting Users

Maintenance phase
System Analysis and Design
AAPP007-3-2
10

a) Obtaining Maintenance Request (maintenance-demand)
b) Transforming Request into Changes (change mapping)
c) Designing Changes (change design)
d) Implementation Changes (change implementation)
Outcome: A new version of the software and design documents
Types of maintenance
o Corrective maintenance
o Adaptive maintenance
o Preventive maintenance
System Analysis and Design
AAPP007-3-2
11

1.2 Feasibility study
1.2.1 Operational Feasibility
Operational feasibility is the process of assessing the degree to which a
proposed system solves business problem or takes advantage of business opportunities.
This will be refers to a system that users will accept and use effectively to support
business objectives. In this feasibility, PIECES framework that uses to identify
operational problems to be solved and their urgency in a project, PIECES framework
is form by the Performance, Information, Economy, Control, Efficiency and Services.
Performance
- In our generation, the current manual paper system is being the big problem on
the business operation. The troublesome become more in the form of record,
storing information and update. The response time need more attention for the
restaurants in food information always lag changes and driver delivery
information

Information
- The data input is difficult and not accurate, the manual paper system will
increase the probabilities of input errors and the recording is hard to modified
and undo the data capture mistake.
- The stored data is not accessible, not well to organized and secure from
accident. The manual paper system is not accessible to the data, the data
information are become more and more difficult to look through and the time
consuming to find from the files and records on the papers, or organize, when
the amount of information increases. Besides that, the paper records can be
lost easily and get damaged or worn out.
- Data output will lack of necessary information and information is difficult to
produce. The quick format is lacking of information about the order goes to
which restaurant and a lot of management level information. The day deposit
slip, week restaurant payment, daily sales and weekly sales reports is hard to
produce and take time to do report mean time consume a lot.
System Analysis and Design
AAPP007-3-2
12


Economy
- Profits, new markets can be explored when a new system that introduce more
future growth, empower the business to employ more drivers and staff.
Besides that, can contract more restaurants to cover wider area, but most
important is a new online ordering system needed. With the new system, the
current marketing can be improved. More data can be stored and the data can
be use for analysis in future, there will have more innovative new marketing
possible with the new online website.
- The costs are unknown and untraceable, the overall delivery quality decrease
and customer have more complaints which the restaurant will potentially lose
customers. Besides that, the workload increase and the working hours getting
longer make the sales goes up. Staffs being pressure with the stress from
organization, made the staffs decoupled from the company vision, and the
staff become more dissatisfied in this fact, the staffs are less willing to help the
sales to increase.

Control
- The decision making and processing errors occur from the security and control.
The date information poses threats on making errors in decisions like the
allocating delivery jobs to the right drivers. The current system heavily rely on
human, this human error that cannot be avoided part in the process.

Efficiency
- The efficiency on people, machines, or computers will waste materials and
suppliers. The material required and effort required for tasks is excessive in
efficiency. The business run through there will have more data storage needed
and the cost of retaining these papers and storages will increase. The workload
System Analysis and Design
AAPP007-3-2
13

increases by the inefficient system, man power are wasted in the process of
recording, updating and search information.

Services
- The system is awkward to use, not coordinated with other systems, and
inflexible to new or exceptional situations. The hard search for information,
will time consuming to generate important critical information. The current
system data format cannot be reused for other system like the online website
system. The current systems are not meant easily to adapt changes but it will
take a lot of efforts to make changes to adapt to new or exceptional situations.

1.2.2 Economic Feasibility
In this Economic Feasibility study, a system request in the project benefits of
the proposed system outweigh the estimated costs involved in acquiring, installing
and operating it. The estimation of the cost the business to develop the system and the
servicing & maintenance needed. Based on the data of the business, we can get the
estimate return of investment in this project to the business in term of profits.

Cost Benefit
Table below show the costs of the project to work out the development cost of the
project.
DEVELOPMENT COSTS
Personnel: Hours Cost/Unit Total
2 System Analysts 240 20 9600
2 Programmer/ Analysts 240 20 9600
1 System Librarian 250 15 3750
New Hardware & Software
1 Workstation 3000 3000
System Analysis and Design
AAPP007-3-2
14

2 Handheld PDAs 1200 2400
3 Computer 2400 7200
Others 0
Total 35550

The following table is the estimates running cost of the system to the business.
PROJECT ANNUAL OPERATION COSTS
Personnel: Total
1 Programmer / Analysts 3000
1 System Librarian 1000
Expenses:
1 Maintenance 0
Internet 3000
Hosting 599
Total 7599

From above:
The total development cost is RM 35,550
The total annual running cost is RM 7,599

Payback Analysis
This is to analyze the benefit over the next 4 years against the total cost of the
project to justify the investment value of the project. Below is the payback analysis
table for the next 4 years and the 4% inflation value being the discount value.
Payback Analysis
Cash flow description Year 0 Year 1 Year 2 Year 3 Year 4
Development Cost 35,550
System Analysis and Design
AAPP007-3-2
15

Operation & maintenance cost 7,599 7,903 8,219 8,548
Discount factors for 12% 1 0.962 0.925 0.888 0.851
Time-adjusted costs 35,550 7,399 7,399 7,399 7,399
Cumulative time-adjusted costs over lifetime 35,550 42,949 50,348 57,747 65,146

Benefits derived from operation of new
system 0 10,599 26,498 52,996 79,494
Discount factors 1.00 0.96 0.93 0.89 0.85
Time-adjusted benefit 0 9,399 25,298 51,796 78,294
Cumulative time-adjusted benefits over
lifetime 0 9,399 34,697 86,493 164,787
Cumulative lifetime time-adjusted costs
benefits -35,550 -33,550 -15,651 28,746 99,641

The benefit value in the table is based on the increase of profit growth. The
current growth rate in the business is about 2%, assume that the new system is up; the
system will help the business to reduce the cost and increase the sales. The system
will help the business to achieve higher annual growth rate, assume that in second
year growth rate increase to 3%, and the subsequent years are 5%.
The following table are present the assumption of the annual sales.

8,706
14,771
33,269
53,047
0
10,000
20,000
30,000
40,000
50,000
60,000
Year 0 Year 1 Year 2 Year 3 Year 4
The difference
System Analysis and Design
AAPP007-3-2
16


From the chart above, Waiters on Wheels start to get the benefit back with the
new system from 2
nd
year. Although take 2 years to break the investment business
spend on the project, lastly the end of 4 years period running business in Waiters on
Wheels, the benefit outweighs the cost significantly.

ROI/NPV Analysis
In ROI/NPV analysis, there is similar to the Payback Analysis. The calculation
is based on the Payback Analysis just the way to present is few thing change only.\
Net Present Value Analysis
Cash flow description Year 0 Year 1 Year 2 Year 3 Year 4
Development Cost 35,550
Operation & maintenance cost 7,599 7,903 8,219 8,548
Discount factors for 12% 1 0.962 0.925 0.888 0.851
Time-adjusted costs 35,550 7,399 7,399 7,399 7,399
Cumulative time-adjusted costs over lifetime

65,146

Benefits derived from operation of new
system 0 10,599 26,498 52,996 79,494
Discount factors for 12% 1.00 0.96 0.93 0.89 0.85
Year 0 Year 1 Year 2 Year 3 Year 4
Cumulative lifetime
time-adjusted costs
benefits
-35,550 -33,550 -15,651 28,746 99,641
-60,000
-40,000
-20,000
0
20,000
40,000
60,000
80,000
100,000
120,000
R
M

Cumulative lifetime time-adjusted
costs benefits
System Analysis and Design
AAPP007-3-2
17

Present value of annual benefit 0 9,399 25,298 51,796 78,294
Total present value of lifetime benefits

164,787
Net Present Value

99,641
The ROI calculation:

1.2.3 Technical Feasibility
A system request has technical feasibility if the organization has the resources
to develop or purchase, install and operate the system.
The Basic System Requirement
- Workstation
- Database
- Server
- Payment System
Basic Hardware Requirement
- PC or Laptops
o Dell Inspiron 15
o Dell Inspiron 14
o HP TouchSmart 600 Quad series
- Modem
- PDA or mobile phone
Software Requirement
- Operating System
o Window 7
System Analysis and Design
AAPP007-3-2
18

- Microsoft Office 2007
o Microsoft Office Professional 2007
o Microsoft Office 2007 Blue Edition Precracked
o Microsoft Office Access 2007
o Microsoft Office Project Professional 2007
o Microsoft Office Visio Professional 2007
o Any Microsoft Office
Service Requirement
- Internet access services
The new system is easy to learn and the expectation of learning the system is low.
The software needed to use the on-going licensed software, the on-going software will
help and support from us will be required.
The domain name and web hosting service or the dedicated ISP service are
required in the project. For the PDA or mobile phone will possibly require Internet
access service and Wi-Fi support from the mobile phone providers. The technologies
required for the systems can get in the market easily.
With the basic software and hardware support, it will increase the entire business
sales. The efficiency and productivity of staff will increase to the maximum with their
good performance.


System Analysis and Design
AAPP007-3-2
19

Chapter 2 Analysis
2.1 Questionnaires
Below are the questionnaires for staff who work in Waiters on Wheel.
Please answer with your truly opinion.
1. How long had you work?
a. Less than 1 year
b. 2 3 year
c. 4 year above

2. How do you deal with the problem that customer change the meal set?
a. Change the meal set for the customer
b. Change the meal set for the customer with extra charges
c. Do nothing to the customer meal change ( Ignore )

3. How do you deal while the customer changes the time to get their meal?
a. Change the time and let the staff know
b. Change the time in the system and confirm with the customer
c. Check the time and let the customer know is it the time still available
for delivery the meal

4. What is your opinion about the current delivery system and service?
a. Good
b. Average
c. Bad
Reason:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
System Analysis and Design
AAPP007-3-2
20

5. If any new system applies in the organization, what system you hope the
system is?
a. Simple
b. Friendly use
c. Not complicated
d. All of them
e. Other :
_________________________________________________________
_________________________________________________________
_________________________________________________________

6. If the online ordering system applies, what would you think the system will
increase the entire delivery system?
a. Yes
b. No
c. Maybe

7. Do you think a professional staff of Waiters on Wheel need training?
a. Yes
b. No
Reason:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________


System Analysis and Design
AAPP007-3-2
21

Below are the questionnaires for customer. We would like to get the feedback from
you all about the system that we use.
Please answer with your truly opinion.
1. Will you use online or phone call ordering your meal?
a. Yes
b. No
Reason:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________

2. How often do you use online or phone call ordering your meal in a week?
a. 1 3
b. 4 6
c. Everyday
d. No

3. Do you face any problem with the online or phone call ordering system?
a. Cannot call in to the service
b. Order until half only disconnect to the phone call
c. Internet disconnect
d. While fill in the form almost finish, disconnect all the data need to re-
fill in a gain

4. Do you think an online or phone call ordering system needed to set timing for
delivery to you?
a. Yes (15 min 20 min)
b. Yes (20 min 25 min)
System Analysis and Design
AAPP007-3-2
22

c. At least get within 30 45 min, other not a problem
d. No

5. Do you recommend the online or phone call ordering system to your friends
and family?
a. Yes
b. No
Reason:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________

6. What is your opinion about the system that we using?
a. Good
b. Average
c. Bad

7. For you as a guess of Waiters on Wheel, do you think the system we using
now need to improve?
a. Yes
b. No
Reason:
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
System Analysis and Design
AAPP007-3-2
23

2.1.1 Questionnaires analysis
Below is the analysis of the questionnaires for staff and customer of the
Analysis bar chart of questionnaires for staff works in Waiters on Wheel

(Chart 1: Staff works in Waiters on Wheel.)

Analysis bar chart of questionnaires for customer

(Chart 2: customer of Waiters on Wheel.)

0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
1 2 3 4 5 6 7
e
d
c
b
a
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
1 2 3 4 5 6 7
d
c
b
a
System Analysis and Design
AAPP007-3-2
24

2.1.2 Sample answer from staff
Method: Using pen and the question paper, ask few staff to answer the questionnaires.
Below are the questionnaires for staff who work in Waiters on Wheel.
Please answer with your truly opinion.
1. How long had you work?
a. Less than 1 year
b. 2 3 year
c. 4 year above

2. How do you deal with the problem that customer change the meal set?
a. Change the meal set for the customer
b. Change the meal set for the customer with extra charges
c. Do nothing to the customer meal change ( Ignore )

3. How do you deal while the customer changes the time to get their meal?
a. Change the time and let the staff know
b. Change the time in the system and confirm with the customer
c. Check the time and let the customer know is it the time still available
for delivery the meal

4. What is your opinion about the current delivery system and service?
a. Good
b. Average
c. Bad
Reason:
The delivery system and services not so efficiency, but still can improve__
time by time._________________________________________________

5. If any new system applies in the organization, what system you hope the
system is?
System Analysis and Design
AAPP007-3-2
25

a. Simple
b. Friendly use
c. Not complicated
d. All of them
e. Other

6. If the online ordering system applies, what would you think the system will
increase the entire delivery system?
a. Yes
b. No
c. Maybe

7. Do you think a professional staff needed in Waiters on Wheel?
a. Yes
b. No
Reason:
In Waiters on Wheel really need more professional staff to serve our_____
customer in order to avoid misunderstanding between staff and customer._


System Analysis and Design
AAPP007-3-2
26

2.1.3 Sample answer from customer
Method - using pen and the question paper, when reach delivery to customer. Ask
customer help to fill in the questionnaires form.
Below are the questionnaires for customer. We would like to get the feedback from
you all about the system that we use.
Please answer with your truly opinion.
1. Will you use online or phone call ordering your meal?
a. Yes
b. No
Reason:
Phone call ordering meal._______________________________________

2. How often do you use online or phone call ordering your meal in a week?
a. 1 3
b. 4 6
c. Everyday
d. No

3. Do you face any problem with the online or phone call ordering system?
a. Cannot call in to the service
b. Order until half only disconnect to the phone call
c. Internet disconnect
d. While fill in the form almost finish, disconnect all the data need to
re-fill in again

4. Do you think an online or phone call ordering system needed to set timing for
delivery to you?
a. Yes (15 min 20 min)
b. Yes (20 min 25 min)
c. At least get within 30 45 min, other not a problem
System Analysis and Design
AAPP007-3-2
27

d. No

5. Do you recommend the online or phone call ordering system to your friends
and family?
a. Yes
b. No
Reason:
Depend on time and place, and give the right suggestion to my friend.

6. What is your opinion about the system that we using?
a. Good
b. Average
c. Bad

7. For you as a guess of Waiters on Wheel, do you think the system we using
now need to improve?
a. Yes
b. No
Reason:
Should improve in the way of services and the delivery driver wont send
wrong meal.__________________________________________________



System Analysis and Design
AAPP007-3-2
28

2.2 Observation
In the fact-finding of observation, our group has chosen the restaurant of Mc
Donald, Pizza Hut, and KFC to be observed. When in the observation time, our group
member does not use this opportunity to have a meeting. We decide to have our lunch
in the restaurant that we chose and with few groups of people go there enjoy our meal
over there. The analysis will be the way descript in the paragraph below.
The way we observes is how they provide their service, the services include the
delivery system, face to face order system, calling order system and their staff
performance.
First we talk about the KFC business system they use, KFC restaurant they use
the delivery system but their delivery system since start until now still have not
improved. We can say that, their delivery system just wills delivery to the customer
order near to the shop around 2-3 km area. So they have no strong delivery system to
support their business, they using the face to face system to take order more than
delivery system. Normally, the customer wanted to have KFC to be their lunch, they
will go to the restaurant directly. Customer will enjoy their meal in the restaurant,
they will feel the restaurant environment, they way all customer enjoying meal like
their slogan Finger Licking Good. By the way, there is less KFC restaurant use the
online order system in their business.
Next our observation restaurant is the Pizza Hut; their delivery system is much
stronger than the KFC restaurant. Their delivery system need to delivery on time and
let the meal still in hot. Many customers like to have their lunch or dinner by using the
phone call delivery system. Their system is much efficiency then other restaurant, this
was support their restaurant business keep growth in period. The step in customer
enjoy their meal as well as the service provided, there will have the environment
feeling and the way staff services with their performance.
Last restaurant is the Mc Donald fast food restaurant (MCD); delivery system
in the restaurant is almost same as the Pizza Hut restaurant. In group of people,
normally they hungry the first idea will be the MCD, because of their service that
provided have phone call order system, step in order, delivery system and drive-thru
system make their business growth in period, like the slogan Im loving it..
System Analysis and Design
AAPP007-3-2
29

2.3 Process Modeling
Process modeling is to model solution processes of the system in the
project. With the process modeling, there will able to should out the data flow
diagram. In the data flow diagram, there is some separation of the type of
showing the data. The type of data flow diagram as context diagram, level 0
diagram and level 1 diagram.

2.3.1 Data Flow Diagram
[Link] Context Diagram
Context diagram is to show the external entities and the data flows. Also
knows as terminators, it show out a person, department, outside organization or other
information system that provides data to the system or receives data from the system
in the diagram, it may be a source, a sink or both. The source can be an external entity
that supplies data as origin. The sink will be an external entity that receives data as
destination. Context diagram is named by using the singular form of the name.

Customer
Restaurant Driver Food Ordring
Staff
Order Info
Financial Info
Order Food Info Order Delivery
Staff info


System Analysis and Design
AAPP007-3-2
30







[Link] Level 0 Diagram
Customer
Driver
Restaurant
Staff
Customer info
2.0
Process
Orders
3.0
Driver
Orders
4.0
Process
Payment
1.0
Take order
Food Info
Orders Info
D2 Foods
D3 Orders
D3 Drivers
D4 ID
D1 Customers Customer Info
Foods Info
Foods Info
Order Info
Order Info
Order Info
Order status
Orders info
Food available
Customer info
Order delivery info
Driver location
Delivery status
Driver info
Driver location
Driver status
End of day reports
Order info
Weekly sales report
End of day deposit slip
End of week restaurant payments
Payment info retrieval
Payment info

System Analysis and Design
AAPP007-3-2
31

2.4 Logical Model

Logical model is the representations of the model in the solution logic.
With this, the logical model can present in 3 ways that is the structure English,
decision table and decision tree. Decision table is a matrix representation of
the logic of a decision which specifies the possible conditions for the decision
and the resulting actions.
Below decision table is based on the statement of the project problem.
Without
computerization
Y Y Y Y Y Y Y Y N N N N N N N N
With computerization Y Y Y Y N N N N Y Y Y Y N N N N
Online ordering Y Y N N Y Y N N Y Y N N Y Y N N
Delivery system Y N Y N Y N Y N Y N Y N Y N Y N
Business drops X
Business growth X X
Both X X X X X X X X X X X X X

Without computerization Y Y N N
With computerization Y N Y N
Business Drops X
Business Growth X
Both X X

Online Ordering Y Y N N
Delivery system improved Y N Y N
Business Drops X
Business Growth X
Both X X


2.5 Model conceptual data
Model conceptual data is to show the ER diagram. An ER diagram is
models that identify the concepts that exist in the system and the relationships
between those entities.
System Analysis and Design
AAPP007-3-2
32




System Analysis and Design
AAPP007-3-2
33

Chapter 3 Design
In this chapter design, it is to show out the logical design or logical data modeling,
physical design or designing physical files, the program structure design or program
and system structure design using structure charts, designing forms and reports,
designing interfaces and dialogues and designing inputs and outputs of the project.
For the logical design or logical data modeling, it is to develop a logical data
modeling for each view of the application using normalization principles and translate
the conceptual E-R data model into normalized relations. With this the end of the
project will show out each data element is a raw data either kept in the systems
database or can be derived from data in the database.
Physical design or designing physical files is to choosing the storage formal or the
data type in use, its group the attributes from the logical data model into physical
records. Select media and structures for storing data to make access more efficient. By
the physical design or designing physical files shows a set of specifications of
physical file and database design and referential integrity.
Program structure design or program and system structure design using structure
charts to show out a set of structure charts of the project. Besides that, designing
forms and reports, designing interfaces and dialogues and the designing inputs and
outputs is almost same as the storyboarding type. This will show a set of physical
design specifications for each separate part of the system.
In this chapter, the data of the project will show in the appendix E with the
drawing of the storyboarding.





System Analysis and Design
AAPP007-3-2
34

3.1 Logical Design or Logical Data Modeling
3.1.1 Data Dictionary
External Entities
External Entity Description Input Dataflow Output Dataflow
Customer Order food by
using the phone
call system or
website
Order details
Customer detail
Foods info and
Customer info
Driver Get order to
delivered
Order delivery
information
Order delivery
information and
status
Restaurant Information of food
and provide food.
Return payment
slip weekly.
Order info and
weekly statement
Food available info
Staff Receive the
financial info
Deposit slip,
weekly sale report
and monthly report


Data Store
Data Store Description Input dataflow Output Dataflow
Customers All customer info Customer info Customer info
Drivers All driver info Driver info Driver info and
status
Foods All food info Restaurant info Food info
Id Payment detailed
info
Payment info Payment info



System Analysis and Design
AAPP007-3-2
35

3.2 Input & Output
3.2.1 OFFLINE SYSTEM
In this system we also create offline system. We create offline system in
Microsoft Access. This system will use by staff to take order from customer by phone
and online. In detail, this system contains few forms. That is Customer Information
form, Driver information form, Employee information form, Restaurant information
form, Food ordering form, Food list form, Weekly report form, Monthly report form,
Switchboard item form, Transaction count form, and Feedback form. These forms are
to take the order and delivery the food to customer. Follow on are the forms and the
explanation.

Diagram 1: Customer information
This is customer information form. In this form contained Customer ID,
Customer name, IC number, Mobile number, Home address and Postcode. This
system is creating to have clear and systematic information. It is easy to refer by staff
and deliver the information in the right circumstances and prompt. Furthermore, it
delivers the relative and relevant information about the ordered food. Following form
shows driver details.

System Analysis and Design
AAPP007-3-2
36


Diagram 2: Driver information
This is driver information form. In this form contained Driver ID, Driver name,
Driver IC number, Driver mobile number, Driver home address, and postcode, status,
and vehicle number. We required this information to safety purpose and legal.

Diagram 3: Driver Information Report
These are driver details. It shows they have three drivers.
System Analysis and Design
AAPP007-3-2
37



Diagram 4: Employee Information
This is employee information form. In this form contained Employee ID,
Employee name, Employee IC number, Employee mobile number Employee home
address, and Employee position. We required this information to safety purpose and
legal.
System Analysis and Design
AAPP007-3-2
38



Diagram 5: Employee Information Report
It shows employee detail information report.

System Analysis and Design
AAPP007-3-2
39


Diagram 6: Restaurant Information
This is restaurant information form. This form is to key in the restaurant
information, restaurant name, restaurant address, and restaurant email id.

Diagram 7: Restaurant Information Report
System Analysis and Design
AAPP007-3-2
40

This report contained 5 restaurant information details. That is restaurant KFC,
restaurant Macdonald, restaurant Pizza Hut, restaurant Pontain Noodles, and
restaurant Hong Kong Snack.

Diagram 8: Food Ordering
This is food ordering form. This form to take order from customer and it
generate the total billing system.
System Analysis and Design
AAPP007-3-2
41


Diagram 9: Food Ordering Report
It shows the food ordering report. At last it show the total bill of the order
items.

System Analysis and Design
AAPP007-3-2
42


Diagram 10: Food List
This is food list form. After complete the food ordering form, this form shows
the food list form to confirm the order.

Diagram 11: Food List Report
System Analysis and Design
AAPP007-3-2
43

This is food list report. This report is to check for the food available and
confirm the order.

Diagram 12: Monthly Report
This is monthly report form. Its shows the weekly sales report to the Waiters
on Wheel restaurant.

System Analysis and Design
AAPP007-3-2
44


Diagram 13: Weekly Report
This is weekly report form. It shows the weekly sales report by the Waiters on
Wheel restaurant. It is auto generate billing system.

System Analysis and Design
AAPP007-3-2
45


Diagram 14: Home Page
This is home page to this system. It link to specific page. It link by hyperlink.
All buttons link specific page. The button in the bottom right is to close the main form.

System Analysis and Design
AAPP007-3-2
46


Diagram 15: Report Page
This is report generator page, from home page can link to this report generator
page with the report button. It all refers to specific form. Beside the each specific
button have the printer icon; the icon is the shortcut button to print out the report. And
the bottom right icon with a door, the button is to close the form of report generator.

3.2.2 ONLINE SYSTEM
In this system also required a online system. It used to customer to make order
from online. These systems create in Microsoft Web Expression 3. This software
helps us to create web page easily. Customer also anytime can access this page by
online. This web page contained home page, menu, order, about us, and contact us.
System Analysis and Design
AAPP007-3-2
47

Background image download by Google search engine. And it edit by using Picasa
software. The title is edited. Follow on are the web pages and explanation.

Diagram 16: Home Page
This web page is the home page to the online system. This page contained four
buttons that are menu button, order button, about us button, and contact us button. All
button link to the specific page, it just the link button for customer easy enter the page
they needed.

System Analysis and Design
AAPP007-3-2
48

Diagram 17: Menu Page
This is menu page. It link from home page menu button. Menu page contained
few restaurant images. Restaurants are KFC, MCDONALD, CHINESE
RESTAURANT, and PIZZA HUT.

Diagram 18: Order Page
This is order page. It link by menu page. Customer can make order by click
the checkbox. After click the checkbox customer can click submit button to confirm
the order.
System Analysis and Design
AAPP007-3-2
49


Diagram 19: Login Page
This is login page. This page contained customer name, home address, phone
number, and type of payment. After key in the details customer can submit.

Diagram 20: Contact Us
This is contact us page. This page is to help customer to ask question to
Waiters on Wheel restaurant.
System Analysis and Design
AAPP007-3-2
50

Chapter 4 Implementation
In implantation phase, the coding, testing, evaluation, installation,
documenting the System, training users and supporting users are important for
a development to implement a new system.

Coding is a process of translating a design into machine-readable codes
and brings out the source code and a workable new system.

For Testing is any activity aimed at evaluating an attribute or
capability of a program or system and determining that it meets required
results with the test case, test plan, final performance test metrics and a tested
system

For Evaluation is to verify that the new system meets specified
requirements, complies with user objectives and achieves the anticipated
benefits with the outcome of a system that meets requirements.

For Installation is the organization process of changing over from the
current information system to a new one with fully converted data files and
installed system.

Documenting the System and training users is to doing the report of the
system that implemented and give training to the user to let the user know how
to control easily. Physical training is provided for organization to use the
system that implemented.

Supporting users is the system documentation, user documentation,
publishes documents user training plan, user training modules and user
support plan that needed to give support to the system that was implemented.
One of the documentation will be this project report.
Database access
Internet application

System Analysis and Design
AAPP007-3-2
51

Chapter 5 Maintenance
The service maintenance are obtaining maintenance request (maintenance-
demand) to the system. The maintenance will bring the transforming request into
changes mean the change of the mapping system, each time the service maintenance
goes on. Besides that, the maintenance will also change the design when needed.
Lastly, the maintenance will bring the changes of implementation of the system and
finally will produce a new version of the software and design documentation.
There is few types of maintenance service can be done. There is the corrective
maintenance, adaptive maintenance and preventive maintenance. The corrective
maintenance is the types that refer to changes made to repair defects in design, coding,
or implementation of the system. It usually happened after installation. It simply
focuses on removing defects from the system without adding new functionality.
Adaptive maintenance is the type that involves making changes to an
information system to evolve its functionality to changing business needs or to
migrate it to a different operating system.
Preventive maintenance is the type that involves changes made to a system to
reduce the chance of future system failure.

Final Analysis
We completed the project to our at most expected level. We consider the
developed System to be a systematic as we included the entire necessary prompt in
order to provide a solution to the organization. Also the system we developed in
Microsoft Access is a very user friendly and simple system for the user to understand
which covers both end validations.


System Analysis and Design
AAPP007-3-2
52

Chapter 6 Project Management
6.1 Gantt Chart
This Gantt chart will be the simple form and more detail will be in the system
development methodologies System Development Life Cycle. Below is the table
part of the Gantt chart.

And this will be the bar chart of the progress.

The full view will be this type.


Gantt chart is almost like minutes of meeting. Its a schedule which includes
our separation of tasks. More, it alerts us on our date and duration. It helps a lot to
complete our system and assignment as effective and fast.


System Analysis and Design
AAPP007-3-2
53

6.2 Pert Chart

System Analysis and Design
AAPP007-3-2
54

6.3 Workload Breakdown Matrix
Work Load Yu Kang Wei Natheni A/P Raj
Introduction *
Planning
- Initial Evaluation * *
1. Problem Identification * *
2. System Development Methodologies *
- Feasibility Study
1. Operational Feasibility *
2. Economic Feasibility *
3. Technical Feasibility *
Analysis
- Questionnaires * *
1. For Staff *
2. For customer *
3. Analysis data * *
- Observation *
- Data Flow Diagram * *
- Decision Table
- ER Diagram *
Design
- Logical Design * *
- Physical Design * *
- Structure Chart *
- Forms and Report *
- Interfaces * *
- Input and Output * *
Implementation
- Coding (database access) *
- Coding (Internet application) *
- Testing * *
System Analysis and Design
AAPP007-3-2
55

- Evaluation * *
- Installation *
- Documenting System *
- Training User *
- Supporting User *
Maintenance
- Corrective Maintenance *
- Adaptive Maintenance *
- Preventive Maintenance *
Project Management
- Gantt Chart *
- Pert Chart *
- Workload Matrix *
Minutes of Meeting *













System Analysis and Design
AAPP007-3-2
56

CONCLUSION
In conclusion, the best system development methodology is System
Development Life Cycle. SDLC method is suitable to developer to develop a new
system. It follows step by step to complete the process of phases in the method of
planning, analysis, design, implementation and maintenance. With the steps, the
project will run smoothly to complete. Moreover, it is systematic to run the process.
The system analysis has guide on systems thinking, organization knowledge,
problem identification, problem analysis & solution. Process of scoping, planning,
staffing, organizing, directing & controlling the development of an acceptable system
at minimum cost within a specified time frame and is an on-going process which is
very important throughout the entire SDLC. By following the steps and process has
help to create the system and develop it systematic and successfully.
GANTT chart is a horizontal bar chart that graphically displays the time
relationships between the different tasks in a project. It was used throughout the
minutes of meeting. Furthermore, by doing work breakdown structure (WBS) which
is the process of dividing the project into manageable tasks and logically ordering
them to ensure a smooth transition between tasks. It helps us to be schematic and
discipline in this project.
to show the processes that data undergo in a system
to show how data moves and changes through an information system in a
graphical, top-down fashion
to produce a logical model of an information system in a simple, direct way

System Analysis and Design
AAPP007-3-2
57

Reference
Dell Home page. (n.d.). Retrieved from Dell Home page: [Link]
HP Compaq Home page. (n.d.). Retrieved from HP Compaq Home page:
[Link]




System Analysis and Design
AAPP007-3-2
58

Appendix A. Minutes of meetings

Minute of meeting October 21, 2010
Date: October 21, 2010
Time: 08.30 10.30
Venue: TPM ENT 3 1-4: Room 1

Attended Members:
- Yu Kang Wei
- Natheni A/P Raj

Meeting topics:
- Work load assigning
- Time frame discussion

Discussion outcome:
Contact numbers collected and know each other.
Start discussion on SAD Group Assignment 2010 initial evaluation Problem
identification.
And idea for the problem solving to the project.


Minute of meeting October 28, 2010
Date: October 28, 2010
Time: 08.30 10.30
Venue: TPM ENT 3 1-4: Room 1

System Analysis and Design
AAPP007-3-2
59

Attended Members:
- Yu Kang Wei
- Natheni A/P Raj

Meeting topics:
- Gantt chart and Pert chart discussion
- Systems Development Methodology discussion

Discussion outcome:
Lecturer review October 21, 2010 work.(Initial Evaluation)
Discussion on the Gantt chart and Pert chart
Each member does one of the charts.
Microsoft Office Visio 2007 are being use to draw out the chart.
Documentation will use the standard software Microsoft Office 2007
Compare the Systems Development Methodology.


Minute of meeting November 4, 2010
Date: November 4, 2010
Time: 08.30 10.30
Venue: TPM ENT 3 1-4: Room 1

Attended Members:
- Yu Kang Wei
- Natheni A/P Raj

Meeting topics:
- Feasibility study discussion
System Analysis and Design
AAPP007-3-2
60


Discussion outcome:
Lecturer review October 28, 2010 work.(Gantt chart and Pert chart)
Lecturer review October 28, 2010 work.(System Development Methodology)
Discussion on Feasibility study.

Minute of meeting November 11, 2010
Date: November 11, 2010
Time: 08.30 10.30
Venue: TPM ENT 3 1-4: Room 1

Attended Members:
- Yu Kang Wei
- Natheni A/P Raj

Meeting topics:
- Fact-finding discussion

Discussion outcome:
Fact-finding discussion.
Separate the work to each member to do the fact-finding.

Minute of meeting November 18, 2010
Date: November 18, 2010
Time: 08.30 10.30
Venue: TPM ENT 3 1-4: Room 1

Attended Members:
System Analysis and Design
AAPP007-3-2
61

- Yu Kang Wei
- Natheni A/P Raj

Meeting topics:
- Data Flow Diagram discussion

Discussion outcome:
Lecturer review October 28, 2010 work.(Fact-finding)
Each member shows their work of Data Flow Diagram.
Compare both work and draw out a new Data Flow Diagram.
New Data Flow Diagram did lecturer review.


Minute of meeting November 25, 2010
Date: November 25, 2010
Time: 08.30 10.30
Venue: TPM ENT 3 1-4: Room 1

Attended Members:
- Yu Kang Wei
- Natheni A/P Raj

Meeting topics:
- Input and Output discussion

Discussion outcome:
Discussion about the input output of the system.
Each group member does one system.
System Analysis and Design
AAPP007-3-2
62

The work should show out the print screen of the input and output.

System Analysis and Design
AAPP007-3-2
63

Appendix B: Hardware and Software

Inspiron 15

Online Price RM 1,499.00

Build My Dell
Genuine Windows 7 Home Premium 64bit (English)
Intel Pentium Dual Core T4500 (2.3Ghz, 800MHz, 1M cache)
1Yr Ltd Hardware Warranty, InHome Service after Remote Diagnosis
Dell Online Backup 2GB
Accessorise My Dell
Microsoft(R) Office Starter 2010
No Carrying Case
Also Includes
LCD Back Cover - Black
McAfee SecurityCenter (Multi-Language) - 15 Months Version
15.6 Widescreen HD WLED display with TrueLife
2GB (1 X 2 GB) 1 DIMM DDR3 1333Mhz
320GB 5400RPM Hard Drive
DVD+/-RW Optical Drive
Mobile Intel Graphics Media Accelerator (GMA) 4500MHD
Dell Audio - 2x1 watt
65W AC Adapter
Atheros 802.11n WiFi Module (MY)
Dell Wireless 365 Bluetooth Internal Mini-Card (MY)
Inspiron 15 (N5030) - Direct Base
Dell(TM) Keyboard with Touchpad (English)
T510905MY-Inspiron 15
Integrated 0.3MP Webcam and Analog Microphone
Inspiron(TM) Delivery Charges (East Malaysia)
System Analysis and Design
AAPP007-3-2
64

Laptop Batteries Carry One Year Warranty Only From Invoice Date
Dell's Terms and Conditions apply
Great Technical Tips & Information available 24x7 at [Link]
3-in-1 Flash Memory Reader: SD/MMC/MS
Integrated 10/100 Ethernet LAN
Discount is only valid if the corresponding upgraded item is selected above.
Limited time promotional offer only. No further discounts apply.
APCC Info Mod
Direct Ship Info
Resource DVD
Adobe Reader 9.0
Dell(TM) Welcome
Dell(TM) Connect Software
Skype Software
Energy Star Label
Break the Seal Sticker
Technical Support
NB-OS-CTO Handling and Insurance Charges (Malaysia)
6-cell Lithium Ion Battery
Dell PC Restore Software
(Dell Home page)

Inspiron 14
Online Price RM 1,799.00
Build My Dell
Genuine Windows 7 Home Premium 64bit (English)
LCD Back Cover - Black
Intel Core i3-370M Processor (2.4Ghz, 4Threads, 3M cache)
McAfee SecurityCenter (Multi-Language) - 15 Months Version
1Yr Ltd Hardware Warranty, InHome Service after Remote Diagnosis
System Analysis and Design
AAPP007-3-2
65

Dell Online Backup 2GB
Accessorise My Dell
Microsoft(R) Office Starter 2010
Media Kit Not Included
Targus Synergy Top Loading Case 15.6" (DFD)
Also Includes
14.0 HD WLED Glossy (1366x768)
2GB (1 X 2 GB) 1 DIMM DDR3 1333Mhz
320GB 5400RPM Hard Drive
DVD+/-RW Optical Drive(Win7 Home Premium)
Intel HD Graphics
Integrated Stereo Sound
2.2AHr 6-cell Lithium Ion Battery
65W AC Adapter
Dell Wireless 1501 802.11b/g/n Half Mini Card (MY)
Dell Wireless 365 Bluetooth Internal (2.1+EDR) Mini-Card (MY)
Dell(TM) Keyboard with Touchpad (English)
Genuine Windows 7 OS Label
Inspiron 14 (N4030) Direct Base
Dell PC Restore Software
(Dell Home page)


HP TouchSmart 600 Quad series

Multi-touch All-in-One PC with Intel quad core processor, integrated webcam, discrete graphics, Blu-ray
drive, HDMI and game console connectivity, beats audio, and two-year warranty
Genuine Windows 7 Home Premium 64-bit
Intel(R) Core(TM) i7-740QM quad-core with Turbo Boost [up to 2.93GHz, 6MB L3 cache,
DMI 2.5GT/s]
FREE UPGRADE! 8GB DDR3-1333MHz SODIMM [2 DIMMs] from 4GB
System Analysis and Design
AAPP007-3-2
66

FREE UPGRADE! 1TB 7200 rpm SATA 3Gb/s hard drive from 750GB
1GB NVIDIA GeForce GT230M
Wireless-N LAN card and Bluetooth(R )
2-year In-Home limited hardware warranty
(HP Compaq Home page)

Software


Microsoft Office Professional 2007 Microsoft Office 2007 Blue Edition Precracked

Microsoft Office Access 2007 Microsoft Office Project Professional 2007

System Analysis and Design
AAPP007-3-2
67



Microsoft Office Visio Professional 2007 Any Microsoft Office


System Analysis and Design
AAPP007-3-2
68

Appendix C: Individual Evaluation
YU KANG WEI
In this modules, can say that is already done before when the year of form 6
computing subject. SAD System Analysis and Design - SDLC System Development
Life Cycle, Project Management, preliminary investigation, feasibility study, systems
analysis, Data Flow Diagram, Process Specification, input & output design and the
Data Dictionary was the knowledge of APIIT lecturer give, and this make refresh to
my mind. This time I was taking the opportunity to do practice for further use. In this
project Im the leader. Im not a good leader I can say that.
In the project, with the special case of the class student number we have, our
group just has the total of 2 members only this means me and my project partner
Natheni.
I would like to apologies that my modules exemption already approved and
actually I can stop to do this project but Im not that kind of bad guys. Before the
hand in date (10/12/2010), the work that I already done with the project will pass it to
my project partner. Many of my friends ask me to stop doing assignment with no
marks no benefit think. Even ask me to delete some data in the system that I have
done. Why my friends ask me to stop doing this project, but my mind keep thinking of
the project? Is there any reason can let me know about that? I think no reason about it.
That why Im not a good leader.
Lastly, this project was done perfectly, but in my mind keep think how to
improve it and this not a perfect project to me. Thanks you Ms Palvin.








System Analysis and Design
AAPP007-3-2
69

Natheni A/P Raj
From this assignment I have learn how the system work in offline and online. I
have created a web page to my assignment. I have gain sum experience when create
the web page. And also my group member and I created offline system in Microsoft
access. From this I have learn how to create offline system and how it generate. From
this assignment I have gain some experience to know about system. I have analyzed
that the system was not that much systematic compare to current system. As an IT
student I have known about the current system by SAD curriculum. Before this I
dont about the data flow diagram, data dictionary but now I understand how it helps
us to make our system more perfect. We also learn about System Development Life
Cycle. It s like a planning phase. Have created some question to staff and customer.
From this we know what problem are staff and customer facing by using this system.
End of this assignment I have learnt about the system and how it work. I must thank
to my lecture Ms. Palvin for guide me and encourage me throughout the assignment.


System Analysis and Design
AAPP007-3-2
70

Appendix D: Peer to Peer Evaluation
Name : YU KANG WEI
Student ID : TP 022372
[1]
Never
[2]
Rarely
[3]
Sometimes
[4]
Usually
[5]
Always
I have made a serious effort at assigned work before group meetings
*
2. Total amount of time spent in group meetings: 6 or more
ASIA PACIFIC INSTITUTE OF INFORMATION TECHNOLOGY
AAPP007-3-2 Systems Analysis & Design
Part A : Self Evaluation
100
c. Fact-finding
d. Project Management
e. Initial evaluation
6 or more 3. How many group meetings were held?
1. What was your contribution to the project?
Example : Prepared Gantt Chart
b. Access Database
% contribution
100
100
a. Feasibility Report 100
f. Design phase, Implementation phase, Maintenance phase
*
I have attempted to make contributions in group meetings
I have cooperated with the group effort
*
4. How many group meetings have you attended? all
100
100
100
5 List reasons for not attending meetings, if any.
Please assess using the scale
No Reason

System Analysis and Design
AAPP007-3-2
71

Please List Team Members' Names Here
Student Name : A Natheni A/P Raj
Student Name : B
Student Name : C
Student Name : D
Student Name : E
Student Name : A *
Student Name : B
Student Name : C
Student Name : D
Student Name : E
Student Name : A *
Student Name : B
Student Name : C
Student Name : D
Student Name : E
Student Name : A *
Student Name : B
Student Name : C
Student Name : D
Student Name : E
Sign : _________________
Part B : Peer to Peer Evaluation
1. Do you feel that the distribution of the tasks was fair? Please explain.
For me is this fine for it.
[5]
Always
Please assess using the scale
Has he / she made a serious effort at assigned work before group
meetings?
Has he / she attempted to make contributions in group meetings?
[3]
Sometimes
[4]
Usually
[2]
Rarely
[1]
Never
Has he / she cooperated with the group effort?


System Analysis and Design
AAPP007-3-2
72

Appendix E: Storyboard
The Components of DFD use are the type of Gane & Sarson. The way of the
components as below:
Description component
Data Flow Customer Info

Process

Data Store

External Entity (Source / Sink)