CHAPTER FOUR

SYSTEM DESIGN
4.0 Introduction
Based on the user requirements and the detailed analysis of the existing system, the new system
must be designed. This is the phase of system designing. It is the most crucial phase in the
developments of a system. The logical system design arrived at as a result of systems analysis is
converted into physical system design. Normally, the design proceeds in two stages:
1. Preliminary or General Design: In the preliminary or general design, the features of the new
system are specified. The costs of implementing these features and the benefits to be derived are
estimated. If the project is still considered to be feasible, we move to the detailed design stage.
2. Structured or Detailed Design: In the detailed design stage, computer-oriented work begins in
earnest. At this stage, the design of the system becomes more structured. Structure design is a
blue print of a computer system solution to a given problem having the Computer applications
same components and inter-relationships among the same components as the original problem.
Input, output, databases, forms, codification schemes and processing specifications are drawn up
in detail. In the design stage, the programming language and the hardware and software platform
in which the new system will run are also decided. There are several tools and techniques used
for describing the system design of the system. These tools and techniques includes flowchart,
data flow diagram (DFD), data dictionary, structured English, decision table, decision tree and so
on.

4.1 Design goals

There are many aspects to consider in the design of on every project. The importance of each
Should reflect the goals the system is trying to achieve. Some of these aspects are:

 Efficiency – this system will have a piece of hardware on which the system will
run and a piece of software to run it, this design will be efficient and provide
users easily interact with the system without any delay.
 Integrity - the new system will present accurate information and will cut down
the redundancy of the data by improving the integrity of the dat.
  Extensibility–the new system will accept future development of the company
and improvement of the technology and can be added new capabilities to the
system without major changes to the underlying architecture.
 Fault-tolerance - The system is resistant to and able to recover from component
failure.
 Reliability–the new system will able to perform required function under stated
conditions for a specified period of time.
 Security –The security of the new system will be high and can access the system
authorized users only, and if user will try to copy URL of the system to get
access power in to the system the new system will reject all unauthorized users
attempt the system.

4.2 Database design

Database design is the process of producing a comprehensive data model for any database with
storage and management parameters being pre-set. The database development life cycle starts
with requirements specification for the database and ends with its support and maintenance after
its implementation and deployment. Nowadays every business needs a database for the
management of its business data based on different querying models suitable for different
organizations. By carrying out a comprehensive analysis of Organizational database needs and
provide database solutions that fulfill business needs. As a carefully thought database forms the
foundation of business functionality and adds efficiency to the whole system. Database design
has basically three different Phases: - 1. Conceptual design: To begin with, one needs to be clear
about the Information System requirements, for which database and the procedures are to be
designed. This can be done by adopting systematic technique for structured analysis. It is a
process of constructing a data model for each view of the real-world problem which is
independent of physical considerations. This step involves: a. constructing the ER Model b.
check the model for redundancy c. validating the model against user transactions to ensure all
the scenarios are supported including ER Modeling, pictorial representation of the real world
problem in terms of 32 entities (which have attributes) and relationship between the entities is
referred as ER diagram. 2. Physical design: The actual structures of tables are created using a
particular DBMS package. The physical design shows how the files, records, fields are actually
stored on the physical storage media, depending upon the type of database, the DBMS supports.
This physical design giving complete logical view (the way user wants to view it) of the
database, is called schema. Various applications developers have the choice of getting different
logical views (which may be even partial) of the same database. They can customize these views
as per their specific needs. Such logical view is called subschema. DBMS provides tools for
creating the subschema. 3. Logical design: Logical database design helps us to define and
communicate our business information requirements. When we create a logical database design,
we have to describe each piece of information that we need to track and the relationships among,
or the business rules that govern, those pieces of information. Once we create a logical database
design, we can verify with users and management that the design is complete and it is accurate.
Creating a logical data design is an information-gathering and it is a iterative process. It includes
following steps: a. Define all table b. Establish Relationship between table c. Determine content
of each table and it constraints d. Normalize the form of table

4.3 Entity relationship diagram (ERD)

