1.

INTRODUCTION
1.1ABOUT THE PROJECT
The project Production planning and controlling system serves the automation Product manufacturing companies process to store the all the information. The automation of product Planning and controlling provides the overall process of production. The ultimate objective of production planning and control, like that of all other manufacturing controls, is to contribute to the profits of the enterprise. As with inventory management and control, this is accomplished by keeping the customers satisfied through the meeting of delivery schedules. Specific objectives of production planning and control are to establish routes and schedules for work that will ensure the optimum utilization of materials, workers, and machines and to provide the means for ensuring the operation of the plant in accordance with these plans. The system makes the tasks of planning and controlling have a raw material details, product details, export details, branch details, delivery details, order details and stock. Bill receipt includes the items distributed with products. Using the Product planning and controlling system the buying and selling process are done through the electronic money format. These processes minimize the cash flow and faster transaction to the customer. The project consists of various modules such as raw materials, vendor details, purchase order, repair section, quality inspection etc. Each one performs its own process. However, the main objective of the project is purchasing raw materials from the vendors and assembling them as finished products for purchase. These products after quality inspection in case of any damage are sent back to the assembling section, and if not, are sent to the warehouse for sales. Individual reports are provided for each module, these includes various stock transactions Reports are provided as day wise, month wise, as weekly reports and so on.

1.2

HARDWARE SPCIFICATION
The configuration given below is the hardware for the system development. Processor RAM Hard Disk Floppy Drive Cache Memory Monitor Mouse Keyboard : : : : : : : : PENTIUM IV 2.66 GHz 256 MB RAM 80 GB 1.44 MB 512 MB Zenith 15 COLOR MONITOR Zenith 3 button optical mouse 110 Keys (Zenith)

1.3

SOFTWARE SPECIFICATION The configuration given below is the software handled for the system development. Operating system Front- End Back-End : : : Windows XP Visual Basic 6.0 MS Access

1.3.1 SOFTWARE DESCRIPTION

Visual Basic 6.0 Visual Basic is a Windows programming language that has been developed at Microsoft Corporation in 1982. Visual Basic is a powerful programming language to develop sophisticated windows programs very quickly and event-driven programming. Visual Basic is one of this RAD (Rapid Application Development) tools as it enables the programmer to develop applications very easily and very quickly. The Visual part refers to the method used to create the Graphical User Interface (GUI). Rather than writing numerous line of code to describe the appearance and location of interface elements, simply add pre built object into place on screen. The Basic part refers to

the BASIC language, a language used by more programmers than any other language in the history of computing. Visual Basic Edition Visual Basic software comes in three editions: Learning Editions: which includes the Visual Basic development environment and use of standard tools to develop applications Professional Edition: is used by computer professionals as it supports the tools to develop ActiveX and Internet controls Enterprise Edition: which includes all the features of professional edition well as Microsoft Visual Source safe for source code control and Automation and Component manager Visual Basic 6.0 Version 6.0 of Visual Basic is specially designed to utilize the internet. It comes with several controls that allow user to create web-based application called ActiveX executables. Additional features 1. OLE Automation is an industrial standard technology that application uses to expose their OLE objects to development tools, macro language, and other application that support OLE Automation. 2. To distinguish Visual Basic project files from source files used by other development tools, the file extension. VBP used. 3. Object Browser is used for hierarchal display of classes, properties, and methods available to the application. 4. The 32-bit version of Visual Basic supports long files names. 5. programmers can define classes, which are contained in Visual Basic class module. Class module is the one, which contains the definition of class; its properties and definition. 6. Enhanced Object Browser, Auto list numbers features and auto quick information feature is also provided.

