Chapter 4

Design and Implementation

4.1 System Design

The systems objectives outlined during the feasibility study serve as the basic from which the work of
system design is initiated. Most of the activities involved at this stage is of technical nature requiring a
certain degree of experience in designing systems, sound knowledge of computer related technology
and through understanding of computers available in the market and the various facilities provided by
the vendors. A system cannot be designed in isolation without the active involvement of the user. The
user has a vital role to play at this stage. As we know that data collected during feasibility study will we
utilized systematically during the system design. It should be kept in mind that detailed study of the
existing system is not necessarily over with the completion of the feasibility study. Depending on the
plan of feasibility study, the level of detailed study will vary and the system design stage will also vary
in the amount of investigation that still needs to be done. This investigation is generally an urgent
activity during the system. Sometimes this investigation may form a separate stage between feasibility
study and computer system design. Designing a new system is a creative process, which calls for logical
lateral thinking. The logical approach involves systematic moves towards the end product keeping in
mind the capabilities of the personnel and the equipment at each decision-making step. Lateral thought
implies encompassing of ideas beyond the usual functions and equipment.

4.2 System Design Considerations

The system design process is not a step-by-step adherence of clear procedures and guidelines. Though,
certain clear procedures and guidelines have emerged in recent days, but still much of design work
depends on knowledge and experience of the designer. When designer starts working on system design,
he will face different type of problems. Many of these will be due to constraints imposed by the user or
limitations of the hardware and software available in the market. It is difficult to enumerate the
complexity of the problems and solutions there. The variety of likely problems is so great and no
solutions are exactly similar. However, following considerations should be kept in mind during the
system designing phase:

4.2.1 Design Objectives

The essential target of the plan of the framework is to convey the requirements determined in the
achievability reports. The following plan goals ought to be remembered.
4.2.2 Cost
It is desirable to point for a framework with a base expense subject to the condition that it should fulfill
all the necessities.

4.23 Flexibility
The framework ought to be modifiable relying upon the changing requirements of the user. The
alterations ought not involve broad diversion of software. It ought to be portable to different computer
systems.

4.2.4 Security
This is very important aspect of the design and should cover areas of hardware reliability, fall
back procedures, physical security of data and provision for detection of fraud and abuse.
System design involves first logical design and then physical construction of the system. The
logical design describes the structure and characteristics of features, like the outputs, inputs,
files, database and procedures.

4.3 Major System Design Activities

A few advancement exercises are completed during organized design. They are database design,
implementation planning, system test preparation, system interface specification, and user
documentation.

4.3.1 Database design

Database design activity deals with the design of the physical database. A key is to determine how them
access paths art to be implemented. Database design is a decision on the programming language to be
used and the flowcharting, coding, and debugging procedure prior to conversion. The operating system
limits the programming languages that will run of the system. System and program test preparation.
System testing is done after all programming and testing finished the test on system and program test
necessities become a piece of plan determinations an essential to usage.

4.3.2 Design Process

The computer system design process is an exercise of specifying how, the system will work It is an
iterative process, which is based on what the system will be do as shown in the feasibility report. The
system design process are following five parts to complete it.
4.3.2.1 Output Design
The beginning stage of the design process is the appropriate information on system requirements which
will be changed in terms of output.

4.3.2.2 Input Design

The output requirements have been concluded, the following stage is to discover what information
should be made accessible to the system to deliver the ideal outputs. The essential records wherein this
information is accessible should be identified.

4.3.2.3 File Design

The input information is caught in the system, these might be protected either for a short or extensive
time. These information will by and large be put away in records in a legitimate way. The designer
should devise the techniques of storing and recovering information from these records.

4.3.2.4 Procedure Design

This step involves specifications of how processing will be performed.

4.3.2 Control Design

The control design indicates essential methods that will guarantee the rightness of processing, the
accuracy of the information, timely output. This will ensure that the system is working according to
design.

4.3.2.6 Software Requirements Specification

