ABSTRACT

The project titled INVENTORY SYSTEM provides the facility about all customer details and service details computer. The main objectives of this we can obtain the details immediately with Accuracy. It provides easier means to the user to interact with the systems Reports can be generated continuously. In all the way tremendously reduces Man power and avoid inconsistency in the manual operation. The project consist of number of module, They are, 1) Product master 2) Customer master 3) Bill order 4) Supplier master 5) Purchase order 6) Stock order 7) Sales order This project was developed on VB6.0 and MS Access provides the security And high speed accessibility.

ACKNOWLEDGMENT
We express our sincere thanks to our chairman M.,principal and head of the department .for providing us all the facilities needed for completing the process. We wish to place on record our deep sense of gratitude to Lect ..project coordinator ,for her invaluable guidance, suggestions and encouragement throughout the course of this project. We also wish to express out sincere thanks to the review committee members and also all the department teaching non-teaching staff members. We are also thankful to all the members for the valuable suggestion and guidance for completing this project. Finally, we wish to express our indebtedness to our parents, the ultimate force behind us who directly and indirectly help us in completing this project work.

TABLE OF CONTENTS
Ex. No 1. 2. 3. Title Introduction System specification 2.1 Hardware specification 2.2 Software Specification Project description 3.1 User module 3.2 Objectives 3.3 Need for software 3.4 Problem description System Analysis & Design 4.1 Existing system 4.2 System analysis 4.3 System planning 4.4 Feasibility study System design 5.1 Activity diagram 5.2 Class diagram 5.3 Collaboration diagram 5.4 Component diagram 5.5 Deployment diagram 5.6 Sequence diagram 5.7 Use case diagram Software Description 6.1 Front End 6.2 Back End Coding Testing User Manual Conclusion Bibliography Page. No

4.

5.

6. 7. 8. 9. 10. 11.

INTRODUCTION

1. INTRODUCTION
Today the world has been changing towards the computer for higher information transaction with low time and manpower. So the computer has become inevitable. We change our vision to computer; we need software for all Sides. The software makes an important role in computer world, which only makes all activities on the computer. This project also uses one of the software for maintaining the Purchase, sales & stock verification details of the most common developments. In this, we us VB as a front-end and back-end as MS-ACCESS. With the help of this project, we maintain the complete information About the purchase and sales department. It also includes what are the Items ordered received, sales details and billing details. The transactions are done with the help of object Database Connectivity Application Programming Interface (ODBC API).

SYSTEM SPECIFICATION

2. SYSTEM SPECIFICATION

HARDWARE SPECIFICATION: INTEL PENTINUM IV COMPATIBLE MOTHER BOARD INTEL PENTINUM IV PRECESSOR @ 2GHZ 512 MB RAM WINDOWS & PC COMPATIBLE KEYBOARD WINDOWS & PC COMPATIBLE MOUSE COLOUR MONITOR

SOFTWARE SPECIFICATIONS:

FRONT END BACK END OPERATING SYSTEM DESIGN TOOL

: : : :

VB 6.0 MS_ACCESS 2000 WINDOWS 98/2000/XP RATIONAL ROSE

PROJECT DESCRIPTION

3. PROJECT DESCRIPTION
INVENTORY SYSTEM 1.1USER MODULE Computer has main form it includes all details like as Button based on the click event users go to the desired area. Then user can enter the new detail or edit, cancel, view and so on. 3.2 OBJECTIVE The main objective of this project is to maintain all the details about. The computer sales project basically created very rich user interface any one can easily interact with the system. The project created on event driven programming language, so user will get the information immediately. 3.3NEED FOR SOFTWARE In a large organization where computers are used manual recording of large volumes of data increase human errors and man-hours spent for the work. It is difficult to maintain the registers and more time is required for searching information. The user cannot be provided with accurate information at any instance of time. Hence the need for job a sub system is identified, which eliminates procedures.

3.4 PROBLEM DESCRIPTION 1. 2. 3. 4. 5. 6. Existing system extract large manpower It is a time consuming process Hard task to search a detail Complexity is more in existing system Security is less in existing system Entry level validation is not possible

