Report On

Chapter: 1.0

Organization Part

Engineered by:

Report On

Organizational Overview
DHAKA CENTRENIC IT Limited is web and graphics solutions provider at its core with the highly
qualified designers having experience of more than 7 years in various and complex designs. Other
than our core service like web design and development DHAKA CENTRENIC IT Limited has
satisfied the clients with the services like Mobile app Design and development, Software and Mobile
Testing, SEO and Social Media Designing & Development. We are customer centric and divert our
efforts to act as a one stop solution provider in the area of IT. In every area of our operations we
work hard in understanding the Clients requirement and providing the DHAKA CENTRENIC IT
Limited made solution.

Our Philosophy
We firmly believe in the philosophy of Our Asset Our People. We take pride in a team of highly
qualified, skilled and motivated Professionals who are encouraged to lead, innovate and excel. Our
team consists of top professionals who share a common vision and passion, providing our clients
with critical insights and advise to succeed in today's competitive environment. We believe in
delivering Expertise, Excellence Services through our past Experience and providing the highest and
best end use of services to our client.

Our Services

Apps Development
Web Design
Software Development

Engineered by:

Report On

Apps Development
In the past two years, the app market has exploded. In less than 9 months the Apple store reported over a
billion downloads, and then doubled that number in half the time. The app craze has spread to Android,
Blackberry, iOS and every other mobile market under the sun.
Having an app for your business or promotion or whatever it may be can be a game changing marketing
tool to drive traffic and revenue. On the highest end of the spectrum, you see Angry Birds making $50M
off a simple game. Then you also see people who put out basic free apps and still get thousands of
downloads for doing nothing.
A lot of conversations Ive had in the past year dont even talk about apps because the client thinks its
clearly going to be too expensive and they have no idea where to even start. The most important news
for client is that apps development is not much expensive what you thing.
Types of apps we develop
You can develop different kinds of apps its actually depend on your requirement and wanting what
type of apps you want to develop
We develop
1. Basic table functionality.
2. Database driven custom functionality.
3. Games
4. Enhancement or modification of the device firmware or hardware.
5. Fully dynamic apps.
6. Everything else.
For different mobile platform like

IOS

Android

Windows Apps

Social apps

Engineered by:

Report On

Our Apps Development Process

We develop apps in four different parts
1. The Idea: You need idea to build apps. So just give us your idea what you want to develop for
your company we will develop apps on the basis of your ideas.
2. Functionality Layout: The amount of functionality that needs to be defined and built will also
play a part in the cost of your apps.
3. Design: We ensure your exclusive design. We have an experience team those who will design
your desire apps for your company.
4. Going Live: This is a final stage of your apps development

Web-Design
At DHAKA CENTRENIC IT Limited we focus on creating search engine friendly, aesthetically
appealing and interactive website designs.
It is a known fact that to build a strong web presence and to secure the countless marketing opportunities
available on the internet, a good website is imperative, thus triggering a race for Website Design while
designing and developing your website, our professionals keep in mind key factors like easy-navigation,
overall consistency and content quality, stipulated timeframes and budget. Higher ranked on the Search
Engine result pages.

Engineered by:

Report On
Software Development
At DHAKA CENTRENIC IT Limited we offers fully integrated software development and technical
support solutions.
DHAKA CENTRENIC IT Limited is well-experienced custom software Development Company and
software outsourcing company. We have great expertise in the development of custom software
applications due to our professional team efforts in performing the work according to the need of our
offshore clients. We strive to focus on the customer and deliver solutions designed around their
requirements rather than focusing on a specific technology and expecting the customer to adapt to the
technology and platform of our choice. We use to fulfill specific needs of our clients as per their
convenience for their business.

Our Location at Bangladesh

Location
House: 34, 9th Floor, Sonargaon Janapath.
Sector: 11, Uttara.
Dhaka-1230.
Bangladesh.
Vision

To build a trusted IT Companies in Bangladesh

To be the largest Software Companies in Bangladesh
To be the largest online retailer
To be the best choice for people when they like to Apps Development
To be the largest SEO (search engine optimization) Marketing Company in Bangladesh
To be the largest IT company in World.

Mission
5

Engineered by:

Report On
Produce excellent service in the field of IT Service, Software Development, Website Design &
Development, Apps Development, SEO (Search Engine Optimization), SMM (Social Media Marketing),
Online Advertisement, e-database systems and banking home and abroad, E-commerce and Consultancy
with maximum effort driven toward customer satisfaction.

Our Mission at a glance:

To achieve maximum customer satisfaction over the entire life cycle of our customer solution via
our excellence of products and solutions.
To consistently enhance our competitiveness and deliver profitable growth.
To practice highest standards of corporate governance and be a financially sound company.
To be a partner in nation building and contribute towards Bangladesh economic growth.
To encourage ideas, talent and value systems and become the customers of choice.
To earn the trust and confidence of all customers, exceeding their expectations.
To uphold the guiding principles of trust, integrity and transparency in all aspects of interactions
and dealings. Vision to build upon a reputation of being one of the most innovative IT Solution
and Service provider. We believe in doing our work in the most efficient way with robust and
structured methodology, with gradual evolution from hard-work to smart- work culture, at
clients end also.