Inventory Management System is a computerized system which can helps a user to manage the daily
stock report in electronic format. It reduces the risk of paper work such as file lost, file damaged and
time consuming. It can help user to manage the transaction or record more effectively and time-saving.
4.4 Details System Design

4.4.1 Use Case Diagram

Add/Edit/Delete
User

Add/Edit/Delete
Group

Add/Edit/Delete View Brands

Brands

Add/Edit/Delete
Category
View Category

Add/Edit/Delete
Admin Stores

Add/Edit/Delete Staff
Products

View
Create/Edit/Delete Products
Orders

Manage Create Orders

Inventory
Report

Edit Profile
Edit Company
Details

Edit Profile

Fig: Use Case Digram

Admin Class Diagram

Admin Group Brand

User
User_id Group_id Brand_id
User_name Group_name Brand_name
Password Permission Status
Email
First name
Last name
Phone
Gender

Category
Category_id
Category_name Store
Status Store_id
Store_name
Status

Product
Product_id
Product_name Order Company
Sku Order_id Company_id
Price Bill_no Company_name
Qty Customer_name Service_charge_value
Image Customer_address Address
Description Customer_phone Phone
Brand_id Date_time Country
Category_id Gross_amount Message
Store_id Service_charge_rate Currency
Status Service_charge
Vat_charge_rate
Vat_charge
Net_amount
Discount
Paid_status
User_id

Fig: Admin Class Diagram

Staff Class Diagram:

Staff Brand Category

Brand_id Category_id
User_id Brand_name Category_name
User_name Status Status
Password
Email
First name
Last name
Phone
Gender

Product
Product_id
Product_name
Sku
Price
Qty
Image
Description
Brand_id
Category_id
Store_id
Status

Fig: Staff Class Diagram

 Admin ER Diagram: Id
has Name

Id
Status
Name
Status
Category
Brand SKU
Status Name
Price
Id
Qty
has
has
Product

Image
S_Id B_Id
select Select
Desc.
C_Id
Stock

User_Id
Status
includ
e Vat_C
Vat_C_R
Id
Id
Store S_C
Name
Order Bill_no
S_C_R
Status
Gross_amount C_Name
Id
Date C_Phone C_Address
Name
Net_Amount Discount Company
S_C_V

Id give Address
has
Name Group have Country
e
Status Message
Admin
Id
Phone Currancy
Name
Gender
Phone
F_Name Email Password
L_Name

Fig: Admin ER Diagram

 Staff ER Diagram: Id
has Name

Id
Status
Name
Status
Category
Brand SKU
Status Name
Price
Id
Qty
has
has
Product

Image
S_Id B_Id
select Select
Desc.
C_Id

User_Id
Status
includ
e Vat_C
Vat_C_R
Id
S_C

Order Bill_no
S_C_R

Gross_amount C_Name

Date C_Phone C_Address

Net_Amount Discount

give

Staff
Id
Phone
Name
Gender

F_Name Email Password

L_Name
Fig: Staff ER Diagram
ER Diagram often use symbols to represent three different types of information. Squire box
commonly use to represent entities. Oval use to represent attributes. Diamonds use to represent
operations. Lines use to represent relations between entities.

4.5 Data Flow Diagram

Figure: level 0

Figure: level 1
Figure: level 2 Process 1

Figure: level 2 Process 2

Figure: level 2 Process 3

Figure: level 2 Process 4

 Figure: level 2 Process 5

Figure: level 2 Process 6

4.6 Hardware requirements & cost:

 Monitor: Dell E1715S 17 Inch Monitor (9000*3=27000 BDT)

 CPU: Octa-core (50000 BDT)
 RAM: 8GB (4000*3=12000 BDT)
 Hard Disk: 3TB (4000*3=12000 BDT)
 Cache Memory: 3TB (2000*3=6000 BDT)
 Printer: HP 107w Single Function Laser Printer (9000 BDT)
Software requirements & cost:

 Microsoft Windows 10
 Microsoft office 13
 Visual Studio 2015