compiled (SAAD)

69
Page | 1 Table of Contents Table of Contents............................................ 1 Introduction................................................. 2 Overview of the Current System...............................3 Problems..................................................... 4 Opportunities................................................ 5 Objectives................................................... 6 Fact-findings................................................ 7 Questionnaires..............................................7 Interviews..................................................7 Feasibility Report........................................... 8 Technical Feasibility.......................................8 Economic Feasibility.......................................10 Operational Feasibility....................................13 Schedule Feasibility.......................................16 Selection of methodologies..................................17 SSADM (Structured Systems Analysis and Design Method)......17 RAD (Rapid Application Development)........................19 OOP (Object Oriented Programming)..........................21 Choosing SSADM.............................................22 Logical Design.............................................. 23 Context Diagram............................................23 Data Flow Diagram (DFD)....................................25 Entity Relationship Diagram (ERD)..........................28 Entity Life History........................................29 Use Case Diagram...........................................31 Class Diagram..............................................33 References.................................................. 36 Appendices.................................................. 37 Appendix 1:................................................37

Transcript of compiled (SAAD)

Page 1: compiled (SAAD)

P a g e | 1

Table of Contents

Table of Contents.....................................................................................................................1

Introduction..............................................................................................................................2

Overview of the Current System...............................................................................................3

Problems...................................................................................................................................4

Opportunities...........................................................................................................................5

Objectives.................................................................................................................................6

Fact-findings.............................................................................................................................7

Questionnaires.....................................................................................................................7

Interviews.............................................................................................................................7

Feasibility Report......................................................................................................................8

Technical Feasibility..............................................................................................................8

Economic Feasibility...........................................................................................................10

Operational Feasibility........................................................................................................13

Schedule Feasibility............................................................................................................16

Selection of methodologies....................................................................................................17

SSADM (Structured Systems Analysis and Design Method)................................................17

RAD (Rapid Application Development)...............................................................................19

OOP (Object Oriented Programming).................................................................................21

Choosing SSADM.................................................................................................................22

Logical Design.........................................................................................................................23

Context Diagram.................................................................................................................23

Data Flow Diagram (DFD)....................................................................................................25

Entity Relationship Diagram (ERD)......................................................................................28

Entity Life History................................................................................................................29

Use Case Diagram...............................................................................................................31

Class Diagram.....................................................................................................................33

References..............................................................................................................................36

Appendices.............................................................................................................................37

Appendix 1:.........................................................................................................................37

Page 2: compiled (SAAD)

P a g e | 2

Introduction

Through the years, technology has grown to become a very vital aspect in our

lives. Almost every task in our everyday routines involves the assistance of

technology’s innovations. This includes us being able to acquire our everyday needs

with most ease and convenience. Among these needs include food. More and more

restaurants have developed strategic systems and services to enable their hungry

customers to obtain the food they desire within a shorter period of time. These

services include doorstep food delivery, catering services and online ordering.

Apart from all those services, Sue and Tom Bickford have managed to come

up with a very convenient restaurant meal-delivery service. Patrons of a variety of

restaurants are able to order their desired food via a simple phone call without having

to leave their homes. This brainchild of theirs has been branded Waiters on Wheels, or

simply dubbed as WOW. The main objective of WOW is to increase convenience and

reduce time consumption for people when it comes to getting their meals.

Page 3: compiled (SAAD)

P a g e | 3

Overview of the Current System

Waiters On Wheels have only been dealing with two restaurants initially and

one driver to deliver the meals to their customers during the dinner shift. However,

WOW has been expanding and the numbers of restaurants they are contracting with

have been increasing as well.

Besides that, WOW does not utilize computers in their daily transactions. The

current system of WOW is using only telephone services to obtain orders from

customers. WOW has a limit of 10 lines available for this service. Moreover, WOW is

currently using the “paper-and-pen” method when taking orders from customers. The

staff will note all the orders placed by the customers, and sequentially sends the

details to the delivery man. The delivery man will then head to the location based on

the project.

Publicity of WOW is not much of a widespread. Their funds are to support

advertising as well. Flyers printed are simple, only in black and white and are given

throughout the most common places in the Klang Valley such as the Bukit Bintang

area, Petaling Jaya area, and Titiwangsa area.

Page 4: compiled (SAAD)

P a g e | 4

Problems

With reference to the overview of the current system, a number of problems

faced by Waiters On Wheels has been identified. First of all, the system currently

being implemented for WOW’s transactions is not effective. It may suffice for their

previous operations which only involved two restaurants. However, presently they

have been expanding in terms of the number of restaurants as well as customers.

WOW’s current system lacks the ability to keep track of all the customer

orders and other details in association with their daily transactions, such as customer

details as well as sales reports. This is due to the fact that there hasn’t been any usage

of computers in their operations. With a computerized system, WOW will be able to

swiftly get their hands back on a specific order and update the details with the

restaurant selected in case of amendments done by the customer. This can help make

transactions by the employees faster and easier. According to the current system, vital

data can’t be stored effectively with easy access to them later on. This causes

difficulties when the customer calls again wishing to change their order and also

wastes the employees’ precious duty time.

The current system in WOW is only using telephone services to customers.

WOW only has 10 lines available for this service. This will become a huge bottleneck

when peak hours come; of the customers during lunch breaks and dinner times. As a

result, the customers will have a hard time trying to call WOW for food reservations.

This may lead WOW losing several customers as their service does not meet

expectations.

Page 5: compiled (SAAD)

P a g e | 5

Opportunities

By using the new system, the effectiveness of WOW can be improved

radically. Firstly, the installation of computerized systems to completely replace their

conventional “paper-and-pen” way of dealing with customers and their orders needs

