You are on page 1of 70

DEVELOPMENT OF ORDER PROCESSING SYSTEM

by

M.ARUN KUMAR
Reg.No: 71104631002

of

KONGU ENGINEERING COLLEGE

A PROJECT REPORT

Submitted to the

FACULTY OF MANAGEMENT SCIENCES

In partial fulfillment of the requirements


For the award of degree

of

MASTER OF BUSINESS ADMINISTRATION

JUNE 2006

1
BONAFIDE CERTIFICATE

Certified that this project report titled “DEVELOPMENT OF ORDER

PROCESSINNG SYSTEM” is the bonafide work of Mr. M.ARUN KUMAR

(Reg No: 71104631002) who carried out the research under my supervision. Certified

further, that to the best of my knowledge the work reported herein does not form part of

any other project report or dissertation on the basis of which a degree or award was

conferred on an earlier occasion on this or any other candidate.

Head of the Department / Director Faculty Guide

Viva Voce Examination Held On ……………

Internal Examiner External Examiner

2
ABSTRACT

The order processing system aims to process the customer orders to calculate the
requirements of raw materials. Order processing system is developed using visual basic
as front end and SQL as back end. Planning is done to identifying the scope and
boundary of the problem. Feasibility study is conducted to determine whether the new
order processing system economically, technically and operationally feasible.

The user requirements are analyzed to identify the information needs of the end
users, the organization environment and the existing system. The user desires
computerization of customer order, internal order, yarn requirements, pack details and
purchase order which are done manually at present. The requirements have been analyzed
and divided into small modules for easy access.

Databases are designed with care to accommodate growth in future. User friendly
forms have been designed for data entry. These incorporate combo boxes for yarn
specification, color, order number etc, for easy data entry. The system have been
developed using procedural design. The procedures used in the design have been
discussed with the user before coding. Number of validation checks has built in to ensure
the integrity of data entry. In addition to low level validation such as number field,
character field etc and higher level validation has also been incorporated.

The system is implemented in SNQS International Socks Pvt Ltd and tested for
errors. Training had been provided for the users regarding the operations of the system.
Post implemented review had been conducted to monitor, evaluate and modify the system
as needed by the user. The user has expressed satisfaction with the system implemented.

3
RUf;fk;

Mh;lh; Guh]\pq; mikg;G thbf;ifahsh;fspd; NjitfisAk;> mth;fspd;


Njitfhd %yg;nghUl;fis mwpa cjTfpwJ. ,e;j mikg;G tpRty; Ngrpf;if %d;
gFjpahfTk; v];f;Avy;-iy gpd; gFjpahfTk; nfhz;L ,aq;FfpwJ. ,e;j mikg;G
nghUshju hPjpahfTk;> njhopy;El;g hPjpahfTk; kw;Wk; nray; hPjpahfTk;
rhj;jpag;gLkh vd;gJk; fz;lwpag; gl;Ls;sJ.

gad;gLj;JNthhpd; Njitfis ghprpyid nra;J ,Wjp gad;ghl;lhsh;fs;>


cgNahhfpj;jpy; cs;s mikg;G kw;Wk; epWtdj;jpd; gad;ghL Mfpatw;wpw;F
Njitahd jfty;fis mwpag;gl;Ls;sJ. gad;ghl;lhsh;fspd; tpUg;gk;
fzpzpkakhf;fg;gl;l Efh;Nthh; Njit> cs;shh;e;j Njit> E}y; Njit>
ngl;bayplypd; tpguq;fs; Kjyhdit jw;NghJ ,ay;G Kiwapy; eilngw;Wf;
nfhz;Ls;sJ. Njitfs; Muhag;gl;L NkYk; vspikahf Vw;Wf;nfhs;s rpW rpW
myFfshf gphpf;fg;gLfpd;wJ.

%d;whtJ epiy tbtikg;G gFjp> kpFe;j rpuj;ijAld; jfty; Fwpg;NgL


tbtikf;f nray;gl Ntz;Lk;. nkd;nghUs; tbtikg;G cgNahfpg;ghsUld;
fye;Jiuahb mth;fsJ Njitf;Nfw;g tbtikf;fg;gl;Ls;sJ. tiuKiw vOJjy; gFjp ehk;
nfhLf;Fk; jftyhdJ nry;yj;jf;fjh vd Nrhjpf;fpwJ.

mkyhf;Fjy;; epiyapy;> ehk; jahhpj;j nkd;nghUs;> v];.vd;.f;A.v];


epWtdk;> cgNahfpg;Nghhpd; fzpzpapy; ghpNrhjpf;fg;gl;lJ.
cgNahfpg;NghUf;F gapw;rp toq;fg;gl;lJ.

JizGhpjy; epiyapy;> cgNahfpg;ghshpd; Njitf;Nfw;g nkd;nghUs;


rpwpJ khw;wp tbtikf;fg;gl;lJ. ,g;NghJ Mh;lh; Guh]\pq; mikg;G>
v];.vd;.f;A.v]; epWtdj;jpy; KO gad;ghl;by; cs;sJ.

4
ACKNOWLEDGEMENT

I express my sincere thanks to Thiru.P.Sathyamoorthy B.E., M.B.A., M.S

Correspondent, Kongu Engg College for providing me the necessary support to undertake

this project.

I express my deep sense of gratitude to Dr.A.M.Natarajan B.E.,M.Sc.,(Engg).,

Ph.D.,MISTE.,MIEE.,F.I.E., Principal, Kongu Engg College who has given me an

opportunity to undergo my management studies.

I also thank Prof.P.Sureshkumar M.Sc., (Agri), M.B.A Director, Department of

Management Studies, Kongu Engg College for his guidance and encouragement through

out my project.

