1.

INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

The project of “PRODUCTION CONTROL” keeps track of various parameters such as

Customer details, Tools information, Production Monitoring and Updation details, Supplier
Details and the Raw Material Details in the form. A complete record of the availability and
demand of the materials of the industries can be maintained. The allotment to the work to each
employee in the Industry also becomes very easy. The record of work done by a particular
employee can also be tracked.

In this project, Visual Basic.Net is used as the front End and the SQL Server 2000, is used
as the Backend. Visual Basic is referred to as an “Event Driven” programming language because
all the code is triggered by specific events that the user performs. This puts the user firmly in
control of how the program flows and therefore increases user satisfaction with the program. The
key portions of a Visual Basic.net project are the forms, controls, and code modules. A form or
control has properties that you can alter. The program’s code is contained primarily in events.

The project helps in real time feeding of details on the system, instead of maintaining and
entering the details in the ledger. It reduces the man power and time consumption. It also helps in
keeping the track of the product in each and every stages of the manufacture. From the
knowledge of the status of the product the date of the release of the product can be determined.

1
 2. SYSTEM STUDY

System analysis is a process of gathering the facts concerning the system breaking them

into elements and relationship between elements. It provides a framework for visualizing the

organizational and environmental factors that operate on a system. The quality of work

performed by a machine is usually uniform, neat and more reliable when compared to doing the

same operations manually.

2.1 EXISTING SYSTEM

In the existing system all the details are maintained manually. There are no reports to

view as the monthly reports.

2.1.1 DRAWBACKS OF EXISTING SYSTEM

 The existing system has no security measure.

 The end user has to remember a lot of command to make efficient use of the
system.
 The system does not have any descriptive reports and thus did not help
management in decision-making.
 The case Information’s per day is unable to find.
 Enormous amount of time is consumed

2
2.2 PROPOSED SYSTEM
Computerization is very much need in the modern administration. It is beneficial for both
in terms of economy and manpower. If the information is in paper then the retrieval time is more.

2.2.1 ADVANTAGES OF PROPOSED SYSTEM

 The required information can be retrieved easily.
 The details can be stored in the storage system permanently.
 Time will not be wasted in the calculations.
 Corrections can be made easily.
 High speed.
 Reports can be generated.
 Wastage of manpower is reduced.
 Large volume of records to process.
 Less Time

3
 3. SYSTEM SPECIFICATION

3.1 HARDWARE SPECIFICATION

Processor : Pentium IV
Hard Disk Capacity : 40 GB
Internal Memory Capacity : 128 MB
Keyboard : Logitech of 104 Keys
Mouse : Logitech Mouse

3.2 SOFTWARE SPECIFICATION

Operating System : Windows 7/8
Front End : VB.NET 2008
Back End : SQL Server 2005

4
SOFTWARE FEATURES
VISUAL BASIC.NET
Visual Baic.Net has revolutionized windows programming windows programming and
with an object based, event driven approach to software designs. Visual basic.Net applications
act as a front end to the database. Visual basic.Net application provides the interface between the
user and the database. Sophisticated features that make the language truly object oriented and
interfaces it with the latest in the database technology.
.NET provides a new, object-oriented API as a set of classes that will be accessible from any
programming language. This book describes this framework of classes and provides a reference
to what is available and how you can use this framework to write Windows applications in the
brave new world of .NET.
Microsoft .NET Framework is a computing platform for developing distributed applications
for the Internet. Following are the design goals of Microsoft .NET Framework:
 To provide a very high degree of language interoperability
 To provide a runtime environment that completely manages code execution
 To provide a very simple software deployment and versioning model
 To provide high-level code security through code access security and strong type
checking
 To provide a consistent object-oriented programming model
 To facilitate application communication by using industry standards such as SOAP and
XML.
 To simplify Web application development