SUPPLIER MASTER MAINTAINANCE SCREEN This screen is used to store all the item master details. In this we can store material bin code, description of material item, unit of measure, quantity on hand, economic order quotient and reorder level that are stored in the bin master maintenance screen updating can be done in this screen.

PRODUCER MASTER SCREEN In this screen we can store the vendor details, name of vendor, address, city and postcode that are maintained by this screen. Using this well know the vendor details. STOCK MASTER WITH COST CENTER In this screen we can maintain material code and name of the cost center code. By this we can be able to use the code in bin master maintenance screen. CUSTOMER MASTER MAINTENANCE SCREEN In this we can store all customer details. Here the customer codes, name of the customer address, city and postcode that are

stored here. If we enter a duplicate code for customer. It will display the suitable warring message. The deletion of customer also done here. PURCHASE ORDER MAINTENANCE SCREEN Here the purchase order details are maintained. Here purchase order number order data, vendor code order quantity, order quantity, order rate and order value, this above are maintained in purchase order screen. SALES ORDER MAINTENANCE SCREEN This table affect the supplier and producer for sales order maintenance screen. Here sales order numbered. Order data and customer code this are maintained and stored here. BILL OF MATERIAL MAINTENANCE SCREEN In this screen the material transaction bills that are maintained. Here the supplier table is affected. In rejection of money is shown in percentage.

SYSTEM STUDY AND ANALYSIS

4. SYSTEM STUDY AND ANALYSIS

4.1 EXISTING SYSTEM The existing system is based on console programming return in C, C++ language. In case of wrong entry the user not aware of weather the entered data was correct or not. In existing system, there is no possibility for entry level validation it does not support more features which is efficient for database applications. Although the existing system doesnt provide the accurate data. Besides it will take more time and man power.

4.1.1 LIMITATIONS OF EXISTING SYSTEM enters the wrong data 4.2SYSTEM ANALYSIS

There is user friendly environments End users doesnt know to do if he/she

UNDERSTANDING THE PROBLEM before the system to create analysis model. There is a tendency to rush to a solution, even before the problem is understood.

DEVELOP PROTOTYPES that enable a user to understand how human/machine interaction will occur. Since the perception of the quality of software is often based on the friendliness of the interface prototyping (And the iteration that results) are highly recommended.

RECORD THE ORGIN of and the reason for every requirement. This is the first step in establishing traceability back to the customer.

 USE MULTIPLE VIEWS OF REQUIREMENTS building data, functional, and behavioral models provide the software engineer with three different views. This reduces the likelihood that something will be missed and increases the likelihood that something will be missed and increases the likelihood that inconsistency will be recognized. RANK REQUIREMENTS tight deadlines may preclude the implementation of every software requirement. If an incremental processes model is supplied those requirements to be delivered in the first increment must be identified. WORK RE ELIMINATE AMBIGUITY because most requirements are described in a natural language, the opportunity for ambiguity abounds. 4.3 SYSTEM PLANNING: Analysis principle is applied and a model of the software to be build called a planning (prototype) is constructed for customer and developer assessment. The close-ended approach is often called throwaway prototyping. Using this approach a prototype serves solely as a rough demonstration of requirements. It is then discarded and the software is engineered using a different paradigm. An open-ended approach, called evolutionary prototyping, uses the prototype as the first part of an analysis activity that will be continued into design and construction. The prototyping of the software is the first evolution of the finished system. 4.4 FESIBILITY STUDY Preliminary investigation also determines whatever the system requested is feasible or not the likelihood the system will be useful to the organization. To ascertain the feasibility of the project the following were considered.

4.4.1 OPERATIONAL FEASIBILITY There is sufficient support from the concerned personnel is favor of the project. The change is acceptable to the users or not. There is no harm from the proposed system. The output from the proposed system will be more useful. The users will be able to access information more quickly. 4.4.2TECHNICAL FEASIBILITY The required technology and equipment are variable for the project to be under taken. There is no need of new technology. The proposed system will provide adequate responses. The system can be expanded and further development according to the needs of the future.

SYSTEM DESIGN

5 DATABASE DESIGN

TABLE NAME: product table

FIELD NAME item Code Product name No. of items cost Manufacture name Expiry date quantity

FIELD TYPE Number Text number currency text Date\time text

DESCRIPTION item Code Number Product Description Number of items Cost of the item Name of the manufacture Expiry date of items Quantity of item