I express profound indebtedness to Mrs. P. Vidyapriya M.B.A., for providing

constructive support and valuable guidance to do this project work.

I am very thankful to Mr.T.Suresh babu EDP-In-Charge, SNQS International

Socks Private Limited for giving me an opportunity to undertake my project work in his

organization.

I also wish to express my sincere gratitude to my parents, all my friends, well

wishers, and those who helped me directly or indirectly in successfully completing this

project.

5
LIST OF CONTENTS

CHAPTE
R PARTICULARS PAGE NO

1. INTRODUCTION

1.1 Company Profile 1


1.2 About The Project 4
1.3 Existing System 4
1.4 Proposed System 6
1.5 System Development Life Cycle 7
1.6 Objectives 9

2. DEVELOPMENT PROCESS

2.1 Analysis 10
2.2 Problem Analysis 11
2.2 System Design 12
2.3 Programming Environment 15
2.4 System Analysis Tool 21
2.6 System Construction 36
2.7 Testing 55
2.7 Implementation 56
2.8 System Support 58

3. SUGGESTION AND CONCLUSION 60

6
LIST OF TABLES

S.NO PARTICULARS PAGE.NO

1. Color Master 30

2. Design Master 30

3. Yarn Specification 31

4. Customer Details 31

5. Pack Master 31

6. Customer Order 32

7. Order Sheet 1 32

8. Internal Order 1A 33

9. Purchase Entry 34

10. Pack Entry 34

11. Yarn Requirements 35

CHAPTER 1
INTRODUCTION

7
1.1 COMPANY PROFILE

SNQS Group had its beginning in 1990 when SNQS INTERNATIONAL,


apparel was founded by Mr.Elangovan, a qualified textile engineer. The dynamic
leadership of the founder has helped the group grow rapidly over the years to successfully
establish and operate the following companies

 SNQS INTERNATIONAL,TIRUPPUR
 SNQS INTERNATIONAL SOCKS PRIVATE
LIMITED,COIMBATORE
 SNQS INTERNATIONAL-GARMENT DIVISION,NEW
TIRUPPUR
 JEYA VISHNU SPINTEX PRIVATE LIMITED ,
COIMBATORE
 INDITEX PROCESSORS PRIVATE LIMITED,PERUNDURAI

SNQS INTERNATIONAL SOCKS PRIVATE LTD, was established in the


year 2001 as a 100% Export Oriented Company to engage in the business of manufacture
and export of socks.

The company is located in the suburbs of Coimbatore, a textile city in the southern
part of India. The company is registered as a private limited company with nine directors.
 The paid up capital is USD 2 Million.
 The managing director is Mr.V.Elangovan.
The company entered socks export business by sending the export opportunities
emerging for textile products from India because of opening up of markets as an outcome
of WTO agreements.

8
The company has a manufacturing space of 50000 sq.ft and has invested in the latest
State Of Art Machinery required for socks production. The total number of socks knitting
machines installed including various cylinder diameters/needles is 205.

The company‘s installed capacity is 12 million pairs/year. The present capacity


utilization is between 80-85%.owing to rising demand the company is adding capacity
every six months. Within 3-4 years time the company expects to double the installed
capacity to 24 million pairs.

 The company exports more than 90 % of production to Europe.


 The company achieved a turn over of USD 5 million in 2005.
In 2006 it estimates to reach USD 7 million.

The company produces the complete range of knitted socks including men’s,
ladies and children in jersey and knits in plain/design types

The Mission of the company is to be Reliable manufacturing partner for reputed


global brands/stores by consistently and supplying right quality socks by using the latest
technologies. Further, while engaging in this business to ensure that the company fulfills
all legal and social requirements and accord priority to sustainable development.

To help consolidate the growth of the socks business and to control the supply
chain, SNQS Group has set up a spinning mill named JEYAVISHNU SPINTEX
PRIVATE LIMITED near Coimbatore. The group has also made a project plan for
processing unit. The processing project is scheduled to go on stream in a year’s time

9
In SNQS, there are several departments. Some of them are

 Personal Department
 Finance Department
 Production Department
 Marketing Department
 Time Office Department
 Central Excise Department
 Store Department
 EDP Department
 Electrical & Maintenance Department

SNQS ADVANTAGES

 Easy access to raw materials


 High-End infrastructure
 Cutting-edge technology
 Korean Trained technicians
 Manual Linking
 Better Shaping
 Fast Delivery
 More Variety in Colors and Designs

Quality, Precision, Comfort and Style have made SNQS what is today- A well Known
name in India and a trend-setter across the Globe. SNQS aims to expand its export
markets to cover entire EUROPE and explore markets ASIA and USA

10
1.2 ABOUT THE PROJECT

An order processing system is an organized combination of people, hardware,


software, and communication networks and data resources technologies. It collects,
transforms and disseminates information in an organization. It is a system that accepts
data resources as input and processes them into information product as output. This
supports an organization’s business strategies, business processes and organizational
structures and culture to increase the business value of the enterprise in the dynamic of
business environment.

1.3 EXISTING SYSTEM

In SNQS INTERNATIONAL SOCKS PVT.LTD, presently operates manually,


all the details of the Order processing system. They are maintaining different types of
notes (Manual Entry Notes) such as,
Customer order form
Internal order form
Yarn requirements
Packing materials
Production methods, etc.

It consumes more time, and involves more risk and it requires more human power.
There may be a chance of missing, and getting confused.

11
LIMITATIONS OF EXISTING SYSTEM:

Due to the manual system, the firm faces some of the following problems.

 Sluggish search of details


 Poor calculation
 Timing constraints were ignored
 Information mishandling
 Tedious report generation

NEED FOR NEW SYSTEM:

Computerization of any type of transactions or event in a firm will provide a better