Engineered by:

Report On

Chapter: 2.0

Project Introduction

2.1

Introduction
7

Engineered by:

Report On
Internship is a practical exposure of theoretically gained knowledge and can be measured as a
preliminary trial to be aware with any organization and to make oneself confident enough to enter into
service life and start building career. As the outside world is very much competitive for anyone after
graduation, IUBAT-International University of Business Agricultural and Technology provides such an
opportunity to build up the capability with most appropriate opportunities. The student gets the chance
to apply his theoretical knowledge and practical skill that he has gained in the entire under graduation
student life. This documentation includes the details description of my project work during my
internship at The Dhaka CertreNIC IT Ltd. The internship period was for at least 16 weeks.
As I am intern at Dhaka CertreNIC IT Ltd, this project named as Shop Management system has been
assigned to me. This report is generated to describe the processes and works done in different levels of
management system development. In this report we have described every part of the development
segments with proper illustrations.

2.2

Background Of Study

Now a days management software is common software for all of us. Each and every office needs
management software for manage all the work done in the office. Before start the work we have done
some study such as which type of company it is. What they want in the software is, to add employee
information, take daily attendance, calculate their employee salary, add products by category and last of
all purchase report or generate billing paper.

2.3

Objectives

Around in attendance world, everything is technically sophisticated. Therefore, throughout the emergent
of this scheme I tried to give an intercontinental stance. The ultimate objective of the system is to
8

Engineered by:

Report On
provide facility to the user for management of a company. Security of this system is very high and the
possibility of doing wrong in the calculation is low. Since, now-a-days every system become
increasingly technically advanced, the proposed system will involve computerized Apply system,
Recruitment system, database storage, retrieval (through several functions), evaluation, agreement,
modifications and decision making supports which will make all processes involving the system much
faster and easier for the users.
The main objective of this system is to record all information including stocks and profit of a month,
which is essential when we need any kind of information than we can easily find out whenever needed.
This software provides to find out the information of employee. It will also generate the report of all
features of retail shop.

2.3.1 Broad Objective

The broad objective of this project is to use our institutional educational experience in the real life
working environment by developing Shop Management System for ZS. Computer.

2.3.2

Specific Objective

1. Add, Edit, Delete employee.

2. Update employee details
3. Take daily attendance of employee and also check monthly status of an employee.
4. Store all the product details with necessary information by its Category.
5. Calculate employee salary, check all paid salary and print salary report.
6. Calculate monthly profit store and print the profit.
7. Create Bill according to customer purchase and print bill.

2.4

Proposed System
9

Engineered by:

Report On
Management system is a system which can control and manage a company. Our proposed system is
management software which can store employee details, calculate the salary of the employee, and take
everyday attendance to the employee. The system can calculate every month profit, also calculate the
salary of every employee, and store the all products by its category and generate purchase report of a
customer.

2.5

Methodology

The development process on Shop Management System for ZS. Computer through Waterfall Process
Management Model will complete following the structure described later on Software Analysis &
Design.
This study on Shop Management System for ZS. Computer Waterfall Process Management Model is
tentative in nature. It aims to development of management System. The variables identified to
manipulate through a handy inspection and from primary and secondary data.
2.5.1

Data Sources:

For this project in data collection phase we collected two types of data i.e.
Primary Data
Secondary Data

Primary data are generated within the organization. The organizations practical experience,
observation, and face-to-face interview with our own web administrators helped us generate the
primary data.
Secondary data are generated by studying different articles, newspapers, research papers and of
course information collected via Internet. Data, facts and statistics collected from different web
sites and sources made us understand the project better.

2.6

Limitation of the Project

10

Engineered by:

Report On
As we had mentioned early in this report that practicum is the bridge between theoretical and practical
life, practicum program at IUBAT has given me this great opportunity to see how theories are put into
action. From our point of view, a 12-16 weeks practicum program is not good enough for a fresh
graduate to undergo. In my case, there were lots of terms, conditions and systems that were not
understandable for us at the beginning of our organizational attachment; however, lately I made our self
familiar with those terms that took over five weeks. So far, we have learned seeing my senior classmates
and friends, they had experienced the same during their time as well. One of the limitations of this
internship project is constraints of time. After applying the software engineering procedures, it is very
difficult to develop the complete software within short time. For this reason, the scope of the internship
project has become short. Moreover, many problems have been arisen in the data collection for the
software and also have load shading.
Therefore, we think personally that practicum program duration should last for at least six months for
the sake of clarifying theories put into practice and to better prepare for the working world. But at the
later stage I made myself familiar with the overall scenario.

2.7

Process model
11

Engineered by:

Report On
In our project we are using the Waterfall Model. The Waterfall Model is a linear-sequential life
cycle model. It is very simple to understand and use. In a waterfall model, each phase must be
completed fully before the next phase can begin. This type of model is basically used for the project
which is small and there are no uncertain requirements. Thats why we are chosen this type of
process Model.