to be implemented. The company should purchase more than two computers to enable

and effective backup system in terms of safe-keeping all vital information as well as

having a preparative for the service in the event of computer breakdowns.

According to the current systems, WOW only does their business in certain

areas; the company covers very little area. To earn more business and increase the

popularity, WOW will expand the range of their coverage. Hence, it is best they open

more branches of the WOW organization to increase efficiency of their services.

With the practical software inside the new computer, WOW can run their

business easily and more effective. As mention before, the current system of WOW is

using the ‘paper-and-pen’ method to take down the order from customer. With the

new system, the whole menu will be listed and saved in the customized software used.

Therefore, when a customer calls to make an order, besides the customer detail, the

staffs of WOW just need to note down what order that customer require by clicking

the list of menu that display on screen. Then again, the menu need to be categorized

and arranged appropriately to avoid confusion among the staffs. For example, in Pizza

Hut restaurant, types and sizes of pizza that offered are categorized accordingly in

their menu. Moreover, 10 phone lines for the service is not enough, especially during

increase during peak hours.

The drivers on the other hand are best contacted through the simple ‘walkie-

talkie’ devices. These devices can cut cost, as well as transfer information regarding

pending orders to all the drivers at once and receive confirmation of order collection

immediately from specific drivers. When a driver agrees to collect an order and

speaks it through his walkie-talkie, the operator as well as the other drivers receives

this information. Besides that, information can be transferred at a higher speed, if

compared to the conventional telephone calls.

Page 6: compiled (SAAD)

P a g e | 6

Objectives

The owners, Tom and Sue had set several goals to be accomplished since 5

years ago. This system is to expand their service vicinity as far as possible. More parts

were covered from time to time by opening new branches. Besides that, as the

establishment goes, the customers’ service time is reduced. When this is implemented,

the customers will tend to make more orders with WOW next time.

Other than that, the objective of WOW is to ensure the people will easily be

able to get their food by us sending to them instead of them driving to the restaurant.

WOW is meant to reduce the hassle of the people to go out to buy food since

nowadays the petrol prices which are hiking up discourages people to drive out. With

the existence of WOW, people will think that this service is convenient, resulting

WOW to have new customers.

Page 7: compiled (SAAD)

P a g e | 7

Fact-findings

The techniques that we used to perform fact-finding is through questionnaires

and interviews. These techniques enable us to get feedback from the public from

questionnaires and the interviewee from interviews.

Questionnaires

From the response of the questionnaires, a number of 150 people were chosen

randomly at Bukit Bintang, Kuala Lumpur without taking into account about their

physical looks and their religions. 81.3% of the total number was locals while the

remaining 18.7% was foreigners. As of the locals, 48.4% was Malays, 35.2% was

Chinese, 13.1% was Indians, and 3.3% was other races.

76.7% of the public has ordered through food delivery. Majority of them used

this service from the main fast food outlets such as McDonalds and Pizza Hut. On the

whole, they made the order approximately once to twice a month and usually on

weekdays. Most of the time, their total cost of their delivery is around RM20-RM35.

While making their orders, they mostly make their delivery through telephone

calls. This is because they did not want to drive as the petrol prices are high

nowadays. Furthermore, online services were not as well known compared to

telephone services. Generally, the time taken to collect their delivery is about 30 to 45

minutes.

Interviews

To extend our research, we did an interview with the manager of Dominos

about their delivery service. We asked the manager about how their delivery process

works and how they cope with their problems faced.

Page 8: compiled (SAAD)

P a g e | 8

Feasibility Report

Waiters On Wheels have evolved rapidly from a simple restaurant delivery

system which initially only deals with a choice of two restaurants, to one that has

begun dealing with a wider range of restaurants. The current system utilized is not at

all suitable for their expanded business operations. Therefore, WOW has requested a

computerized system which will be able to perform the following tasks effectively:-

1. To acquire orders from customers either via telephone or the company

website.

2. To enable customers to choose from a wide range of restaurants listed.

3. To allow their drivers to notify WOW’s centre when they are finished with

a delivery.

4. To record when each driver reports for work.

5. To generate fundamental reports such as:

(a) End-of-day deposit slips

(b) End-of-week restaurant payments

(c) Weekly sales reports

Technical Feasibility

With the current system that WOW has, the equipment that they have now

would not be sufficient for this system to work well. The new equipment which is

about to be used will put an impact on the flexibility by improving it. The process of

buying these equipments is not too much of a challenge for the company. All that is

needed is a person with much required technical expertise to be able to identify and

only install what is needed without wastage of any resources. Although the initial cost

for the technical upgrades of the current system may be high, the costs are well worth

it for a long-term usage. Judging by the rapid expansion of WOW’s business, it is safe

to view these technical costs in a long-term basis.

There are a number of individuals who play vital roles in order to build a

technically appropriate system. First of all, the project manager is obligated to ensure

the smooth development of the project. The manager must only carry out important

Page 9: compiled (SAAD)

P a g e | 9

decisions after much consideration in terms of costs, time consumption, as well as

delegation of tasks to his team members.

Other than that, the project manager must also choose the best technicians to

deal with technical issues. These issues include, building an effective network,

installing fundamental software as well as the hardware required for this system.

Besides, a good system designer is also required to plan and construct a proper

system for WOW to utilize in its transactions. The system designer must include all

the requested features into the system, as well as produce a user-friendly interface for

the system.

Among the additional features which would be required for higher efficiency

of the company’s activities does not only incorporate hardware, but also softwares.

These features include:-

- Hardware

Desktops

Servers

Cables

Modem & Wireless Router

Telephone

Mobile phones

Walkie-Talkies

- Software

Custom-made WOW System

Microsoft Office 2007

