DETAILED DESIGN

1 .INTRODUCTION

The design level in which the internal design of the modules, or how the specifications of
the module can be satisfied is decided, is often called as the Detailed Design or Logic
design. Detailed design essentially expands the system design and the database design to
contain a more detailed description of the processing logic and data structures so that the
design is sufficiently complete for coding.
The first step before the detailed design or code for a module can be developed is that the
specification of the module be given precisely specified, the internal logic for the module
that will implement the given specification can be decided.

2 .APPLICABLE DOCUMENTS

This section describes the general factors that affect the software and its requirements.
Specific requirements are not mentioned, but mentioned, but a general overview is
presented to make the understanding of the specific requirements easier.
The proposed software is intended to collect, maintain and update all the information
about the shop. It is used to define the class of the establishment.
Management any faculty can also use this software to search out information of their
interest.
This software has been developed using PHP as front-end language and MySQL server
as back-end language which is supported by Microsoft Windows Operating System.

1
3. Structure of the software package
3.1 Functional Components
Functional components identified during the system design are listed below:

 Functional components 1: Home Page

Sub Module

 User Registration

 User Login

 Functional component 2: User Profile

Sub Module

 Contact information

 Profile Information

 Interests

 Language

 Functional component 3: Search friends

Sub Module
 Search by Email ID
 Search by User Name
 Search Profile

 Functional component 4: Message

Sub Module
 Wall post

 Blogs

 Functional component 5: Video / Photo Sharing

Sub Module
 Create Album

 Upload Photo

 Upload Video

2
  Functional component 6: Logout

4 Modular Decomposition of components

4.1 Modules of component1- Master
4.1. 1 Design assumptions
After the successful login entries the details of new items arrived for instances
invoiceno,date,custname,itemname,sellingprice,inviceqty,tprice,discount,totalprice,
grandtotal,remarks,amtwords,uname.
4.1.2 Identification of modules
User,Backup,Exit
4.1.3 Structure chart

Master

user information

backup
details
,
User Backup Exit

4.1.4 Datastructures and shared among modules

Table used is Biilbackup.
4.2 Modules of component2-Inventory
4.2.1 Design Assumption
Using this module we can identify the stock details.
4.2.2 Identification of modules
Newstock,Stock

3
4.2.3 Structure chart

Inventory

Newstock Stock

To add to view stock

Newstock

Stock Entry Addstock Viewstock

details

4.2.4 Datastructures and shared among modules

Table used is Itemdetails.

4.3 Modules of component3- Transaction

4.3.1Design Assumption
This modules stores the customer order,expense and Refund details
4.3.2 Identification of modules
Customer order,Expenses,Refound
4.3.3 Structure chart

Transactions

Customer Expense
details details

Customer order Expenses Refund

4
 Invoice Invoice view

4.3.4 Datastructures and shared among modules

Table used is Expense,Refund

4.4 Modules of component4- Reports

4.4.1 Design Assumptions
This form will generate reports for transactions and customers who have
taken products.

4.4.2 Identification of modules

Stock Reports,Bill Reports

4.4.3 Structure chart

Reports

Stock Reports Bill Reports

4.4.4 Data structures and shared among modules

Table used is Invoicebill,billbackup table

4.5 Modules of component5- Login

4.5.1 Design Assumption
It is used for the purpose of login as per the user type.
4.5.2 Identification of modules
Login

5
 4.5.3 Structure chart

Incorrect Input
Login
Uname,
Password,
utype

Login Close

4.5.4 Datastructures and shared among modules

Table used is Login table.

4.6 Modules of component6- Search

4.6.1Design Assumptions
This module will search for customers details based on his/her name or address.
Also he can search for products based on product ID or product name or description

4.6.2 Identification of modules

Bill search,Invoice search

4.6.3 Structure chart

Search

Bill search Invoice search

6
 4.6.4 Data structures and shared among modules
Table used is Invoicebill table

5.Detailed Design
5.1Module Design of comphonent1-Master
5.1.Master
5.1.1 Inputs: usertype,username and password

5.1.2Procedural Details(Flow chart)

Start

Create usertype,username and

password

Is input is correct

False

True
Displays on the table Enter Correctly

Stop

5.1.3 File I/O Interfaces

5.1.3 Outputs: Details is displayed in table.
5.2 Inventory
5.2.1 Inputs: Date, Stockid,itemname, companyname,phone,unitprice,qty,
totalprice, sellingprice, exprydate

7
 5.2.2Procedural Details(Flow chart)

Start

Date, Stockid,itemname,
companyname,phone,unitprice,qty, totalprice,
sellingprice, exprydate

Is input is correct

False

Enter Correctly
True

Stop

5.2.3 Outputs:Input details will be showned.

5.3Module Design of comphonent3-Transaction
5.3.1 Inputs: Here transaction details are entered such as customer name,
product description

8
 5.3.2Procedural Details(Flow chart)

Start

Check if user selects item

5.4.6.3. Output: It gives the details of transaction along with cost.

Add product to cart

Check if any items removed from the transaction

Remove item Buy

from transaction
list

Calculate total
amount

9 Display detail
Item removed
 Stop
5.4Module Design of comphonents4-Report

5.4..1. Inputs: Here customer name and date are entered.

5.4.2.Procedural Details: It retrieves transaction details. When generate button is

clicked it display the record. When we click transaction date wise button is
clicked the dates retrieves the transaction

Start

Customer Name and Date

Retrieve Transaction
Report from database

Display
the
Report

Stop

Figure 5.19: flow chart of reports.

5.4.3. Output: It gives the details of transaction.

10
5.5Module Design of Components5-Login
5.5.1.Input:Username and password.
5.5.2 Procedural Details (Structured Chart)

start

Input Username,Password

Is
Input is False
correct

True

Login

stop

Figure 5.13: flow chart of login

5.5.3.File I/O interface:-

Functional components login when clicked after giving the username
and password correctly it takes us to a new page which is the home
page, with other functional components.

5.5.4.Output:
Allows administrator to enter into a new page.

11
5.6.Module Design of Components6-Search
5.6.1 Inputs : Here search details are entered such as customer name, address,
phone ,credit, description, Quantity, expire date, total price.
5.6.2Procedural Details : It retrieves Customer and product search details. When
save button is clicked it search the record.

Start

Check if user selects False

search option

True

Category detail

Show product details

Stop

flow chart of search detail

5.6.3. Output : It gives the details of search along with their customer name,
address, phone , description, Quantity, expire date, total price.

12
13