Figure 2.2: Waterfall model

12

Engineered by:

Report On
2.7.1 Why Waterfall Model
1. Simple and easy to understand and use.
2. Easy to manage due to the rigidity of the model each phase has specific deliverables and a
review process.
3. Phases are processed and completed one at a time. Phases do not overlap.
4. Works well for smaller projects where requirements are very well understood.

2.8

Feasibility Study
Feasibility study determines whether that solution is feasible or achievable for the organization.
There are three major areas of feasibility study.

13

Technical feasibility

Economical feasibility

Operational feasibility

Engineered by:

Report On

Technical feasibility
The technical feasibility assessment is focused on gaining an understanding of the present
technical resources of the organization and their applicability to the expected needs of the
proposed system. It is an evaluation of the hardware and software and how it meets the need of
the proposed system. The proposed system is compatible with a low qualification of computer
with an internet connection only, as because its a web based software. As our client have well
organized laptop and desktop. To maintain our system need a computer with a browser and
internet connection which is already exists within the organization. In this way we can say that
our software is technically feasible.

Economical feasibility
The purpose of the economic feasibility assessment is to determine the positive economic
benefits to the organization that the proposed system will provide. Our system is economically
feasible because by using the proposed system many works can be done within small time and
which is not possible by man power within the same time. It also reduces the man power needed
for providing the inventory report, sales report, stock report and billing report. So they have to
pay less salary where the current system needs many employee and they are paying much salary.
So we can say that, if they use proposed system they will be economically benefited.

Operational Feasibility
User can easily operate the proposed system because the system is user friendly. Its easy to
insert inventory products and easy to create stocks. If the stuff of the organization has the basic
to computer knowledge they could operate the software easily. Every features and the activity
that are combined within the system is designed and developed belongs to previous format they
had used with a more attractive user interface.

14

Engineered by:

Report On

Chapter: 3.0

Requirement Engineering

Hardware Requirement:
15

Engineered by:

Report On

The hardware listed by no means a minimum requirement to run the system, but rather a base
limit for running the system smoothly and comfortably. This is also considering the potential amount of
traffic that may go through the server.

1 x Intel Pentium Dual Core G3250 - 3.2 GHz Processor.

2 GB (DDR3) RAM.

80 GB 7200 rpm SATA Hard Drive.

2 x 10/100/1000 Ethernet, 1 PCIe 2.0x16 slot.

Software Requirement:
-

Web Server
Xampp Server

Server Side Scripting

PHP 1.3

Database Engine
MySQL 5.1.34

Database Tools
MySQL Administrator
MySQL Query Browser

Designing Tools
Adobe Photoshop CS6

Text Editor
Notepad ++

Word Processor
Microsoft Word 2010

16

Engineered by:

Report On

Software Requirement for client:

Browser
-Windows Internet Explorer 8.0 or above
-Mozilla Firefox version 47.0.1
-Google Chrome 52.0.2743.82

3.1

Benefits Of The System

i.
ii.

Administrator will be able to maintain this system more accurately.

All the information will be stored on to the computer with its formatted

iii.

screens and built in databases.

All the information can be carried out more easily or quickly than any other

iv.

manual process.
Admin can easily take all information any time when he needs that stored by

v.

himself previously.
Admin can easily input the profit and cost information so that he/she can
create a report for profit analysis.

17

Engineered by:

Report On

Chapter: 4.0

System Planning

18

Engineered by:

Report On
4.1

Function Proposed System

Login into the System

F1

Add Employee

F2

Edit Employee

F3

Remove Employee

F4

Take In Attendance

F5

Add Stock

F6

Add Salary

F7

Calculate Salary

F8

Add Profit

F9

Create Bill

F10

A detailed view of the effort distribution chart illustrated below

4.2
19

Project Scheduling
Engineered by:

Report On
Project scheduling is an activity of distributing the estimated efforts within the planned project duration.
There are some basic rules for project scheduling. They are as follows
Compartmentalization The project must compartmentalize into a number of manageable activities and
tasks.
Interdependency The interdependency of each compartmentalized activity or task must be determined.
Some tasks must occur in sequence while others can occur in parallel.
Time allocation Each task to be scheduled must allocated some number of work units.

Effort validation Every project has a defined number of staff members. It should ensure that no more
than the allocated number of people has scheduled at any given time.
Defined responsibilities Every task that is scheduled should assign to a specific team member.

Defined outcomes Every task that is scheduled should have a defined outcome. The outcome is
normally a work product or a part of a work product.

4.2.1 Project Scheduling Chart

20

Engineered by:

Report On
Total system development is a combination of set of tasks. These set of tasks should done sequentially
and timely. Project schedule works as the guideline of the system developer. The following is the
schedule chart of this project.
Time

W1

W2

W3

W4

W5

W6

W7

W8

Activities
Requirement
Analysis &
Design
Coding & Unit
test
System testing

Figure 4.3: Project Schedule Chart

4.2.2 Personnel Requirement Chart

21

Engineered by:

W9

W10 W11 W12

Report On

Phases

W1

CC

1c
c

Planning

W2

W3

W4