Visual basic.net lets the user to add menus, text boxes, command buttons, option buttons,
check boxes, list boxes, scroll bars, and file directory boxes to blank windows. Visual basic.net
has many different tools.
The Common Language Runtime
The CLR is the mechanism through which .NET code is executed. It is built upon a
single, common language—IL—into which source languages are compiled and includes
mechanisms for executing the compiled code. This includes code verification and just-in-time
(JIT) compilation, garbage collection and enforcement of security policies, and the provision of
profiling and debugging services.

5
 The CLR provides a lot of added value to the programs it supports. Because it controls
how a .NET program executes and sits between the program and the operating system, it can
implement security, versioning support, automatic memory management through garbage
collection, and provide transparent access to system services.
The user interface is the part of the program that responds to the key press and mouse
clicks. The action is referred to as events of the form and controls in the form. The form is a
visual object where a set of object controls is placed to communicate with backend databases
and validation checks. VB.NET provides a vast properties and methods for each controls, which
helps to utilize all them, functions for record manipulations.
IMPORTANT FEATURES
 The application is a graphical user interface.
 Client-Server architecture benefits picture and image box can be easily handled using bit
mapped files and icons.
 Bit mapped files and icons are used as simple debugging tools.
 With the advent of .NET, Microsoft has introduced many new technologies that make
writing component-based distributed systems easier, more flexible, and more powerful
than ever before.
 It is now easier than it has ever been to write components in any programming language
that can interoperate with components on other machines, which may not be Windows-
based at all.
SQL SERVER 2005
The purpose of this document is to help you migrate your applications when you are
migrating the underlying database from Microsoft SQL Server to Some other Database. Most of
the issues encountered when migrating applications to use an SQL Server Database are related to
database incompatibility. This paper presents these incompatibilities and provides solutions for
many issues. It familiarizes yourself with this document prior to migrating your databases. The
choices made about how to migrate your application affect how you migrate the underlying
database from Microsoft SQL Server to some other Database.
If the application uses the Microsoft OLE DB Provider for SQL Server or a third-party
OLE DB Provider to connect the Microsoft SQL Server database, use the SQL Server Provider
for OLE DB (SQLOLEDB) to connect to the migrated Database.

6
 There are quite a few reasons, the first being that SQL is a feature rich program that can
handle any database related task you have. You can create places to store your data build tools
that make it easy to read and modify your database contents, and ask questions of your data.
SQL is a relational database, a database that stores information about related objects. In MS SQL
that database means a collection of tables that hold data. It collectively stores all the other
related objects such as queries, forms and reports that are used to implement function effectively.
SQL Server Security
 Login Authentication.
 Windows NT Authentication
 SQL Server Authentication
 Permissions validation on user database.
 T-SQL statements sent to SQL Server.
 SQL server checks user permissions on receipt of T-SQL statements
FEATURES
 Created by Microsoft and Sybase in the 80s.
 Is SQL Compliant - Uses ANSI SQL
 Supports SQL – 92 standards - Uses T-SQL
 Stores data in a central location and delivers it to clients on request
 New Server Architecture
 Graphic Administration Tools
 Maintains ANSI standards and 6.x Compatibility
 Data integrity means reliability and accuracy of data.
 Integrity rules keep data consistent.
 Supports Client/Server model.
 Request response dialog.
 Workload is split between the client and the server.
 Operating System compatibility.
 Runs on Win 95/98 NT, Netware, UNIX, OS/2, AppleTalk, Banyan VINES.
 SQL Server must have Service Pack 4 (SP4) to run on Windows NT 4.0.
 Multiple protocol compatibility.

7
 4. SYSTEM DESIGN
