MATERIAL MANAGEMENT SYSTEM By K.R.SIVAGANESH (Reg.

No: 35203151) A PROJECT REPORT Submitted to the Department of Computer Applications in the FACULTY OF ENGINEERING & TECHNOLOGY

In partial fulfillment of the requirements for the award of the degree of

MASTER OF COMPUTER APPLICATIONS

S.R.M. ENGINEERING COLLEGE S.R.M. INSTITUTE OF SCIENCE AND TECHNOLOGY Deemed University May, 2006

ii

BONAFIDE CERTIFICATE

Certified that this project report titled MATERIAL MANAGEMENT SYSTEM is the bonafide work of K.R.SIVAGANESH (Reg. No: 35203151) who carried out the project 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.

Signature of Internal Guide Name:

Signature of the H.O.D

Signature of External Guide Name:

1. 2. Signature of Examiner(s)

iii ABSTRACT The Material Management System is used for over all management of the materials in an organization. The core process of the concern is managing the materials which were done through this project. This enables the inventory, assembling and other essentials for the concern which increases the efficiency of the concern. It should be monitored and should be handled. The concern handles different parts of materials and it assembles the sub materials into finished parts and products.

The inventory control over three stages of materials handles a wide variety of planning, processing and management in an integrated manner. The other key processes are finding alternatives, work places, structuring etc.

There can be different materials under same type, which can be known under alternate part. The overall structuring and designing of the materials in to products can be done in structure module. The different work Places for the different works can be analyzed with some parameters. The process sheet outlets the reports for our need. The Engineering change note is the place where we can do changes on the structures for improvement of efficiency or for the customer needs.

These abstractions are done using components. Java Server Pages (JSP) bridges the whole operation between the user and services. The database is a RDBMS with high security and authentication. The database connection and its operation have been done using JDBC.

iv ACKNOWLEDGEMENT If words are considered as symbols and tokens of acknowledgement then let the words play the heralding role of expressing my gratitude to all who have helped me directly or indirectly during my project work. I feel it is a great pleasure to thank Mr. T.R. Pachamuthu, B.Sc, M.I.E, Chairman and founder of S.R.M Group, Chennai for providing me excellent facilities. I owe my gratitude to the Dean, S.R.M Institute of Science and Technology, Mr. R. Venkatramani, B.E, M.Tech, F.I.E, for giving me an opportunity to exhibit my excellence. I am indebted to Professor Mr. S. Sagayaraj MCA, M.Phil, Head of the Department, Department of Computer Applications, S.R.M Institute of Science and Technology, for his unparalleled guidance and help through out the duration of this project. I express my gratefulness to my project coordinator Mr. M. Eliazer MCA, Senior Lecturer, Department of Computer Applications, S.R.M Institute of Science and Technology, for all the necessary help and support rendered to me through out the project. I express my sincere thanks to my guide Mrs. S. Anjugam MCA, M.Phil, Lecturer, Department of Computer Applications, S.R.M Institute of Science and Technology, for the necessary support and guidance rendered to me through out the project. I am most grateful to Mr. K.Pradeep Onspec Technology Solutions Pvt Ltd, for giving me the opportunity to do a project at their concern and for finding time and patience in explaining and guiding me through out the project.

v TABLE OF CONTENTS CHAPTER ABSTRACT LIST OF TABLES LIST OF FIGURES 1 INTRODUCTION 1.1 Organization Overview 1.2 Project Overview SYSTEM STUDY AND ANALYSIS 2.1 Existing System 2.2 Proposed System 2.3 Feasibility Study SYSTEM ENVIRONMENT 3.1 Hardware Requirements 3.2 Software Requirements 3.3 Software Overview 3.4 Process Scheduling SYSTEM DESIGN 4.1 System Flow Diagram 4.2 Data Flow Diagram 4.3 Database Design 4.4 Input Design 4.5 Output Design SYSTEM DEVELOPMENT 5.1 Modules 5.2 Module Description SYSTEM TESTING 6.1 Introduction 6.2 Test Plan 6.3 Test Plan Analysis SYSTEM IMPLEMENTATION MAINTANENCE AND FUTURE ENHANCEMENTS 8.1 Maintenance 8.2 Future Enhancements CONCLUSION APPENDIX A.1 Screen Shots BIBLIOGRAPHY DESCRIPTION PAGE NO v v v 1 1 3 7 7 8 9 10 10 11 12 16 17 17 18 22 28 29 30 30 30 33 33 34 35 36 37 37 38 39 40 40 60

7 8

vi

LIST OF TABLES SL.NO 1 2 3 4 5 6 7 8 9 10 11 12 TABLE NO. 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 6.1 DESCRIPTION INV_P_T_M INV_P_G_M INV_P_M UOM_M ALT_P_M WORKING_M PROD_STRUCT ACC_STRUCT PRO_SHEET ECN_ACC ECN_PROD Test Plan PAGE NO. 22 22 23 24 24 25 25 26 26 27 27 35

vii