W5

W6

W7

W8

W9

W10 W11

W12

Risk

Analysis

1
analyze

Design

1 designer

Developmen
t

1 coder

Testing

1 tester

Figure 4.4: Personnel Schedule Chart

4.2.3 Resource Requirement Chart

22

Engineered by:

Report On

Phases

M1

M2

M3

M4

Business
Modeling

Paper, Pen, Desktop PCs, Phone, Internet

Data
Modeling

Windows 7, Microsoft Office 2010, Draw.io

Process
Modeling

Windows 7, Microsoft Office 2010, Internet

Application
Generation
Testing & QA

Xampp, Notepad++
Xampp, Windows 7, Browser

Figure 4.5: Resource Schedule Chart

4.3

Cost Estimation

Cost analysis represents the total cost to complete any project. In this project, there are five factors to
analyze and calculate the cost. The factors are personnel cost, software cost, hardware cost and other
cost.
Personnel cost: Personnel cost is the salary of the customer communicator, system analyst and designer,
coder and tester. For estimating the cost the analyzer used the minimum industrial average.

i.

Software cost: It is the cost of the software is which used in this project
23

Engineered by:

Report On
ii.

Hardware cost: cost of the computer that used to complete the project.

iii.

Other cost: Other cost includes the cost of the house rent, telephone bill, electricity bill,
convenience and so on.

iv.
v.
vi.
vii.
viii.
ix.
x.
xi.
xii.
xiii.

Number of days in a year = 365

Number of government holidays in a year = 24
Number of weekly holidays in a year = 52
Total number of working days in a year = 365-(52+24) = 289 days
Total number of working days per months to develop the project = 289 /12 = 24.08 days
Organizations working hours per day = 8 hours
Organizations working hours per month = 24.08 *8 = 192.64 hours
Duration of the project
= 4 months
Total working hours per month
= 192 hours
Total working hours for the project
= 192*4 = 768 hours

4.3.1 Personal Estimation Cost

Position
System Analyst
Designer
Coder

24

Engineered by:

Salary/ Month
30720
24960
19200

Salary /Hour
160.00
130.00
100.00

Report On
Worker

No. of

Working

Total

First

Remaining Remaining

Position

Person

Hours

Salary

Payment

40%

40% Salary Salary

in 4

at 60%

Payment

distributed

of Salary

Each

months of Salary

Total

768

122880

73728

49152

Month
12288

632

82160

49296

32864

8216

82160

632

63200

37920

25280

6320

63200

122880

System
Analyst
Designer
Coder
268240
Total

TK

4.3.2 Hardware Cost

Cost of the computer that used to complete the project.
Name
Computer
Router
Printer

Number
2
1
1

Price
60000
2400
5600

Total Hardware Cost (10000 + 800 + 1900) = 12700 TK

25

Engineered by:

Description
60000 / 24 * 4
2400 / 12 * 4
5600 / 12 * 4

Total
10000
800
1900

Report On
4.3.3 Software Cost
It is the cost of the software is which used in this project.

Software

Number

Amount

OS (Windows 7)

50

MS Office

50

Xampp

Free

Notpad++

Free

4.3.4 Other Cost

Others Cost=1000/=

4.3.5 Total Cost

Total Cost (BDT) = 268240 + 12700 + 100 + 1000
= 282040 TK
In word: Sixty nine thousand and one hundred taka only

26

Engineered by:

Total

100

Report On

Chapter: 5.0

Risk Management

5.1

Risk Management
27

Engineered by:

Report On
Risk analysis and management are a series of works that help a system development team to understand
and manage uncertainty. Many problems can arise while developing a system. A risk is a potential
problem it may happen may not. There are several steps to analyze and manage risks. The first step is
risk identification. Next each risk is analyzed to determine the likelihood that it will occur and the
damage that it will do if it does occur. Once this information is established risks are remarked. Finally, a
plan is developed to manage those risks with high probability and impact.
There are different Stages of risks. They area:

1. Risk identification: Risk identification is the process of detecting potential risks or hazards
through data collection. A range of data collection and manipulation tools and techniques exists.
The team is using both automated and manual techniques to collect data and begin to
characterize potential risks to Web resources. Web crawling is one effective way to collect
information about the state of Web pages and sites.
2. Risk classification: Risk classification is the process of developing a structured model to
categorize risk and fitting observable risk attributes and events into the model. The team
combines quantitative and qualitative methods to characterize.
3. Risk assessment: Risk assessment is the process of defining relevant risk scenarios or sequences
of events that could result in damage or loss and the probability of these events. Many sources
focus on risk assessment. Rosenthal describes the characteristics of a generic standard for risk
assessment as "transparent, coherent, consistent, complete, comprehensive, impartial, uniform,
balanced, defensible, sustainable, flexible, and accompanied by suitable and sufficient guidance.
4. Risk analysis: Risk analysis determines the potential impact of risk patterns or scenarios, the
possible extent of loss, and the direct and indirect costs of recovery. This step identifies
vulnerabilities, considers the willingness of the organization to accept risk given potential
consequences, and develops mitigation responses.
5. Risk management implementation: defines policies, procedures, and mechanisms to manage and
respond to identifiable risks. The implemented program should balance the value of assets and
the direct and indirect costs of preventing or recovering from damage or loss.

