CHAPTER ONE

INTRODUCTION

1.1 Introduction

This chapter begins with the discussions of the historical or background of the area of foam
factory management system theoretically , conceptually and contextually around the world,
then the problem statement of this project , also presents the purpose of it . In this chapter
includes the objectives of this project , where it is used , what is used and the technology that
is used the developing of this project. At the end of the chapter presents the benefits of the
study for this project and how it is organized its contents.

1.2 Background of study

Investments dried up since State resources went to the war effort.( Creyf, H. and B.
Veenendaal, 1989).
In the world there are many factories that produce foam or mattress
Atlas Foam Products has been in operation for over 50 years. Located in Sylmar, Calif., it
provides an array of products, including flexible polyurethane, polyethylene, expanded
polystyrene (EPS), cross-linked polyethylene (L-200) and neoprene. The firm has over 100
varieties of foam formulations in stock. Atlas Foam Products provides services to various
local areas, such as Los Angeles, San Fernando Valley, Santa Clarita Valley, Simi Valley,

1
 Ventura, Oxnard, Orange County, Riverside and San Bernardino. It provides foam to
corporations, individuals and non-profit organizations.

American Foam Corporation is a designer and manufacturer of specialty foam packaging

material. With an 80,000-square foot facility, the company is a manufacturer of Sim-U-Vel
decorative and protective packaging. Its materials include Sim-U-Vel decorative flocked
velvet-like foam, polyurethane foams polyethers and polyesters, polyethylene foams and
cross-linked foams. American Foam Corporation converting processes include flocking, die
cutting, laminating and profiling. Some of the industries utilizing American Foam
Corporation s products include cosmetics, jewelry, medical, electronics and retail packs.

Before 1991, most of the industries were State-owned and managed and their
productivity had collapsed years before. Problems faced by this sector were
numerous. First of all, many industries worked thanks to Russian experts (costing very
little) who were expelled in 1977 since the Soviet Union was not eager to support the
war against Ethiopia.

After the collapse of the Somali government in 1990, industries and business were
totally neglected. While many of the Somali business men fled the country, those who
remained found themselves in extremely difficult conditions where they could not be
start a new business or build new industries because of the civil war and clannish feuds.
Situations are however improving in many parts of the country and consequently many
business men started to invent new Industries

Somali Foam Industry is the first foam factory built in Somalia. A private industry
established by local businessmen Ibrahim Salah and partners in 1977. It supplied foam
to all the regions in Somalia . Shakirbros started their business journey as local traders
in 1982. Since its inception Shakir has made consistent growth & also diversified itself
into new products and business lines. Whereby they turned to a representative &

2
 supplier of quality products sourced from various countries worldwide in 1991. The
principal products being tyres (Tires) batteries & Tubes from China, Korea and India. It
was 2003 when they brought to a foam factory to Mogadishu and named after Shakir
Foam Factory, and it is now the leading foam producer in Somalia. (Maxamed Sheekh
Yuusuf and Yaxya Amiir Ibraahim , August 2002)
Anshuur Co. produces mattresses. The plant started operating in February 2001. The
company has 5 shareholders of which two are managing it. The equipment comes from
Taipei and one Somali engineer was sent there to be trained. Raw material comes from
Dubai. The capacity of production is 300 mattresses (185cm X85 cm X 30cm) a day but
at the time of the survey only 170 were produced daily. Average price for an imported
mattress is US$ 13-15, while the locally produced one is sold US$ 10-11. An agent within
Bakara provides the marketing intelligence.

1.3 Problem Statement

As we are Computer Science graduators in Somali Institute of Management and

Administration Developments (SIMAD). We saw Shakir’s current system many problems,
here we define some of the problems:-
➢ File system
The main problem is that the file system requires a lot of time, costs of buying materials and
it lacks sufficient information and reliable reports about the current system.
➢ Lack of data sharing
This point is the central issue of investigation in the current system that doesn’t provide data
sharing, basic information and member of department.
When we observed the problems of the current system, we preferred to develop a new
system, in order to get these advantages:-
A. Convert from file system to database system
B. Facilitate the complexity of the job
C. Make data more reliable , accurate and secure
D. Make data flexible for updating

3
1.4 Purpose of Study

The aim of this study is to develop a desktop-based Shakir Foam Factory Management system
that will help the process of servicing customers in SHAAKIR.
The project will help from the customer to make the customer services process easily and to
retrieve the customer’s information in good manner, it will also increase the performance and
reduces size of space needed in the services process.

1.5 Objectives of the research

The objective of this Project is:

1) To study the related work for this project and opinions the experts in this area. 2)
To propose foam factory management system using data flow diagram (DFD)
3) To implement foam factory management system using JAVA with Netbeans 8.2 as front
end and SQL server 2008 as back end.

1.6 Scope of Project

The project will implement for Shakir foam factory in Mogadishu Somalia. Time scope this
study will be conducting in between In March 2015 August 2015.
The Elements of or tasks which this project will be completed are followings:

➢ Easily to register the customer’s information.

➢ Easy record the new Customer if it is need.
➢ Easy to Update and Delete the information when is not needed.
Since this is our final project for undergraduate level we develop it in six months
using JAVA with Netbeans 8.2 as front end and SQL server 2008 as back end.

4
1.7 Research Questions

Questions that highlight or serve as point scenario to proceed the study is here with the
relevant answer
✓ What is purpose for development of this system?
✓ How do we use for this system?
✓ What is the benefit of this system?
✓ Why do we need this system?
✓ What is the difference between this system and old system?

1.8. Significance of Study

There is relationship between Foam factory management system and Business development.
When to develop software that supported this reduces the Employee’s efforts because this
system is analyzing and planed Business solutions which allows making thousands of
Employee.

1.9 Project organization

The content of this project has been arranged to be read chapter by chapter as follows:
Chapter 1: Gives an introduction and background about the problem of the Foam factory
management system , In addition to that, this chapter will cover the objectives, scope,
significance of this project, expected outcome and how the project is organized.
Chapter 2: Presents an overview of the project in details (i.e. Components and Factors),
furthermore, this chapter cover and discusses the relevant literature of the Foam factory
management system.
Chapter 3: Describes how the data collected, analyzed, how the questionnaire has been done
and the finding of the analyzed data.

5
Chapter 4: Proposes the design of the project (Foam factory management system) in details
using Data Flow Diagram(DFD) and Deployment Diagram to make easy the implementation
of this project .
This chapter also covers or displays the Entity Relationship Diagram (ERD) , Database
design, table design and form design.
Chapter 5: is the last phase of the project and describes the implementation of this project
and testing it to produce complete functioning system.
Chapter 6: Finally this chapter provides conclusion and recommendations by describing the
strengths and achievements of the projects. This chapter also gives the weaknesses of this
project (Foam factory management system) and its future enhancements.

6
 CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction

The literature review deals with the issue and the researches that would help to understand
foam factory management system and the existing systems that are similar to it. The
objective of this literature review is to analyze the related work to this research and method
used in previous studies, and to evaluate their area (Egan, B. A.; Heinold, D. W.)
2.2 Foam factory and related environments
In the following section we briefly illustrate the concepts and ideas related to the online
foam factory systems used today in the world
2.2.1 Overview of Foam mattresses