LIST OF FIGURES SL. NO 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 FIGURE NO. 4.1 4.2 4.3 4.4 4.5 A.1 A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 A.10 A.11 A.12 A.13 A.14 A.15 A.16 A.17 A.18 A.19 A.20 DESCRIPTION System Flow Diagram Level 0 DFD Level 1- Inventory DFD Level 1- Structure DFD Level 2 DFD Admin Form Inventory Form Part Type View Form Part Type Add Form Part Type Edit Form UOM master View Form Alternate Part Master View Form Alternate Part Master Add Form Alternate Part Master Edit Form Work Place View Form Structure View Form Structure-1 View Form Structure-1 Add View Form Structure-2 View Form Structure-2 Add View Form Ecn-1 View Form Ecn-2 Add View Form Process Sheet Report View Form Report For Product View Form Report For Ecn View Form PAGE NO 17 18 19 20 21 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

viii CHAPTER 1 INTRODUTION 1.1 ORGANIZATION OVERVIEW Onspec Technology Solutions Pvt Ltd., is a full-fledged software development and consulting company with IT education as a separate division called ONSPEC.edu. Onspec is a blend of the best of 3 entities viz., Onspec Technologies Singapore, Lambent Softsystems Chennai, ONSPEC Software Chennai. Onspec is now a subsidiary of Onspec Technologies, USA.

Onspec has some of the best resources to take up large systems automation and is over 100 people strong. The company derives its strength from the top management having over 500 man years of experience in IT development, implementation, training and consulting.

The company has taken over Steerprise ERP from ONSPEC Software along with the resources and the clients. The company has full potential to serve and take forward all its clients from their present state.

Onspec is an ERP developer and is an implementation partner to ORACLE for Oracle APPS ERP in India. Onspec is a partner to Sun Microsystems for Java and Sun Solaris OS, a partner to Redhat on Linux, a partner to IBM for Rational Testing tools, a partner to Oracle on Oracle 9i/10g database and applications training and has a fullfledged development lab (ODC) in Chennai.

Onspec is part of M/s. Specvision Global LLC., USA. Onspec has its group offices in India, Singapore, London, San Jose USA, Malaysia, Indonesia and Muscat, Oman.

Onspecs Project / ERP clients include TVS Group, TI Group, Johnson Lifts, Anabond, Madras Fertilizers, KSB Pumps, Binani Zinc, Seshasayee Paper & Boards, Rainbow Carpets, Oman Optic Fibres, Tirumalai Chemicals, Cholayil Pharma, Citadel Aurobindo Biotech, Hitech ARAI, London Sumatra, Citibank N A, Hidesign Leathers, Gee Dee Weiler, Taurus Tanneries, GM India, Cholamandalam Insurance among others.

ix

Onspec has its Consulting division in Chennai which works with clients like Infosys, Covansys, HP, Hexaware, HCL Technologies, TVS Electronics, CSS, NetVision, ALLSEC, e-serve, on contractual and professional manpower services. EDGES, as the division is referred, have direct overseas placement services too by coordination with its global offices.

Onspec has a separate division for technical consulting and corporate resourcing. ONSPEC.edus consulting division called EDGES works with clients viz., Covansys, Infosys, TVS Electronics, HP India, HCL Technologies, e-logistics, TI Cycles, Candeosoft, Gavs, Kumaran Systems, FSS, Changepond Technologies, Ready Test Go, Saksoft, Sword Global, J&B Soft, Transnet, I Interchange, Gmac among others for manpower consulting and re-sourcing.

Onspec is a blend of the best of 3 entities viz., Onspec Technologies Singapore, Lambent Softsystems Chennai, ONSPEC Software, Chennai.

1.2 PROJECT OVERVIEW MATERIAL MANAGEMENT SYSTEM is an application used for the management of materials and related operations. The Material Management System is a project module of a well comprised production and sales concern. The Material Management System is used to maintaining the information about the company to increase the productivity. The company handles different parts of materials and if assembles the sub materials into finished goods. The different cost of the materials, at the different times will need flexible changes in the product cost. The core process of the concern is managing the materials which were done through this project. This enables the inventory, assembling and other essentials for the concern which increases the efficiency of the concern.

The user of the system can be categorized as Administrator

x 1.2.1 ADMINISTRATOR LOGIN Initially the login page was displayed, the user should be an administrator. After successful login home page was displayed. The page contains the following modules, Inventory Alternate Part Structure Work Place Process Sheet ECN

1.2.2 INVENTORY MODULE

The inventory module is to maintain the part type materials, part group materials, part master materials and also uom master. The Inventory module is used to maintain the raw materials and the finished products. In this Inventory module, the material from the Material Management is divided in to three types, they are part type master, part group master and part master. The Inventory module has the following sub modules, Part Type Master Part Group Master Part Master. UOM.

Part type master are the basic and interior part which are maintained with details like part code, description, notes. Any new part can be added, removed, edited here.

Part Group Master is the assembled parts with the part type master. It also has its own part code and description and notes. Which can also be added, removed, edited.

Part master is the final product which is the assembled part with the part group master. The maintenance of this type is also the same as the other two.

xi The UOM is the unit of measurement for the materials such as part type master, part group master and part master. UOM has some measurement such as centimeter, inches, and box. Etc.

1.2.3 ALTERNATE PART MODULE

When there was a need for alterations in the designed product, then we can able to undergo alterations. Since, there are numerous parts its not possible to find the alternative part for any part code. Here the assembling of each part in different possible combinations can be known. The part type master, part group master, part master intern are search for the alternatives. The final product can be able to design by our own predicted economy.