Kaspersky Anti-Virus

Microsoft Windows Server

2003

Microsoft SQL

Page 10: compiled (SAAD)

P a g e | 10

Economic FeasibilityWith the new system that mention above, Waiters On Wheels are able to

attract customer easily, as it service are very convenient and customer gain a lot of

benefit through it. If more customers choose to order through Waiter on Wheels, this

can help the organization to gain more profit and also attract other restaurant that

wanted to form a partnership with WOW. Below are the estimated prices for the

whole system.

Development Cost

Items Quantity

Cost per Item (RM)

Total Cost (RM)

HP ProLiant ML150 G5 Server series

2 5500 11000

HP Compaq dc7800 Ultra Slim Desktop PC

(GC762AV)

6 2700 16200

HP VS19e 19 inch LCD Monitor 6 630 3780

Belkin N Wireless Router - Wireless router + 4-port

switch

3 380 1140

HP Deskjet F4200 All-in-One Printer series 1 290 290

LAN Cable (100 Meters) 6 30 180

Avaya 4620 IP Telephone 5 3500 17500

Microsoft® Office 2007 Professional OEM Addition 1 1,090 1,090

Kaspersky Anti-virus 6 23 138

Project Manager (3 Months) 1 700

0

21000

System Analyst (3 Months) 2 5000 30000

System Designer (3 Months) 1 4,000 12,000

Walkie-talkie 12 200 2400

Webhosting (Setup Fee + Domain Name Fee) 1 64.62 64.62

Telekom Business Line 1 470 470

TM Net Streamyx 4Mbps 1 163 163

Transportation (van, motorbike) (2,10)

Drivers 10 1500 15000

Page 11: compiled (SAAD)

P a g e | 11

Annual Operating Cost

Items Total Cost

(RM)

Maintenance Fee 6000

Petrol (2 Van + 10 Motorbike) 10800

Operators (6 Operators) 78,000

Drivers Salary (12 Drivers) 108,000

Telekom Rental Charges 3600

Printer Toner 7200

TM Net Streamyx 5000

Total Operating Cost (RM) 218600

Annual Benefits

Benefits Total Cost (RM)

Delivery Benefits (RM 5* 200 order per day) 365,000

Return on Investment (ROI), Net Value & Payback Period

YearEntity

0 1 2 3 4 5

Value of Benefits

0.00 365000.00 428000.00 527000.00 637000.00 738000.00

Discount Factor (10%)

1.00 0.90 0.81 0.73 0.66 0.59

Present Value of Benefits

0.00 328500.00 346680.00 384710.00 420420.00 435420.00

Cumulative 0.00 328500.00 675180.00 1059890.00 1480310.00 1915730.00

Page 12: compiled (SAAD)

P a g e | 12

Present Value of Benefits

YearEntity

0 1 2 3 4 5

Cumulative Present Value of Benefits

0.00 262,800.00 558,450.00 891,056.00 1,265,238.28 1,686,193.07

Cumulative Present Value of Cost

333015.62 554505.62 753846.62 933499.62 1095925.62 1241124.62

Cumulative Present Net Value

-333015.62 -291705.62 -195396.62 -42443.62 169312.66 445068.45

Payback Duration = 1*365+(1– (195396.62/(195396.62+291705.62)))*365

= 583Days / 1 Year 218 Days

Return on Investment = (1,686,193.07-1241124.62) / 1241124.62

= 35.86%

ROI = [(Payback - Investment)/Investment)]*100

YearEntity

0 1 2 3 4 5

Development Cost

333015.62 - - - - -

On Going Cost

0.00 246100.00 246100.00 246100.00 246100.00 246100.00

Discount Factor (10%)

1.00 0.90 0.81 0.73 0.66 0.59

Present Value of On Going Cost

0.00 221490.00 199341.00 179653.00 162426.00 145199.00

Cumulative Present Value of Cost

333015.62 554505.62 753846.62 933499.62 1095925.62 1241124.62

Page 13: compiled (SAAD)

P a g e | 13

Payback period = (cost of project/investment) * (%annual cash flow)

Page 14: compiled (SAAD)

P a g e | 14

Operational Feasibility

In the functional side, the system has to take into consideration whether it can

fully support the business’ aims. With the existence of this system, it should be able to

help the business by solving any problem that occurs as well as taking advantage of

any opportunities that can help the business to be considered successful or useful by

the company. On the whole, the PIECES framework can be used to work out any

operational problems that take place. PIECES signifies; Performance, Information,

Economy, Control, Efficiency, and Services. Those are the different types of features

that the system will look into in order to solve the problem.

Performance

Performance is the capability of the system to fulfil business needs like such

as whether it provides real time responses and throughput. When a customer calls the

operator to place his or her orders, the built system must be able to have a response

immediately. This is to ensure the operator can keep up with the information being

received from the customer. It benefits the most especially during peak hours so that

other customers whom are waiting for queue would not need to wait for so long.

Moreover, when a regular customer calls the operator, the system also needs to be

able to retrieve the customer details from the database to prevent the case of

redundancy.

Information

Another part to be concerned with is the information produced so that it is

precise and helpful information to the operators. All the information entered needs to

be stored in the database in an appropriate format. This will result with more accurate

information which is easily loaded from the records. Furthermore, when there are any

changes of information being stated by the customer, action will be taken

immediately. The customers’ details will be updated automatically by the system. On

top of that, the information in the database can be used to produce reports for the

managers to keep as their record and also to view at a more presentable form.

Page 15: compiled (SAAD)

P a g e | 15

Economy

For the economy part, it explains about how the system is cost affordable. It

also determines whether the funds used are fully utilized to prevent excess. When the