7. ActiveX is a new buzzword that refers to technologies that previously may have been associated with the term OLE. ActiveX is Microsofts name for technologies that are based on the Component Object Model (COM). 8. Visual Basics internet capability allows one to create powerful applications hosted by standard browser. Visual Basic as a front-end tool Visual Basic is Windows application development platform with a strong combination of a front-end tool and programming language .The ease of the visual approach coupled with the power of programming and the straightforward BASIC language syntax makes programming easy. By using visual Basic, the programmer can create powerful, full feature application that exploit the key feature of MS Windows, including Multiple Document Interface (MDI) , Object Linking and Embedding (OLE), Dynamic Data Exchange (DDE), graphics and many more. Visual Basic can be extended by adding custom controls and by calling procedure in Dynamic Link Libraries (DLLs). Using MDI in Visual Basic: MDI stands for Multiple Document Interface. Visual Basic application can have only one MDI form. A child form is an ordinary form that has its MDI-Child property set to true. The application can include MDI-Child forms. At run time, child forms are displayed within the internal areas of MDI form. When a child form is minimized, its icon appears on the MDI form instead of appearing on the desktop. Element of Visual Basic Visual Basic interface consists of the following elements. Toolbar Provides quick access to commonly used commands in the programming environment. An icon in the toolbar can be clicked to carry out the action represented by that icon. Toolbox Provides as set of tools that can be used at design time to place controls on a form. Menu bar Displays the commands that can be used to build an application.

Form Serves as a window that can be used to customize the interface of an application. Controls, graphics and pictures can be added to a from to create the Visual effect required by the user. Project Window Lists the dow form, code, modules and custom control files that make up the current project. A project is the collection of files that a programmer uses to build up his application. Total number of controls The maximum number of controls allowed on a single form up to 254. The limit control array index is 0 to 32,767 on all versions. Code Limitations Each procedure per module can contain up to 64k of code. There is no limit on the number of procedure. The amount of code is limited to 65,534 lines into a form, class or module. MS-ACCESS (Back-End Tool) Ms-access is a powerful multi user relational database managements system developed by Microsoft used to implement large amount of information with minimum memory allocation and auto make repetitive task, such as maintaining and generating invoice. Data in ms-access is organized in the form of tables within a table records are arranged to a common reference value known as primary key. FEATURE OF MS-ACCESS Access is window based application and therefore it has an interface similar to windows. Access maintains a single disk file for a database and all its associated objects. Access lets you import from or export to foxpro, oracle and other data form. Access wizard is a vitality that helps to perform complex task by guiding through out the access. Access contains nearly hundred. Wizards to design database application, tables, forms, reports, graphs, mailing labels, control and properties.
5

ADVANTAGES OF MS ACCESS: Less time consumption and quick response. Access has a friendly environment. Microsoft access is not needed for keeping register for recording.

DISADVANTAGES OF MS ACCESS: The data security is very less. The database would not be opened. No availability of temporary tables.

2. SYSTEM ANALYSIS
System analysis is the process of gathering and interpreting facts, diagnosing problems, and using the information or recommend improvements to the system. This is the job of the system analyst. In the case of systems analysis, the substance is the business system under investigation and the parts are the various sub-systems, which work together to support the business. Before designing a computer system, which will satisfy the information requirements of a company, it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination will then provide the design teams with the specific data they require in order to ensure that all the clients requirements are fully met. The investigation or study conducted during the analysis phase may Build on the results of an initial feasibility study and will result in the Production of a document, which specifies the requirements for a new system. This document is usually called the requirements specification or functional specification, and it is also described as a target document because it establishes goals for the rest of the project.

2.1 PROBLEM DEFINITION

Every business needs marketing system to carry out its day-today operation faster and to reach all in all way. This topic is closely concerned with the purchase raw material, production, and purchase return, sales return and stock details to run a day-today activity very effectively. Nowadays the computer, software packages are useful in analyzing the purchase and sales details. Successful business planning requires information about potential target of market, the competition prevailing in the market, the individual and their reactions towards the products. To give the accurate information and to simplify the manual system and also against the requirement of the company we have split the project into three major modules.

2.2 SYSTEM STUDY

System is not independent entities but exists in an environment. There are many relationships between a system and its environment and some of these are indirect rather than the direct relationships. The functioning of a system can be affected by changes in the system environment in ways that can be very difficult to predict. As in the physical environment systems are also situated in an organizational environment. In this organizational is not properly understood. Systems may be inappropriate and rejected by users and organizational managers. System analysis aims in providing a scientific approach for solving the problems created by complex situations. The system analysis helps in finding out the various ways in which the system can be developed and also helps mainly in making beneficial decisions in an organization. So, System analysis is mainly needed for decision making and planning in an organization.

2.3 PROPOSED SYSTEM