1.2.4 STRUCTURE MODULE

The different parts available in inventory have to be assembled or designed in some way to get various structures. The code number, which is unique, enables the description and its sub parts to be listed in tree format. It can be easily selected for our new designing. From there itself the sub assembled parts can be visited. It has two sub modules,

For Products. For Accessories and Consumables.

The For Products sub module is used to create the structure for the finished product/materials. We can add the extra materials/parts with existing finished product.

For example, let us take the finished product such as car, now we can add the extra parts in the finished product with the help of structure module.

We can add the additional accessories and consumables with the help of For Accessories and Consumables sub module.

xii 1.2.5 WORKPLACE MODULE

Work Place module mainly used to know the productivity in each and every department and also know the capacity of the department.

The different parts can have different work place where it can be used. The description for each products work place is maintained which can be referred at any time. In this module we can improve the productivity and control the productivity. By analyzing, we can decide which the best workshop for the particular product is.

1.2.6 PROCESS SHEET MODULE

The report can be generated for the code number of the product. This is same for the report by giving product name. . The processes done, Ecn by date and alternative parts can be taken out as report.

1.2.7 ECN MODULE (Engineering Change Notes)

Engineering change note can be prepared for products and for accessories & consumables. Which is the basic information given for each product.

It has two sub modules,

For Products. For Accessories and Consumables.

This module is mainly used to design the finished product/material by various tests. If the concern wants to change the design and improve the efficiency of the product, then the ECN change the design technically by the test. Finally we can get the best product and then change the structure of the finished product.

xiii CHAPTER 2 SYSTEM STUDY AND ANALYSIS 2.1 EXISTING SYSTEM The organization which produces some finished products by assembling the different assembling parts using a basic level management over materials ,but other core processes like maintaining inventory, alternating etc are not in their existing system.

They are done manually and entered as data in to the system. The concern was not feeling good on their existing system, since there are many more maintenance has to be done manually. They want their system to be user friendly. So, they needed a system which will handle the complete maintenance of materials. They also needed some existing process have to be altered with new strategy.

The limitations of the present system are

Large amount of clerical time is required. Data reliability and maintainability is difficult. Accessibility of accurate information is difficult. There is always delay in information search and retrieval. Large amount of storage is needed. But present existing system configuration, memory is not support extremely stored database.

xiv 2.2 PROPOSED SYSTEM The proposed system is fully designed as satisfying the users need. The system has the separate modules of maintaining the materials. Other then inventory, other processes such as alternating parts, structuring etc are included in the proposed system.

The navigation and usage of the system is user friendly. The system and databases are designed such that they are fully secured.

The system maintenance is easy and the system is flexible for future modifications if needed.

Merits of Proposed System

It would be the best user-friendly system. Avoid duplication work. Fast and accurate report generation. It reduces the clerical time. A complete security is providing for the reading, writing and deleting of data by authorized person only. Data handling like insertion, deletion and updating is made easy. Fast search and information retrieval is possible. It provides safe storage of large volume of data. Data back up is also provided in the proposed system.

2.3 FEASIBILITY STUDY The objective of the feasibility study is not only to solve the problem but to acquire a sense of its scope. During the study, the problem definition is crystallized and aspects of the problem to be included in the system are determined. Consequently, costs and benefits are estimated with greater accuracy at this stage.

Three key considerations are involved in the feasibility analysis.

xv Financial & Economical feasibility Technical Feasibility Operational Feasibility

2.3.1 FINANCIAL & ECONOMICAL FEASIBILITY

Economical feasibility deals about the economical impact faced by the organization to implement a new system. Not only cost of hardware, software etc is considered but also the benefits in the form of reduced costs. The project "MATERIAL MANAGEMENT SYSTEM" is installed will certainly be beneficiary since there will be a reduction in manual work, and increasing the speed of work.

2.3.2 TECHNICAL FEASIBILITY

Technical consideration evaluates the hardware requirements, software etc. This system uses the Jsp and Servlet as front-end and Oracle Server as back-end and also provides sufficient memory to hold and process the data. As per the requirements both these software and hardware were already exists this project is technically feasible.

2.3.3 OPERATIONAL FEASIBILITY

Proposed system is beneficial only if they can turn into information systems that will meet the organization's operating requirements. User should be involved in the planning and development of the project. This system will certainly be supported since it produces good result and reduces manual work. Authorized user can access the data in the project and hacking of data by unauthorized users is also avoided by providing username and password.

CHAPTER 3 SYSTEM ENVIRONMENT

xvi 3.1 HARDWARE REQUIREMENTS

Processor Hard Disk Memory Monitor Software Keyboard

: Intel Pentium PC with 166MHz or Higher : 2.1 GB or more : 32 MB RAM : Color Monitor : Internet Explorer and Windows 95 and above : 104 Keys Win95 Keyboard

3.2 SOFTWARE REQUIREMENTS

Operating System Web Designing Tools Scripting Language Web Programming Tools Server Database Language Platform

: Windows 95, 98, NT. : HTML, Java Script, Jsp, Servlets. : Java scripts : Java, Jsp, Servlets : Apache Tomcat Server 4.0 : Oracle 8i : J2EE