System design is the process of planning a new system to complement or altogether
replace the old system. The purpose of the design phase is the first step in moving from the
problem domain to the solution domain. The design of the system is the critical aspect that
affects the quality of the software. System design is also called top-level design. The design
phase translates the logical aspects of the system into physical aspects of the system.
4.1 INPUT DESIGN
Input design is the process of converting the user-oriented. Input to a computer based
format. The goal of the input design is to make the data entry easier, logical and free error. Errors
in the input data are controlled by the input design. The quality of the input determines the
quality of the system output.
The entire data entry screen is interactive in nature, so that the user can directly enter
into data according to the prompted messages. The users are also can directly enter into data
according to the prompted messages. The users are also provided with option of selecting an
appropriate input from a list of values. This will reduce the number of error, which are otherwise
likely to arise if they were to be entered by the user itself.
Input design is one of the most important phases of the system design. Input design is the
process where the input received in the system are planned and designed, so as to get necessary
information from the user, eliminating the information that is not required. The aim of the input
design is to ensure the maximum possible levels of accuracy and also ensures that the input is
accessible that understood by the user.
The input design is the part of overall system design, which requires very careful
attention. If the data going into the system is incorrect then the processing and output will
magnify the errors.
The objectives considered during input design are:
 Nature of input processing.
 Flexibility and thoroughness of validation rules.
 Handling of properties within the input documents.
 Screen design to ensure accuracy and efficiency of the input relationship with files.
 Careful design of the input also involves attention to error handling, controls, batching
and validation procedures.

8
 Input design features can ensure the reliability of the system and produce result from accurate
data or they can result in the production of erroneous information.
4.2 OUTPUT DESIGN
Output design is very important concept in the computerized system, without reliable
output the user may feel the entire system is unnecessary and avoids using it. The proper output
design is important in any system and facilitates effective decision-making. The output design of
this system includes various reports.
Computer output is the most important and direct source of information the user.
Efficient, intelligible output design should improve the system’s relationships with the user and
help in decision making. A major form of output is the hardcopy from the printer.
Output requirements are designed during system analysis. A good starting point for the
output design is the data flow diagram. Human factors reduce issues for design involved
addressing internal controls to ensure readability.
4.3 DATABASE DESIGN
A database should provide integration, Integrity and a data independence table in a
database contains information pertaining to a specific entity. To maintain the tables in an
effective way, it should be normalized to ensure that the number of tables does no exceed the
optimum level unless it is mandatory.
To prevent unauthorized access, security measures have been provided. This may prevent
unauthorized persons using data that is private. The normalization techniques have been used to
design the table such that the use of all the tables is made easy.
The various relations between different tables, the number of fields in each table and the
type, width of each field were analyses. The names of the fields and tables where so chosen that
the users would not face any problem in identifying the table structure.
The various relations between different tables, the number of fields in each table and the
type, width of each field were analyses. The names of the fields and tables where so chosen that
the users would not face any problem in identifying the table structure.
A database is a collection of interrelated data stored with minimum redundancy to serve
many users quickly and efficiently. The general objective of database design is to make the data
access easy, inexpensive and flexible to the user.

9
Table name : Customer Details

Primary key : Cus Id

Field Name Data type Size Description

CusId Int 10 Customer Id

CusName Varchar 20 Customer Name

Address Varchar 50 Address

City Varchar 20 City

State Varchar 20 State

Pin Varchar 10 Pin Code

MobileNo Varchar 10 Mobile No

DateAndTime Varchar 25 Date And Time

Table name : Product Details

Primary key : ProId

Field Name Data type Size Description

ProId Int 10 Product Id

ProName Varchar 20 Product Name

ToolName Varchar 20 Tool Name

Qty Varchar 10 Quantity

Price Varchar 10 Price

DateAndTime Varchar 25 Date And Time

Table name : Employee Details

10
Primary key : EmpId

Field Name Data type Size Description

EmpId Int 10 Employee Id

EmpName Varchar 20 Employee Name

Address Varchar 50 Address

City Varchar 20 City

State Varchar 20 State

MobileNo Varchar 10 Mobile Number

Exp Varchar 15 Experience

DOJ Varchar 20 Date of Joining

Design Varchar 20 Designation

Salary Varchar 10 Salary

DateAndTime Varchar 25 Date And Time

Table name : Stock Details

Primary key : ProId

Field Name Data type Size Description

ProId Int 10 Stock Id

ProName Varchar 20 Product Name

