46

9.1 Introduction
Design is the meaningful engineering
representation of something that is to be built. In the software
engineering context, design focuses on four major area of concern:
data, architecture, interfaces and component. Once the software
requirements have been analyzed and specified, software design is the
first of three technical activities—design, code generation, and test—
are required to build the and verify the software. After making
Software Requirement Specification of the education for all, now we
are in position to design the software. As discussed earlier data design
is the backbone of any RDBMS product. So firstly, we are emphasizing
on database design. The data design transforms the information
domain model created during analysis into data structures that will be
required to implement the software.

9.2 Database Design

As we have discussed earlier about the under
developing system, which is based on fulfillment of requirement of a
Mobile Shop so our database will be centralized database which will
run on sql server.

9.2.1 Data Structure

Data structure is a representation of the logical
relationship among individual elements of data. Because the structure
of information will invariably affect the final procedural design, data
structure is as important as program structure of the representation of
the software architecture. Data structure dictates the organization,
method of access, degree of associativity and processing alternatives
of the information.

9.2.2 Functional Dependencies

47
 The Functional dependencies (FD) are the
consequence of the interrelationship among attributes of an entity
represented by a relation or due to the relationship between entities
that is also represented by a relation.

9.2.3 Normalization
Normalization is a technique used in RDBMS to
decompose into table into two or more different tables to remove
functional dependency as well as redundancy. The normalization has
different form namely—First NF, Second NF, Third NF, BCNF and Fourth
NF. The decomposition of the table should be in the manner that data
should not be lost i.e. the union of the decomposed table should must
give the actual table. Normalization is also necessary to maintain
referential integrity. In our context, we used normalization technique
up to a three NF as our project had much number of DFDs and case of
data redundancy.

9.2.4 Table Description Table Structure

Table Structure:

There will be 6 tables in the CELL SHOP MANAGEMENT SYSTEM. The

normalized form of the table with their structure is described as under: -

Table 1: Login

48
Table 2 Customer Details

49
Table 3: Supplier Details

50
Table 4: Purchase Table

51
Table 5: Item Table Details

Table 6: Issue Table Details

52
9.3.1 Project Modules

Administration Process: This is one of the most important

modules. It involves the creation of users for the application. This
process deals with the login security and permission management
for each user to make data secure in the system.
Transaction Process: This function has been added keeping in
view the customer feedback regarding the product. This process
involves complaint / enquiry handling in efficient through manner so
as to establish long lasting customer satisfaction.
Report Generation Process: Any large-scale operation involves
generation of tremendous amount of data, which needs to be
analyzed by the management in order to have a clear and concise
picture of operation being carried out. Keeping in view this essential
requirement, there is a provision of Report Generation.
Master Process: The concept behind this module is totally
originated from the manual system. As per the old system, this
automated system also needs some initial data related to products
available in the showroom. Basically it is an entry module.
Updation Process: This module deals with the Updation of stock
values of products after each sale or receipt of product. It simply
updates the value of that particular product.
Complain-status process: This process deals with the complain
status. Complain status will be updated after its fulfillment. From
this, management will be smooth in customer service.

53