The drawbacks which are faced during existing system can be eradicated by using the proposed system. The main objective of the existing system is to provide a user-friendly interface.The proposed system now computerizes all the details that are maintained manually. Once the details are fed into the computer there is no need for various persons to deal with separate sections. Only a single person is enough to maintain all the reports. The security can also be given as per the requirement of the users. This Production Planning and controlling system is a proposed system, which replace the existing manual system in an appropriate way. This System is having all the details about products having wider usage. It makes all work to be easy and saves the time. The correctness of data is tested at the time of input. The proposed system generally has the facilities like Control data redundancy Supports data independence Providing more information at low cost Supports accuracy and integrity Do away with as much payer work as possible
8

2.3.1 Advantages of the Proposed System Large volumes of data can be stored easily. Maintenance of file is flexible. Records stored are updated easily. Reports can be generated with ease. Accurate calculations are made. Less manpower required. Accuracy and error free transaction process. Neat and clear representation of report. User satisfaction at high level. Efficient service. Reduce data redundancy. Any form of reports can be produced instantaneously. Updating is very easy. Accurate information will be provided when the information is needed. 2.3.2 Objective of the Proposed System . The Data redundancy is eliminated Validation checks are performed at instances. Data Integrity is maintained. Hundred percent Client Server techniques can be achieved. Providing table level locking, Row level locking. Providing user friendly entry screens to the end users as GUI based. Reliability, Portability and Flexibility are the main advantages. Even a non Computer professional can also handle.

3. SYSTEM DESIGN
3.1 FILE SPECIFICATION
A database is defined as a collection of data items organized in such a way that the specific data or record can be retrieved and processed when required. The proposed system has following tables. Table Name : User Purpose : The table is used to creating the fields for user login which stores the details about the user login information Name Username Password Table Name Purpose Field Name M_Code M_Name M_Sno M_MDate M_Type M_BNo M_BDate M_CName M_MCA M_Inc : : Data Type Text Text RawMaterial To store details of Raw Material Field Size Field Description 5 Material Code 20 Material Name 10 Material Serial No 8 Material Make Date 20 Material Type 8 Material Bill Number 8 Material Bill Date 20 Material Company Name 25 Material Manufacture 25 Company Name Material In charge Name Constraints Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Size 20 8 Description User Name Password Constraints Primary Key Not Null

Field Type Number Text Number Date Text Number Date Text Text Text

Table Name Purpose

: :

ProductDetail To store details of Product Details

10

Field Name P_Code P_Name P_Sno P_Qty P_Date P_Weight P_Price P_TPrice M_Inc Table Name Purpose Field Name E_Code E_Name P_Sno E_Qty E_Date E_Weight E_Price E_TPrice E_Inc

Field Type Number Text Number Number Date Number Number Text Text : :

Field Size Field Description 5 Product Code 20 Product Name 10 Product Serial No 10 Product Quantity 8 Product Quantity Date 8 Product Total Weight 8 Product Unit Price 8 Product Total Price 25 Material In charge Name

Constraints Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null

ExportDetail To store details of Export Details Field Size 5 20 10 10 8 8 8 8 25 Field Description Export Code Export Name Export Serial No Export Quantity Export Quantity Date Export Total Weight Export Unit Price Export Total Price Export In charge Name Constraints Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null

Field Type Number Text Number Number Date Number Number Text Text

3.2

MODULE SPECIFICATION
The system Production Planning and Controlling System can be used to manage

the data of all type of production companies. It will support both stand alone and also networking environment. The system uses VB Technology. The main modules involved in this system are: Login
11

Login module is used to check whether the user is an authorized person to use the system or not. For this the user should give the correct user name and password. The different types of users are 1. Admin 2. Employee

Planning and controlling details This process have a details of raw material details, product details, export details, company branch details, product delivery details, order details and stock details. Machine Details This module or process have contain the details of machine like machine id ,machine name, machine serial no, machine make date, machine worker name etc., Employee Details This module contains the details of the employee. The employee details have employee id no, employee name, employee address, employee date of birth, etc.,

4. TESTING & IMPLEMENTATION

4.1. SYSTEM TESTING
Testing is an important phase encountered in any developed product or framework is the testing phase. It is because, the developed product should be free from errors and it should be validated for accuracy. The product should work under normal conditions as long as the user gives proper inputs and therefore it should be checked for its robustness and should withstand and inform the users about the erroneous input.
12