Database Connectivity Tools : JDBC

xvii 3.3 SOFTWARE OVERVIEW 3.3.1 J2EE ARCHITECTURE The J2EE platform uses a multi tiered distributed application model for enterprise applications. Application logic is divided into components according to function and the various application components that make up a J2EE application are installed on different machines depending on the J2EE environment to which the application component belongs. The following list describes the J2EE tiers. Client-tier components run on the client machine. Web-tier components run on the J2EE server. Business-tier components run on the J2EE server. Enterprise information system (EIS)-tier software runs on the EIS server.

Although a J2EE application can consist of three or four tiers, J2EE multitiered applications are generally considered to be three-tiered applications because they are distributed over different locations: client machines, J2EE server machine, and the database or legacy machines at the backend. Three-tiered applications that run in this way extend the standard two-tiered client and server model by placing a multithreaded application server between the client application and back-end storage. The J2EE server used in this online applications is Apache Tomcat 4.0.1.

3.3.2 JSP

JSP is a technology developed by Microsoft to take text scripts in an HTML context and run them on the Web server to create dynamic and interactive pages. While JSP is different from HTML, it is usually written as scripts within an HTML document. HTML is a static document that the Web server displays upon request by the browser. But if the HTML has JSP scripts embedded within it, the server will run those scripts and then display the results within the page on the browser.

TEMPLATE TEXT: STATIC HTML

xviii

In many cases, a large percent of your JSP page just consists of static HTML, known as template text. In all respects except one, this HTML looks just like normal HTML, follows all the same syntax rules, and is simply passed through to the client by the Servlet created to handle the page. Not only does the HTML look normal, it can be created by whatever tools you already are using for building Web pages. The one minor exception to the template text is passed straight through rule is that, if you want to have <% in the template text.

3.3.3 INTRODUCTION TO JAVASCRIPT

JavaScript is a scripting language developed by Netscape. It works in all major browsers that are version 3.0 or higher. In the project the java script is used for both the client side and server side validations, such as text box input check, range check validation etc. JavaScript is a scripting language A scripting language is a lightweight programming language A JavaScript is lines of executable computer code A JavaScript can be inserted into a HTML page JavaScript is an open scripting language that anyone can use without purchasing a license JavaScript is supported by all major browsers like Netscape and Internet Explorer

3.3.4 JDBC ODBC

The project involves the JDBC connectivity for the interaction of the front end to the database. JDBC is a Java API for executing SQL statements. The API consists of a set of classes and interfaces written in Java programming language. JDBC provides a standard API for tool/database developers and makes it possible to write database applications using a pure Java API. JDBC is a low-level interface, which means that it is used to invoke (or call) SQL commands directly. In addition, JDBC is a base upon

xix which higher-level interfaces and tools such as JMS and EJB are built. The JDBC driver used in this application is JdbcOdbcDriver.

3.3.5 SERVLETS

The servlet is used for some extent . Servlet is a generic server extension - a java class that can be loaded dynamically to expand the functionality of a server. Servlets are commonly used with Web servers, where they can take the place of CGI scripts. A Servlet is similar to a proprietary server extension, except that it runs inside a Java Virtual Machine on the server, so it is safe and portable. Servlets operate solely within the domain of the server: unlike applets, they do not require support for Java in the web browser.

Another advantage of Servlets is that they are portable: both across operating systems as we are used to doing with Java and also across web servers. Almost all of the major web servers support Servlets. It is believed that Java Servlets offer the best possible platform for web application development. Although Servlets are most commonly used as a replacement for CGI scripts on a Web server, they can extend any sort of server. Imagine, for example, a Java-based FTP server that handles each command with a separate Servlet. New commands can be added by simply plugging in new Servlets. Or, imagine a mail server that allows Servlets to extend its functionality, perhaps by performing a virus scan on all attached documents or handling mail filtering tasks.

3.3.6 TOMCAT SERVER

The Tomcat server is a Java-based web application container that supports the Servlet and JSP (Java Server Pages) specifications. It has grown into one of the industryaccepted standards for implementing Servlet and JSP APIs within web applications

Tomcat is the Servlet container that is used in the official Reference Implementation for the Java Servlet and Java Server Pages technologies. The Java Servlet and Java Server Pages specifications are developed by Sun under the Java

xx Community Process. Tomcat is developed in an open and participatory environment and released under the Apache Software License. Tomcat is intended to be a collaboration of the best-of-breed developers from around the world. We invite you to participate in this open development project. To learn more about getting involved, click here.

3.3.7 ORACLE 8i Oracle is the most widely used database in the world. It runs on virtually every kind of computer. Including IBM mainframes, DEC VAX minicomputers, UNIX-based minicomputers, Windows NT, and several proprietary hardware-operating system platforms; it is clearly the worlds largest RDBMS vendor. At the time of the writing, Oracle is the worlds leading supplier of software for information management and the worlds leading supplier of software for information management and the worlds second (only to Microsoft) largest software company.