28

Engineered by:

Report On
5.2

The RMMM Plan

RMMM Plane No: BR-01

Description
Impact
Prevention
Cure
Status

Installment risk for the project

It will make misunderstanding between client and organization
We will try to sell the project with full down payment.
License code implementation
Working on process

Business Risk
Disaster

RMMM Plane No: BR-02

Description
Impact
Prevention
Cure
Status

The project obsolescence to the clients

Business Risk
It will effect to clients when they organized it.
Disaster
Some extra features include within the projects. It will help us.
Reduce the project system for clients and develop much
updated way.
Done

RMMM Plane No: BR-03

Description
Impact
Prevention
Cure
Status

Competition of different market competitors.

Business Risk
It will increase the competition among organizations.
Disaster
Include some extra features within the projects. It will help us
to convince the clients.
Reduce the project cost for clients and focus on
Done

Description
Impact
Prevention
Cure
Status

RMMM Plane No: BR-04

Privacy and security risk of project
Client will hamper and hopeless about the system.
Included extra privacy and security system.
Resell the project very strongly by password system
Done

29

Engineered by:

Business Risk
Disaster

Report On
Description

RMMM Plane No: TR-01

Lack of adept technical persons for organization

Status

Technical
Risk
If it is happen then the client organization will be unable to Marginal
operate the system.
Arrange the training session for operators.
To send an expert process to the client organization for solve this
problem
Done

Description

RMMM Plane No: TR-02

Lack of implementation for organization

Impact
Prevention
Cure

Impact
Prevention
Cure
Status

The client fall in danger situation.

It will manage for the client to operate the system.
For solving this problem, modify this system with more
implement.
Done

Description

RMMM Plane No: TR-03

Responsive for different devices

Impact
Prevention
Cure
Status

Description
Impact
Prevention
Cure
Status

30

If the system is not responsive then it will not possible to browse

the site by different devices like tabs, mobiles etc.
Develop the system as responsive.
If problem arise then need to update the system for responsive.
Working on process.

Technical
Risk
Marginal

Technical
Risk
Disaster

RMMM Plane No: PR-01

Lack of required knowledge or skill
Project Risk
The development will hamper.
Marginal
Make detail conversation with the clients about their
requirement before.
To needed update the system according the clients requirements.
Done.

Engineered by:

Report On
Descriptio
n
Impact
Prevention
Cure
Status

RMMM Plane No: PR-02

Expire the project accomplishment time.
The agreement can be dismissed by the client
Try to complete the project within time limit.
Add extra team member with the development team.
Considered this term.

Project Risk
Disaster

RMMM Plane No: PR-03

Description Unclear or misunderstood scope/objectives
Project Risk
Impact
It will effete to the client organization and that will be unable to Marginal
operate the system.
Prevention Clean and clearly declared for operators.
Cure
Change some scope/objectives for solve this problem
Status
We will work this way in future.

31

Engineered by:

Report On

Chapter: 6.0

Analysis & Design

32

Engineered by:

Report On
In system analysis a study of the system as detailed as possible will occur with the help of some
diagrams i.e. Use Case Diagram, Activity Diagram, Swim Lane Diagram Data flow Diagram and Entity
Relational Diagram etc.

6.1

Use Case Diagram

A use case diagram at its simplest is a representation of a user's interaction with the system that shows
the relationship between the user and the different Use Cases in which the user is involved. A use case
diagram can identify the different types of users of a system and the different use cases and will often be
accompanied by other types of diagrams as well.

Fig 6.1: Use Case Diagram

6.2
33

Activity Diagram
Engineered by:

Report On
Activity diagrams, which are related to program flow plans (flowcharts), are used to illustrate activities.
In the external view, I use activity diagrams for the description of those business processes that describe
the functionality of the business system.
Contrary to use case diagrams, in activity diagrams it is obvious whether actors can perform business
use cases together or independently from one another.

Activity
An activity diagram illustrates one individual activity. In my context, an activity represents a business
process. Fundamental elements of the activity are actions and control elements (decision, division,
merge, initiation, end, etc.):

Elements are connected by so-called "activity edges" and form the "control flow", which can also be
casually called 'flow'. The execution of an activity can contain parallel flows. A border can surround the
activity, meaning the entire activity diagram.
Action
An action is an individual step within an activity, for example, a calculation step that is not
deconstructed any further. That does not necessarily mean that the action cannot be subdivided in the
real world, but in this diagram will not be refined any further.

34

Engineered by:

Report On
The action can possess input and output information The output of one action can be the input of a
subsequent action within an activity. Specific actions are calling other actions, receiving an event, and
sending signals.
Edge (Control Flow)
Edges, represented by arrows, connect the individual components of activity diagrams and illustrate the
control flow of the activity:

Within the control flow an incoming arrow starts a single step of an activity; after the step is completed
the flow continues along the outgoing arrow. A name can be attached to an edge (close to the arrow).
Initial Node
The initial node is the starting point of an activity. An activity can have more than one initial node; in
this case several flows start at the beginning of an activity:

It is also possible that an activity has no initial node, but is initiated by an event (action: accepting an
event).
Activity Final Node
The activity final node indicates that an activity is completed. An activity diagram can have more than
one exit in the form of activity final nodes:

If several parallel flows are present within an activity, all flows are stopped at the time the activity final
node is reached.

35

Engineered by:

Report On
Activity Diagram of Shop Management System

Fig 6.2.1: Activity Diagram

36

Engineered by:

Report On
Activity for Add Employee

Fig 6.2.2: Activity Diagram for Add Employee

37

Engineered by:

Report On
Activity for Edit / Delete Employee

Fig 6.2.3: Activity Diagram for Edit / Delete Employee

38

Engineered by:

Report On
Activity for Take Attendance

Fig 6.2.4: Activity Diagram for Take Attendance

39

Engineered by:

Report On
Activity for Add Category

Fig 6.2.5: Activity Diagram for Add Category

40

Engineered by:

Report On
Activity for Add Product

Fig 6.2.6: Activity Diagram for Add Product

41

Engineered by:

Report On
Activity for Add Profit

Fig 6.2.7: Activity Diagram for Add Profit

42

Engineered by:

Report On
Activity for Generate Bill

Fig 6.2.8: Activity Diagram for Generate Bill

43

Engineered by:

Report On
6.3

Entity Relationship Diagram (ERD)

The Entity Relationship Diagram (ERD) enables a software engineer to specify the data objects that are
input and output from a system, the attributes that define the properties of these objects and their
relationship. It provides an excellent graphical representation of the data structures and relationship.
They provide a clear view of the logical structure of data within the boundary of interest and allow the
engineer to model the data without considering the physical form. Some of the basic terms used in ERD
described below:
Entity: An entity is an object with physical existence or may be an object with conceptual existence. For
example a car, a student, an employee, an applicant.

An entity represented by a rectangle.

Relationship: A relationship is a logical linkage between two or more entities which describes how the
entities are associated with each other. A relationship described by a diamond.

Attribute: Attribute is a piece of information that describes a particular entity.

Primary Key: A primary key is an attribute or collection of attributes that allow us to identify an entity
uniquely.

44

Engineered by:

Report On
Foreign key: A foreign key is an attribute of a relation, which refers to an existing attribute of another
relationship.

Relationship Cardinality
Relationship cardinality refers to the number of entity instances involved in the relationship. The
cardinality ratios are:

1:1 (One to One)

1:M (One to Many)

M:M (Many to Many)

45

Engineered by:

Report On
.

ERD

Fig 6.3.1: Entity Relationship Diagram

46

Engineered by:

Report On
6.4

Data Flow Diagram (DFD)

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modeling its process aspects. A DFD is often used as a preliminary step to create an overview of
the system, which can later be elaborated. DFDs can also be used for the visualization of data processing
(structured design).
A DFD shows what kind of information will be input to and output from the system, where the data will
come from and go to, and where the data will be stored. It does not show information about the timing of
process or information about whether processes will operate in sequence or in parallel (which is shown
on a flowchart).

A context level DFD of the system is given below

Figure 6.4.1: Context Level DFD

47

Engineered by:

Report On
Level 1 DFD

Figure 6.4.2: DFD Level 1

48

Engineered by:

Report On

Level 2 Process 1

Figure 6.4.3: DFD Level 2 Process 1

Level 2 Process 2

Figure 6.4.4: DFD Level 2 Process 2

49

Engineered by:

Report On
Level 2 Process 3

Figure 6.4.5: DFD Level 2 Process 3

Level 2 Process 4

Figure 6.4.6: DFD Level 2 Process 4

50

Engineered by:

Report On
Level 2 Process 5

Figure 6.4.7: DFD Level 2 Process 5

Level 2 Process 6

Figure 6.4.8: DFD Level 2 Process 6

51

Engineered by:

Report On
Level 2 Process 7

Figure 6.4.9: DFD Level 2 Process 7

52

Engineered by:

Report On
6.5

Swim Lane Diagram

Figure 6.5.1: Swim Lane Diagram

53

Engineered by:

Report On

Chapter: 7.0

Interface Design

6.5.1 User Interface

54

Engineered by:

Report On
Home Page

Add Employee

55

Engineered by:

Report On
Manage Employee

Take Attendance

56

Engineered by:

Report On
Todays Attendance

Monthly Attendance

57

Engineered by:

Report On
Add Category

Add Product

View All Products

58

Engineered by:

Report On

Calculate Salary

All Paid Salary

59

Engineered by:

Report On

Add Profit Month

All Month Profit

60

Engineered by:

Report On

Billing

61

Engineered by:

Report On

Chapter: 8.0

Quality Assurance

62

Engineered by:

Report On
8.1

System testing