performance. It reduces the degree of time consumption to a great extent. When the
existing manual system is computerized then,

 Time and Labor is saved


 Accurate calculation can be done
 Human tensions and risks can be overcome
 Report generation at ease
 Hi-fed status to the firm
 Search of information at ease
 Wastage of resources can be saved

Comparative Study

Since at present everything is done manually it has a lot of drawbacks. The major
drawbacks are time consumption and search of information. It is a tedious process. The
proposed order processing system which could solve all these problems.

12
1.4 PROPOSED SYSTEM

The proposed system was developed in such a way to solve the above problems
faced by the present normal system by using latest technology. For this, the ideal
environment is the windows environment; as it is the most popular multitasking system
available today. The front end used to develop the system is visual basis6.0 for its
flexibility and compatibility.

The proposed system use SQL Server as back end, which has powerful querying
functions, easy accessing methods and user – friendly, enough securities are provided to
the database and the new system. A good user interface is provided with the system.
User will be able to generate Valuable reports based on

 Customer Order form

 Pack Material

 Yarn Requirements

 Stock

 Purchase order

This system helps to provide communication between different departments, and can be
able to share the necessary information. So that, it saves time and helps to make the
decision quickly.

Necessity of the System:

At present every transaction is carried out manually. The volume of the data to
be handled is very large. It is also necessary to speed up the data in order to get quick
reports, enabling quick decision by the management. Taking all this in to consideration

13
the conversion processing using VB is an obligatory. The transaction will help the
management in coping with emerging trends in data processing industry.

ANTICIPATED ADVANTAGE

 The process becomes faster.


 The calculation becomes accurate.
 Reports can be taken quite easily than it was in the previous system.

1.5 SYSTEM DEVELOPMENT LIFE CYCLE

A system development life cycle is a systematic and orderly approach to


solving system problems. System problem solving is the act of studying a problem
environment In order to implement corrective solutions that take the form of new or
improved systems. The SDLC consists of five distinct phases. They are:

 Planning
 Analysis
 Design
 Implementation
 Support

1.5.1 PLANNING

Planning is the process of identifying the scope and boundary of the problem
and plans the development strategy and goals. A feasibility study is conducted to
determine whether the system is a feasible solution.

1.5.2 ANALYSIS

14
Analysis is the process of analyzing the information needs of end users, the
organizational environment and any system presently used. It helps to develop the
functional requirement of a system that can meet the needs of end users.

Planning

Analysis

Design

Implementation

Support

1.5.3 DESIGN

This phase continues the work done in the analysis phase. The designer’s
approaches the system from the perspective of the data objects that the program needs
and the operations performed on them. The first perspective leads to the creation of data
types and second the considerations of design strategies. Here in student information
system the data objects might include students, branch and staff members.

1.5.4 IMPLEMENTATION

15
In implementation phase the analyst acquire hardware and software for the
system. Testing will be performed with variety of input data to remove errors. Training
will be provided to the users to operate and use the system.

1.5.5 SUPPORT

In this phase the system analysts will provide ongoing support to the
implemented system. They analyze the implemented solution, refine the design and
implement improvements to the solution. It uses a post implementation review process to
monitor, evaluate and modify the system as needed.

1.6 OBJECTIVES

1.6.1 PRIMARY OBJECTIVE

To design and develop an Order processing system and to implement it in


SNQS Socks International Pvt Ltd.

1.6.2 SECONDARY OBJECTIVE

 To develop a system that is user friendly


 To develop a system to analyze the yarn requirements
 To develop a system to produce internal order sheet
 To develop a system to produce purchase order

16
CHAPTER 2

DEVELOPMENT PROCESS

2.1 ANALYSIS

2.1.1 SYSTEM ANALYSIS

The system analysis phase is a five step process. They are

 Investigation
 Technical feasibility study
 Economic feasibility study
 Operational feasibility study
 Requirements definition

2.1.1.1 INVESTIGATION

Investigation is the first step in system analysis which determines whether there
is a real need for a system and whether the system is conceived feasible. The existing
system in the organization is manual order processing system. Due to fatigue and
boredom among human frailties user may cause 1% to 10% of human error in
computation and clerical tasks.

2.1.1.2 TECHNICAL FEASIBILITY STUDY

17
Technical feasibility is to know whether reliable hardware and software
capable of meeting the needs of a proposed system developed by an organization in the
required time. The order processing system is developed by visual basic and sql server.
The minimum hardware and software required to run this system. So it is technically
feasible.

2.1.1.3 ECONOMIC FEASIBILITY STUDY

Economic feasibility is to know whether expected cost savings, increased


revenue, increased profits and reduction in required investment exceed the costs of
developing and operating a proposed system. Through order processing system the
organization can reduce raw material cost because this system gives accurate
requirements. So this system is economically feasible.

2.1.1.4 OPERATIONAL FEASIBILITY STUDY

Operational feasibility is the willingness and ability of management,


employees, customers and suppliers to operate, use and support a proposed system. The
order processing system is developed by visual basic, user friendly application. So the
order processing system is feasible.

2.1.1.5 REQUIREMENTS FEASIBILITY STUDY

Requirements are concerned with understanding the so-called mission of the


order processing systems within the enterprise and problems that the system should solve.

2.2 PROBLEM ANALYSIS

The existing system in the organization is manual order processing system.


Due to fatigue and boredom among human frailties user may cause 1% to 10% of human

18
error in computation and clerical tasks. So the organization decides to develop a
computer order processing system to process the order data more effectively and
efficiently. The modules in this system are

 Customer Order Form

 Internal Order Sheet –I

 Internal Order Sheet-IA

 Pack Material Entry

 Yarn Requirement Form