Oracle concentrated on its RDBMS. Lately, it has launched many successful horizontal and vertical products, such as Oracle Application Server. Also, Oracle has provided many capable development tools over the years, which is perhaps one of the reasons behind its steady rise to the top. These tools for example, include the Designer/2000 CASE tools and the Developer/2000 development package. These latter tools, now simply referred to as Designer and Developer, have become increasingly Web-based, as have all of their tools, following industry precedent. In addition, Oracle Applications, including the popular Oracle Financials, bring in a robust business for Oracle to supplement their core RDBMS business.

3.4 PROJECT SCHEDULING

Gantt chart for ERP for Small Business Tasks Weeks System Study Data Analysis 1 Jan 2006 2 3 4 1 Feb 2006 2 3 4 1 Mar 2006 2 3 4 Ap2006 1 2

xxi Database Design System Design Master Modules Inventory Modules Sub Modules Reports Generation Testing & Validation Documentati on Implementati on CHAPTER 4 SYSTEM DESIGN 4.1 SYSTEM FLOW DIAGRAM

Monitor

Logon

Process Sheet

Inventory

Work Place

Alternate Part

Ecn

Structure

Oracle Data base

xxii

Fig 4.1 System Flow Diagram

4.2 DATA FLOW DIAGRAM Data Flow Diagram (DFD) is used to define the flow of a system and its resources such as information. Data flow diagrams are a way of expressing the system requirements in a graphical manner. DFD represents one of the most important tools used for structured analysis. A DFD is also known as bubble chart. It has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. 4.2.1 LEVEL 0

xxiii

User

login

Material Management System

Report

Inventory

Work Station

Structure

Process Sheet

Ecn

Fig 4.2 Level 0 DFD

4.2.2 LEVEL 1 INVENTORY

xxiv

Inventory

Part Type M t

Part Group M t

Part Master

Uom

Add and Edit the part type material

Add and Edit the part group material

Add and Edit the part material

Add and Edit the measurement

INV_P_T_M

INV P G M

INV P M

UOM M

Fig 4.3 Level 1- Inventory DFD

xxv STRUCTURE
Structure

For Product D i

For a&c Design

Add and Save the product structure

Add and Save the accessories structure

PROD STRU

ACC STRUC

Fig 4.4 Level 1- Structure DFD

xxvi

4.2.3 LEVEL 2

Login

Inventor y

Alternat e Part

Monitor

Process Sheet

Alternate Part Type

Workplace

Structur e

Report

Product

A&C

INV_P_T_M

Ecn

Part Group Master

INV_P_G_M ECN_PROD

Part Master

INV_P_M

Fig 4.5 Level 2 DFD

xxvii

4.3 DATABASE DESIGN The database design briefs the entire design of the database used in the project.

4.3.1 Table Name INV_P_T_M

Table Structure

Field Name PTCODE PTDESC PTNOTES

Type CHAR(6) VARCHAR(20) VARCHAR(50) Table 4.1 - INV_P_T_M

Key Value PRIMARY KEY

4.3.2 Table Name INV_P_G_M

Table Structure

Field Name PGCODE PGDESC PGNOTES

Type VARCHAR(6) VARCHAR(20) VARCHAR(50) Table 4.2 -INV_P_G_M

Key Value PRIMARY KEY

xxviii

4.3.3 Table Name

INV_P_M

Table Structure

Field Name PCODE PDESC PTCODE PTDESC PGCODE PGDESC PTNATURE MANUFACTURING STKUOM RECVUOM ISSUOM

Type VARCHAR(6) VARCHAR(20) VARCHAR(6) VARCHAR(20) VARCHAR(6) VARCHAR(20) VARCHAR(25) VARCHAR(25) VARCHAR(10) VARCHAR(10) VARCHAR(10) Table 4.3 -INV_P_M

Key Value PRIMARY KEY

FOREIGN KEY

FOREIGN KEY

NOT NULL NOT NULL NOT NULL NOT NULL

xxix 4.3.4 Table Name UOM_M

Table Structure

Field Name UOM UOMDESC RELUOM RELUOMDESC

Type VARCHAR(10) VARCHAR(15) VARCHAR(10) VARCHAR(15) Table 4.4 -UOM_M

Key Value PRIMARY KEY

NOT NULL

4.3.5 Table Name ALT_P_M

Table Structure

Field Name PTNO PPDESC CHPNO CHPDESC

Type VARCHAR(6) VARCHAR(20) VARCHAR(6) VARCHAR(20) Table 4.5 - ALT_P_M

Key Value PRIMARY KEY

NOT NULL

4.3.6 Table Name

xxx WORKING_M

Table Structure

Field Name WPNO WDESC PARAMS CAPACITY

Type VARCHAR(6) VARCHAR(50) VARCHAR(100) VARCHAR(100)

Key Value PRIMARY KEY

NOT NULL NOT NULL

Table 4.6 - WORKING_M

4.3.7 Table Name PROD_STRUCT

Table Structure

Field Name PTNO PDESC PDNO STRUCT PROCESSFLAG

Type VARCHAR(6) VARCHAR(50) VARCHAR(10)

Key Value PRIMARY KEY

NOT NULL

VARCHAR(4000) NOT NULL VARCHAR(1) NOT NULL

Table 4.7 PROD_STRUCT

4.3.8 Table Name ACC_STRUCT

xxxi

Table Structure