4.3.1 De-normalization of entity relational diagram
The word ‘de-normalization’ is used to describe changes to the table design that cause the
physical tables to differ from the normalized entity relationship diagram.
4.3.2. Normalization
Normalization is the process of organizing data in a database. This includes creating tables and
establishing relationships between those tables according to rules designed both to protect the
data and to make the database more flexible by eliminating two factors: redundancy and
inconsistent dependency. Redundant data wastes disk space and creates maintenance problems.
Most popular Normalization stages include:
 First Normal Form (1st NF)
 Second Normal Form (2nd NF)
 Third Normal Form (3rd NF)
The data is un-normalized form as the following
That entered data in the above table is un-normalized since a relation model does not permit this;
the table has to be normalized first. It stores details of the voter, candidate, position and voting
result.
First Normal Form (1NF): the following table shows the First normal form of Normalization.
Table 4.3.2.1 Table First normal form
ID branchname Adress Manager Contact

1 Varchar(15) Varchar(16) Varchar(15) Int (15)

Second Normal Form (2NF):

Table 4.3.2.2 second normal form (a)
I fullna email Adress gender branch job mo ph status userna Passw
D me name bile oto me ord

0 Varcha Varcha Varcha Varcha Varcha Varcha Int blo Varcha Varcha Varcha
1 r(19) r(19) r(19) r(19) r(19) r(19) (20 b r(19) r(19) r(19)
)

Table 4.2.4 second normal form (b)

ID product ID product_name quantity price

1 Int (15) Varchar(14) Int (15) Float

Third Normal Form (3NF) to be in Third Normal Form (3NF) the relation must be in 2NF
and no transitive dependencies may exist within relation.
Table 4.2.5 third normal form (a)
Store_ID Product_id Product_name quantity

Int (15) Int (10) Varchar(20) Int (15)

4.3.3Data dictionary
Data dictionary is central store house of information about System’s data. We will use it to
collect, document, and organize specific facts about system include the data flows, data stores,
external entities, and processes. The data dictionary also defines and describes all data elements
and meaningful combinations of data elements.
Table 1: Add branch table

Table 2: Add user table

Table 3: Order branch table

Table 4: Story Entry table

Table 5: Store table

4.4 Table design
Table 2: 4.4.1. Food Table

Column Type Attribute Null

s
F_ID Int (10) No
Name Varchar(30) No
price decimal(10,2) No
description varchar(50)
Image varchar(30) No

Table 4: 4.4.2 Order Table

Column Data type Attributes Null

Order ID Int (30) No

food name Varchar (30) No

Price Decimal (10,2) No

Qty Int (30) No

total Decimal (10,2) No

Order Date Date/time No

Status Varchar (30) No

Cust_name Varchar (30) No

Cust_contact Varchar (30) No

Cust_email Varchar (30) No

Cust_Address Varchar (50) No

Table 5:4.4.3 Category Table

Column Type Attribute Null

s
C_ID Int (10) No
Title Varchar(30) No
Image varchar(30) No

Table 3:4.4.4 manager Table

Table 6:4.4.5 Contact Table

4.5 Form design
Form design is where the developer of the system deeply explains system tasks and how forms
of the system are working together by observing the sequential flows.
Main Home Form Manager form

User Registration Form manager Registration form

Log In form Manager view Form

Food view form Restaurant registration form

4.5.1 Login form

Figure 4.1 login

4.5.2 Add branch form

Figure 4.2 Add branch

4.5.3 Order branch form

Figure 4.3 Order branch

4.5.4 Story Entry form

Figure 4.4 Story Entry

4.5.5 Add User form

Figure 4.5 Add User

4.6 Report design
Although many organizations try to reduce the flow of paper and printed reports and even
necessary. Reports, like other elements of the user-computer, interface, should be attractive and
must include the information that user needs. From a user’s point of view, a report with too little
information is off no value. The essential goal is to much the report to user’s specific
information needs.

4.7 Chapter summary

This chapter discusses about the design and the implementation of the project. Software and
database design were the following steps of this chapter which was the conversion of the
requirement analysis, to show the interior design of the system. After that we discussed the
database Design, Data Dictionary, Table Design, Form design and etc. Although we have
covered majority of the project still, we are going to the coding step of the project.