The testing phase involves testing the system using various test data. Preparation of test data plays a vital role in the system testing. After preparing the test data, the system is tested using those test data. Errors are found and corrected by using the following testing steps and corrections are recorded for future reference. Thus a series of testing is performed on the system before it is ready for implementation. Testing is applied at different levels in the development lifecycle. Each level of testing done is different in nature and has different objectives at each level. The focus of all levels of testing is to find errors, but different types of errors are looked for at each level. The quality of system is confirmed by the thoroughness of its testing. Duration and cost of testing and debugging is a significant fraction of the system development cycle and hence influences overall productivity during the development. In this phase, the errors in the programs or modules are localized and modifications are done to eliminate them. The testing makes a logical assumption that all parts of the system work efficiently and the goal is achieved. VERIFICATION TESTING The purpose of the requirement phase is to ensure the users needs are properly understood before translating into design. Requirements are difficult to develop because it is hard to distinguish needs from wants.

VALIDATION TESTING Validation is achieved through a series of testing that demonstrate conformity with requirements. Both the plan and the procedures are designed to ensure that all the functional requirements are satisfied. All behavioral characteristics are achieved. All performance requirements are attained.

BLACK-BOX TESTING

13

Black-box testing is an approach to testing where the tests are derived from the program or component specification. The system is a block box whose behavior can only be determined by studying its inputs and the related outputs. Another name for this is functional testing because the tester is only concerned with the functionality and not the implementation of the software. The following methods are commonly used: The following methods are commonly used: Equivalence partitioning Boundary-value analysis Error guessing.

Equivalence partitioning Equivalence partitioning is a systematic process that identifies, on the basis of whatever information is available, a set of interesting classes of input conditions to be tested, where each class is representative of a large, set of other possible tests. Error guessing Error guessing is an ad hoc approach, based on intuition and experience, to identify tests that are considered likely to expose errors. The basic idea is to make a list of possible errors or error-prone situations and then develop tests based on the list. Some items to try are Empty or null lists/ strings Zero instances/ occurrences Blanks or null characters in strings Negative numbers. Testing for pixel value is zero or not.

WHITE-BOX TESTING When testing is done knowing the internal workings of a product, tests can be conducted to ensure that internal operations are performed according to specifications and all internal components are adequately exercised. This type of testing is called as white-box testing or glass-box testing.
14

White-box testing of software is predicated on close examination of procedural detail. Providing test cases that exercise specific sets of conditions and/or loops tests logical paths through the software. The status of the program may be examined at various points to determine if the expected or asserted status corresponds to the actual status. White box test is done to Guarantee that all independent paths within a module have been exercised at least once Exercise all logical decisions on their true or false sides Execute all loops at their boundaries and within their operational bounds. Exercise internal data structure to assure their validity.

Testing was done for the grouping row and column pixels. There are some basic forms of logic coverage Statement coverage: Each statement is executed at least once. Decision coverage: Each statement is executed at least once; each decision takes on all possible outcomes at least once. Condition coverage: Each statement is executed at least once; each condition in a decision takes on all possible outcomes at least once. Decision/condition coverage: Each statement is executed at least once; each decision takes on all possible outcomes at least once; each condition in a decision takes on all possible outcomes at least once; Multiple/condition coverage: Each statement is executed at least once; all possible combinations of condition outcomes in each decision occur at least once. Whether correct statistical values are getting from the given grouped rows, grouped pixels. UNIT TESTING Unit testing focuses on the verification effort of the smallest unit of design module. Attention is diverted to individual modules, independently to locate errors. This has enabled the detection of errors in coding and logic. The various modules of the system are tested in
15