system is under development, its cost is high. Nevertheless, after some time, the initial

development cost can be settled after several months. With the fact that computers

will be the key for this system, human labour can be used more often as a temporary

alternative to save costs. After awhile, when the efficiency of the system improves,

customers will be more attracted to the services provided which will result to increase

in profits.

Control

When the system is used, it must have protection against frauds which

guarantees security as well as accuracy of data and etc. With the help of protection

software such as Kaspersky Anti-Virus, these problems are easily dealt with.

Furthermore, hackers, viruses, spywares and malware will be blocked or deleted by

this protection software from attacking the system. Critical information such as

customer information will be set privileges so that only certain individuals can gain

access to it. This is to prevent this information to be stolen by other people.

Efficiency

In efficiency, the ability of the system is to make full use of the current

resources available for the business to run smoothly. This is also one of the aspects

that will lead to the achievement of the business. Besides that, records must be easily

opened to save time. Along with that, the system has to be accessible for the operators

so that they will be able to perform their task without any difficulty to boost the

productivity rate.

Services

Services are the capability of the system to offer quality and reliable services

and whether it can adjust to the environmental changes. If a company does not adapt

to the environmental changes it will certainly miss an opportunity to other companies.

In view of the fact that the system is simple to use, operators will not have much

problem to understand how the system works. Nonetheless, training is provided to

those who are computer illiterates or if there are changes made to the system that

Page 16: compiled (SAAD)

P a g e | 16

some operators cannot handle. Technicians are also recruited to keep up the operation

of the system so that it does not fail in peak hours.

Page 17: compiled (SAAD)

P a g e | 17

Schedule Feasibility

The objective of schedule feasibility is to divide the tasks and time in a proper

way, then implement and terminate it effectively. The design of the system needs to

combine some particular area in order to complete the whole system. The Gantt chart

and Pert Chart are placed in Appendix which illustrates the areas, progresses and time

divisions of the system. By following the time that has already been distributed in the

charts, we not just can accomplish the entire system, thus also can avoid misuse and

exceed the appointed time. In addition to that, the workload matrix attached in

Appendix is also an important material in the process. It divides the tasks for each

member to take charge to avoid unfair circumstances occur.

Page 18: compiled (SAAD)

P a g e | 18

Selection of methodologies

SSADM (Structured Systems Analysis and Design

Method)

SSADM is a methodology developed originally by UK consultants Learmonth

and Burchett Management System (LBMS) and the Central Computing and

Telecommunication Agency (CCTA), which is responsible for computer training and

some procurement for the UK Civil Service (Avison & Fitzgerald, 2006, p. 419). The

main reason of this was to improve government service to public.

The main target for SSADM is produced computer system that fit the acquired

purpose, by putting framework, carry out given task and also support organization IT

strategy according to the timeline given.

SSADM is a data-driven method. Besides that, it also can consider as basic

assumption that systems have a fundamental, generic, data structure which make no

changes, even know processing condition may change. Within SSADM, this

underlying data structure is modelled from early stage. The structured of techniques

of SSADM fit into the framework of steps and stages, each will defined with input

and output.

If the task that had been assigned cannot be fully completed on time, no

further steps can be taken. To prevent this for happening, one should plan in details all

the works so that it can be done before dateline.

Everything also should have it advantages and also disadvantages, below are

all the advantages and disadvantages of SSADM:

Page 19: compiled (SAAD)

P a g e | 19

Advantages:

1. Planning is easier with structure framework

2. Stages can be break down as it is useful for teamwork

3. This method is suitable for big project

4. Allow delegations of simpler tasks to junior personnel

5. Free for usage

Disadvantages:

1. Too much documentation

2. Not suitable for small projects

3. Can be very complex, as the documentation had a lot of stages

Page 20: compiled (SAAD)

Functionality

Time Resources

ResourcesTime

Functionality

Traditional development

RAD development

P a g e | 20

RAD (Rapid Application Development)

RAD is a term which has been introduced by James Martin from the year

1991. The goal of RAD is to speed up the development process that has been on the

agenda of both general management and information systems for a long period

(Avison & Fitzgerald, 2006, p. 128). Furthermore, RAD also promises better and

cheaper deployment when the system developers and end users work together to

develop this system.

RAD is used in order to speed up the development of the project by using

computer-based tools to work as a key to overcome problems which might interrupt

the delivery of the system. Apart from that, RAD divides the process of carrying out a

system while working in a parallel to decrease time and efforts consumed by limiting

development cycles.

There are a few RAD phases which come together in order to be more focused

to the systems’ efficiency and user interface requirement, while other stages like the

duration of development and design has been reduced. However, the system can be

reverted to the planning phase, as it is possible to go back to development from the

cutover phase.

If this company wants to use RAD as the methodology to perform this project,

the users have to be involved in this project. This is due to the fact that they will affect

the progress of the system overall, as the users will be the ones who will use it. As a

result, the task implementation during the cutover phase is easy, because it meets

users’ requirements as it was designed by them with guidance from the system

analyst.

Page 21: compiled (SAAD)

P a g e | 21

The diagram shows about the differences of traditional development when compared

to RAD development (Avison & Fitzgerald, 2006, p. 129).

RAD benefits:

Time needed to develop a system is lesser.

Development cycles are shorter which will result in a cheaper system.

User involvement is broader.

RAD detriments:

Planning is not a main concern.

It mainly focuses on resources and time as its functionality reduces (Avison &

Fitzgerald, 2006, p. 129).

Elements and prototypes which are reused again may cause irregularity in the

designs.

Page 22: compiled (SAAD)

P a g e | 22

OOP (Object Oriented Programming)

Object-oriented programming (OOP) is a programming language model