Here the order data are feed into the system by the user. The order processing
system processes these data into useful information’s for the organization. The system
will prepare the report about the purchase order, yarn requirement, stock details. This will
help the organization to make corrective action. The order processing system is
developed with menu interaction where lists of system options are provided and a
specific command is invoked by user selection of menu option.

2.3 SYSTEM DESIGN

System design is the evaluation of alternative solutions to a business


technology for the selected solution. The purpose of this phase is to device the means to
meet all the business requirements detailed in the requirements report. Design phase
consists of four sub phases.

2.3.1 LOGICAL DESIGN

19
Logical design is a translation of user requirements into detailed functions of a
proposed order processing system. This phase of SDLC immediately precedes the
physical design. During the logical design phase, the designers design the following
components:

 Input files – The files that will be used to capture the data.
Input forms like customer order form, internal order form, etc.
 Procedures – The logical algorithms used to process the
output. The procedures will later be transformed into code written in
programming language
 Output files – The files that will be used to show the user
requirements. In this system reports like stock detail, purchase order
etc can be taken
 User dialogue – The manner in which the users will interact with the
system: windows, menus, icons etc
 Interfaces – The process of system interacting with other systems.

2.3.2 PHYSICAL DESIGN

Physical design is the process of designing order processing system. It


includes specifying the necessary software and hardware needed to support it. It involves
detailed design of user interface products and methods, database structures, processing
and control procedures. Software designers use their knowledge of business operations,
order processing and hardware and software to specify physical design of an order
processing system.

20
2.3.2.1 SYSTEM SPECIFICATION

• HARDWARE SPECIFICATION
Processor : Processors with minimum 133 Hz.
Co-Processor : Math-Co Processor, Float-Co Processor
RAM Capacity : 32 MB.
Monitor : 14’ color monitor preferred.
Floppy Disk Drive : 1.44 MB
Hard Disk Drive : 4 GB
Serial Ports : PS/2, COM1, COM2
Parallel Ports : RJ-232
Cache : 512 MB
Video RAM : 256 MB

• SOFTWARE SPECIFICATION

During Development Stage:


 Front End : Visual Basic 6.0
 Back End : SQL Server 6.0
 Operating System : Windows ‘X since GUI supporter

At Implementation Stage:
 Only the necessary .DLL files to execute the program are required.

21
 As the database is centralized, the back end is shared from the server.

2.4 PROGRAMMING ENVIRONMENT


2.4.1 VISUAL STUDIO

Microsoft Visual Studio is one of the best GUIs and version 6.0 is the latest Version
of the popular programming language. With its new features, Visual Studio is an even
stronger contender in the application development area then ever before.
Microsoft Visual Basic, the fastest and easiest to create applications for Microsoft
windows. Visual Basic provides with a complete set of tools to simplify Rapid
Application Development (RAD).

VISUAL BASIC 6.0

The “Visual” part refers to the method used to create the graphical user interface
(GUI), Rather than writing numerous lines of code to describe the appearance and
location of interface elements, we simply add rebuilt objects into place on screen. The
“Basic” part refers to the BASIC (Beginners All - Purpose Symbolic Instruction Code)
language, a language used by more programmers than any other language in the history
of computing. Visual Basic has evolved from the original BASIC language and now
contains several hundred statements, functions and keywords, many of which relate
directly to the windows GUI.
The purpose of Visual Basic is to develop robust stand-alone application, games,
and utilities less time than it takes in other languages. We can use also ActiveX
technology to create internet-enabled applications that are limited only by our
imagination.

22
Visual Basic 6.0 is the newest addition to the family of Visual Studio products. It
allows us to create Windows applications for our PC without being an expert in C++ or
other programming languages.

Visual Basic 6.0 is specially designed to utilize the Internet. It comes with several
controls that allow us to create web-based applications called ActiveX executables. They
will work just like stand-alone visual basic application, but they are accessed through the
Microsoft Internet explorer 3.1 Web browser. This allows us to revise our applications
and distribute them through the Internet.

Some new features in visual basic 6.0 are given below:

 VB 6.0 is most productive tool for creating high-performance


enterprise and web-based applications.
 VB 6.0 integrated visual database tools and new data environment
designer can visually design oracle and MS SQL sever databases and
create reusable data access queries all without leaving the VB
environment.
 Data report designer can quickly drag and drop custom data-bound
controls to create forms or reports. Creation of custom data
hierarchies is as easy as filling out a dialog box and dragging the
command to the form.
 VB 6.0 professional edition is designed for individual professional or
corporate developer who needs to create a client/server or Internet
based applications.
 With the emergence of dynamic HTML page designer, multimedia
rich applications can be developed using the document.
 Object model and dynamic HTML surface.

VISUAL BASIC 6.0 FEATURES

23
The Visual Basic Enterprise Edition contains all of the features includes
with the Visual Basic professional edition and the Visual Basic learning edition. In
addition, it contains the following features, available in the enterprise edition only.
For more information about other editions of Visual Basic, see Visual Basic editions.

VISUAL COMPONENT MANAGER:

This tool stores, organizes, and shares reusable components. It can contain
wizards, ActiveX components, Database connection objects, and many other
components used in Visual Basic projects. It is suited to enterprise-wide component
cataloguing and reuse because it is based on the open and scalable Microsoft
Repository.

VISUAL DATABASE TOOLS INTEGRATION:

With these designers you can visually create and modify database schemes
and queries: Create SQL Server and Oracle database tables drag and drop to create
views, and automatically change column data types.

NEW FEATURES OF VISUAL BASIC 6.0


DATA ACCESS:

1. ADO (ActiveX Data Objects).


2. Data Environment.
3. ADO Data Control.
4. Enhanced Data Binding.
5. OLEDB Support.
6. Visual Database Tools Integration.
7. Setup Wizard Data Enhancement.
8. Data Report.