Field Name PTNO PDESC PDNO STRUCT PROCESSFLAG

Type VARCHAR(6) VARCHAR(50) VARCHAR(10)

Key Value PRIMARY KEY

NOT NULL

VARCHAR(4000) NOT NULL VARCHAR(1) NOT NULL

Table 4.8 - ACC_STRUCT

4.3.9 Table Name PRO_SHEET

Table Structure

Field Name PTNO PDESC CHILDPDESC OPNDESC QTY WPDESC

Type VARCHAR(6) VARCHAR(30) VARCHAR(30) VARCHAR(30) VARCHAR(30) VARCHAR(30) Table 4.9 - PRO_SHEET

Key Value PRIMARY KEY

NOT NULL

4.3.10 Table Name ECN_ACC

xxxii Table Structure

Field Name PTNO PDESC PDNO ECNDATE REASON STRUCT ECNNO

Type VARCHAR(6) VARCHAR(50) VARCHAR(10) DATE VARCHAR(60) VARCHAR(4000) VARCHAR(6) Table 4.10 - ECN_ACC

Key Value PRIMARY KEY

FOREIGN KEY

FOREIGN KEY

4.3.11 Table Name ECN_PROD

Table Structure

Field Name PTNO PDESC PDNO ECNDATE REASON STRUCT ECNNO

Type VARCHAR(6) VARCHAR(50) VARCHAR(10) DATE VARCHAR(60) VARCHAR(4000) VARCHAR(6)

Key Value PRIMARY KEY

FOREIGN KEY

FOREIGN KEY

Tale 4.11 ECN_PROD 4.4 INPUT DESIGN The decisions for handling input specify how data are accepted for computer processing. The design of input also includes specifying the means by which end-users and system operators direct the system in which actions to take. For example, a system

xxxiii user interacting through a workstation must be able to till the system whether to accept input, produce a report, or end processing. The following are the input design used in this tool.

4.4.1 Inventory Inputs

The inputs in inventory can be of three types of input. The three main strategies of the inventory namely part type, part group and part master have their individual inputs. The materials are inputted in the add form for their persistence. Each part have its unique code to be inputted with its description and notes. The inputs for the part type and part group are same but the part master has some additional inputs such as uom details and its interior part details.

4.4.2 Alternate part Inputs

The alternate part form has the input for the products which all are have the alternative parts. The part code has to be selected and the corresponding alternative have to be added, so that it can be available for accessing alternatives.

4.4.3 Workplace and structure Inputs

The different work places with its parameters and its capacities should be inputted in the workplace add form. The structure has the part code and design code as initial input where the new structures are designed.

4.4.4 Process Sheet and Ecn Inputs

Process sheet have the input for generating the required report. The ecn has the input of alternate or more efficient restructures.

4.5 OUTPUT DESIGN

xxxiv Computer output is the most important and direct source of information to the user. While designing the output, the following procedure must be accomplished. Determining what information to be present. Decide whether to display or print the information.

4.5.1 Getting Alternative Parts

Here as the part code is given it is possible to find the alternative parts for that particular part. There was a need for alterations in the designed product, then we can able to undergo alterations. Since, there are numerous parts its not possible to find the alternative part for any part code. Here the assembling of each part in different possible combinations can be known.

4.5.2 Structure Outputs

The different structuring designs can be outputted by which the part master and part group master are manufactured. Its possible for us to get some efficient alternative designs in the ecn structuring.

4.5.3 Reports

The process sheet which outputs the report for the alternative parts and workplace, operation and quality of the part given. Report can be used to handle more complex work, which makes the work to look much easy and also provides a more feasible to understand and the user who is using this will get more involved and develops the system in a more easier way.

xxxv CHAPTER 5 SYSTEM DEVELOPMENT 5.1 MODULES

The core modules identified within the scope of the project are

Inventory Alternate Part Structure Work Place Process Sheet Ecn

5.2 MODULE DESCRIPTION 5.2.1 INVENTORY MODULE

The inventory module is used to maintain the part type materials, part group materials and part master materials. The Inventory module is used to maintain the raw materials and the finished products. In this Inventory module, the material from the Material Management is divided in to three types, they are part type master, part group master and part master. The Inventory module has the following sub modules, Part Type Master Part Group Master Part Master. UOM. Part type master are the basic and interior part which are maintained with details like part code, description, notes. Any new part can be added, removed, edited here. Part Group Master is the assembled parts with the part type master. It also has its own part code and description and notes. Which can also be added, removed, edited.

xxxvi Part master is the final product which is the assembled part with the part group master. The maintenance of this type is also the same as the other two. The UOM is the unit of measurement for the materials such as part type master, part group master and part master. UOM have the some measurement such as centimeter, inches and box. etc.

5.2.2 ALTERNATE PART MODULE

When there was a need for alterations in the designed product, then we can able to undergo alterations. since, there are numerous parts its not possible to find the alternative part for any part code. Here the assembling of each part in different possible combinations can be known. The part type master, part group master, part master intern are search for the alternatives. The final product can be able to design by our own predicted economy.

5.2.3 STRUCTURE MODULE

The different parts available in inventory have to be assembled or designed in some way to get various structures. The code number, which is unique, enables the description and its sub parts to be listed in tree format. It can be easily selected for our new designing. From there itself the sub assembled parts can be visited. It has two sub modules,