structured that surround by objects and data rather than actions and also logic. Here

are the method of how input are produce and become output, as one specified

program will been viewed as logical procedure that takes input data, process it and the

final results will known as output data.

Besides that, it can also use simple objects and produce it to simple design

application and also computer programs as this can improve the software

construction. Here are a few steps that have to take to convert input data to output

data:

I. Identify all the objects you want to manipulate

II. Relationship between all the objects that you had identify (data

modeling)

III. Generalize it as class of objects using Plato concept

IV. Define kinds of data and also logic sequences that can manipulate

(Toodarkpark.net, 2000)

Each distinct logic sequence is known as method. What you run in computer is

known as object or class instance, besides that it also provide computer instruction

and class object characteristics which provide relevant data in the end of the day.

Page 23: compiled (SAAD)

P a g e | 23

Choosing SSADM

There are 3 types of methodology had been mention above, which include

SSADM, RAD and also object-oriented. After making comparison among the three,

our group had decided and also come out with a conclusion that we will be choosing

SSADM.

Based on the research that has been done so far, they had come out a

conclusion that SSADM had considered the most matured types of method in UK.

Besides that, after a few years it was introduced, government had included it into the

consideration of main method as they wanted to ensure its usability and practically.

One of the main advantages is that SSADM builds up several unusual views of

the system which are used to cross-check one another. Take building as an example,

to help the customer to gain a deeper understanding on the structure of the building,

the architect drew several different type of diagram and also explain to customer in

details about the building structure. This probably helped the architect to validate the

plans as he made sure that each view was consistent with the others. In SSADM, three

different views of the system are developed in analysis. These views are closely

related to one another and are cross-checked extensively for consistency and

completeness.

SSADM are divided into 3 views:

a. The underlying structure of the system’s data (the Logical Data Structure)

b. How data flows into and out of the system and is transformed within the

system (Data Flow Diagram)

c. How the system data are changed by events over time (Entity Life Histories)

(Ashworth & Goodland, 1990, p. 7)

Page 24: compiled (SAAD)

P a g e | 24

Logical Design

Context Diagram

The context diagram is an ‘overview of an organizational system that shows

the system boundaries, external entities that interact with the system, and the major

information flows between the entities and the system.’ It is a highest view of the

system. Besides, the context diagram does not include data store, holds one process,

and few data flow and source/sinks (Hoffer et al, 2002). Context diagram is just a

simple process or known as a beginning process of the system. It is easy to

comprehend and not very complicated.

Page 25: compiled (SAAD)

P a g e | 25

The entities of the WOW Food Delivery System basically consist of customer,

restaurant, driver, and accounting apartment. First, customer calls in to make food

ordering, tell their own information, and make payment when they get the food. On

the other hand, the system will generate a receipt for customer in return. Second, the

restaurant receives the food order list from the system and informs the food amount to

the system. The system makes payment to the restaurant at the end of the week. Third,

the driver report in to the system and get the information to make food delivery.

Lastly, the accounting department receives the deposit slip and weekly sales reports

from the system.

Page 26: compiled (SAAD)

P a g e | 26

Data Flow Diagram (DFD)

Data Flow Diagram Level 0

Page 27: compiled (SAAD)

P a g e | 27

Data Flow Diagram Level 1

Data Flow Diagram (DFD) describe as the movement of the data between

external entities and the processes and data store within a system, and can use to

represent both the logical and physical information systems (Hoffer et al, 2002).

Basically, the DFD shows the relationship between the inputs, output, and process

that occurs in the system and how they connect to each other.

Data Flow Diagram encompasses Level 0 and Level 1. The DFD level 0

shows the main processes of the system, data flows, and data store a high level of

Page 28: compiled (SAAD)

P a g e | 28

detail. Moreover, the DFD level 1 is explained more detail about the sub processes

from the particular process on the DFD level 0.

In DFD level 0, the customer start informing their own customer ID by calling

in thru telephone. The operator will key in the customer ID to find and check the

account inside the customer database. If is a new customer, then have to make new

registration to create a new account. Generate order begin which is process 3 when

customer wants to make order. The operator will update the order information that

require by customer to the customer database. Process 4 begin when the system send

the customer order list to particular restaurant. After that, the driver from WOW

Company will be informed to go to pick the order from the restaurant; this stage goes

in under process 5. Later on, in process 6, the driver will start deliver the food to the

customer. Customer will pay the customer charges for the order. Customer database

will update the customer payment in process 7. At the same time, reports will generate

deposit slip and weekly sales report to send to the accounting department.

DFD level 1 is the sub part of the level 0. Process 3 from DFD level 0 had

been explored in detail. In process 3.2, if the customer wants to make changes of the

order, WOW Company will update the previous order. Afterwards in process 3.3,

total price of order will be calculated and update order to the customer database, also

inform the new total amount to the customer, new order list will be produced after

this.

Driver makes food delivery in DFD level 0 process 4. Before that, in process

4.1, the WOW Company will identify who is free at the time and the free driver will

report back. In process 4.2 and 4.3, the driver will receive the order detail and identify

the restaurant location.

Process 5.1 and 5.2 shows the driver go collect the food from the restaurant,

then start deliver food to the customer. In process 5.3, driver will give receipt to the

customer and get the payment. Customer database for payment will be updated and

calculate the total for one day simultaneously.

Page 29: compiled (SAAD)

P a g e | 29

Entity Relationship Diagram (ERD)

The Entity Relationship Diagram is a model that shows the logical

relationships and interaction among system entities according to Shelly Cashman

Rosenblatt (2008). The ERD represent the entities as rectangles and relationship as

diamond shapes. The data flow from top-to-bottom and left-to-right. The diagram can