24
9. Data View Window.
10. SQL Editor.
11. Hierarchical Flex Grid Control.
12. Data Repeater Control.
13. Passing ADO Record sets.
14. Data Form Wizard Enhancement.
15. Data Object Wizard.
16. File System Objects.
17. Format Objects.

ADO CONTROL:

The ADO Data control user Microsoft ActiveX Data Objects (ADO) to
quickly create connections between data-bound control and data provides. Data-
bound controls are any controls that feature a Data Source property. Data provides
can be any source written to the OLEDB specification. We can also easily create our
own data provider using Visual Basic’s class module.
Although we can use the ActiveX Data Objects directly in our
applications, the ADO Data control has the advantage of being a graphic control (with
back and Forward buttons) and an easy-to-use interface that allows me to create
database applications with a minimum of code.

DATA REPORTS:

The Microsoft Data Reports designer is a versatile data report generator


that features the ability to be created, banded hierarchical reports. Used in conjunction
with a data source such as the Data Environment designer, we can create reports from
several different relational tables. In addition to creating printable reports, we can also
export the report to HTML or text files.

USES:

25
 Automatically create reports that are exported in HTML format for
instant distribution on the Internet.
 Create reports that show the sums of transactions occurring on a daily
basis.

ADVANTAGES OF VISUAL BASIC:


The following key points make Visual Basic an excellent development tool:

 Visual Basic applications are event-driven. Event driven means the


user is in control of the application. The user generates a stream of
events each time by clicking the mouse or by pressing a key on the
keyboard.
 Visual Basic supports the principles of objects oriented design, means
that we can compartmentalize different aspects of our application as
objects and develop and test those objects independently of the rest of
the application. By modifying certain properties and invoking the
methods of these objects.
 Visual Basic is infinitely extensible through the use of Active X
controls, dynamically linked libraries (DLLs), and add-ins. We can
create those Active X controls and DLLs for use in other
windows applications such as Excel, word or access.

2.4.2 ABOUT THE MS SQL SERVER 2000

SQL server 2000 is a powerful database management system and user can create
entire application that requires little or no programming language application. SQL server
is easy enough to use that in a short time; beginners can learn to manage their own data.
This server also has some advanced installation options like:

 Performing an unattended installation

26
 Rebuilding the registry
 Installing a virtual server configuration
 SQL server language support

Silent Features That Makes SQL Server A Compelling Choice Is

 Provides GUI Interfacing – SQL server presents wizards for


performing almost every operation. Wizard – a step-by-step procedure
that guides the user.

 Profile Security Utilization – Database objects are highly secured by


means of authentication mode, granting various security roles,
granting access to databases.

 Provides efficient Data Transformation Services - Allows


exporting and transforming heterogeneous data between many popular
data formats including databases, spreadsheets and text files.

 Effective Database Management – Performs backing up and


restoring with various backup options in a flexible way. And a
maintenance plan can be created that the SQL server agent on a
regular basis. Various features are running database Integrity check,
Updating database Statistics.

New in Meta Data Services

Microsoft SQL Server 2000 Meta Data Services extends and renames the
former repository component known as Microsoft Repository. Meta Data Services
extends repository technology by introducing a new browser for viewing data in a

27
repository database, new Extensible Markup Language (XML) interchange support, and
new repository engine features.

Microsoft SQL Manager provides powerful tools for MicrosoftSQL Server


administration and object management. Its Graphical User Interface (GUI) allows
create/edit all Microsoft SQL database objects in a simple and direct way, design
databases visually, run SQL scripts, manage users and administrator user privileges,
extract print, and search metadata, create database structure reports in HTML format, and
supplies many more services that will make our work with Microsoft SQL server as easy.

Topic Description

Meta Data Browser New in this release, Meta Data Browser is a tool that you
Enhancement can use to browse a repository database.
XML Encoding Enhancements New in this release, XML Encoding supports a new
implementation of meta data interchange in Meta Data
Coalition (MDC) Open Information Model (OIM) XML.
Repository Engine Programming enhancements detail new and better ways for
Programming Enhancements programming against an installed Information model.
Repository Engine Modeling Modeling enhancements support new definitions that you
Enhancements can include in an information model.

2.5 SYSTEM ANANLYSIS TOOL

System analysis tool is a model building activity, using notation. It is used to


create models that depict information (data or control) flow and content. It will be
partitioned by function and depict the essence of what must be built. Data is transformed
as it flows through a computer based system. The system accepts input in a variety of
forms like customer order form, internal order form etc., applied hardware, software and
human elements to transform input into output, and produce output in variety of forms.
The input gets from the key board and stored in the hard disk. The output derived from

28
the hard disk and shown in the monitor. Structured analysis is a data flow and content
modeling technique. The overall function of the system represented as a single
information transform.

2.5.1 DATA FLOW DIAGRAM

The order data moves through software, it is modified by a series of


transformations. The Data flow diagram is a graphical technique that depicts information
flow and the transforms that are applied as data move from input to output. The data flow
diagram is also known as data flow graph or bubble Chart. The data flow diagram may be
used to represent a system or software at any level of abstraction. In fact, DFDs may be
partitioned into levels that represent increasing data flow and functional detail. Therefore,
the DFD provides a mechanism for functional modeling as well as data flow modeling. In
so doing, it satisfies the second operational analysis principle. DFD graphical notation
must be augmented with descriptive text. A process specification can be used to specify
the processing details implied by a bubble within a DFD. The process specification
describes the input to a function, the algorithm that is applied to transform the input and
the output is produced.

29
CUSTOMER ORDER FORM

Cust detail

Update table cust detail

NEW ORDER FORM CUSTOMER


ORDER
Order info FORM

Update table cust order

Cust order