According to the common process framework (CPF), the software testing is the final activity that has to
initiate after testing. Software testing is a critical element of software quality assurance and represents
the ultimate review of specification, design and code generation.
The objectives of software testing are:
Testing is a process of executing a program with the intent of finding an error.
A good test case is one that has a high probability of finding an as-yet-undiscovered error.
A successful test is one that uncovers an as-yet-undiscovered error.
The design of tests for software can be challenging as the initial design of the product itself. Software
can be tested in one of two ways:
Knowing the specified function that the software has been designed to perform, tests can be
conducted that demonstrate each function fully while at the same time searching for errors in
each function. This approach is known as black-box testing.
Knowing the internal workings of software, tests can be conducted to ensure that internal
operations are performed according to specifications and all internal components have been
adequately exercised. This approach is known as white-box testing

8.1.1 Software Testing Strategy

A strategy for software testing integrates software test case design methods into a well-planned series of
steps that result in the successful construction of a software. The strategy provides a road map that
describes the steps to be conducted as part of testing.
Testing strategy that will be followed in this software project

Unit testing

Integration testing

Validation testing

The first step in software testing is unit testing. Unit testing concentrates on each unit of the software as
implemented in source code. Unit testing focuses on each component individually. The unit test is whitebox oriented. Thus, unit testing of this library software will be done after completion of every module or
component.
63

Engineered by:

Report On
The next step is integration testing. Integration testing is a systematic technique for constructing the
program structure while at the same time conducting tests to uncover errors associated with interfacing.
The objective of integration testing is to take unit tested components and build a program structure that
has been dictated by design.
The integration testing strategy that has been chosen for this project is top down testing. Black-box
testing method is the most prevalent for integration testing. Top down integration strategy will be used to
perform integration testing. Top down integration will be done by breadth-first manner. Breadth-first
integration incorporates all components directly subordinate at each level, moving across the structure
horizontally.
After the software has been integrated, a set of high order tests are conducted. Hence, the validation
criteria that have been mentioned in requirements engineering should be tested. Validation testing
provides final assurance that software meets all functional, behavioral and performance requirements.
The black-box testing method is exclusively used in validation.

8.2

System Testing Methodology

Black-box Testing
Black-box testing which is also known as behavioral testing focuses on the functional requirements of
the software. It enables the software engineer to derive sets of input conditions that will fully exercise all
functional requirements for a program. Black-box testing method will be applied to test the modules of
LMS.

64

Engineered by:

Report On

Figure 8.1: Black box & White box testing

White-box Testing
White-box testing, which also known as glass-box testing, is a test case design method that uses the
control structure of the procedural design to derived test cases. Using white-box testing methods,
software engineer can derive test cases that,
1.

guarantee that all independent paths within a module have been exercised at least once

2.

exercise all logical decisions on their true and false sides

3.

execute all loops at their boundaries and within their operational bounds

4.

Exercise internal data structures to ensure their validity.

The modules that contain some complex calculations or decision making code such as check the
availability of the library item will be tested using white-box method.

65

Engineered by:

Report On
8.3

Testing Design

Scenario
Inputs
Desired Outputs
Actual Outputs
Verdict

Testing scenario No: 1

Admin Login testing scenario of our system
Username, password of admin for Login
When enter username, password then get access level define.
For login our system work correctly
Getting result from Desired Outputs and Actual Outputs decided
this system is successful for login.

Testing scenario No: 2

Scenario
Admin can add employees
Inputs
employees basic info for registration
Desired Outputs When enter all basic info correctly, employee will be registered in
the system.
Actual Outputs For employee registration our system work correctly
Verdict
Getting result from Desired Outputs and Actual Outputs decided
this system is successful for employees registration.

Testing scenario No: 3

Scenario
Admin can edit and delete employees details.
Inputs
employees basic info updated and deleted by the admin
Desired Outputs When changed basic information for the employee by the admin.
Actual Outputs For update and delete employee info our system work correctly
Verdict
The process is worked correctly and successfully.

66

Engineered by:

Report On

Scenario
Inputs
Desired Outputs
Actual Outputs
Scenario
Verdict
Inputs
Desired Outputs
Actual Outputs
Verdict

Testing scenario No: 4

Give attendance to the employee
Admin can give attendance
Attendances save in the database.
Testingand
scenario
No:outputs
5
I check this process
get actual
System
adds
the
stocks
product
with
basic information.
The process is worked correctly and successfully.
Admin adds stocks with all information.
System takes all information display the product in stocks.
I check this process and get actual outputs.
The process is worked correctly and successfully.

Scenario
Inputs
Desired Outputs
Actual Outputs
Verdict

Testing scenario No: 6

Calculate employee salary with a calculator.
Admin takes employees monthly attendance from database.
Systems take all the attendance and calculate the salary.
I check this process and get actual outputs
The process is worked correctly and successfully.

Actual Outputs
Verdict

Testing scenario No:7

Calculate monthly profit and view all profits.
Admin give whole month all cost and incomes.
Systems take the information and calculate monthly profit and show
the all months profit.
I check this process and get actual outputs
The process is worked correctly and successfully.

Scenario
Inputs
Desired Outputs
Actual Outputs
Verdict

Testing scenario No: 8