TABLE NAME: PURCHASE TABLE

FIELD NAME sl.no Date Supplier name Supplier address No. of items Amount of purchase Invoice no.

FIELD TYPE Text Date/time Text Text Number Currency Number

DESCRIPTION Serial number of products Date of purchase Name of the supplier Address of the supplier Items listed in number Amount of items purchase Code number of specified concern

TABLE NAME: sales-table FIELD NAME date Customer name Customer address No. of items Amount of sales Bill number DATA TYPE Date/time Text Text number number Number DESCRIPTION Date of purchase Customer Name Address of Customer Number of items sold Amount of items sold Bill number

TABLE NAME: STOCK TABLE FIELD NAME Sl.no Stock available Quantity Stock sold Amount Balance DATA TYPE number Text Text Text Text Text DESCRIPTION Serial number Availability of stock Quantity of stock stock sold Amount of stock sold Stock remaining

5.1 Activity diagram

STOCK

PURCHAS E

NO ...

IF PRODUCT SOLD

STOCK NOT UPDATED

YES

STOCK UPDATED

5.2 Class diagram

manager login :string() database:string()

ordering name of items:string() no of items:int()

stock name of item:string() no of item:int()

supplier name of supplier:string() items supplied:string()

sales name of items:string() name of item:int()

updated items add() delete()

5.3 Collaboration diagram

1: 2:1 REQUEST FOR STOCK DETAILS MANAGER 2: 6:6 STOCK DETAILS VIEWED 3: 4:3 PRODUCTS DELIVERED 5: 3:4 PENDING ORDERS SUPPLIER STOCK MAINTENANCE

4: 5:5 STOCKS UPDATED

5.4 Component diagram

ordering

supplier

deliveries

manager

stock

sales

customer

5.5 Deployment diagram

stock maint...

monitor

5.6 Sequence diagram

MANAGER

STOCK MAINTENENCE Request for stock details order for products

SUPPLIER

products delivered

stock updated

stock details viewed

5.7 Use case diagram

odering

sales

supplier details

customer details

operator

product details supplier

order list

delivery list

sales list

exit system

SOFTWARE DESCRIPTION

SOFTWARE DESCRIPTION

6.1

FRONT END VISUAL BASIC

Visual basic is a RDBMS package, which provides faster and easier way to create application for Microsoft windows. Visual basic provides a complete set of tools to simplify rapid application development Word, Word Processor, Microsoft Excel spreadsheet and other Windows app locations. We can even automate applications and objects created using 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 simplify drag and drop pre-built object into place on screen. The BASIC parts refer 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 original basic language and now contains several hundred statements, functions and keywords many of that relate directly to the windows GUI. The Visual Basic programming language is not unique to Visual Basic. The Visual Basic programming system, application edition included in Microsoft Access and much other window application uses the same language. The Visual Basic professional Edition provides computer professionals with full features set of tools for developing solutions for others. It includes all the features of the learning, plus additional Activex controls, including Internet controls and the crystal reports.

VISUAL BASIC TOOLS: Data access features allow you to create database and front-end application for most popular database formats, including Microsoft SQL server and other enterprises-level database. Activex Tm technologies us to use the functionality provided by other applications, such as Microsoft professional or Enterprise edition of Visual basic. Internet capabilities make it easy to provide access to documents and application across the Internet from within out application. The finished applications a true.exe file that uses a run-time dynamic link library (DLL) that you can freely distribute.