A mattress is a large pad for supporting the reclining body, used as or on a bed. Mattresses
may consist of a quilted or similarly fastened case, usually of heavy cloth, that contains hair,
straw, cotton, foam rubber, etc.; a framework of metal springs; or they may be inflatable.

The word mattress derives from the Arabic matrah, which means "something thrown down"
or "place where something is thrown down" and hence "mat, cushion". During
the Crusades Europeans adopted the Arabic method of sleeping on cushions on the floor,
and the word mater as eventually descended into Middle English through the Romance
languages.( Nutt, A.R. and D.W. Skidmore, 1987)

7
Mattresses are usually placed on top of a bed base which may be solid, as in the case of
a platform bed, or elastic, e.g. with an upholstered wood and wire box spring or a slatted
foundation. Flexible bed bases can prolong the life of the mattress( CalRecycle (2012) )
Popular in Europe, a divan[3] incorporates both mattress and foundation in a single
upholstered, footed unit. Divans have at least one innerspring layer as well as cushioning
materials. They may be supplied with a secondary mattress and/or a removable "topper."(
Wayne, NJ, 1998.)

Early mattresses contained a variety of natural materials including straw, feathers or horse
hair. In the first half of the 20th century, a typical mattress sold in North America had an
innerspring core and cotton batting or fiberfill. Modern mattresses usually contain either
an inner spring core or materials such as latex, viscoelastic or other
flexible polyurethane foams. Other fill components include insulator pads over the coils
that prevent the bed's upholstery layers from cupping down into the innerspring, as well as
polyester fiberfill in the bed's top upholstery layers. Mattresses may also be filled with air
or water, or a variety of natural fibers, such as infutons. In Southeast Asia, bedding is
made with kapok. In 1900 English-born engineer, James Marshall introduced the first
individually wrapped pocketed spring coil mattress now commonly known as marshall
coils and founded Marshall Mattress,[4] a company that bears his name and is still in
operation in Toronto, Canada. He allowed VI-Spring patent rights in England where they
were known as Marshall Mattress of England until the 1930s.( Odell, R.T.; J.C. Dijkerman
Dijkerman)

In North America the typical mattress sold today is an innerspring; however there is
increasing interest in all-foam beds and so-called hybrid beds, which include both an
innerspring and high-end foams such as visco-elastic or latex in the comfort layers. In
Europe, polyurethane foam cores and latex cores have long been popular and make up a
much larger proportion of the mattresses sold. In South Asia, coir is a common mattress
material(Wiley, Y. M. J. & Sons. (1997).

2.2.2 Types of foam factory info system

8
 A mattress forms a considerably large part of the bed and it is responsible for providing
comfort and support to the body. Because a mattress can last for many years, buyers who
are searching for a mattress can benefit from investing time and effort in finding the right
one for their needs. There are different types of mattresses on the market, and the most
popular ones are the spring type and the foam varieties.

Mattresses are composed of three components: the core, the foundation, and the exterior
material. Originally, the core of the mattress consisted of natural materials such as straw,
feathers, and sometimes even paper or rice. Modern mattresses have an inner spring core -
coiled steel springs support the sleeper. Conversely, this technology also allows for
mattresses to be produced and sold for less depending on the use of certain materials. The
comfort and durability of innerspring mattresses depend largely on the number of coils in
addition to their gauge and thickness of the coils. Generally, a higher coil count is considered
a higher quality mattress. (Wayne, NJ, 1998.)Consumer Reports' June 2005 issue said a coil
count of 390 on a queen-sized mattress was plenty.

2.3 World foam factory systems

Foam Factory has grown from humble beginnings as a family owned

and financed business more than 30 years ago to become a global presence in the industry,
fabricating and distributing a broad range of foam, rubber, sponge and upholstery
products. With the uses for foam expanding rapidly, from assisting in commerce and
construction to the comforts of home, Foam Factory's ability to combine both
manufacturing and retail offers the most customization at the lowest cost. Providing a
wide range of products and services to "Foam Your World," we are able to cater to both
the personalized request of an individual as well as the larger needs of businesses,
allowing you to accomplish your goals(D. and Watson. (2001).
Through the ingenuity of our customers and team, we always have an eye open for
new, practical solutions that our products can provide to the public. With uses ranging
from packaging, pillows and bedding, to furniture, molding and in flooring, we are

9
committed to finding applications for our products that satisfy your needs at the best
possible price.

Located in Southeast Michigan, Foam Factory operates from a facility encompassing

nearly 310,000 square feet, allowing us to keep a large amount of inventory on hand to
deliver the quickest service while keeping costs low. Also, we are always looking for
ways to become more efficient in our solutions to customer needs(Walther, S. (1998). Our
continued investment in computer-controlled machinery and other technologies provides
even more precision and versatility in manufacturing our products. And through the
recently redesigned website, Foam Factory makes it even easier to discover new uses for
our products and place orders. But most importantly, it allows us serve you better.

2.4. Somalia foam factory systems

A huge fire gutted down the main building of Mubarak Foam Factory, one of largest foam
production factories operating in Somalia capital, Mogadishu, destroying property worth
hundreds of thousands of US dollars.
Witnesses told that the a mysterious fire blaze started at 12: 00 pm local time on Saturday
night in Huriwa district, north of Mogadishu after a sudden fire erupted inside the factory
before spreading to nearby stalls.
Mahad Abdukadir, the chief executive officer (CEO) of Mubarak Foam Factory, said
Sunday that the overnight fire did not cause any human casualties, but they lost a large and
bulk of property.
“The building of the factory was also severely damaged as electric and production machines
went up with flames” he said, adding that the cause of the fire was not immediately
identified.” ( Steve J. Lautze of the City of Oakland)
The situation was worsened by the strong winds making it difficult for the fire fighters from
the local residents to put it off or prevent the spread of the fire into the whole building.
Mubarak foam factory is a private industry established by local Somali businessmen in
Mogadishu, the capital of Somalia.( Cabdulqaader Maxamed Xasan,2002)

10
2.5 Advantages of Foam mattress

Advantage of foam mattress is already quite mature , it has a good air permeability and
impact resistance. its softness and strength to support body are more responsible, and most
cost-effective . Relatively speaking the chain early spring can force average and thereby
increasing the life of the mattress . the late independent spring can fully reflect body curve
engineering.

2.6 Existing Similar system

The information about the content is needed to carry out the analysis of the needs of current
strategy and improvement for teaching so that new design of the Foam factory system
achieves the maximum learning and teaching effect. The design stage which includes the
involvement of researchers and helps to develop the best system for the purpose of research.

2.6.1 Esun International CO.,LTD.

Specializes in manufacturing mattress-making machineries. Our whole range of mattress-
making machineries adopts America, Switzerland etc advanced standard of technology and
design. Thus our machineries are more highly automated with high production rate and
efficiency, saving more labor cost and Power consumption, occupying less space and have
longer life spans and many other Advantages. It include: spring machine, foam machine,
quilting machine, packing machine and so much equipments, also our supply widest
platform for clients to choose: mattress ticking, mattress spring-net clip, staples, pneumatic
tool, ventilated air hole, mattress handle, steel wire, mattress tape and so a series of
production.

All along, our company has continuously imports foreign countries

technology, combining it with our own Chinese technology to produce

11
generation and generation of new machineries. Now, we are proud that our
machineries have sold to all parts of the world: South-East Asia, America,
Europe, Africa, Middle East, etc. We have also appointed agents in many
of these countries to provide better service and support for all our customers.
Our company with our responsible, honest and always-improving attitude,
strives to achieve better service and support for all old and also new
customers.

2.6.2 Foshan City Maxdon Furniture CO.,LTD.

Foshan City Maxdon furniture Co., Ltd. mainly produces mattresses, sofas, sofa-beds
(fabric and leather) series and office chairs with high quanlity and competitive price. And
the products we produce are sold very well in the world wide, such as Japan, America,
Europe, and the Middle East, ect. We warmly welcome all of you!

A comparison on few similar existing systems is conducted in order to find out the
similarities and the differences among them . this will assist in identifying the strength and
weakness of the proposed system foam factory management system . the comparison was
done based the following criteria login , search , comment , symptom , consultation and
report as shown in the above table . the weaknesses of the proposed system (Foam factory
management system). The comparison was done based on the following criteria: Login,
Search , Comments, Symptom
Esun International Co., Ltd. ESUN is a specialized mattress machine manufacture and
mattress accessories supplier. It was established in the beginning of 2000 and has over 10
years experience of manufacturing and distribution. Main mattress machine includes:
Mattress machinery, quilting machinery, foaming cutting machinery, foaming machinery
and other mattress accessory machines.
In the meantime, ESUN also specialize in offering mattress materials, including: All kinds
of mattress fabric, felt(pad), non-woven fabric, plastic nets, mattress tape, mattress clips,
staples, ventilated air hole, matterss handles, sewing threads, semi-finished quilted ticking,

12
and steel wire for spring, mattress springs, mattress spats, mattress labels, mattress legs,
mattress packing film, mattress packing bags and so on.

they supply, Superior products, ,Competitive price, Professional marketing

advice, Timely and efficient after-market service ,Honest and reliable management
style
Serious and responsible working attitude, Smooth and effective business communication,
Timely and stable delivery date, Timely products update,
while Foshan City Maxdon Furniture Co., Ltd. is oshan City Maxdon furniture Co., Ltd.
mainly produces mattresses, sofas, sofa-beds (fabric and leather) series and office chairs
with high quality and competitive price. And the products we produce are sold very well in
the world wide, such as Japan, America, Europe, and the Middle East, ect. We warmly
welcome all of you!

2.7 Chapter Summary

This chapter is about the literature review that discusses the researches of existing
systems, which gives a better understanding of Online Foam factory management system.
It also shows the similarities and the differences that the existing systems have by
comparing them and discusses related things of the current system. It will represent the
border or limitation of the current system.

13
 CHAPTER THREE

REQUIREMENT ANALYSIS

3.1 Introduction

In this chapter , Requirement analysis we will present the requirement analysis used in
this project, and will defined how the project problem has been solved. It starts with the
project approaches and followed by a presentation of the project design, the data
collection tools and furthermore a description of how the data is analyze. So it also
presents the user requirement analysis process of the study. It outlines user requirement
specification; data gathering techniques and procedures which were used , feasibility
study and etc.

3.2 User Requirement Analysis

This project uses as analysis tool the DFD to describe the proposed system's analysis
phase activities and the end product of the system analysis phases.

3.2. Data flow diagram (DFD)

A data flow diagram (DFD) is a graphic representation of the ‘flow’ of data through
business function or processes. More generally, a data flow diagram is used for the
visualization of data processing. It illustrates the process, data, and external entities.
Note that: A data flow diagram (DFD) show how data moves through an information
system but doesn’t show program logic or processing steps.

DFDs use four basic symbols which are:

14
 1. Process

2. Data Flow

3. Data Store

4. External entity

Context Diagram

Customer Foam Supplier

Level
Factory0
managemen
t
System

15
 1

USER AUTHENTS ADMIN

CADE

AUTHENTICATED USER AUTHENTICATED ADMIN

Retrieving CreateInformation
and Retrieving Create and Create and Create and Report
Create and
General retrieve Employee retrieve retrieve retrieve Capability
retrieve
Transaction Customer Transaction General Customer Supplier
Employee
Transaction Information Capability
Transaction Transaction Transaction Transaction

Employee Report
Employee
transaction Customer transaction
Transaction

Transaction

16
 Level 1 (GENERAL TRANSACTION)

USER ADMIN

Checking
Application

USER INFO ADMIN INFO

Create and Create and Create and Create and

retrieve retrieve retrieve retrieve
Customer Customer Customer Customer
Information Information Information Information

17
 LEVEL 2 (CUSTOMER TRANSACTION)

USER

Authenti
cating
User

REGISTER
CUSTOMER
CUSTOMER REGISTRATION

UPDATE
CUSTOMER

18
 LEVEL 3 (CUSTOMER ORDER)
CUSTOMER

ORDERING
PROCESS
CUSTOMER REGS

CHECKING
CUSTOMER

CREATE DELIVERY
INVOICE ORDER

CUSTOMER INFO

3.3 Current system

19
 After long time o investigation current system we proposed to develop a new system of
foam factory management system (FFMS) which services as documentation as the
name of information needs to record.
The current system which Shakir works now, depends on these parts;-

➢ Sales and marketing department

The marketing and selling department of the industry is meant for to produce filterized
mattresses from the industry so as to take to the customers generally .The office of this
department also manages the employees and the structure of the work they are
doing...This office use file system for the daily work routine especially they use
Ms excel and Shakir packages which is especial software they use

➢ Cash department

Cash department of the industry maintain its role to record the list of the money that make
the department and the outgoing money of the industry, and also it manages and gives
the employees' salaries. The cash department office uses software like:
Ms word and excel. Shakir packages which is especial software that uses to cover
customer balance and deposits.

3.4 Data gathering

Some techniques were used to collect data from the Shakir foam Industry, including
Interview
The interview is the primary techniques for information gathering during the systems
analysis phases of project development phases. It is a skill which must be done by
every analyst in order to know what information you have gathered, the quality and in-

20
 depth of that information. Interviewing, observation, questionnaire and research are the
primary tools in the data gathering of the project. When we were collecting the data, we
met the director of Shakir foam Industry (SFI). We have asked about twenty five
questions. Some of them are:-

1) When the Industry was established?

2) Why it is established? And how to satisfy it’s customers?
3) And also asked its parts, branches, how they communicate, number of plastics they
produce per day?

The director of sells marketing department told us:

❖ The way customers deliver the mattresses.

❖ How they take their employers by environmental or educational experience
❖ How they communicate using nation link telecommunication
❖ Service providers customers by cash and totally.
❖ Numbers of employee the Industry have.

Observation

After we observed how the industry works , we saw that the industry uses software
like :- MS word , Excel , and especial software which the industry implements its
services . According to our observation, we also saw that the industry uses automatic
machine using for its production . And also saw how the industry manages its
employees.

21
3.5 Feasibility Study

Depending on the results of the initial investigation the survey is now expanded to a
more detailed feasibility study. “feasibility study” is a test of system proposal according
to its workability, impact of the organization, ability to meet needs and effective use of
the resources. Feasibility study is more important and it’s the high level study of a
system that clarifies the objectives of the proposed system it provides a better
understanding of organization problems it access and recommend what courses of
action should be taken for its solution. Feasibility study is divided into four main areas:

• Technical feasibly study

• Operational feasibility study
• Schedule feasibility

3.5.1 Technical Feasibility

The new proposed system will be developed with expert personnel, software technology
and the current equipment. According to feasibility analysis procedure; the technical
feasibility of the system is analyzed and the technical requirements such as software,
hardware facilities, procedures, and inputs are identified. It is also one of the important
phases of the system development activities. What kind of hardware and software will be
required? We have just mentioned above that technical requirements we will be needed to
develop the new system. But before that, it’s a good scheme to propose or designed what
to do (this means what category of software and hardware we need and their minimum and
maximum quantity). So the table below illustrates the hardware requirements with its
maximum and minimum quantity.

22
 No Name Description QTY Unit Total
Price
1 Computer 80 GB HDD, 1GB 1 $500 $500
RAM, core i3 : 2.3
GHZ
2 Printer HP Laser Jet 1320 1 $100 $100
(any other laser printer )
3 Software 1 WIN7/8, 1Anti- 1 $20 $20
Packages Virus , Visual Studio ,
SQL server and
Microsoft office
Total $620

• Table 3.1 Technical feasibility

3.5.2 Operational Feasibility

The system is operationally feasible as it is very easy for the end users to operate it. It
only needs basic information about Windows platform. Furthermore, compared to the
existing system; the proposed system will provide a better working environment in which
there will be ease of work and the effort required will be comparatively less than the
existing system. Also the time required generating a report or for doing any other work
will be comparatively very less than in the existing system. Record finding and updating
will take less time than the existing system. The new system is a user friendly system but
in order to implement the new system, the current employee should upgraded and give
some training. This training will take no longer than 2 weeks. The users will have an
ability to work and manage the new system by using documentation guidelines. They
also should have general idea and good concept about PC’s, this helps the operators to
manage and work efficiently their data and retrieve everything related for manipulating
the data. The cost that spend for training users is maximum $300 but there is cost that is
used for maintainace of the project that is $ 1100 because of the importance of it.

23
3.5.3 Economical feasibility

Economically feasibility is the most important part of the feasibility study of this project.
This involves questions such as whether Shakir foam factory can afford to build the
system, whether its benefits should substantially exceed its costs, and whether the project
has higher priority than other projects that might use the same resources. New budget
requirement of the new system is shown in the following table:

Name Cost

Technical $620
Operational $1400

Development $1500
Cost
Total: $3520

Table 3.2 : Economic feasibility of OSDS

3.5.4 Schedule Feasibility

Time evaluation is the most important consideration in the development of project. The
time schedule required for the developed of this project is very important since more
development time effect machine time, cost and cause delay in the development of other
systems. Since this project is intended for academic purpose specially undergraduate
degree ,it is developed for six months or one semester.

24
3.5.5 Feasibility Study Report

After we find the needs to build this new system according to the Technological,
economical, and operational modal, we illustrated that if we get all these needs we will
develop this new System accurately, we will install it to your computers and it will able
to fulfill all requirements specifications needed by the proposed system which intends to
be developed.
In this investigation phase we use feasibility report to explain overall the new system;
especially feasibility study is to evaluate the conclusion products of the investigation
phase. It is, in addition, estimated the objectives of completing the whole project to prove
it with possible time into a report that will be feasible to the control of the employee
management system. The idea behind the feasibility study is to weigh up the outcome
products of the investigation phase and the investigation made to the existing manual
system. It also estimates both goal accomplishment processes and to confirm it with a
short report that will be possible to the power of the organization. Estimate the feasibility
report. Finally we sure this project will Facilitate a lot of existing problems rapidly and
support for enhancement in the near Future.

3.6 New Proposed System

Now it comes to the development of a new system, that’s able to convince and solve all
drawbacks with the old system in terms of security, reliability, and accuracy. The new
system will not need to be hired for a new employee; it will require only upgrading the
skills of the current employees. New system will satisfy Managers and Employees

25
3.6.1 Goals of proposed system

1. Planned approach towards working: - The working in the organization will be

well planned and organized. The data will be stored properly in data stores, which will
help in retrieval of information as well as its storage.
2 . Reliability: - The reliability of the proposed system will be high due to the above
stated reasons. The reason for the increased reliability of the system is that now there
would be proper storage of information.
3. No Redundancy: - In the proposed system utmost care would be that no information
is repeated anywhere, in storage or otherwise. This would assure economic use of
storage space and consistency in the data stored.
4. Immediate retrieval of information: - The main objective of proposed system is to
provide for a quick and efficient retrieval of information. Any type of information
would be available whenever the user requires.
5. Easy to Operate: - The system should be easy to operate and should be such that it
can be developed within a short period of time and fit in the limited budget of the user.
3.6.2 User Characteristics
Every user should be:
• Comfortable of working with computer.
• He must have knowledge in industry field.
• He must also have basic knowledge of English too.

3.6.3 Constraints
• GUI is only in English.
• Login and password is used for identification of users.

26
3.7 Solution Strategy

After we had discovered the current system’s problems, we decided to develop a new
system, which stands the needs of the Shakir foam factory . This solution is associated
with implementing sufficient reliable and wiping out the current existing problems;
therefore, we considered the solutions and strategies proposed by experts to reach this-
like goal and program high quality system

Option 1 Java with Netbeans & SQL server 2008 Best option
Option 2 PHP and MYSQL server Second option
. Table 3.3 : Solution strategy and option
Option One
In our group discussion; we decided to take JAVA with Netbeans as front-end and SQL
server 2008 as back-end since all projects are subject to limited resources and time; we
determined Our work within the following economic, technical and operational
boundaries.

3.7.1 Front-end and Back-end selection

An important issue for the development of a project is the selection of suitable front-end
and back-end. When we decided to develop the project we went through an extensive
study to determine the most suitable platform that suits the needs of the organization as
well as helps in development of the project.

Front end selection is Java with Netbeans which has the following advantages:
• Security
• User Friendly
• Flexibility
• Easy to debug and maintain.

27
 Back end selection is SQL server 2008 and the following advantage
:
• Multiple users
• Operating System compatibility
• High performance and processing

3.8 System Requirement Specification

3.8.1 System Interface

Application would be a self-contained system. It will not access data of any other
application nor will other application have access to its data.

3.8.2 User Interface

Application will be accessed through a Browser Interface. The interface would be
viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. No user would be
able to access any part of the application without logging to the system.
3.8.3 Hardware Interface

Server Client

Core i3 2.4 GHZ or above Dual core 2.3 GHZ or above

4 GB RAM or above 2GB RAM or above

500 GB HDD or above and NIC 240 GB HDD or above and NIC

28
3.10 Chapter Summary

In this Chapter, we have discussed important points on the User Requirement Analysis
of the system starting form introduction of the chapter then the User Requirements after
that we discussed the Preliminary Investigation, Organizational Profile, Data Gathering,
DFD Diagrams, Feasibility Study and User Requirements Specifications. Finally, we
have covered all that now we are going to step the Design step of the project.

29
 CHAPTER FOUR

SYSTEM DESIGN

4.0. Introduction

Design is one of the system design life cycle steps, during the system design, we contract a
physical model of the information system based on the logical model We developed in the system
analysis phase .
In this chapter, we will focus on how to design the user interface , input , Procedures, and output
required to support business requirements, a key design Element is user interface , which
describes how users interact with the System and often the user interface mainly consisted of
process-control screens that allowed the user to send commands to the system and user interface
design requires an understanding the human computer interaction which Describes relationship
between the computer and people who use them to Perform business-related task
4.1. Design goals
The flowing goals were kept in mind while designing the system:
Make system easy and flexible for users:
End users who aren’t programmers should be apple to have an extreme amount of control over
their purposes, this could be used efficiently and system could act as catalyst in achieving
objectives.
Make the system compatible:
I.e. it should fit in the total integrated system, future maintenance an enhancement must less.
Make the system reliable, understandable, coast effective.

30
4.2. Database Design

Designing a Database Like most tasks, building a database starts with a design. After all, you
wouldn’t try to build a house without a blueprint, and most people wouldn’t attempt to prepare a
new dish without a recipe. Like these other tasks, having a good design for your database is a major
first step in creating a successful project.
In designing a database application, you must set up not only the program’s routines for
maximum performance, but you must pay attention also to the physical and logical layout of the
data storage. A good database design does the following:
 Provides minimum search times when locating specific records
 Stores data in the most efficient manner possible to keep the database from growing too
large.
 Makes data updates as easy as possible
 Is flexible enough to allow inclusion of new functions required of the program

4.3. Database Design Objectives:

When you’re creating the design for your database , you must several objectives in your mind.
Although meeting all these design objectives is desirable, sometimes they are mutually
exclusive.
The primary design objectives are as follows:
 Eliminate redundant data
 Be able to locate individual records quickly
 Make enhancements to the database easy to implement
 Keep the database easy to maintain

4.5. Database Design Methodology

Design methodologies deal with how a company goes about designing a database. A design
methodology is the approach taken toward the design of a database. It is the process of designing
a database with a sound plan from the beginning.

31
For individuals lacking the proper knowledge and experience, designing a database probably
involves a great deal of trial and error. If an individual understands database fundamentals and
design concepts, the basic steps of the database design process, and has a structured plan (has
selected a design methodology), the design process should produce a quality product to the
customer.
Some of the advantages of using a design methodology include:
 It provides a step by step guide toward database design.
 Little or no trial and error is involved.
 It is easy to document the database and application with the availability of design
plans, drawings depicting the organization’s needs, and other deliverables specified.
 It is easy to modify the database in the future as organization and planning eases the
tasks of managing changes.

Design methodology traditionally involves the following three phases:

 Requirements analysis
 Data modeling
 Design and Normalization

4.6.Entity Relationship Diagram

Entity relationship diagram (ERD) is a model that identifies the concepts or entities that exist
in a system and relationships between those entities.
ERD is often used as a way to visualize relational database; each entity represents a database
table, and the relationship lines represent the keys in one table that points to specific records
in related table.

32
Entities
An entity is a business object that represents a group, or category of data. For example, a
category of information associated with an online book shopping is book titles. Another category
is authors because an author might have written many books.
Entities are objects that are used to logically separate data.

Attributes
An attribute is a sub-group of information within an entity. For example, suppose you have an
entity for book titles. Within the book titles’ entity, several attributes are found, such as the
Actual title of the book, the publisher of the book, the author, the date the book was published, and
so on. Attributes are used to organize specific data within an entity.

Relationship
Relationships are associations between entities, and they are shown by lines that connect the
entities together. Every relationship has a parent entity and a child entity, the parent being the first
entity in the relationship, and the child being the second.
ERD Symbols
ER diagram is used to represent database schema.
 A rectangle represents an entity set.
 A Diamond represents Relationship
 An ellipse represents an attributes.
 Lines represent linking of attributes to entity sets & of entity sets to relationship sets.

Attribute Line
Entity Set Relationship
Figure 4.1:
Entity Relationship Diagram Basic Symbols

33
Types of Relationship

Relationship is an association among one or more entities. This relationship can be broadly
classified into the following sections: -

Relation Type Representation

One-to-one

One-to-many

Many-to-many

Many-to-one

Table 4.1: Types of relationship

 One-to-one:

A one-to-one relationship represents a relation between entities in which one occurrence of data
in one entity might have one occurrence of data in the related entity. Entity A might have only one
occurrence of related data in entity B, and entity B might have only one occurrence of
related data in entity A.

A B

 One-to-many

In most relational databases that we have seen, the one-to-many relationship seems to be the
most common relationship that exists. A one-to-many relationship represents a relation between
entities in which one occurrence of data in one entity might have one or more occurrences
of data in the related entity. For example, entity A might have several occurrences of related data
in entity B.

34
 A B

 Many-to-many

A many-to-many relationship exists if multiple occurrences of related data are allowed

to exist between two entities, in either direction. For instance, entity A might have many
occurrences of related data in entity B, and entity B might have many occurrences of
related data in entity A..

A B
 Many-to-one

The relationship between customer and order details is an example of many to one relationship,
because customer may have several order occurrences order details.

A B

35
 Customer

Item Store

Order request

Add Item

Item manager

Deliver
Get Items

Figure 4.2. Entity Relationship Diagram

36
4.7. De-normalization

De-normalization is the process of taking a normalized database and modifying table structures
to allow controlled redundancy for increased database performance. However. Data redundancy
is increased in a de-normalized database, which might improve performance but requires more
extraneous efforts in order to keep track of related data. When de-normalization is employed, it’s
usually a derivative of normalized data, so that even if an atomic unit of data exists in several
places, it is derived form one source. De-normalizing a database: Why would you ever want to do
that? Attempting to improve performance is the only reason to ever de-normalize a database. A
de-normalized database is not the same as a database that has not been normalized. De-normalizing
a database is the process of taking the level of normalization within the database down a notch or
two. Remember, normalization might actually slow performance with its frequently occurring
table join operations.
De-normalization might involve recombining separate tables, or creating duplicate data within
tables. This will reduce the number of tables that need to be joined in order to retrieve the requested
data, which results in less I/O and CPU time.
Regards to our previous analysis, we came up with four entities, they are customer, item store,
deliver and item manager so that we will need to change the names of two entities like item store
as books and item manager as

4.8. Normalization

Normalization is the process of reducing the redundancy of data in a relational database.

Redundant data refers to the data that is stored in more than one location in the database.
Data should not be redundant, which means that the duplication of data should be kept to a
minimum for several reasons. For example, it is unnecessary to store an customer’s home address
in more than one table. With duplicate data, unnecessary space is used. Confusion is always a
threat when, for instance, an address for customer in one table does not match the

37
address of the same customer in another table. Which table is correct? Do you have documentation
to verify the customer’s current address? As if data management is not difficult enough,
redundancy of data could prove to be a disaster. On the other hand, there are also
benefits to databases that have not been normalized, mainly related to increased database
performance.
Thus, we focus on the process that a developers might take to normalize a database during design.
Many issues must be confronted during database design that might have an impact on
normalization. In this project, the following topics are discussed in detail:
 Overview of normalization, including the advantages and disadvantages of normalization
 Discussion of the NORMAL FORMS, or levels of normalization

4.8.1: Overview of Normalization

Normalization is the application of a set of simple rules called FIRST, SECOND, and THIRD
NORMAL FORM to assign attributes to entities in the ERD. Although there are additional levels
of normalization beyond THIRD NORMAL FORM such as Boyce-Coded, FOURTH, and FIFTH
levels of NORMAL FORM (which we will discuss), normalization of a production
Relational database generally stops at the THIRD NORMAL FORM.

4.8.2: Purpose of normalization

Its purpose is to eliminate data redundancy, avoid data update anomalies that can occur in un
normalized databases (databases that have not been normalized), and to simplify enforcement of
integrity constraints.
A database that is not normalized can include data that is contained in one or more different tables
for no apparent reason. This is not optimal design with regard to security reasons, disk space usage,
query retrieval speed, efficiency of database updates, and most importantly, data integrity. A
database before normalization is one that has not been broken down logically into smaller, more
manageable tables.

38
4.8.3: Levels of Normalizations

NORMAL FORM is a way of measuring the levels, or depth, to which a database has been
normalized. A database’s level of normalization is determined by the NORMAL FORM. The three
common NORMAL FORMS are as follows:
1. The first normal form
2. The second normal form
3. The third normal form

1. FIRST NORMAL FORM: The Key

The objective of the FIRST NORMAL FORM is to divide the base data into logical units called
entities, or tables. When each entity has been designed, a primary key is assigned to it.
The entity has a UID (key) and all attributes must be single valued. A repeating or multi valued
attribute is an attribute or group of attributes that will have multiple values for one occurrence of
the UID. You would have to repeat the attribute(s) multiple times in the entity structure in
order to capture all the possible occurrences of the event being modeled. The solution is to move
repeating attribute(s) to their own entity and create a relationship between the two decomposed
entities. Working with tables in design, you’d move the repeating columns to heir own table along
with a copy of the original entity’s UID as a foreign key. As you look at an entity, ensure that
each entity attribute is single-valued with no repeated attributes allowed.

39
Example of First Normal Form (1NF):
This data is un normalized one: `

Order_id Customer_id Item_name Qty Price category Deliver

1 101 Jodari 12 20$ mumtaz Salim

2 102 Kursi 8 10 2dabaq Fatxi

Table 4.2. Un Normalized Formy

This table contains repeating columns, and un normalized data for example: if you want to delete
or to update one column of this table there will be update problems.
In order to achieve the First Normal Form, data has to be broken into logical units, each having a
primary key, and moving data to the related primary key, and ensuring that there are no repeated
groups in any of the tables.
First Normal form

Oder detail table

Order_i Customer_i Cost_ Sub_tota Cost Shipping Shipping Shippin

d d Subtota l _tota _first_nam _ g
l _shippin l e Address _city
g
1 56 67 7878 89 Bohol Dolow Gedo
garas

2 67 7 66 8 Elbuur Galgadud Baqbaql

e

40
 Table 4.3. Oder detail table First Normal Form
Item Table
Isbn Item_Name Deliver_id Cat_id Qty Price description Deliver
408 Jodari 4 4 1 30 New Salim
version

846 Kursi 3 5 5 9 Update Salim

matter

Table 4.4. item Table, First Normal Form

Customer Table

Cus_id password confirmpass name address city phone

1 2222 2222 Hassan Wadajir baydhabo 67676

2 4444 4444 Hussein Hoddan Gedo 87878

Table 4.5. Customer Table, First Normal Form

Category table

Category id Category name

2 Mumtaaz

6 2dabaq
Table 4.6 Category table first Normal form

Deliver Table

Deliver_id Deliver_name Address

2 Five Star Soma

6 Barkin Good Night Bakaro

Table 4.7 Deliver table first Normal form

41
2. SECOND NORMAL FORM (2FN) : The Whole Key

The objective of the SECOND NORMAL FORM is to take data that is only partly dependent
on the primary key and enter it into another table.
The entity is in FIRST NORMAL FORM and if an entity has a composite UID (that is, it takes
more than one attribute to make an instance of the entity unique), all the non-UID attributes must
be dependent on all the UID attributes—not just one or some of them.

Example of Second Normal Form (2FN):

The Second Normal Form is achieved by separating attributes that are only dependent on part of
a primary key, as follows:

Item Table
Isbn Item_Name Deliver_id Cat_id Qty Price Description Fk
Pk
408 Joodari 4 4 1 30 New version

846 Kursi 3 5 5 9 Update item

Table 4.8 Item table second Normal form

Customer Table

Cus_id(pk) Password Confirmpass Name address city fk

1 2222 2222 Saacid Yaqshid baydhabo

2 4444 4444 Ibrahim Hoddan Gedo

Table 4.9 . customer , Second Normal Form

42
Oder_details table
Order_id(pk) Cus_id ISBN Quantity Fk
1 1 002 87

2 2 887 23
Table 4.10. Oder_details, Second Normal Form

The second normal form , the order_details table has been split into five tables, item table and
deliver table, order_details table and customers table.

3. THIRD NORMAL FORM: And Nothing but the Key

The THIRD NORMAL Form’s objective is to remove data in a table that is not dependent on the
primary key. The entity is in SECOND NORMAL FORM and a non-UID attribute can’t depend
on another non-UID attribute. All non-UID attributes should depend directly on the whole UID
and not on each other. Put another way, attributes don’t have attributes of their
own. If attributes do have attributes, they’re really entities.

Example of Third Normal Form (3fn)

An attribute dependency on the UID—which is not direct but only passes through another
attribute that is dependent on the UID—is called a transitive dependency. Transitive dependencies
are unacceptable in Third Normal Form.
Category need to be moved from the Books entity to their own category entity as a violator of

43
THIRD NORMAL FORM.
The second normal form , again, the books table has been split into two tables, books table and
category table .

Item table
Customer Table Order table

Isbn(pk) Customer_id(pk) Order id (pk)

Password(pk) Customer_id(fk)
Item_name (pk) name
address

Un-normalized
(UDF)

Remove repeating
groups
First Normal Form
(1NF)
Remove partial
dependencies
Second Normal Form
(2NF)
Remove transitive
deficiencies
Third Normal Form
(3NF)

Figure 4.4: Common first three normal forms for normalization

44
The following figure shows how all tables in the database design are connected together:

Figure 4.5 Database Relationship diagram

45
4.9. Data Dictionary

Data dictionary, or data repository, 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 4.11: Customers

Column Type Null

customer_id varchar(50) No
Name varchar(50) No
Address varchar(50) No
Email varchar(100) No
phone_number int(12) No

Table 4.12: Customer_Service

Column Type Null

Transaction_No Int(7) No
ID varchar(255) No
Cust_name varchar(50) No
Item Int(4) No
Type Int(4) No
Quantity Int(4) No
Price Int(4) No
Amount double(4,2) No
Descount
NetAmount Text No
Date Date No

46
Table 4.13: Store Table

Column Type Null

Pro_No int(5) No
Pro_Name varchar(50) No
Type varchar(50)
Quantity int(4) No
Date Date No

Table 4.14: Return_Table

Column Type Null

Ret_Id int(4) No
Name varchar(50) No
Type varchar(50) No
Quantity varchar(50) No
Date varchar(50) No

Table 4.17: User_account

Column Type Null

User_id int(4) No
User_name varchar(50) No
Password varchar(50) No
Confirm varchar(50) No
User_Type varchar(20) No
Secret_Quation double(7,2) Yes
Secret_Answer varchar(255) No
Date varchar(100) No

47
Table 4.20:: Production

Column Type Null

Pro_Id varchar(120) No
Name varchar(120) No
Type varchar(20) No
Quantity varchar(100) No
Date varchar(100) No

4.10. Designing Data Entry Form

The most effective method of data entry is a form filling, in which a blank form that duplicates
or resembles the source document is completed on the screen. The user enters the data and then
moves to the next field. The form can have many control features such as menu navigations, labels,
text boxes, command buttons, drop-down, check boxes, Radio buttons and
more others the design of data entry forms shall consist of the following forms:
 User Login form
 User Creation form
 Store Form
 Production Form
 Customer Registration form
 Customer Services Form
 Customer Receipt Amount Form
 Return Form

48
 Before designing these forms, we would prefer to explain the controls of the forms

Text Box

Label Label

Drop-down list


Button


Radio button Check box

Button
Figure 4.6: description of form controls

User Log in page

User Name

Password

Log in Cancel

Figure 4.7: log in form

49
User creation Form

User_Id

name

Password

Confirm

Type (Select One)

Secret_Quation (Select One)

Date

Create Cancel

Figure 4.8: sign up from

50
 4.11. Report Design

Although many organizations strive 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.12. CHAPTER SUMMARY

In this we have discussed important points on the Design of the system starting form introduction

of the chapter then the goals of system such as security reliability and others goals after that we

discussed the database Design, ERD, Data Dictionary, Table Design, Form design, and Report

Design although we have covered majority of the project still we are going to the coding step of

the project.

51
 CHAPTER FIVE

SYSTEM DEVELOPMENT

5.0 Introduction

The goal of coding phase is to translate the design of the new Shaakir Foam Factory
Management System, in chapter four Design phase was discussed that is translated into code
written in one of the most powerful programming language which JAVA The aim of the phase
is to implement the design in the best possible manner. The coding phase affects both testing
and maintenance profoundly. A well written code reduces the testing and maintenance effort.
The remaining of this chapter discusses the followings in section I will discuss the coding
phase which makes the system easy understandable for coding; in section II will also be
highlighted at Types of Testing, and the User Documentation will be discuss in section III, and
in section IV an Implementation will be highlighted

5.1. CODING PHASE

Testing and debugging is next phase once the coding phase is completed. Testing phase is the
process of executing a program or system with the intent of finding errors. Or, it involves any
activity aimed at evaluating an attribute or capability of a program or system and determining
that it meets its required results. Although crucial to software quality and widely deployed by
programmers and testers, software testing still remains an art, due to limited understanding of

52
the principles of software. The difficulty in software testing stems from the complexity of
software: we cannot completely test a program with moderate complexity
The purpose of testing can be quality assurance, verification and validation, or reliability
estimation. Testing can be used as a generic metric as well. Correctness testing and reliability
testing are two major areas of testing. Software testing is a trade-off between budget, time
and quality. The complete coding phase of the project can be achieved on the attached CD
Disk.

5.2. TYPES OF TESTING

Testing phase is the process of executing a program or system with the intent of finding errors.
Or, it involves any activity aimed at evaluating an attribute or capability of a program or system
and determining that it meets its required results. Although crucial to software quality and
widely deployed by programmers and testers, software testing still remains an art, due to
limited understanding of the principles of software.

. The purpose of testing can be quality assurance, verification and validation, or reliability
estimation. Testing can be used as a generic metric as well. Correctness testing and reliability
testing are three major areas of testing.

5.2.1 Unit testing

The testing of individual program or module is called unit testing. The objective is to identify
and eliminate execution errors that could cause the program to terminate abnormally, and
errors that could have been missed during the checking. Test date should contain both correct
date and erroneous date and should test all possible situations that could occur. For

53
example, for a field that allows a range of numeric values outside that contain minimum values,
maximum values outside the acceptable range, and alphanumeric characters.

5.2.2. Integration testing

Integration testing is the phase in software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before system testing.
Integration testing takes as its input modules that have been unit tested, groups them in larger
aggregates, applies tests defined in an integration test plan to those aggregates, Testing more
than one program that depend on each other is called integration testing, or link testing.

5.2.3. System testing

After completing integration testing, system testing will performed, which involves the entire
information. A system test includes all typical processing situations and is intended to assure
users, developers. During system testing, user enter data including samples of actual, or live,
data, perform queries, and produce report to simulate actual operating condition.

54
 TEST CASE:
Instructor Main Form:
When the administrator wants to register new instructor the administrator will select instructor
menu and clicks registration and registration form will appear this form also allows the
administrator to update, delete and search any registered record, the form looks like this:

Figure 5.0 Main Form

55
HOW TO LOGIN THE SYSTEMS;
TEST LOG:
Log In Form:
Here we are going to how the login page works and its validation because we are in test log,
so this project is a well-organized in fully mistake protected so we are not only mention the
validation rules but we display as well.
Look here: if the user enters invalid account the system present message box which appears
like this:

Figure 5.1 Login Form

If user enter incorrect user name or password will prompts this massage.

56
 5.3. USER DOCUMENTATION

Documentation describes an information system and helps the users who must interact with it.
Accurate documentation can reduce system downtime, cut cost, and speed up maintenance

task. Documentation is essential for successful system operation and maintenance. In addition
to supporting a system’s users, accurate documentation is essential for developers

who must modify the system, add new features or perform maintenance. Documentation
includes program documentation and user documentation. Mostly of the documentations are
presented in project as help and users will get there. There are many types documentations
include: program documentation and system documentation.

CREATING NEW USER:

If the user differs the password and the confirm password fields the system will presents the
following message box which looks like this

HOW TO CREATE NEW USER ACCOUNT:

➢ Go to file menu and click create new user account
➢ Fill in the fields that you see on the form
➢ If the user tries to create an existing username he/she will be denied and will told that this
user is already exists
➢ If the user enters deferent password in password and confirm password fields he/she will be
informed that these fields does not match
➢ If the admin corrects all requirements and selects register button he/she will be informed that
new user has been created successfully.

57
Figure 5.2 User Form

58
Customer Services Form

Figure 5.3

5.3.1. Program Documentation

Program documentation describes the inputs, and processing logic for all program modules,
the program documentation process starts in the system analysis phase and continues during
systems implementation. In the system analysis phase will prepare overall documentation, such
as process description and report layout, early in system development life cycle.

59
 5.3.2. System Documentation

System documentation describes the system’s functions and how they are implemented.
System documentation includes data dictionary entries, data flow diagrams, screen layout,

source documents. System documentation is necessary reference material for Programmers

who must support and maintain the system.

Customer Registration Form

Figure 5.4

60
After the Customer Compelete the task must pays the amount of Services based on thier
Cashier

Figure 5.5 Receipt Form

61
After make payment this page shows the Gustomer get report that displays all important
informations and visitor can’t print this report

Figure 5.6. Payment form

62
5.4 IMPLEMETATION

The implementation phase takes the requirements and design phase products and
implements them using appropriate technologies. In the case of validation testing, it is during
this phase that test cases are completed and automated in preparation for validation testing.
Typically, a lot of testing on the early system versions is also performed during this phase, not
only to validate the system, but to validate that there are no problems with the test cases
themselves.
The goal of the implementation phase is to implement a system correctly, efficiently, and
quickly on a particular set or range of computers, using particular tools and programming
languages. The implementation stage is primarily environmental and works with the realities
of particular machines, system, language compilers, tools, developers, and clients necessary to
translate a design into working code. Just as the design phase may include some analysis efforts
approached from a computational standpoint.

In Shaakir Foam factory Management System, no person can login with out any user
account. has different users and different privilages (User, Adminstrator), so if you login the
the administrator role you see the previllages and do every thing in the system. While the others
can see only their privileged environments only.
As system developers want to strength and increase security of the new system, since it is
based on web application. As we know hackers and intruders are increasing day after and the
deployed software especially web based applications are continuously under attack.

63
5.5 Summary

We already mention above testing, documentation, and implementation. Objective of testing:

discover faults a test are successful only when a fault is discovered. Documentation describes

an information system and helps the users who must interact with it. Accurate documentation

can reduce system down time, cut cost, and speed up maintenance task. Implementation is

where implement how the system works as the sequential flow of Forms

64
 CHAPTER SIX

RECOMMENDATION & CONCLUSION

6.1 INTRODUCTION

This chapter includes the works that have been done during the previous
documentations of this project. In addition, this chapter will recover the objectives of the
project and illustrates how the work of this project meets the project’s objectives. Also, it
debates the experiences that have been gained during development of this project and it also
includes the future recommendation which will facilitate how to improve the functionality
and features of this shaakir foam factory management system for SHAKIR CO.

6.2 CONCLUSION

In this book, we discussed about how our system is working; we also provided some
guidelines of how the user will deal to this system and what strengths and weakness it has.

Strengths:
65
every project has some strenths and weaknesses ; so , we would like to identify some of
strenths and good features that Shaakir Foam Factory Management System will provide to
users :
this system is very friendly system and it has a good interface that can be usable by every
person who is computer literate.
More over , if the user make a mistake it generate an error message that easily
understandable by the user and it gives you the necessary utilities in your project , and
other tools that you may need while you are working with the project.

WEAKNESSES:

On the other hand , every project has its own weaknesses , so, in this project the only
problems that you might face is alerting messages that appear when ever you misuse to the
system , and if you are not familiar with this system you might find it difficult to manage it
, please don’t confuse, just read carefully what the message is carrying out and then click
on the appropriate button.

ENHANCEMENT:
This project was developed by using different types of software, so, If some one tries to
develop this project , or enhance some of its functionalities and features , he/she should be
able to know how to use Jave, SQL server 2008 Database, and iReport Application in JAVA.
Every application has its own merits and demerits. The project has covered almost all the
requirements. Further requirements and improvements can easily be done since the coding is
mainly structured or modular in nature.
Changing the existing modules or adding new modules can append improvements. Further
enhancements can be made to the application.

REFERENCES

66
A. Alkilani M. M., Sopian K., Mat Sohif, and Alghoul M.A., “Output Air Temperature

B. Creyf, H. and B. Veenendaal, 1989,Flexible Foam Manufacturer's Experience in

Substituting CFC Blowing Agents, Presentation at the International Conference on
CFC and Halon Alternatives, Washington, D. C., October 10-11.

C. El Qarnia Hamid, “Numerical Analysis of a Coupled Solar Collector Latent Heat

Storage Unit Using Various Phase Change Materials for Heating the Water’’,
Energy
Conversion and Management, Vol. 50, pp.247-254, 2009.
D. Halawa E. and Saman W., “Thermal Performance Analysis of A Phase Change
Thermal Storage Unit for Space Heating’’, Renewable Energy, Vol. 36, pp. 259-
264, 2011.

E. Hoshi Akira, Mills David R., Bittar Antoine, and Saitoh Takeo S., “Screening of
High Melting Point Phase Change Materials (PCM) in Solar Thermal
Concentrating Technology Based on CLFR”, Solar Energy, Vol. 79, pp. 332-339,
2005.
F. Prediction in a Solar Air Heater Integrated with Phase Change Material”, European
Journal of Scientific Research , ISSN 1450-216X Vol. 27, No. 3, pp. 334-341,
2009.
G. Regin A. Felix, Solanki S.C., and Saini J.S., “An Analysis of A Packed Bed Latent
Heat Thermal Energy Storage System Using PCM Capsules: Numerical
Investigation’’, Renewable Energy, Vol. 34, pp. 1765-1773, 2009.

H. Trp Anica, Lenic Kristian, and Frankovic Bernard, “Analysis of the Influence of
Operating Conditions and Geometric Parameters on Heat Transfer in Water-

67
 Paraffiffiffiffin Shelland-Tube Latent Thermal Energy Storage Unit’’, Applied
Thermal Engineering, Vol. 26, pp. 1830-1839, 2006.

I. Veerappan M., Kalaiselvam S., Iniyan S., and Goic Ranko, “Phase Change
Characteristic Study of Spherical PCMs in Solar Energy Storage’’, Solar Energy,
Vol. 83, pp. 1245-1252, 2009.

J. Wu Shuangmao, Fang Guiyin, and Liu Xu, “Thermal Performance Simulations of

A Packed Bed Cool Thermal Energy Storage System Using n-tetradecane as Phase
Change Material’’, International Journal of Thermal Sciences, Vol. 49, pp. 1752-
1762, 2010.
K. Xia L., Zhang P., and Wang R.Z., “Numerical Heat Transfer Analysis of the
Packed Bed Latent Heat Storage System Based on an Effective Packed Bed
Model’’, Energy, Vol. 35, pp. 2022-2032, 2010.

68