Customer order form is a modified form which is given by the customer for getting
clear view about the order. It includes the information about the customer who gives the
order to the company and production method.

30
INTERNAL ORDER FORM 1

WEIGHT

Weight/Socks

Cust order info

Customer order INTERNAL METHOD


ORDER-1 Method
Of production

Update Table Int order 1

INTERNAL ORDER

Internal order sheet-I shows the brief requirements of the yarn, specification,
production procedure and weight per socks which can be determined form sample

31
production. Weight per socks is to calculate yarn requirements for the total quantity of
production.

INTERNAL ORDER FORM 1A

COLOR

Yarn color

INT ORDER 1 INTERNA SPECIFICATION


L ORDER Yarn detail
1A
Int order 1 info

Update table Int Order 1A


INT ORDER1A

Internal order sheet-I A shows the detailed requirements of yarn and its
specification for the production. It shows the yarn requirement in each color for the
particular design of socks. Both internal order sheets are used in the production area and
checks with the availability of yarn in store.

32
YARN REQUIREMENT FORM

SUPPLIER

INT ORDER 1A YARN


REQUIRE QUANTITY
MENTS

YARNREQUIREMENT

Yarn Requirement Form shows the customer required quantity and supplier of yarn
for production. It also shows the need of cotton, spandex, nylon and rubber thread in each
and every color for the particular design of socks.

33
STOCK

COLOR

QUANTITY
SPECIFI
CATION

Issue order

PURCHASE
Verification

YARN REQUIREMENTS
Yarn info STOCK

STOCK

Update Table stock

34
Stock data flow diagram shows as per requirements of raw materials it will
checks with store for the availability of raw materials. If all the materials are available it
displayed as available otherwise it will prepare purchase order.

2.5.2 CONTEXT DIAGRAM

Context diagram is the highest level data flow diagram. It defines the
boundaries of a system by showing a single major process and the data inputs and outputs
and external entities involved. A common to begin is to model the whole system by one
process. The data flow diagram that is involved in this is known as the context diagram. It
is diagram that shows inputs and outputs of a system.

The following context diagram is the overview of the order processing system
that shows the system boundaries, external entities that interact with the system and the

35
major data flow between the entities and the system.

METHOD ORDER FORM

INTERNAL ORDER1
QUANTITY

YARN INTERNAL ORDER1A


SPECIFICATION ORDER
PROCESSING
SYSTEM
PACK MATERIAL YARN
REQUIREMENTS

WEIGHT/SOCKS PURCHASE ORDER

The context diagram contains only one process, order processing system. It
has ten data flows and does not contain any data stores and ten sources/sinks. The

36
sources/sinks represent its environmental boundaries. Since data stores are conceptually
inside the process no data stores appear on context diagram.

2.5.3 DATA BASE DESIGN

A database is an integrated collection of logically related records and files. In


every project the data is necessary to store. The impact of data structure on program
structure and procedural complexity causes data design to have profound influences on
software quality. Design logical and physical structure of one or more databases to
accommodate the information needs of the user in an organization for a designed set of
application.

The goal of database design

 Satisfy the information content requirements of the specifies user and


applications.
 Provide a natural and easy-to-understand structuring of the
information.
 Support processing requirements and any performance objectives such
as response, time, processing time and storage space.

The goals are very hard to accomplish and measure, and they involve an
integrate tradeoff. If one attempts to achieve more naturalness and understandability of
the model, it may be at the cost of performance. The problem is aggravated because the
data base design process often begins with informal and poorly defined requirements. In
contrast, the result of design activity is rigidly defined database schema that cannot easily
be modified once the database is implemented. The choice of DBMS is governed by
nature of factors. The technical factors are concerned with the suitability of the DBMS
for the task at hand. Issues to consider here the type of DBMS(relational, object oriented,

37
object, other), the storage structure and access paths that DBMS support, the user and
programmer interfaces available, the type of high level query languages, the availability
of development tools, ability to interface with other DBMS via standard interface.

2.5.3.1 DATA DICTIONARY

TABLE NAME: COLOR MASTER


DESCRIPTION: This table stores yarn colors.

COLUMN NAME DATA TYPE WIDTH NULLABLE

Color Code BigInt 16 N

Color Name VarChar 50 N

TABLE NAME: DESIGN MASTER


DESCRIPTION: This table stores different designs.

COLUMN NAME DATA TYPE WIDTH NULLABLE

Design Code BigInt 16 N

Design Name VarChar 50 N

TABLE NAME: YARN SPECIFICATION


DESCRIPTION: It stores information about the yarn specification.

38
COLUMN NAME DATA TYPE WIDTH NULLABLE

Yarn Id BigInt 16 N

Specification VarChar 50 N

TABLE NAME: CUSTOMER DETAILS


DESCRIPTION: This table stores customer details.

COLUMN NAME DATA TYPE WIDTH NULLABLE

Customer Id BigInt 16 N

Customer Name VarChar 50 N

Address VarChar 50 N

Contact NO BigInt 16 N

E-Mail VarChar 50 N

TABLE NAME: PACK MASTER


DESCRIPTION: This table stores information about packing material.

COLUMN NAME DATA TYPE WIDTH NULLABLE

Product Id BigInt 16 N

Product Name VarChar 50 N

TABLE NAME: CUSTOMER ORDER


DESCRIPTION: It stores information about customer order.

39
COLUMN NAME DATA TYPE WIDTH NULLABLE

Internal Order No BigInt 16 N

Customer Order No BigInt 16 N

Needle BigInt 16 N

Sock Name VarChar 16 N

Pair VarChar 16 N

Specification VarChar 16 N

TABLE NAME : ORDER SHEET1


DESCRIPTION: It stores information about the production method.