describe the relationship in further aspects by using methods call cardinality. ERD use

a common method of cardinality which called crow’s foot notation to represent the

relationship by using some special symbol.

The crow’s foot notation ERD shows above. As illustrate from the ERD, one

customer places many order at the time and many order can be placed by one

customer. Another example of connection that has is between restaurant and food.

One restaurant produces many foods and many food produce by one restaurant.

Another connection includes is between customer and receipt. One customer can

accept only one receipt and one receipt accepts by one customer.

Page 30: compiled (SAAD)

P a g e | 30

Entity Life History

Entity Life History is to define the rules and regulations required for the

actions with entities such as insert, update, and delete (Webmaster, 2002). This

diagram attaches two basics diagram together, which is the Data Flow Diagram

Page 31: compiled (SAAD)

P a g e | 31

(DFD) and Entity Relationship Diagram (ERD). This diagram represents three types

of entities which are the sequence, iteration and selection (Skidmore and Wroe, 1992).

For the sequence type, there are no marked indicated and the event read from left to

right. On the other hand, the iteration type will mark an asterisk (*) symbol and the

selection type is indicated by marking with a small circle. Mark of both iteration and

selection types are stated in the upper right hand corner.

As shows on the Entity Life History, customer is the first entity involved and

the event contains new registration, telephone call in, account management, order, and

order completed. Customer can edit their account by make changes and update their

detail, and also can make changes of the order.

Second entity is the restaurant. The event involved is following the sequence

type of entity. Firstly, receive order, then prepare food, generate bills, and lastly send

out the food.

Driver is the third entity. The event involved is receive work and delivery

order. Before deliver the food to the customer, the driver receives customer order,

customer detail, and restaurant detail. When comes to delivery part, driver go pick the

food and then deliver to the customer and receive payment from customer.

Page 32: compiled (SAAD)

P a g e | 32

Use Case Diagram

Use Case Diagram defined as depicts the use cases and actors for a system

(Hoffer et al, 2002). This diagram help classify the objects and the high-level

relationships and responsibilities. To set up a Use Case Diagram, need to categorize

the primary elements which are the ‘actors’ and ‘Use Cases’ first. Firstly, the actor

uses a stickman as the symbol and indicates its name below. Secondly, the use cases

use an oval shape as the symbol and indicate its name underneath.

The actors that have in the diagram are Customer, Restaurant, Driver, WOW

system, and Accounting Department. The customer calls in thru telephone to make

order with the WOW system. The system then informs the order list to the restaurant.

The driver will be told and go pick up the order from the restaurant. The driver

Page 33: compiled (SAAD)

P a g e | 33

delivers the food to the customer and collects the payment from the customer. The

system will generate report to the accounting department of the company.

Page 34: compiled (SAAD)

P a g e | 34

Class Diagram

As mentioned from Shelly Cashman Rosenblatt (2008), a class diagram stands

for a detailed view of a single use case, shows the classes that participate in the use

case, and documents the relationship among classes. Class diagram converts the

entities, data stores, and processes to data structures and program code. In class

diagram, contains the class name at the top, and then followed by the attributes and

methods. Besides, the lines that link shows the relation between the classes. The class

diagram use UML notation symbol to identify the relationship between classes.

Page 35: compiled (SAAD)

P a g e | 35

The UML notation symbol shows in below:

As demonstrated from the class diagram above, one customer can have

anywhere from zero to many orders. One restaurant can have one to many orders, at

the same time; each order can have anywhere one or many food items.

UML

Notation

Nature of the

Relationship

0..* Zero or many

0..1 Zero or one

1 One and only one

1..* One or many

Page 36: compiled (SAAD)

P a g e | 36

Page 37: compiled (SAAD)

P a g e | 37

References

1. Avison, D., & Fitzgerald, G., 2006, Information Systems Development, 4th edn,

McGraw Hill, Singapore.

2. Ashworth, C. & Goodland, M., 1996, SSADM, McGraw Hill, UK

3. Techtarget.com, definition for object-oriented programming, 2008, [online]

Available from:

http://searchsoa.techtarget.com/sDefinition/0,,sid26_gci212681,00.html

[Accessed on 19th August 2008]

4. Toodarkpark.net, object-oriented programming, 2000, [online]

Available from:

http://objc.toodarkpark.net/oop.html

[Accessed on 2nd August 2008]

5. Anon, SSADM, 2008, [online]

Available from:

http:// gawain.soc.staffs.ac.uk/modules/levelm/ce00218-m/slides/ssadm/

ssadm1v2.ppt

[Accessed on 4th August 2008]

6.

Page 38: compiled (SAAD)

P a g e | 38

Appendices

Appendix 1:

1. HP ProLiant ML150 G5 Server series

Processor, operating system and memory

Processor type 450164-371: Intel® Xeon® E5410 Quad Core Processor 2.33 GHz

Processor speed 450164-371: 2.33 GHz

Number of processors

1 processor

Processor upgrade Upgradeable to dual processor

Processor core available

450164-371 / 450162-371 / 450163-371: Quad

Internal cache 450164-371 / 450162-371 / 450163-371: Integrated 2 x 6 MB Level 2 cache

System bus 450164-371 / 450162-371 / 450163-371: 1333 MHz Front Side Bus

Standard memory 450164-371 / 450163-371: 2 GB Standard Memory

Maximum memory 16 GB

Memory type PC2-5300 Registered Buffered DIMMs (DDR2-667)

Memory slots 6 DIMM slots

Internal drives

Internal hard disk drive

450164-371 / 450163-371: No hard disk drive in standard configuration

Page 39: compiled (SAAD)

P a g e | 39

Hard disk drive speed

450164-371 / 450163-371: Not applicable