For Products. For Accessories and Consumables.

The For Products sub module is used to create the structure for the finished product/materials. We can add the extra materials/parts with existing finished product. For example, let us take the finished product such as car, now we can add the extra parts in the finished product with the help of structure module. We can add the additional accessories and consumables with the help of For Accessories and Consumables sub module.

xxxvii 5.2.4 WORKPLACE MODULE

Work Place module mainly used to know the productivity in each and every department and also know the capacity of the department. The different parts can have different work place where it can be used. The description for each products work place is maintained which can be referred at any time. In this module we can improve the productivity and control the productivity. By analyzing, we can decide which the best workshop for the particular product is.

5.2.5 PROCESS SHEET MODULE

The report can be generated for the code number of the product. This is same for the report by giving product name. . The processes done, accessories and consumables and alternative parts can be taken out as report.

5.2.6 ECN MODULE (Engineering Change Notes)

Engineering change note can be prepared for products and for accessories & consumables. Which is basic information given for each product. It have the two sub modules, For Products. For Accessories and Consumables.

This module is mainly used to design the finished product/material by various tests. If the concern wants to change the design and improve the efficiency of the product, then the ECN change the design technically by the test. Finally we can get the best product and then change the structure of the finished product.

xxxviii

CHAPTER 6 SYSTEM TESTING 6.1 INTRODUTION Testing presents an interesting challenge for the software programmer. In testing, a series of test cases have been created with intent to demolish the software that has been built. Testing requires that the software developer discard preconceived notations of the correctness of the software developed and overcome a conflict of interest that occurs when errors are uncovered.

6.1.1 Unit Testing In this different test modules are tested against the specification of the modules. Unit testing was done for the verification of the code produced during the coding phase and to test the internal logic of modules. It refers to the verification of the single program module in installed environment.

6.1.2 Boundary testing Boundary testing is the last and most important task of the unit test step. Software often fails at its boundaries. That is, error often occur when the nth of a loop I passes is invoked; when the maximum or minimum allowable is encountered. Test cases that exercise data structure, control flow and data values just below, and just above maxima and minima are very likely to uncover errors.

6.1.3 Module Testing A module is the collection of dependent components such as an object class, an abstract data type or some collection of procedures and functions. The module encapsulates related components that can be tested without other system modules. 6.1.4 User Acceptance Testing User acceptance of a system is a key factor for the success of any system. The system under consideration is tested for the user acceptance by constantly keeping in touching

xxxix in touch with the prospective system users at the time of developing and making changes whenever required.

6.1.5 System Testing The sub-systems are integrated to buildup the entire system. The testing process is concerned with finding errors, which is an outcome of unanticipated interaction between sub-system and system components. If also concerned with validating whether the system meets its functional and non-functional requirements.

6.1.6 Integration Testing Integration testing checks all the modules together in order to make sure that they work as a group. Integration tests are performed incrementally by adding the modules one by one to the system and testing to make sure that it works properly before adding the next module. This makes it easier to trace errors when they are discovered.

6.2 TEST PLAN Each test in the source code test plan consists of the following details The system was found to meet the specified requirements Test plans have been made as soon as the requirements model was complete. Testing was also done by the onsite team members to make it more effective. The test plans were planned and executed focusing on individual components.

6.3 TEST PLAN ANALYSIS

Requirements being tested Admin Name Admin Name Password Password PartTypeCode Null

Input data

Error Message Enter Valid AdminName Enter Valid AdminName Enter Valid Password Enter Valid Password Enter PartTypeCode

Wrong Username Null Wrong Password Null

xl PartGroupCode PartCode PartTypeCode PartGroupCode PartCode Uom Params Capacity EcnDate EcnNumber Null Null Code out of range Code out of range Code out of range Null Null Character Null Null Table 6.1 Test Plan CHAPTER 7 SYSTEM IMPLEMENTATION Software implementation is the process of translating design specification into source code. The primary goal of implementation is to write source code and internal documentation so that conformance of the code to its specification can be easily verified and also that debugging, testing and modification are ceased. Software maintenance is a set of software engineering activities that occur after software has been delivered to the customer and put in operation. Enter PartGroupCode Enter PartCode Enter correct code Enter correct code Enter correct code Uom should not be null Params should not be null Enter only numbers EntervalidDate Enter EcnNumber

It is the process of converting a new or revised system design into a operational one. Conversation means changing from one system to another. The objective of the system implementation is to put the tested system into operation while holding costs, risks and personnel irritation to minimum. The users were trained for the use of system and the training focuses on User capabilities The nature of system being installed. Based on the factors the users are trained to utilize the system.

METHODOLOGY FOR IMPLEMENTATION

xli Implementation is the stage of the project when the theoretical design is turned into a working system. Any system can be implemented in four methods as follows.

1. Direct Method 2. Cut-over Method will 3. Segment Method

: A new system will be designed and implemented. : The existing will be cut down and the be implemented. : The existing system process is divided into number of new system

segments. For the new system the segments are implemented one by one. 4. Parallel Method : The new system is developed parallel independent of

the existing systems.

CHAPTER 8 MAINTANENCE AND FUTURE ENHANCEMENTS 8.1 MAINTENANCE