COLUMN NAME DATA TYPE WIDTH NULLABLE


Internal No BigInt 16 N
Customer No BigInt 16 N
Needle BigInt 16 N
Sock Name VarChar 50 N
Pair VarChar 50 N
Weight BigInt 16 N
Wastage BigInt 16 N
Order Qty BigInt 16 N
Link Method VarChar 50 N
Ship Date DateTime 6 N
Specification VarChar 50 N

TABLE NAME: INTERNALORDER 1A


DESCRIPTION: It stores detailed information about yarn requirement for
production.

40
COLUMN NAME DATA TYPE WIDTH NULLABLE
Internal order no BigInt 16 N
Set VarChar 50 N
Color VarChar 50 N
Quantity BigInt 16 N
Count Name1 VarChar 50 N
Color1 VarChar 50 N
Supplier1 VarChar 50 N
Req Quantity1 BigInt 16 N
Count Name2 VarChar 50 N
Color2 VarChar 50 N
Supplier2 VarChar 50 N
Req Quantity2 BigInt 16 N
Count Name3 VarChar 50 N
Color3 VarChar 50 N
Supplier3 VarChar 50 N
Req Quantity3 BigInt 16 N
Count Name4 VarChar 50 N
Color4 VarChar 50 N
Supplier4 VarChar 50 N
Req Quantity4 BigInt 16 N

TABLE NAME: PURCHASE ENTRY


DESCRIPTION: This table stores information about the purchase order.

41
COLUMN NAME DATA TYPE WIDTH NULLABLE

Purchase id BigInt 50 N

Count Name VarChar 50 N

Color VarChar 50 N

Supplier VarChar 50 N

Balance Qty BigInt 16 N

Additional Qty BigInt 16 N

TABLE NAME: PACK ENTRY


DESCRIPTION: It stores information about the packing material.

COLUM NAME DATA TYPE WIDTH NULLABLE


Product Id VarChar 50 N
Product Name VarChar 50 N
Size VarChar 50 N
Grade VarChar 50 N
Quantity BigInt 16 N
Internal Order No BigInt 16 N
Customer Order No BigInt 16 N

TABLE NAME: YARN REQUIREMENTS


DESCRIPTION: Detailed information about the yarn specification need for
production.

42
COLUM NAME DATA TYPE WIDTH NULLABLE
Internal No BigInt 16 N
Customer No BigInt 16 N
Count Name1 VarChar 50 N
Color1 VarChar 50 N
Supplier1 VarChar 50 N
Req Quantity1 BigInt 16 N
Count Name2 VarChar 50 N
Color2 VarChar 50 N
Supplier2 VarChar 50 N
Req Quantity2 BigInt 16 N
Count Name3 VarChar 50 N
Color3 VarChar 50 N
Supplier3 VarChar 50 N
Req Quantity3 BigInt 16 N
Count Name4 VarChar 50 N
Color4 VarChar 50 N
Supplier4 VarChar 50 N
Req Quantity4 BigInt 16 N

2.6 SYSTEM CONSTRUCTION

System construction is predominantly programming. Professional


programmers translate input, output and processes as described in data flow diagrams
into programs.

43
2.6.1 CODING STYLE

Coding is the process where by the physical design specifications created by


the analysis team are turned into working computer code by the programming team.
Depending on the size and complexity of the system, coding can be an involved intensive
activity. Once the coding has begin, the testing process can begin and proceed in parallel.
Programmers convert the system specifications given to them by the analysts into
instructions the computer can understand.

After source code is generated, the function of the module should be apparent
without reference to a design specification. In other words, code must be understandable.
Coding style encompasses a coding philosophy that stresses simplicity and clarity. In their
land mark text on the subject, writing a computer program eventually boils done to writing
a sequence of statements in the language at hand. How each of these statements is
expressed determines in large measure the intelligibility of the whole elements of style
include internal documentation, methods for data declaration, an approach to statement
construction and techniques for I/O.

FORM DESIGN

MAIN FORM

44
CUSTOMER DEDAIL FORM

45
CUSTOMER ORDER FORM

46
INTERNAL ORDER FORM-1

47
INTERNAL ORDER FORM-1A

48
PACK MATERIAL FORM

49
PURCHASE ORDER FORM

50
YARN REQUIRMENT FORM

51
STOCK FORM

52
REPORTS

MAIN FORM

53
REPORT LIST

54
ENTRY FORM

55
56
PURCHASE ORDER REPORT

57
STOCK REPORT

58
CUSTOMER ORDER REPORT

59
PACK MATERIAL REPORT

60
YARN REQUIRMENT REPORT

61
2.6.2 SYSTEM FLOW DIAGRAM
CUSTOMER ORDER FORM

SAMPLE
PREPARATI
ON

INTERNAL ORDER SHEET -


I

INTERNAL ORDER SHEET -


IA

PACKING MATERIAL YARN REQUIREMENTS

CHECK PRODUCTION
STOCK

PURCHASE ORDER

62
System flow diagram shows the flow of information processing activities
as data are processed by the user and the devices. System flow diagram is widely
used to communicate the overall structure and flow of a system to end users because
they can offer a view that emphasizes the hardware and data media involved.

2.7 SYSTEM TESTING

Testing is the process of executing the program with the explicit intention of
finding errors that makes the program fail. A system is tested for online response,
volume of transactions, stress and recovery from failure. Testing is vital to the
success of the system before the system is ready for user acceptance testing. Testing
steps are unit testing, integration testing and validation testing.

UNIT TESTING:

The first level of testing is unit testing. In this different modules are tested
against the specification during the design for the module. Each module evaluated
using test data and the generated output are compared with desired output. This
enables us to detect and correct errors without affecting the other modules. Unit
testing is always white-box oriented and the step can be in parallel for the modules.
In the order processing system each module is tested individually using test data and
found to be error free. In the order processing system each module like customer
order, purchase order etc, are tested individually against the specification during the
design.