Qty Varchar 50 Quantity

Table name : Production Details

Primary key : ProdId

11
Foreign key : ProId, EmpId

Field Name Data type Size Description

ProdId Int 10 Production Id

ProId Varchar 20 Product Id

ProName Varchar 20 Product Name

Qty Varchar 20 Quantity

ProCompDt Varchar 20 Process Completed Date

EmpId Varchar 20 Employee Id

EmpName Varchar 20 Employee Name

DateAndTime Varchar 25 DateAndTime

Table name : Order Details

Primary key : OrderId

Foreign key : ProId, CusId

12
Field Name Data type Size Description

OrderId Int 10 Order Id

ProId Varchar 10 Product Id

ProName Varchar 20 Product Name

Qty Varchar 10 Quantity

Price Varchar 10 Price

CusId Varchar 10 Customer Id

CusName Varchar 20 Customer Name

DeliDt Varchar 25 Delivery Date

DateAndTime Varchar 25 Date And Time

Table name : Sale Details

Primary key : SaleId

Foreign key : OrderId, CusId

13
Field Name Data type Size Description

SaleId Int 10 Sale Id

OrderId Varchar 10 Order Id

CusId Varchar 20 Customer Id

CusName Varchar 20 Customer Name

ProName Varchar 10 Product Name

Qty Varchar 10 Quantity

Price Varchar 10 Price

TotalAmt Varchar 10 Total Amount

DateAndTime Varchar 25 Date And Time

4.4 DATA FLOW DIAGRAM

LEVEL 0

Production
Control and
14
Planning
System
 ADMIN Customer

LEVEL 1

Manage
CUSTOMER CUS_DB
ADMIN LOGIN
DETAILS

15
 EMPLOYEE EMP_DB
DETAILS

PRODUCT PRO_DB
DETAILS

PURCHASE PUR_DB
DETAILS

ORDER ORD_D
DETAILS B

SALES SAL_DB

DETAILS

REPORT

4.5 ENTITY RELATIONSHIP DIAGRAM

address
name name
Cus_id city Emp_i city
d

Admin Customer Details Employee Details

Lo
gin
16
 Ord Ma
er de

Pro_id Pro_na
Pro_na qty
me
mr
Order_id
qt Pdt_i pric
y d e

Order Details Product Details

Mad
For e

Pdt_id name
Ord_id
Cust_id
Pdtion_i qty
Sale_i qty d
d
Sales Production

5. SYSTEM TESTING

5.1 TESTING
Software testing is a critical element of software quality assurance and represents the
ultimate reviews of specification, design and coding. Testing presents an interesting anomaly of

17
 the software. During earlier definition and development phases, it was attempted to build
software from abstract concept to a tangible implementation.
The testing phase involves the testing of the developed system using various set data.
Presentation of test data plays a vital role in system testing. After preparing the test data the
system under study was tested using test data. While testing the system by using test data errors
were found and corrected. A series of tests were performed for the proposed system before the
system was ready for implementation. The various types of testing done on the system are:
Testing methodology
 Unit Testing
 Integration Testing
 Validation Testing
 White box testing
 Black box testing
UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software design, the
module. It comprises the set of test performed by the programmer prior to integration of the
unit into larger system. The testing was carried out during the coding stage itself. In this step
each module is found to be working satisfactorily as regards to the expected output from the
module.
INTEGRATION TESTING
Integration testing is a systematic technique for constructing the program structure while
at the same time conducting tests to uncover error associated within the interface. The objective
is to take unit tested modules and build a program structure that has been dictated by design. All
modules are combined in this step. The entire program is tested as whole. And chaos in interfaces
may usually result. A set of errors is encountered in such a case.

VALIDATION TESTING
Here in the validation testing we want to check whether the given conditions to the text
box are working correctly. Because in the name place we want to enter the characters and the
special symbols only we should not enter the numbers in the name field. Here while on runtime
we entered numeric values in the string specified columns of product inwards. It raises error. In