Hard disk controller 450164-371: HP E200 8 Internal Port Smart Array SAS/SATA Controller

Internal drive bays 450164-371 / 450163-371: Four/Eight Hot Plug SAS/SATA

Optical drives 16x SATA DVD-ROM

System features

Chassis type 5U Tower

Chipset Intel® 5100 Chipset

Network interface Embedded HP NC105i PCI Express Gigabit Server Adapter 10/100/1000 WOL (Wake on LAN)

External I/O ports Parallel - 0; Serial - 1; Pointing Device (Mouse, PS2) - 1; Graphics - 1; Keyboard (PS2) - 1; USB 2.0 Ports Dedicated USB - 8 total (4 rear, 2 front panel, 2 internal), 1 (available for USB Tape connectivity); Network RJ-45 (Ethernet) - 1 (10/100/1000 Gbits/s); Remote Management: 1 (10/100) via optional HP ProLiant 100 G5 Lights-Out 100c Remote Management Card

Expansion slots Six expansion slots: Two (2) PCI-Express x8, Three (3) PCI-Express x4(x8 connector) and One (1) PCI (32-bit/33MHz). One slot designated for optional HP ProLiant 100 G5 Lights-Out 100c Remote Management Card

Power supply type One 650W Non-Redundant Power Supply, Non-hot plug; 750W Redundant Power Supply option kit, Non-hot plug

Power requirements load 11.6A: 100 to 127 VAC; load: 5.5A at 200 to 240 VAC, 47 to 66 Hz

Compatible operating systems

Microsoft® Windows® 2003 R2 Web edition; Microsoft® Windows® 2003 R2 Small Business edition; Microsoft® Windows® 2003 R2 Standard Edition (x86 and x64); Microsoft® Windows® 2003 R2 Enterprise Edition (x86 and x64); Microsoft® Windows® 2008 Longhorn Standard Edition (x86 and x64); Microsoft® Windows® 2008 Longhorn Enterprise Edition (x86 and x64); Red Hat EL 5/4 (x86 and x64); SLES 10/9 (x86 and x64); Netware 6.5; SCO OpenServer Legend 6.0.1; SCO UnixWare 7.1.4

Dimensions (W x D x H)

42.40 x 61.68 x 20.00 cm

Weight 18.55 kg

Compliance industry standards

ACPI V2.0 compliant; PCI 2.3 compliant; PXE Support; WOL Support; Microsoft® Logo certifications

Security management

Power-on password; Setup password; Diskette boot control

Page 40: compiled (SAAD)

P a g e | 40

Serviceability Easy chassis entry and component access

Manageability features

Optional HP ProLiant 100 G5 Lights-Out 100c Remote Management Card; Embedded IPMI standard reporting

Warranty standard statement

1 year Parts, 1 year Labor, 1-year on-site support

Source: http://h10010.www1.hp.com/wwpc/my/en/sm/WF06a/15351-15351-241434-

3328424-3328424-3580609.html

Page 41: compiled (SAAD)

P a g e | 41

2. HP Compaq dc7800 Ultra Slim Desktop PC (GC762AV)

Fast facts

Processor type Processor Socket T - LGA775 , 800 MHz or 1066 MHz

Compatible operating systems

Genuine Windows XP Professional, Genuine Windows Vista® Business, Genuine Windows Vista® Home Basic, FreeDOS

Chipset Intel® Q35 Express

Maximum memory

4 GB DDR2-Synch DRAM

Memory type PC2-5300 DDR2 667 SDRAM or PC2-6400 DDR2 800 SDRAM

Memory slots 2 SODIMM

Memory upgrade

Expandable to 4 GB through two industry-standard SODIMM slots

Internal drives

Internal hard disk drive

80 to 160 GB

Hard disk drive speed

5400 rpm or 7200 rpm

External drive bays 1 Slimline Drive Bay

Internal drive bays 1 internal 2.5 inch

Hard disk controller SATA 1.5 Gb/s

Flexible disk drive Optional 1.44 MB Diskette Drive

System features

Chassis type Ultra-slim desktop

Graphic subsystem name

Intel® Graphics Media Accelerator 3100

Video adapter features

3D/2D Controller: support is fully compliant with Microsoft® standard API such as Microsoft DirectX®9, DirectXVA®,

Page 42: compiled (SAAD)

P a g e | 42

VMR9, GDI/GDI+; OpenGL® 1.4.; Integrated VGA Controller; integrated 400 MHz RAMDAC; 400 MHz Controller Clock Speed; Overlay Planes: Single overlay support with 5x3 filtering; Maximum Color Depth: 32 bits/pixel; Multi-display Support: 2 displays can be supported via the motherboard's VGA connectors and DVI ADD2 card

Graphic subsystem video card memory

Graphics memory is shared with system memory. Graphics memory usage can vary from 8 to 256 MB depending on the amount of system memory installed and system load

Audio Integrated High Definition audio with ADI1884 codec, 3D audio compliant with AC'97 Rev. 2.3, internal PC speaker

Network interface Integrated Intel® 82566DM Gigabit Network Connection

Network cards Optional Intel® Pro 1000 PT PCIe Gigabit NIC

Available LAN drivers

Microsoft® Windows® Vista®, Microsoft® Windows® XP, Microsoft® Windows® 2000

External I/O ports Rear: 6 USB 2.0, 1 DVI-D graphics port, 2 PS/2, 1 RJ-45, 1 VGA, audio in/out; Front: 2 USB 2.0, audio ports

Security management

Integrated 1.2 TPM Embedded Security Chip (except for Russia), Kensington Lock Support, HP Business PC Security Lock, HP USB Biometric Fingerprint Reader, HP Rear Port Controller Cover

Physical security Kensington Lock, Hood Removal Sensor

Dimensions (W x D x H)

25.1 x 25.4 x 6.6 cm

Weight 3.1 kg

Power features Operating Voltage Range: 90 – 264 VAC; Rated Voltage Range: 100 – 240 VAC; Rated Line Frequency: 50/60 Hz; Operating Line Frequency Range: 47 – 63 Hz; Rated Input Current 80 Plus: 1.5 A; Current Leakage (NFPA 99): < 275 µA; System Heat Dissipation 80 Plus: Typical 133 btu/hr (33.5 kg-cal/hr), Maximum 549 btu/hr (132 kg-cal/hr; Power Supply Fan: None, Power Consumption in ES Mode – Suspend to RAM (S3) (Instantly Available PC): <2.7 W

Power consumption 135 watts maximum

Power requirements Input voltage 90 – 264 / 100 – 240 VAC, 50/60 Hz, 47 – 63 Hz, active PFC standard (External 80% High Efficiency)

Operating temperature range

10° to 35° C

Storage temperature range (Celsius)

-30 to 60° C

Operating humidity range

10 to 90% RH

Page 43: compiled (SAAD)

P a g e | 43

Non-operating humidity

5 to 95% RH

Operating altitude 3,048 m

Non-operating altitude

9,144 m

Source: http://h10010.www1.hp.com/wwpc/my/en/sm/WF06b/12454-12454-64287-

3328898-3328898-3459242-3560405.html?jumpid=reg_R1002_MYEN

Page 44: compiled (SAAD)

P a g e | 44

3. HP Pavilion vs19e Monitor

LCD feature Specification

Display size 19-inch (43.3 cm) diagonal and viewable image

Display type TFT liquid crystal

Interface Input connector:

1 VGA 15-pin D-type connector (analog cable included)

Scanning frequency Horizontal 30-81 Hz

Vertical 56-76 Hz

Recommended resolution (H x V)

1280 x 1024 @ 60 Hz

Power source - AC/DC adapter

Input rating: 100-240 V

Output rating: 12 V, 3.75 A

Frequency: 50/60 Hz

Power consumption: 40 W in operating mode, 2 W in sleep mode

Operating environment

Temperature: 10 degrees C to 35 degrees C (50 to 95 degrees F)

Humidity: 20% RH through 80% RH (without condensation)

Storage environment Temperature: -20 degrees C to 60 degrees C (-4 degrees F to 140 degrees F)

Dimensions H x W x D

Including base: 424 x 426 x 204 mm (16.7 x 16.8 x 8.1 inches)

Weight Unpacked: 6.8 Kg (15 pounds)

Page 45: compiled (SAAD)

P a g e | 45

Tilt stand Maximum tilt angle range: -5 degrees to +30 degrees (tilt range may vary depending on the height adjustment)

EMI standard FCC Class B

EPA Energy Star As an Energy Star Partner, Hewlett-Packard has determined that this product meets the Energy Star guidelines for energy efficiency.

Source: http://h10025.www1.hp.com/ewfrf/wc/document?

cc=my&docname=c00603955&dlc=en&lc=en&jumpid=reg_R1002_MYEN

Page 46: compiled (SAAD)

P a g e | 46

4. Belkin N Wireless Router - Wireless router + 4-port switch

Feature DescriptionExpansion / Connectivity

Interfaces4 x network - Ethernet 10Base-T/100Base-TX - RJ-451 x network - Radio-Ethernet1 x network - Ethernet 10Base-T/100Base-TX - RJ-45 ( WAN )

NetworkingConnectivity Technology

Wireless, wired

Integrated Switch 4-port switchData Transfer Rate 300 MbpsFrequency Band 2.4 GHz

Data Link ProtocolEthernet, Fast Ethernet, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n (draft)

Spread Spectrum Method

OFDM, DSSS

Switching Protocol EthernetRemote Management Protocol

HTTP

Status Indicators Port status, power

FeaturesFirewall protection, dynamic IP address assignment , DHCP support, NAT support, Stateful Packet Inspection (SPI), MAC address filtering, VPN passthrough, MIMO technology

Compliant Standards

IEEE 802.11b, IEEE 802.11g, IEEE 802.11n (draft)

AntennaAntenna Qty 2Directivity Omni-directional

MiscellaneousCables (Details) 1 x network cableEncryption Algorithm

128-bit WEP, 64-bit WEP, WPA, WPA2

GeneralDevice Type Wireless routerForm Factor External

Page 47: compiled (SAAD)

P a g e | 47

Feature DescriptionPower

Power Device Power adapter – external

Source: http://www.softchoice.com/catalog/product.aspx?SCCPartNo=U84635

Page 48: compiled (SAAD)

P a g e | 48

5. HP Deskjet F4200 All-in-One Printer series

The HP Deskjet F4200 All-in-One series is designed for cost-conscious consumer who requires print, copy and scan features. Affordable and easy-to-use, it is designed to be compact with a concise front panel.

Features

• Efficiently print, scan and copy for high-quality, everyday projects and use optional high-capacity ink cartridges to get 3 times more black printed pages and 2 times more color printed pages1.

• Enjoy fast print speeds of up to 26 ppm black and 20 ppm colour.• HP Smart Web Printing2 easily combines parts of web pages into a single page for

smarter printing.

Source: http://h10010.www1.hp.com/wwpc/my/en/ho/WF05a/18972-18972-238444-

410635-410635-3390945.html

Page 49: compiled (SAAD)

P a g e | 49

6.

Source: http://sholl.com.au/dbimages/avaya_4620_ip_screen_phone.jpg

Page 50: compiled (SAAD)

P a g e | 50

Appendix 2