Final Project Report

FOOD MANIA WEBSITE

Project Supervisor:
Mr. AFTAB HUSSAIN

Submitted By:
AHMED SAEED
Roll No: 506

Software & Research Projects Section

Department of IT

GOVERNMENT INSTITUTE OF INFORMATION

TECHNOLOGY, RAWALPINDI
 CERTIFICATE

This is to certify that Ahmed Saeed with Roll No 506 have worked on and
completed his Software Project at Software & Research Projects Section,
Government Institute of Information Technology in partial fulfillment of the
requirement for the Diploma of DIT in IT my guidance and supervision.

In my opinion, it is satisfactory and up to the mark and therefore fulfills the

requirements of DIT.

Supervisor / Internal Examiner

Mr. AFTAB HISSAIN

Supervisor,
Software & Research Projects Section,
Government Institute of IT.

___________________

(Signature)

1
External Examiner/Subject Specialist
Accepted By:

_____________

(Principal)

2
 DEDICATION

This report is the result of a very dedicated work of myself. I

have worked hard to achieve this objective which is my first
professional achievement at this level. I dedicate this report
to my beloved Brother, Teachers and supervisors who
guided me towards this goal of my early life. Without their
prayers, guidance and supervision I could not have achieved
this goal.
Contents:
TOPIC………………………………………………………………………………………………………………………….Page No.
C HAPTER 1 A NALYSIS ............................................................................................................3

1.1 Introduction.....................................................................................................................4

1.2 Product Features............................................................................................................4

1.3 Statement of The Problem...........................................................................................4

1.4 Scope................................................................................................................................4

1.5 Hardware Requirement.................................................................................................5

1.6 Software Requirements................................................................................................5

1.7 Assumptions and Dependencies...............................................................................5

1.8 Deliverables and Development Requirements........................................................5

1.8.1 Deliverables.............................................................................................................5

1.8.2 Development Requirements...............................................................................5

1.9 Requirements Analysis......................................................................................................6

1.9.1 Functional Requirements....................................................................................6

1.9.2 Non-Functional Requirements...........................................................................6

1.9.2.1 Eficiance..............................................................................................................6

1.9.2.2 relavence..............................................................................................................6

1.9.2.3 reliability.................................................................................................................7

1.10 Use Case description...................................................................................................7

Use Case diagram of user...................................................................................................8

C HAPTER # 2 DESIGN.....................................................................................................................9

2.1 Data Flow Diagram:.......................................................................................................10

C HAPTER # 3 PROCESS MODEL .................................................................................................11

1
3.1 Software Development Life Cycle followed...........................................................12

3.1.1 Water fall Model.....................................................................................................12

3.1.2 Figure of Model......................................................................................................12

C HAPTER # 4 DEVELOPMENT .....................................................................................................13

4.1 Languages Used:...........................................................................................................13

C HAPTER # 5 USER GUIDE ..........................................................................................................14

5.1 Home:..............................................................................................................................15

5.2 BAKING:..........................................................................................................................16

5.3. CHINES:...........................................................................................................................17

5.4 CONTINENTAL:............................................................................................................18

5.5 LOCALFOOD.................................................................................................................19

5.6 ABOUT............................................................................................................................20

5.7 CONTECT US...................................................................................................................21

C HAPTER # 6 TESTING .................................................................................................................22

6.1 Software testing.......................................................................................................23

6.1.1 Component testing..............................................................................................23

6.1.2 System testing......................................................................................................23

6.1.3 Cure.........................................................................................................................23

C HAPTER # 7 IMPLEMENTATION ...............................................................................................25

7.1 Tools and Technologies Used..................................................................................26

7.2 Interface Designing.....................................................................................................26

7.2.1 User-Friendly Interface......................................................................................26

7.2.2 Simple Language................................................................................................26

2
CHAPTER 1
ANALYSIS

3
 1.1 Introduction

This is a website developed for food to provide the information about food or
recipes. It uses Adobe Dreamweaver software. It is:

1.2 Product Features

This product includes the following features.

 Provide the whole information about food.

 People can get recipes online.

1.3 Statement of The Problem

In current system these facility are not to be supported without internet
 Peoples found recipes on books

 Consume a lot a time.

 Use a lot of money

In proposed system we provide fast and efficient platform, which solved the
above problem. Like:
 Everyone easily access information on web.

 Spend less amount of costs as compared to current system.

 Consume less time

1.4 Scope
A proposed system performs the following functions.

front:

4
 Website shows information about food recipes.

1.5 Hardware Requirement

Following are the hardware requirements (at minimum)

 CPU: 1GHz

 RAM: 4GB

 Resolution: 1280x768

1.6 Software Requirements

Adobe Photoshop

Adobe Dreamweaver

1.7 Assumptions and Dependencies

User of this website must have some basic knowledge about use of computer. It
is required that he/she must know that how to operate a computer. He /she must
be able to use interface of the website so that they can easily use this application
without help of any others.

1.8 Deliverables and Development Requirements

1.8.1 Deliverables
The deliverables for this project proposal form include the Website along
with the report for the final project.

1.8.2 Development Requirements