INTEGRATION TESTING:

Integration testing is a systematic technique for constructing the program


structure while at the same time constructing tests to uncover errors associated with

63
interfacing. Integration testing addresses the issues associated with the dual problems
of verification and program construction.
Integration testing follows bottom-up approach, in which the integration is
carried out from the low level modules to the top. Bottom-up integration consists of
unit testing of the entire system. After the application has been integrated a set of
high-order tests were conducted.
All modules in the order processing system are integrated and tested with tees
data and found to be free from interface errors.

VALIDATION TESTING:

The main aim of validation testing is to verify that the software system does
what it was designed for. Alpha testing was carried out to ensure the validity of the
system. Software testing and validation is achieved through a series of black box
tests that demonstrate conformity with requirements.
After each validation test case has been conducted, one of the two possible
conditions exists. They are:

 The function or performance characteristics confirm to specification and are


accepted.

 The derivation from specification is uncovered and a deficiency test is


created.
Order processing system is tested under various test conditions. The requirements
as per the specification are met. The performance is tested at full capacity of users
accessing, saving details and regarding the query posted.

2.8 SYSTEM IMPLEMENTATION

In the system implementation stage, we have two phases. They are


construction phase and delivery phase. The construction phase is actually part of a

64
design that implements rapid application development. Given some aspect of the
system design, we construct and test the system components in that design. After
several iterations of the design, we will have built the functional system to be
implemented.

The purpose of the construction phase is twofold:

 To build and test a functional system that fulfils business and design
requirements.

 To implement the interfaces between the new and existing production


systems.

The project team must construct the databases, application programs user
and system interfaces and networks. Some of these elements may already exist as
prototype from design or as existing system components. The implementation of a
new information system is also called delivery. There are three types of
implementation. They are

 Implementation of a computer system to replace a manual system. It includes


converting files, training users, creating accurate files, verifying printouts for
integrity.

 Implementation of a new computer system to replace an existing one. It is a


difficult conversion, because large computer systems need more time to
convert.

 Implementation of a modified application to replace an existing one using the


same computer. Here the conversion is easy to handle, provided there is no
changes to the files.

65
Here the Order processing system is implemented in SNQS Socks
International Pvt Ltd by replacing the manual system. The data are converted into
electronic format and fed into the database of the system. The training is provided to
the user of the system regarding creating accurate files and reports are verified for
integrity.

2.9 SYSTEMS SUPPORT

Once the system is placed into production, the system analyst’s role
changes to systems support. A significant portion of most system analyst’s time and
effort is spent providing ongoing support for existing systems. Systems support is the
ongoing maintenance of a system after it has been placed into operation. Systems
support maintains all the building blocks for a production system. System analysts
wholly coordinate systems support, calling on the services of maintenance programs
and systems designers as necessary. The ongoing activities of systems support are

2.9.1 FIXING SOFTWARE BUGS

How well developed and tested, errors or bugs will occur in a system. The
corrective action to be taken is called system maintenance. Software bugs that
slipped through testing phases during software construction are rectified here.

2.9.2 RECOVERING THE SYSTEM

From time to time, a system failure will result in an aborted program or


loss of data. This may have been caused by human error or a hardware or software
failure. The system analysts may then be called on to recover the system that is to
restore system files and databases, and to restart the system.

66
2.9.3 ASSISTING END USERS

Regardless of how well the users have been trained and how good the
end-user documentation is, users will eventually require additional assistance –
unanticipated problems arise, new users are added, and so forth.

2.9.4 ADAPTING THE SYSTEM TO NEW REQUIREMENTS

New requirements may include new business problems, new business


requirements. All these support activities continue through the lifetime of the
production system.

Here in Order processing system some problems arise after


implementation. The end users face problems in backup data from the system. Post
implementation training had been provided to the end users regarding backing up of
data from the system and how to recover the system from failure.

67
CHAPTER 3

SUGGESTIONS AND CONCLUSION

3.1 SUGGESTIONS

 The extent of computer usage for Order processing maintenance is still at the
initial stage in the organization. The Order processing system has created a
number of user friendly interfaces for data entry in customer order form,
internal order form, and pack material entry. This will help the organization
in reducing manual activities.

 The backup of the database should be taken daily, if required can be


connected to the system using ODBC connectivity.

 The system can be enhanced in future by centralizing all the departments


through Local area network.

 The access to system can also be provided to the customers by locking the
edit option. So that they can view order status and socks details without
altering the database.

68
3.2 CONCLUSION

The order processing system has been developed to meet the present
requirements of SNQS Socks International Pvt Ltd. The system has been developed
using water fall model. The user has expressed satisfaction with the software
developed. The data entries operations for customer order form, internal order form
and pack material entry are useful features. The software has number of validation
features to ensure that the data entered is valid.

The user can view the customer details, internal order details, yarn
requirements, stock details and pack material details. The user-friendly and
growth oriented system has been developed using up to date language and database
design.

69
REFERENCES

• Elmasri, Ramez, Navathe, Shamkant (1997) Third Edition, Fundamentals of


Data Base Management System, Mc GrawHill-International Edition.

• Francesco Balena (1999) Programming Microsoft Visual Basic,


WP Publishers.

• Krishnan.N (2001) Visual Basic 6.0 SciTech Publishers.

• Roger.S, Pressman (1984) Second Edition, Software Engineering, Mc


Graw Hill-International Edition.

• William E .Perry (2000) Second Edition, Software Testing, McGraw


Hill-International Edition.

• C.S.V. Murthy (2004) First Edition, Systems Management, Himalaya


Publishing House.

70