Create, save and print bill.
Admin gives customer details along with product info.
Systems take all the attendance and calculate the salary.
I check this process and get actual outputs
The process is worked correctly and successfully.

Scenario
Inputs
Desired Outputs

67

Engineered by:

Report On

8.4

Quality Assurance Matrix

Requirement
Provided outputs
Decision

Quality Assurance scenario no: 1

The system worked according to requirement.
My requirement was Admin enters the system using username and password.
This system working correctly. We hope our system will work in future.

Requirement
Provided outputs
Decision

Quality Assurance scenario no: 2

The system worked according to requirement.
My requirement was admin can add employees with their details.
This system working correctly. We hope our system will work in future.

Requirement
Provided outputs
Decision

Quality Assurance scenario no: 3

The system worked according to requirement.
My requirement was admin can update and delete employee information.
This system working correctly. We hope our system will work in future.

Requirement
Provided outputs
Decision

Quality Assurance scenario no: 4

The system worked according to requirement
My requirement was admin can take attendance and view month wise
This system working correctly. We hope our system will work in future.

Requirement
Provided outputs
Decision

68

Quality Assurance scenario no: 5

The system worked according to requirement
My requirement was admin can add stocks product with all necessary
informations.
This system working correctly. We hope our system will work in future.

Engineered by:

Report On

Requirement
Provided outputs
Requirement
Decision
Provided outputs
Decision

Quality Assurance scenario no: 6

The system worked according to requirement
Quality
7 using a salary calculator.
My requirement
wasAssurance
admin canscenario
calculateno:
salary
The
system
worked
according
to
requirement
This system working correctly. We hope our system will work in future.
My requirement was admin can calculate the profit and generate a report.
This system working correctly. We hope our system will work in future.

Requirement
Provided outputs
Decision

Quality Assurance scenario no: 8

The system worked according to requirement
My requirement was admin can create bill according customer purchase
This system working correctly. We hope our system will work in future.

69

Engineered by:

Report On

Chapter: 9.0

Conclusion

9.1

Conclusion

70

Engineered by:

Report On
The four years of undergraduate engineering studies gives a student theoretical and practical knowledge.
Using that knowledge and observing live operational system, the practicum program clarifies those
subjects matters to another level blessed with practical working skills. Considering this fact, it gives us
an immense pleasure to say that our practicum was a successful event.

Practical work experience doesnt have any other alternatives. Before getting into the job student should
have a real world work experiences in a major field of study. Now a days recruiter no longer consider
just high grades , good communication skill, part time work experiences. They highly consider the work
experiences of an applicant. Students with better work experiences are getting the better job
opportunities.

Premier Trade Syndicate gives us the opportunity of working in a professional working environment.
During the internship period I have tried my level best to make my system efficient. I followed the
lessons, methods, tools and techniques that I have learned during my study period at IUBAT. Successful
software development is a blend of standard development practices, proper theoretical knowledge and
the developers creativity.

9.2

Future Implementation

Bibliography
Books and Internet Data:
71

Engineered by:

Report On
[1] Chen,

L.

(2000).

Enticing

Online

[8] Kubilus, N. J. (2000). Designing an e-

Consumers: A Technology Acceptance

commerce site for users. September 2000,

Perspective Research- in-Progress.ACM

Crossroads, Volume 7 Issue 1.

Proceedings, SIGCPR.

[9] Wordpress(March2015) [Online].

[2] Silberschatz, Abraham, Korth, Henry F,

Available:https://codex.wordpress.org/Theme_D

and Sudarshan S. Database System

evelopment

Concepts. 4th ed. Boston: McGraw Hill,

[10] Github (March 2015) [Online].

2002.

Available: https://github.com/panique/php-mvc

[3] Kendall, E. Kendall.

System Analysis

and Design.4th edition. New

Delhi:

Prentice Hall, 1999.

[4] Pressman,

Roger

S.

Software

th

5 edition. Boston: McGraw Hill, 2004.

S.

Pressman

Software

Engineering- A practitioners approach,

7th Ed. (BS).

Information

System.8th

International ed.2008.
[7] Miller, Dave. Data Communication and
Networks.1st ed.2006.

72

-statements.php
Available: http://www.codeigniter.com/docs
[13] Bootstrap (March 2015) [Online].
Available:http://www.tutorialspoint.com/bootstr
ap/bootstrap_code.htm
[14] Amazon (March 2015) [Online].
Available: http://www.amazon.com/gp/product/
[15] Ebay (March 2015) [Online].

[6] OBrien, James and M. Markas, George.

Management

Available:http://php.net/manual/en/pdo.prepared
[12] Codeigniter (March 2015) [Online].

Engineering:A Practitioners Approach.

[5] Roger

[11] php.net (March 2015) [Online].

Engineered by:

Available:http://www.ebay.com/cln/inspiredbyc
harm/Unique-ContainerGardens/194775859018
[16] Kaymu (March 2015) [Online].
Available:http://www.kaymu.com.bd/?
gclid=COm3r-OQ7MQCFU8mjgodj0YAkA

Report On
Shop Management System for ZS. Computer

73

Engineered by: