Title:- COMPUTERIZED APPAREL MANAGEMENT SYSTEM FOR

ANUM
ENTERPRISES,SAHIWAL, PAKISTAN.

Name : Naima Shahzadi

ABSTRACT
A computerized apparel management system will be designed for Anum

Enterprises, Sahiwal. The purpose of this research work, is to design and

implement computerized apparel management system. The existing manual

apparel system is very slow in data processing and information retrieval. It is

extremely difficult to handle a large amount of data manually and achieve

valuable results. Through computerization such sort of problems can be

overcome and reliable results can be obtained. The computerized apparel

management system will give a number of facilities to Insert, Delete, Edit, Save

and modify the record in the user-friendly and GUI (Graphical User Interface)

environment. With the help of proposed system, the unexpected mistakes will be

minimized and the chance of error will be eliminated. Using Relational Database

i.e. Oracle®.

NEED FOR THE PROJECT

The production department of Anum Enterprises is currently doing everything

manually. The perceived system will provide a user-friendly environment.

Graphical User interface will be used. System will be based on the Relational

Database Management System (RDBMS). Apparel Management System will

have the capable to generating all kinds of reports related to apparel system. It

will include all the steps from daily purchase order wise to order wise

manufacturing cost. Latest technology will be utilized to develop this system

with more flexibility, reliability and performance.

THE OBJECTIVES OF THE PROPOSED SYSTEM

The perceived system includes:

• Multi User.

• User Friendly.

• Not data redundancy.

• Data concurrency.

• Order history current/previous.

• Prompt, efficient and more productive.

• Proper controlling mechanism and apparel reports availability.

Requirements of (Production Team)

 o To control the production.

o To keep the record of the daily purchase order wise production,

finishing and packing status.

o To decrease the rejection rate by watching operation wise status.

o To keep the record of workers wages.

o To keep the record of packing list.

o To keep the record of Fabric and other accessories.

o Back tracing system.

o Worker wise efficiency report.

o Order wise manufacturing report.

QUERIES INVOLVED IN THE SYSTEM

The success of any system totally based on the collection of raw data/input.

The current system is manual so it is very difficult to maintain the apparel

records .

The following Reports which to be automatically , generated are:

• Order wise Fabric /Accessories Required Report.

• Order wise Fabric / Accessories Received Report.

• Worker wise Payment Report.

• Date wise Payment Report.

• Order wise Payment Report.

SOFTWARE REQUIREMENT:
Operating System

• Window 2000 server (Server).

• Window Professional 2000 / 98 / NT 4.0 (WKS).

System Software

• ORACLE 8i, DEVELOPER 6i.

HARWARE RECOMMENDATION:

Server

• RAM 256 MB.

• Hard Disk Minimum 10GB.

• Network Card 10 / 100 PCI.

• IBM Compatible P-III with speed more than 500 MHz.

• UPS.

• Best Quality Colored Display Device.

Workstation

• RAM 64 MB.

• Hard Disk Minimum 5 GB.

• Network Card 10 / 100 PCI.

• IBM Compatible P-II with minimum speed 300MHz.

• UPS.

• Best Quality Colored Display Device.

REVIEW OF LITERATURE

Atre (2000) stated that following trade-off have to be taken.

• Design a conceptual model of a database.

(i) Data Analysis

(ii) Existing Application

(iii) Potential Application

• Design a logical model of a database.

• Design a physical model of a database.

• Evaluate the physical model of a database.

• Implement the database.

Bayross (2000) stated that for a successfully design and maintain database we
have the following:

1. Identify which part of world's data is of interest to us.

2. Identify what specific objects in the part of the world's data are of
interest to us.

3. Identify a relationship between .the objects.

Elias (2000) gave the following criteria for the selection of the software:

1. Function ability

2. Flexibility

3. Security

4. Performance

5. Service ability

6. Minimal cost
Hoffer (2001) explained two generic database architecture:

1. Centralized databases

2. Distributed databases

Inmon (2002) described the basic database design components of Oracle® as:

1. The column

2. The row

3. The table

While the components of secondary importance are:

1. The table s
2. The segment.
3. The database
Keen (2003) recommended the following steps for the progressive testing:

1. Model Testing

2. Suit Testing
3. System Testing

Rosaleen (2003) stated that all Oracle® products use SQL as the access route

To the data. Following are the rules for writing valid SQL commands:

1. SQL commands may be one or many commands.

2. Causes are usually placed on separate lines.

3. Tabulation can be used.

4. Commands words cannot be split.

5. SQL commands are not case sensitive.

 6. An SQL command is entered at the SQL prompt and subsequent

tines are numbered. This is called SQL buffer.

Skidmore and Wore (2000) defined the system as set of related components that
work

together to fulfill a purpose. The process of studying a system involves; how the

customer's demands are found, and how to deliver the product that meets their
needs

within reasonable budge and schedule. This is called system life cycle which
include

following phases:

1. Preliminary Investigation (Determine the problem)

2. System Analysis (Understand the existing system)

3. Design (Plan the new view)

4. Development (Do the work to bring the new system into being)

5. Implementation (Convert to the new system)

Vesta (2001) described the advantages of database as:

1. Data Independence

2. Redundant data

3. Data integrity

4. Economy of Scale

Weldon(2001) stated the Following Function of the DBA for

Planning the Database

 1. Preliminary database planning

2. Identiflng user requirements

3. Developing user requirements

4. Designing the logical model

5. Choosing a DBMS

6. Developing the physical model

PROCEDURES

The main objective of the project is to develop and implement a Computerized

Apparel Management System for Marium Enterprises, Faisalabad. They have a

manual apparel management system, which is very slow in data processing and

information retrieval. In that manual system, it is extremely difficult to control

large amount of data and obtain valuable results. By this proposed system all

such kinds of problems can be overcome and reliable results can be obtained. The

user can insert ,delete ,edit , save and modify the record in a very friendly

environment. With the help of proposed system, the unexpected mistakes will be

minimized and the chances of errors will b eliminated. Different kinds of queries

and reports can be obtained.

REFERENCES

Atre, S. 2000. Structured Techniques for Design, performance and Management.

A Wiley Interscience Publication. N,Y.USA.

Bayross, I. 2000. Commercial application development using Oracle Developer

2000. BPB Publication B-14, Connaught place, New Delhi, India.

Elias, M.A. 2000. System Analysis and Design. Galgotia Publication Ltd. Delhi,
India.

Hoffer, J. A. 2001. Modern Database Management Reprinted by National Book

Foundation,Islamabad, Pakistan

Inmon, W.H.2002. Oracle Building High Performance Online System. BPB

Publication B-14, Connaught place, New Delhi, India.

Keen, J. 2003. Management System Development. A Willey Interscience

Publication. N.Y, USA.

Rosaleen, B. 2003. Introductions to Oracle RDBMS part-I. Oracle Corporation,

London, U.K.

Skidmore, S. and B. Wore. 2000. Introducing Systems Analysis. NCC Blackwell

Publication, Manchester, U.K.

Vesta, J.A.2001. Understanding Database Management Systems. Woodsworth

Publishing Company, Belmount, California, USA.

Weldon, J.2001. Financial Accounting An Introduction . 6th Ed. Harcout Brace

Jovanovian College Publishers, N.Y, U.S.A.