Maintenance is actually the implementation of the post-implementation review plan. As important as it is, many programmers and analyst are reluctant to perform or identify themselves with the maintenance effort. There are psychological, personality and professional reasons for this. In any case, a first-class effort must be made to ensure that software changes are made properly to keep the system in tune with the user specifications.

One-way to reduce maintenance cost are to maintenance management and software modifications audits. Software modification consists of program rewrites system level updates, and re-audits of low-ranking programs to verify and correct the soft spots. The outcome should be more reliable software, a reduced maintenance backlog, and higher satisfaction and morale among the maintenance staff. The software maintenance is classified into four tasks: Corrective Maintenance Adaptive Maintenance Preventive Maintenance Perfective Maintenance

xlii

8.1.1 Corrective Maintenance The corrective maintenance is to correct the diagnosis errors in this project. It helps to easily identify the diagnosis errors in this software for debugging it.

8.1.2 Adaptive Maintenance It modifies this project with a changing environment.

8.1.3 Preventive Maintenance The Company can change this software to improve future maintainability.

8.1.4 Perfective Maintenance It recommends for new capabilities in any module, Modifications to the existing functions and increases the value of this project i.e., general enhancements

8.2 FUTURE ENHANCEMENT

This package is flexible for further enhancement. Security features can be added while distributing over the network. The developed system is highly interactive one and it is user friendly.

Even when the new system has gone live there may be many need for some system design activity. This will stem from changes that are necessitated by the dynamic nature of the system and its environment. Changes may be required to correct false or to bring about improvements, and may arise as part of the normal changes (or amendments, as they are called) must be carefully controlled by appropriate procedures and documentations and perhaps handled by specialist group of maintenance staff.

It can be further developed to include more operations. Future enhancements can be made to the system at any later point of time. Coding procedures can be modified according to the needs of the user. Reports can be represented in all necessary

xliii prospective. Added options can be included in designing report. After including these additional futures give more flexible than now.

CHAPTER 9 CONCLUSION The "MATERIAL MANAGEMENT SYSTEM razes all the problems faced by the existing system and achieves its goal.

One of the objectives of this system is that it should be user friendly and it has been achieved by Web Designing Tools like HTML, VBScript, JavaScript. The database is designed in such a way that the retrieval is ease, quick and accurate. The flow of data is perfect and it has been checked by entering original data.

This system is more flexible and a future enhancement is possible without any complication. The following points concluded the discussions done so far and from the working experience with the software. The core benefits are

Provides more information about the past, present and future of the Materials. Reduce errors and provides correct result.

xliv APPENDIX A.1 SCREEN SHOTS

ADMINISTRATOR VIEW

Fig A.1 Admin Form

xlv

INVENTORY VIEW

Fig A.2 Inventory Form

xlvi

PART TYPE VIEW

Fig A.3 Part Type View Form

xlvii

PART TYPE ADD VIEW

Fig A.4 Part Type Add Form

xlviii

PART TYPE MASTER EDIT VIEW

Fig A.5 Part Type Edit Form

xlix

UOM MASTER VIEW

Fig A.6 UOM master View Form

ALTERNATE PART MASTER VIEW

Fig A.7 Alternate Part Master View Form

li

ALTERNATE PART MASTER ADD

Fig A.8 Alternate Part Master Add Form

lii

ALTERNATE PART MASTER EDIT

Fig A.9 Alternate Part Master Edit Form

liii

WORKPLACE VIEW

Fig A.10 Work Place View Form

liv

STRUCTURE VIEW

Fig A.11 Structure View Form

lv

STRUCTURE-1 VIEW

Fig A.12 Structure-1 View Form

lvi

STRUCTURE-1 ADDVIEW

Fig A.13 Structure-1 Add View Form

lvii

STRUCTURE-2 VIEW

Fig A.14 Structure-2 View Form

STRUCTURE-2 ADD VIEW

lviii

Fig A.15 Structure-2 Add View Form

ECN-1 VIEW

lix

Fig A.16 Ecn-1 View Form

ECN-2 ADD VIEW

lx

Fig A.17 Ecn-2 Add View Form

PROCESS SHEET REPORT VIEW

lxi

Fig A.18 Process Sheet Report View Form

REPORT FOR PRODUCT VIEW

lxii

Fig A.19 Report For Product View Form

REPORT FOR ECN VIEW

lxiii

Fig A.20 Report For Ecn View Form

lxiv BIBLIOGRAPHY

REFERENCES 1. Bruce Eckel (1998) Thinking in Java Prentice Hall International Ltd, London 2. Clark Christensen, Michael Lee Java Distributed Applications GalGotia Publications Pvt. Ltd. 3. 4. Groh, Peter Norton (2002) Guide to Java Tata McGraw hill, Fifth Edition Hams Bergsten (2001) Java Server Pages Shroff Publishers and Distributors Pvt Ltd, First Edition, 5. 6. Marc Johnson (1996) JavaScript Manual of Style LeafWriters Pvt. Ltd Roger S.Pressman Software Engineering McGraw Hill Publication

WEBSITES REFFERED www.jguru.com www.sun.com www.wrox.com www.Howstuffworks.com www.bea.com