VISUAL BASIC EDITIONS: Visual Basic is available in the three version each geared to meet a specific set of development requirements. The Visual Basic learning edition allows programmers to easily create powerful applications for Microsoft Windows 98 and Windows NT. It includes all intrinsic controls, plus grid, tab and data-bound controls. Documentation provides with this edition includes learn VB now (a Multimedia CD ROM title), a printed programmers Guide, online help, plus visual Basic Books online. The professional edition provides computer professionals with full featured set tools for development solution for others. It includes all features of the Learning edition, plus addition Activex controls, including Internet controls and the crystal Report Writer. Documentation provided with the professional edition includes the programmers guide, online Help, the component tools guide and crystal Reports for Visual Basic Users manual. The Enterprise edition allows professional to create robust distributed application in a team setting. It includes all the features of the professional edition, plus the Automation Manager, Component Manager; database management tools the Microsoft Visual Sources Safe project-oriented version control system, more. Printed documentation provided with the Enterprise edition includes all professional edition pieces, plus the Building Client / Server Applications with Visual Basic book and the Sources Safe Users Guide. ACTIVEX CONTROL: An Activex control is an extension to the Visual Basic Toolbox. You use Activex control just as we would any of the standard build-in controls, such as the checkbox control. When we add an Activex control to a program, it becomes part of the development and run-time environment and provides new functionality for your application. Activex controls leverage our capabilities as a Visual Basic Programmer by retaining some familiar properties, events, and methods, such as the Name property, which behave, as we would expect. Then, however, the Activex controls feature methods and properties that greatly increase our flexibility and capability as Visual Basic programmer.

For example, the Visual Basic professional and Enterprise Editions include the Windows common controls that allow us to crate applications with the tool and feel of Windows98 toolbars, status bars, and tree views of directory structures. Other controls allow you to create application that takes full advantage of the Internet. PROJECT LAMITATIONS: A single project can contain up to 32,000 identifiers, which include butarenotlimitedto, forms controls, modules, variables, constants, procedures, functions, and objects. Variable names in Visual Basic can be no longer than 255 characters, and the names of forms, controls, modules, and classes cannot be longer than 40 characters. Visual Basic imposes no limit on the actual number of distinct objects in project. HIGHLIGHTING FEATURES: NATIVE CODE: Compile a visual basic project to native code for faster execution. Profiles native code using new native code compiler options, and debug native code using the visual C++ environment. CREATE OUR OWN ACTIVEX CONTROLS: Combine existing controls, or create your own from scratch. Activex controls created with visual basic have events, data binding support, licensing support, property pages, internet features, and more.

MULTIPLE PROJECTS: Open multiple projects in the same instance of Visual Basic. Useful for debugging Activex controls.

CREATE ACTIVEX DOCUMENTS: As easy and intuitive as debugging traditional visual Basic applications, Activex documents boost your Visual Basic applications to the internet and intranet browser windows. This allows using the functionality provided by other applications, such as Microsoft Word, Word processor, Microsoft Excel spreadsheet, and other Windows applications. MDI/SDI/EXPLORER-STYLE INTERFACE OPTIONS: Active to do single, multiple, or Microsoft Explorer-style document interface applications. WIZARDS: The activex Control Interface Wizard, Activex Document Migration Wizard, Data form Wizard, and Property Page Wizard, are new. The setup wizard has been enhanced to support distribution via the internet; the installation of remote server components using Distributed COM (DCOM) and Remote Automation; and the ability to create dependency files for projects and components crated with Visual Basic. The professional Edition also comes with the Wizard Toolbar and the Wizard Manager. EXTENSIBILITY MODEL: The new model allows you to programmatically extend the development environment and control projects, events, code and visual element. Declare, Raise, and handle our Own Events: Objects provided by your components can rise that be handled in other applications. You can handle event raised by other application, or by your own objects, using With Events variables. Events provide a simple alternative to asynchronous callbacks. Displays the syntax for statements and functions. Margin indicators mark breakpoint and the current statement, and the Next Statement, indicator is draggable. New Procedure View and Full Module View Buttons make it easy to show either the selected procedure or the entire code in a module Drag and drop from the code

window to the Watch window. Instant watch in Debug mode allows you to get current values as ToolTips. INTERNET COMPONENT DOWNLOADS: You can use Setup Wizard to package your components specifically for deployment on the web. Global Objects: To simplify the creation of reusable code libraries, Visual Basic lets you marks objects in a code component as global, so that their methods can be invoked without explicitly creating as instance of the global object. ENUMS: With the learning Edition, we can define related constants by grouping then in an enumerator, or Enum. With the Professional Edition, Enums can be included in an any developer who uses the component. OLE DRAG AND DROP: Most controls now support drag operations between OLE applications; for example, dragging the contents of Word document into a textbox control. POLYMORPHISM: The Implements feature allows your classes to support multiple interfaces. User of your components can early bind to these interfaces, regardless of the object that implements them.