The following software is required for developing and implementing project
 Adobe Dreamweaver

5
 Google chrome

6
1.9 Requirements Analysis
Requirements analysis, an understanding of the problem domain was developed.
For this several different models of data, functional and behavioral domain may
be produced. A model is an abstract view of the system and the different models
express different kinds of information. The first step to the software requirement
analysis is problem recognition for which the existing step must be studied and
its evaluation and synthesis. The requirements are divided into two parts.

1.9.1 Functional Requirements

The basic functions of the project will be:

 Read online recipes

 Provide information about food.

1.9.2 Non-Functional Requirements

Before designing any software, it is essential and helpful to identify
objectives. Besides, the relative importance of each objective should also
be established. Keeping in mind the following objectives of the proposed
system are set.

1.9.2.1 Efficiency
As efficiency is defined as the economic utilization of available resources for
achieving a desired objective, so the system which is proposed is tried to be
more efficient because it is developed, keeping in mind that it utilizes minimal
human and financial resources, and still its output is far better in terms of time
and appearance and error free.

1.9.2.2 Relevance
Information provided to the people will be relevant, since this information can be
accessed from anywhere in country.

7
.

1.9.2.3 Reliability
The application will be more reliable, due to its accurate, secure and timely
decision-making.

1.10 Use Case description

An excellent technique to improve understanding of requirements is the creation

of Use Case. A use case is a narrative document that describes a set of
sequences; in which each sequence represent the interaction of things outside
the system (its actors) with the system itself (and its key abstractions). These
behaviors are in effect system-level functions that are used to visualize, specify,
construct, and document the intended behavior of your system during
requirements capture and analysis.

8
 Use Case diagram of USER

Baking

Chines

User Continental

Local food

About

Contact us

9
CHAPTE
R 2
DESIGN

10
2.1 Data Flow Diagram:

Reply from the System

HOME

BAKING

CHINES

USER
CONTINANTEL
SERVER

ABOUT

CONNTECT US

Reply from the System

11
CHAPTE
R 3
PROCESS
MODEL

12
3.1 Software Development Life Cycle followed

Keeping in mind the nature of the software and the components, we adopt
Waterfall approach for the development of our Hospital management System.

3.1.1 Water fall Model

The waterfall model is a sequential design process, used in software

development process, in which progress is seen as flowing steadily downwards
(like a waterfall) through the phase of conception, initiation analysis, design,
constriction, testing, production/implementation and maintenance.

3.1.2 Figure of Model

Analysis

Design

Coding

Testing

Implementation

13
 CHAPTER 4
DEVELOPMENT

4.1 Languages Used:

Following techniques are used in the development of FOOD MANIA

Website:

1. Hyper text markup Language (HTML).

2. Cascading Style Sheet (CSS).

3. JavaScript.

14
CHAPTE
R# 5
USER GUIDE

15
5.1 Home page:

1. When the user starts the website, he faces the following main home page
to get required information.

16
5.2 Baking:

When User click on baking button he face the following page and get information

17
5.3 chines:

When User click on chines button he face the following page and get information

18
5.4 Continental:
When User click on continental button he face the following page and get
information

19
20
5.5 Localfood:

When User click on localfood button he face the following page and get
information

21
5.6 about:

When User click on about button he face the following page and get information

22
5.7 contact us:

When User click on baking button he face the following page and get information

23
 CHAPTE
R 6
.

24
6.1 Software testing

Software testing is a process used to identify the correctness, completeness and

quality of developed computer software. Actually, testing can never establish the
correctness of computer software, as this can only be done by formal verification
(and only when there is no mistake in the formal verification process). It can only
find defects, not prove that there are none.

6.1.1 Component testing

 Testing of individual program components;

 Usually the responsibility of the component developer (except sometimes

for critical systems);

 Tests are derived from the developer’s experience.

6.1.2 System testing

 Testing of groups of components integrated to create a system or sub-

system;

 The responsibility of an independent testing team;

 Tests are based on a system specification.

6.1.3 Cure

I have try as much as possible to reduce errors In this website. The errors
were minimized by every aspect humanely possible, and ‘Try – Catch’
statement was used wherever needed, to provide user with the information

25
about the mistake he is making, and also to avoid program from becoming
unresponsive or crashing.

26
CHAPTER# 7
IMPLEMENTATION

27
7.1 Tools and Technologies Used

Microsoft Word is used for documentation and diagrams.

7.2 Interface Designing

Interface is designed in Microsoft Access. I have use built in object of Microsoft

access application i.e. Forms, to design the interface of this database. The output
of this stage will let the user be able to interact with system. The main purpose of
this phase is to develop a user-friendly interface for the ease of customer. The
quality of good interface is that it must be simple, user-friendly, and attractive.
The interface should not be complex.

I have considered the following factors while designing interface:

7.2.1 User-Friendly Interface

I have designed a very simple and user friendly interface. Proper interface
should are displayed on the screen to let the user know about the
guidance.

7.2.2 Simple Language

Very simple language is used on interface of this website so that a

beginner can also use this software without any problem the language
used on the screen should be simple and precise. Language should not
be complex or the steps should not be confusing to the user.

28