18
this phase each module has been tested by wrong inputs, for example Employee Name should be
a character as well as their age should be in numbers.
WHITEBOX TESTING
White box testing, sometimes called glass-box testing is a test case design method that
uses the control structure of the procedural design to derive test cases. Using white box testing
methods, the software engineer can derive test cases.
 Guarantee that all independent paths within a module have exercised at least once.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds.
 Exercise internal data structures to ensure their validity.
BLACK BOX TESTING
Black box testing, also called behavioral testing, focuses on the functional requirements
of the software. That is, black box testing enables the software engineer to derive sets of input
conditions that will fully exercise all functional requirements for a program. Black box testing is
not an alternative to white box techniques. Rather it is a complementary approach that is likely to
uncover a different class of errors than white box methods. Black box testing attempts to find
errors in the following categories.
After preparing the test data the system under study was tested using test data. While
testing the system by using test data errors were found and corrected. A series of tests were
performed for the proposed system before the system was ready for implementation.

6. IMPLEMENTATION

MODULE DESCRIPTION

Customer Details

19
 The customer Details includes Customer Code, Address, Zip Code, Email Id, TNGST No etc., In
the Customer details form Addition, Edit, Find, Deletion and viewing the record is possible.

Employees Details

The Employee Details includes Employee Code, Address, Zip Code, Email Id, Salary etc., In the
Customer details form Addition, Edit, Find, Deletion and viewing the record is possible.

Product Details

The Product Details includes the Product Code, Product Name, Opening Stock, and Price. The
Raw Material Details includes the Raw Material Code, Name, and Opening Stock.

Order Details

This module is described as the order which is received from the customer for the purchase of the
products. This may contain the fields like order no, customer id, product id, product name, no of products
required etc.

Production Details

In the Production Monitoring and Updating form, the information of products and their quantity
is included. The Product Details form includes the availability and need of Raw material of products.

Sales Details

The sales Details include the database of Sales Details like Customer Name, Product Name,
Quantity, Rate, Freight Charges, Tax and Discount Information.

7. CONCLUSION AND FUTURE ENHANCEMENT

7.1 CONCLUSION

20
 The “PRODUCTION MANAGEMENT AND PLANNING SYSTEM” has been

developed to satisfy all proposed requirements. The system is highly scalable and user friendly.

Almost all the system objectives have been met. The system has been tested under all criteria.

The system minimizes the problem arising in the existing manual system and it eliminates the

human errors to zero level.

The software executes successfully by fulfilling the objectives of the project. Further

extensions to this system can be made required with minor modifications. The invention can be

implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in

combinations of them. Apparatus of the invention can be implemented in a computer program

product tangibly embodied in a machine-readable storage device for execution by a

programmable processor; and method steps of the invention can be performed by a

programmable processor executing a program of instructions to perform functions of the

invention by operating on input data and generating output

7.2 FUTURE ENHANCEMENT

As a future enhancement this project is about to become a web application with complete
features. According to developer it can be developed as mobile application.

9. BIBLIOGRAPHY

REFERENCE BOOKS
1. Elias Awath, “SYSTEM ANALYSIS AND DESIGN”, Tata Mc Graw Hill Publication,
Sixth Edition,2003

21
 2. S. Ramachandran, “COMPUTER AIDED DESIGN”, Air Walk Publication, Third
Edition,2003
3. Richard Fairley,”SOFTWARE ENGINEERING CONCEPTS”, Tata Mc Graw Hill
Publication, Second Edition,1997
4. Programming VB.NET: A Guide for Experienced Programmers by Gary Cornell,
Jonathan Morrison
5. Learning VB.NET Through Applications by Clayton Crooks II
6. VB .NET How to Program (2nd Edition) by Harvey M. Deitel, Paul J. Deitel, Tem R.
Nieto.

ONLINE REFERENCES
1. www.msdn.microsoft.com
2. www.microsoftdotnet.net
3. www.dotnet-tricks.com
4. www.sqlmag.com

22