DATA ACCESS OBJECTS: Data Access Features allows us to create databases and front-end applications for most popular database format, including Microsoft SQL server and other entewrprise level database.

6.2 BACK END:

MICROSOFT ACCESS: Microsoft Access in a powerful program to create and manage your databases. It has many built in features to assist you in constructing viewing your information. Access is much more involved and is a more genuine database application than other programs such as Microsoft works. First of all you need to understand how Microsoft Access breaks down a database. Some keywords involved in this process are: Database File, Table, Field, Data type. Here is the Hierarchy that Microsoft Access in breaking down a database. DATABASE FILE: This is your main file that encompasses the entire database and that is saved to your hard-drive or floppy disk. Example StudentDatabase.mdb Table: A table is a collection of data about a specific topic. There can be multiple tables in a database. Example# 1) Students Example# 2) Teachers FIELD: Field is the different categories within a Table. Table usually contains multiple fields. Example #1) Student Last Name Example#2) Student First name Data types: Data types are the properties of each field. A field only has 1 data type. Field Name (Student Last Name Data type) Text.

TABLES: A table is a collection of data about a specific topic, such as students or contacts. Using a separate table for each topic means that you store that data only once, which makes your database more efficient, and reduces data-entry errors.

PRIMARY KEY: One or more fields (columns) whose value or values uniquely identify each record in a table. A primary key does not allow Null values and must always have unique value. A primary key is used to relate a table to foreign keys in other tables. Note: You do not have to define a primary key, but its usually a good idea. If you dont define a primary key, Microsoft Access asks you if you would like to create one when you save the table. For our tutorial, make the Soc Sec # field the primary key, meaning that every student has a social security number and no 2 are the same. To do this, simply select the Soc #field and select the primary key button. After you do this, save the table.

CODING

TESTING

8. TESTING
System testing is the stage of implementation, which is aimed at ensuring that the system works accurately and efficiently.

Testing is vital role to the success of the system. System testing makes a logical assumption that if all the parts of the system are connect, the goal while be successfully achieved. Testing is the process of executing of the indent of detecting errors there are three important ways to the test program. They are testing for correctness, testing for implantation efficiency and testing for computational complexity. Testing of the program is done with the data prepared by experts of lambent soft systems pvt ltd. The importance of software testing and implementation with respect to software quality cannot be over emphasized. Software testing is critical element of software quality assurance and represents ultimate review of specifications, design and coding. The increases visibility of software as system element and the additional costs associated with a software failure are motivating factors for well planned through testing. It is not unusual for a software development organization to expertise 40% of total project effort on testing test case design focuses in asset of techniques for the creation of test cases that meat overall testing objectives . A good test case is one that has a high probability of finding the undiscovered error. A success full test is one that uncovers an undiscovered error. Test case design approaches includes White box and Block box testing.

8.1. TYPES OF TESTING 8.1.1 WHITE BOX TESTING In this approach of testing, tests are made with the complete knowledge about the internal operations of the product perform according to the specifications and all internal components have been adequately tested. Providing the test cases,

which go through all the loops and conditions of the program tests logical paths through the software. Check points at various places could be placed, so that checks are made to see if the status corresponds to the actual status. Test cases designed through this ensure that; all independent paths within a module have been exercised at least once, executing all logical decisions depending on their true or false value. Executes all loops well within their bounds. Exercise internal data structures to ensure their validity etc. White box testing, even though is a through approach, takes long time for testing. The reasons for conducting white box testing, at the expense of time and energy lies in the nature of software defects. Some of them are given below. Logical errors and incorrect assumptions are inversely proportional to the probability that a program path will be executed. We often believed that a logical path is not likely to be executed when, in the fact, it may be executed on a regular basis. Typographical errors are random, which could go undetected, until actual testing begins. 8.1.2 BLACK BOX TESTING In this approach to testing, text cases are prepared with knowledge about the function that the product is designed to perform. Test can be conducted which demonstrates the completed functionality of the product. Tests are done to check, if the product is fully operational rather than checking each loop and condition of the function. At the software level of testing, this approach revolves around testing the software interface. This approach has a very little regard for the internal logical structure of the software. This designed to uncover; they demonstrate the functions are fully operational. They ensure that: The input is properly accepted and desired output is obtained. They also provide for maintaining the complete integrity of the external information such as data files. Black Box testing is not alternative to White Box testing. It is rather a complementary approach that uncovers different kind of errors. This approach involves errors that include incorrect or missing function, incorrect errors, and errors in data structures to external database access, performance errors and