unit testing method. Using the detailed description as a guide, important control parts are tested to uncover errors within the boundary of the module. The relative complexity of tests and the error detected as a result is limited by the constrained scope established for unit testing. This test focuses on each module individually, ensuring that it functions properly as a unit, and hence the name Unit Testing. INTEGRATION TESTING The program as a whole is integrated into a single component and checked with test data. This is to check that the whole program works together correctly. The various modules are integrated first. Then the system is tested as a whole. The behavior of each module with another is identified in this testing. Any misbehavior will lead to dangerous problems or errors in the system. All these problems can be filtered off using this testing. We combined all the modules into a single component and tested for integrity. We found the crude form of our project is meeting the basic requirements like policy-setting according to user, host and time constraints. We integrated the different components we developed like the Server-Client Chat, Policy setting algorithm on the Gateway (Bluetooth Adaptors), System-System File Sharing Process as of Server-Client File Sharing System. We found our primary version worked without any bug .We also checked our software functioning under different environments. We found it working without any problems. i. ii. Bottom-up Integration: low-level components are integrated and tested before the higher-level components have been developed. Top-down Integration: The high-level components of a system are integrated and tested before their design and implementing has been completed. The steps in top-down integration are: Begin with the top module in the execution hierarchy. Stub modules are produced, and some may require multiple versions. Stubs are often more complicated than they first appear. The next module to be tested is any module with at least one previously tested super ordinate module. After a module has been tested, an actual module and its required stubs replace one of its stubs.
16

Here grouping row and column module was integrated with the statistical representation module A classic system-testing problem is finger pointing. This occurs when a defeat is uncovered, and one system element developer blames another for the problem. Rather than indulging in such nonsense, the software engineer should anticipate potential interfacing problems along with the below specified points. 1. Design error-handling paths that test all information coming from other elements of the system. 2. Conduct a series of tests that simulate bad data or other potential errors at the software interface. 3. Record the results of tests to use evidence if finger pointing occurs. 4. Participate in the planning and design of system testes to ensure that software is adequately tested.

17

4.2 SYSTEM IMPLEMENTATION

Implementation means converting a new system or revised system into an operational one. Conversion is main aspect of implementation. It is the process of designing from the old system to the new one. Several procedures and documents are carried during the conversion phase. Implementation of a modified application to replace an existing one. Using the same computer this type of conversion is relatively easy to handle, provided there are no major changes in the files. In implementation, the training for the system user, how to work with this software should be given. The development of operating procedure to repair and enhance the system should be done. The installation new computers with required hardware and software specification are to be performed, if the present system is working manually. If the hardware specification of the present system is below the recommended specification the existing system should be replaced with new one or up gradation of the existing system should be done. It is necessary to check whether the required application should be working properly. Implementation is the stage in the project where the theoretical design is turned in to a working system and is giving confidence on the new system for the users, which will work efficiently and effectively. It involves careful planning investigation of the current system and its constraints. If the implementation neither is nor carefully planned it can cause confusion. Thus it can be considered as the most crucial stage in achieving a successful new system and in giving the users confidence that the new system will work be effective. It is during the implementation phase the system takes shape. The main stages in the implementation are Planning Training System Testing

18

5. CONCLUSION & SUGGESTIONS

CONCLUSION
The implementation has been done in step-by-step process. Each module has been developed and tested. This system has efficient report generation, which provides detailed information about the yarn purchase, sales, customer, buyer, purchase return, sales return, stock details. Special features of this project are: Storing of data in a perishable media High speed of transaction Storage of large volume of data Easy access and report generation Avoids data redundancy completely The main advantage of this project is the speed of information retrieval. Accurate outputs are generated. Access to the required information is easy. This project reduce time and manual work required for record keeping and helps in keeping track of various processes involved.

SUGGESSTION
This software production planning control has been developed in a structured manner. Further development can be done very easily because the coding is done in simplified way as there are more understandable and flexible. While designing the system all the future requirements are considered and there are implemented in the system. Thus no more changes are required in the present system at user point of view.

19

BIBLIOGRAPHY BOOKS:
1. Stephen Walther, VB Programming, Weily Publications, First Edition, 2003. 2. Dan Hurkwitz, Jesse Liberty, Programming in Visual Basic,second Edition, 2008. 3. Robert Hottmalk MS Access, Galgotia Publications, First Edition 2001. 4. Roger S.Pressman, Software Engineering, Tata McGraw Hill Publications, first Edition 1998. 6. Ragu Ramakrishnan , Johannes Gehrke, Database Management System third Edition. 7. Elias M.Awad, System Analysis And Design Tata Mc Graw Hill, third Edition 1997. URL REFERENCES http://www.google.co.in http://www.vbtutor.net/ http://msdn.microsoft.com/en-us/vbasic/ms789056 http://office.microsoft.com/en-us/access/ http://www.softwaretestinghelp.com/

20