initialization and termination errors. This testing is generally applied during the alter stages of testing. The main focus of attention of this approach is on the information domain rather that on the logical testing. Test cases designed using this approach tell us something about the presence and absence of class of errors, rather than an error associated only with the specific test at hand . The attributes of both Black and White Box testing can be combined to provide an approach that validates the software interface and selectively ensures that the internal working of the software is correct. 8.1.3. UNIT TESTING Unit testing focuses verification efforts on this smallest unit of the software design of the module. This testing also known as Module testing. The Modules of this system are tested separated. The testing was carried out during programming state itself. In this resting step, each module is found to be working satisfactory as regards to expected output from the module. 8.1.4 INTEGRATION TESTING Data can be lost across an interface one module can have an adverse effect on another, sub-function, when combined, may not produced desire major functions. Integration testing is a systematic testing for constructing the program structure, while at same time conduction test to uncover errors associated within the interface. The objective is take unit tested modules at build a program structure. All the modules combined and tested as whole.

8.1.5 ALPHA TESTING Verifying and studying software errors stimulated data is done in this project. Subjecting is modified software to the actual live data in Beta Testing and this testing is performed in this work.

8.1.6. REGRESSION TESTING Regression testing involves executing old test cases to test that no new errors have been introduced. This testing is performed some changes are made to an existing system. The modified system needs to be tested to make sure that the new features to be added to indeed work. However, as modifications have been made to an existing system, testing also has to be done the make sure that the modifications have not had undesired side effects of making some of the earlier services faulty. This is the tasks of regression testing. 8.1.7. STRESS TESTING The purpose of stress testing is to prove that the candidate system does not mal function under peak loads; we subject a high volume of data over a short period of time. This stimulates an online environment where a high volume of activities occurs in spurts.

9. USER MANUAL

The following key features used for how to access the system. It is fully created based on event driven program. By using the icons we can get the required information. The menu bar having the following menus.

9.1 FROM MENU

9.1.1 MASTER This form menu having the list of forms that means show the Bin Master Information, Vendor Master Information, Customer Master Information. 9.1.2 ORDER INFORMATION This form menu having the list of forms that means show the Purchase Order Information, Sales Order Information. 9.1.3 OTHER This form menu having the list of forms that means show the Vendor Wise Item, Cost Center, Transaction Information. 9.2 ADD This button is used to add the data into the database. 9.3 DELETE This button is used to delete the current record. 9.4 SAVE This button is used to save the user information.

9.5 EXIT This button is used to mainly proposed for terminate the program.

9.6 UPDATE This button is used to edit the current record. 9.7 FIRST This button is used to show the first record. 9.8 LAST This button is used to show the last record. 9.9 NEXT This button is used to show the next record. 9.10 PREVIOUS This button is used to show the previous record.

10. CONCLUSION

The Inventory control system has been implemented to satisfy the demands on the automation of all departments in the company. This software is used to store details, operation details, transaction details etc and it provides various options on the operation to be performed like Displaying. Modifying, inserting records in to database. It has menu driven device. This project has achieved its objectives by successfully implementing the modules. Any kind of change can be incorporated in to database without much effort. This, feature of this project is menu-driven and user-friendly data entry is easier, reports and queries can be obtained easily Input Validation and verification checks.

BIBLIOGRAPHY

11. BIBILOGRAPHY:

TEXT BOOKS: 1. PROGRAMMING VISUAL BASIC 6.0, Microsoft press, Indian reprint. FRANSESCO BALENA. 2. VISUAL BASIC 6, Tata McGraw Hill, 1988. G.CORNELL. 3. VISUAL BASIC 6, H OW TO PROGRAM,PRENTICE HALL INDIA, 1999.

DEITEL & DEITELT.R.NIETO.

4. UML DISTILLED, Second edition, PHI/Pearson education, 2002. MARTIN FOWLER. REFERENCES: www.a1vbcode.com www.altavista.com www.google.com www.planetsourcecode.com www.codeguru.com

APPENDIX