1.

PROJECT DESCRIPTION

1. PROJECT DESCRIPTION

The Production Management System aims at monitoring the Production operation, online the data and data distribution between various factories and H.O. The main objective of the Production system is to carry out the day-to-day operations in each factory efficiently and to enable the updated information to reach all levels of Hierarchy at the Head Office.

Production Management System (PMS) is a database driven project used to computerize the Stores Department of a Manufacturing Unit. The manufacturing unit is where the product needs are regularized and raw materials are procured for further production. The important aspect of the stores department is that it should not overstock products or be ignorant of the forthcoming requirements as per the ever-changing market conditions. Production process of any material includes accumulation of a number of raw materials or spares put together. Even if any one of the ingredient raw material or spare part is in short supply the whole production comes to a standstill. To avoid this scenario the system has efficient algorithms to detect and maintain sufficient stock so as to keep the production line running without any interruptions.

The following are the features that are to be implemented in the proposed project:  Receiving Orders from concerned departments.  Material Requirement Planning to be carried out for the Order received.  Bill of Materials based on the Material Requirement Plan.  Raising Indents to Stores.  Materials Issuance.  Stock level maintenance.  Re-order level pointers.  Ordering Materials to be procured from supplier.

All these parts are heavily linked together to give a unique interface for the day-to-day needs of the Organization in maintaining the Optimum Level of raw materials. The project titled PRODUCTION MANAGEMENT SYSTEM is a database driven project used to computerize the Stores Department of a Manufacturing Unit. This project has many specialized features. This project consists of seven main modules. They are,

 Login  Main menu  Customer  Order Item  Customer Details  Update order  Update existing Item

 LOGIN: The user can log into the system using the username and the password allotted to him by the system administrator, for better control of the resources of the system.

 MAIN MENU: Once the user is authenticated, the main splash screen of PRODUCTION MANAGEMENT SYSTEM of the company is presented along with the menu bar displaying the various functionalities and transaction details of the Production Monitoring System.

 CUSTOMER: This module is used to store the details of the customer. The customer form contains Customer ID, Customer Name, Address Details, Mobile Number, City, Country and Email Address.

 ORDER ITEM: This module is used for customer. They can order any item from the list shown above. If the ordered item is more than the availability then required number of items does not exist message will be displayed. 3

 CUSTOMER DETAILS: This particular module displays the information regarding customers are updated and added. The address and other contact details of the customers are shown explicitly enabling the user to enter and read the details without much difficulty.

 UPDATE ORDER: This module belongs to the administrator. Here the administrator can add new item, which is getting popular in the market.  UPDATE EXISTING ITEM: This module also belongs to the administrator. Here the administrator can Update the existing item.

2. SOFTWARE SPECIFICATION

1. HARDWARE SPECIFICATION: The hardware for the system is selected considering the factors such as CPU Processing speed, Memory Access Speed, Peripheral Channel Speed, Printer Speed, Seek Time and Relational Delay of Hard disk and Communication speed. The Hardware Specifications are as follows.

PROCESSOR HARD DISK RAM CD DRIVE KEY BOARD MOUSE

: Pentium IV : 40 GB or above : 256MB or above : 40-12-40 : 106 KEYS : Three BUTTON-SCROLLS

2. SOFTWARE SPECIFICATION:

OPERATING SYSTEM BACKEND FRONTEND

WINDOWS 98, WINDOWS XP MS-ACCESS VISUAL BASIC 6.0

3. DESIGN AND DEVELOPMENT

3.1 ARCHITECTURAL DESIGN

3.1 ARCHITECTURAL DESIGN

PRODUCTION MANAGAMENT SYSTEM

MAIN MENU

CUSTOMER

ADMIN

REGISTER CUSTOMER DETAILS

ORDER ITEM

CUSTOMER DETAILS

UPDATE ORDER

UPDATE EXISTING ITEM

INPUT/OUTPUT DESIGN

INPUT DESIGN Inaccurate input data are the most common cause of errors in data processing. Input design is the process of converting user-oriented inputs into computer format. The goal of designing is to make data entry as easy, logic, free from error as possible. In the manual system, paper forms are used to collect information. Therefore, to have compatibility, the electronic form is designed to be like the original form for placing requests. The input design incorporates as much automation as possible. The entries that are to be made by the user are minimized. The inputs are validated. An important part in input design is the checking for incomplete forms. Blank fields do not cause wrong data but incomplete data is equally harmful as the bad data. Before the document is saved, it should be checked for blank details.

OUTPUT DESIGN

Computer outputs are most important and direct source of information to the user. They are encountered everywhere in everyones day-to-day life. The usefulness and clarity of such outputs depends on a great deal on the care with which an analyst designed them, keeping their major purpose in mind. Every kind of business produces some kind of report and many produce a lot. The screens for the display are designed in such a way that the outputs are providing to the user in an understandable form. The design of the output screens include that they are complete with all necessary information requested. The complete summary of the output is displayed depending on the inputs given by the user.

About Visual Basic 6.0

Visual Basic revolutionized the world of program development for Windows 98 & NT. What used to take ours using C in other languages, now takes minutes. A friendly and intuitive interface does not lessen the power of flexibility that Visual Basic offers through its extensive event-driven language, its object based structure, and it supports for OLE.

Every business enterprise maintains large volume of data for its operations. With more and more people accessing this data for their work the need to maintain its integrity and relevance increases. Normally, with the traditional methods of storing data and information in files the chances that the data loses, its integrity and validity are very high.

ADO (ActiveX Data Objects)

This new data access technology features a simpler object mode, better integration with other Microsoft and Non-Microsoft technologies, a common interface for both local and remote data access, remittable and disconnected record sets, a user accessible da binding ta interface and hierarchical record sets.

Data Environment The Data Environment designer provides an interactive, design time environment for creating ADO objects. These can be used as a data source for data aware objects on a form or 10

report, or accessed programmatically as methods and properties exposed off of the Data Environment object. The Data Environment designer supports all the functionality of Visual Basics User Connection designer as well as additional features, including drag and drop, hierarchies, grouping and aggregates.

ADO Data Control

A new OLEDB-aware data source control that functions much like the intrinsic Data and Remote Data controls in that it allows you to create a database application with minimum code.

Data Source Create user controls and classes that are data sources to which other controls can be bound.

Data View Window

We can use the Data View Window to browse all of the databases you are connected to and their tables, views, stored procedures etc.

Data Repeater Control Insert a user control into the Data Repeater to create a custom view of a database, similar to access forms. The user control can contain Text box, Check box, Data grid or other controls bound to data fields.

Data Form Wizard Enhancements

11

Now gives you the ability to build code-only forms where controls are not bound to a data control. It allows you to use ADO code. The wizard is integrated with the Application, Chart and Flex grid wizards.

Data Object Wizard

Automates creating middle-tier objects bound to the Data Environment or User Controls.

Visual Basic revolutionized the world of program development for Windows 98 & NT. What used to take ours using C in other languages, now takes minutes. A friendly and intuitive interface does not lessen the power of flexibility that Visual Basic offers through its extensive event-driven language, its object based structure, and it supports for OLE. Every business enterprise maintains large volume of data for its operations. With more and more people accessing this data for their work the need to maintain its integrity and relevance increases. Normally, with the traditional methods of storing data and information in files the chances that the data loses, its integrity and validity are very high. User Interface The Production Planning and Monitoring System is designed to operate as Graphical User Interface Software. It is extremely user friendly and has all menu driven commands and actions. The system has the advantage of online updating of orders,

materials, stocks and receipts. It gives the status of any pending order at any given point of time. This will immensely help the manufacturing unit to give feedback to their clients on the status of execution of the project.

This project is developed using advanced concepts. So, it is easy to get and post the information quickly.  This software is made up of GUI application.  There is no existing system.  The processing speed is faster. Code Efficiency

12

In Visual Basic user interfaces are easy to use and easy to learn. Visual Basic was selected as the front-end tool and Oracle was selected as the back-end tool. This is because  Visual Basic is user friendly.  Visual Basic is a Graphical User Interface (GUI).  Visual Basic supports Object Oriented Programing Structure (OOPS) concepts. One of the principal advantages of a Visual Basic is that programmer need not write code to display the required component. The list of available components is displayed. The programmer picks up the required component for this list. The component can be moved, resized and even deleted, if so required. There is no restriction in the number of controls that can be placed this way. Moreover, since the programmer is creating the user interface visually, he can align, move or size the components as required without having to resort to writing code. The interface components provided by the Visual Basic has some code built into them. For example, a button knows when it has been clicked upon. In the case of conventional programming tools, the programmer has to write code to determine the component that has been clicked and then execute the appropriate code.

Selection of Operating System The Operating System proposed for the development of PMMS is Windows 95 / 98. As Windows supports a wide range of database products and many user-friendly applications are run on this Operating System, it is preferred. As the project having Windows as the operating system can be operated upon a wide range of platforms, it is quite safe to use this Operating System.

What is Database Management System?

A DBMS is essentially a collection of interrelated data and a set of programs to access this data. This collection of data is called the Database. A Database System consists of two parts namely, Database Management System and Database Application.

Database Management System is the program that organizes and maintains the information whereas the Database Application is the program that lets us view,retrieve and updates information stored in the DBMS. 13

DBMS has to protect database against unintentional changes that could be caused by users and applications In case of multi-user system, it must be capable of notifying any database change to the other user.

Codds Rules

A database management system should obey the following twelve rules of Dr. E.F.Codd for it to be relational.

1. The Information Rule: Each and every piece of data should be represented as datavalue of a table.

2. The Guaranteed Access Rule: Every piece of data must be accessible by specifying the name of the table,column of the data and the primary key value of the row

3. The Systematic Treatment Of Null Values: Database System must support Null value to represent unknown or inapplicable information. It must be different from zero and spaces. NULL value must be independent of data type.

4. The Database Description Rule: The description of database objects stored in the database must also be stored logically as the data and should be accessible to the users with appropriate privileges. It is usually called as System catalog or data dictionary.

5. Comprehensive Data Sub Language Rule: The database system must have a language that supports the following

Data Definition 14

    

View Definition Data Manipulation Integrity Constraints Authorization Transaction Management Operations

6. View Updating Rule: All kinds of views that are theoretically updateable must also be updateable by the system.

7. The Insert and Update Rule: The database language must have a manipulation commands (insertion, updation, deletion) those will act on sets of rows instead of a single row.

8. Physical Data Independence Rule: Application programs must remain unimpaired when any changes are made in storage representation or access methods.

9. Logical Data Independence Rule: The changes / additions that are made with the database objects should not affect the programs that manipulate them.

10. Integrity Independence Rule:

Database system must have a capability to maintain the integrity constraints in the database and not in the application programs.

11. The Distribution Rule:

The system must be able to access or manipulate the data that is distributed in other systems. 15

12. The Non - Subversion Rule: The Non -subversion rule states the different levels of the language cannot subvert or bypass the integrity rules and constraints. To put it in simple words, if an RDBMS supports a lower level language then it should not bypass any integrity constraints defined in the higher level.

About Crystal Reports

Crystal Reports is designed to work with your database to help you analyze and interpret important information. Crystal Reports makes it easy to create simple reports, and, it also has the comprehensive tools you need to produce complex or specialized reports.

Crystal Reports is designed to produce the report you want from virtually any data source. Built-in report experts guide you step by step through building reports and completing common reporting tasks. Formulas, cross-tabs, subreports, and conditional formatting help make sense of data and uncover important relationships that might otherwise be hidden. Geographic maps and graphs communicate information visually when words and numbers are simply not enough.

The flexibility of Crystal Reports doesn't end with creating reports your reports can be published in a variety of formats including Microsoft Word and Excel, E-mail and even over the Web. Advanced Web reporting lets other members of your workgroup view and update shared reports inside their web browser. Application and web developers can save time and meet their users needs by integrating the report processing power of Crystal Reports into their database applications. Support for most popular development languages makes it easy to add reporting to any application.

Whether it's the web master in IT, the promotion manager in marketing, the database administrator in finance or the CEO, Crystal Reports is a powerful tool designed to help everyone analyze and interpret the information that's important to them.

MS-ACCESS 16

Microsoft Access is a relational database management system (DBMS). At the most basic level, a DBMS is a program that facilitates the storage and retrieval of structured information on a computers hard drive. Examples of well-know industrial-strength relational DBMS include,        Oracle Microsoft SQL Server IBM DB2 Informix

Well-know PC-based (desktop) relational DBMS include Microsoft Access Microsoft FoxPro Borland dBase Microsoft generally likes to incorporate as many features as possible into its products. For example, the Access package contains the following elements: Relational database system that supports two industry standard query languages: Structured Query Language (SQL) and Query by Example (QBE); 1. Introduction to Microsoft Access
y

The many faces of Access

a full-featured procedural programming language- essentially a subset of

Visual Basic,
y y

a simplified procedural macro language unique to Access; a rapid application development environment complete with visual form and

report development tools;

a sprinkling of objected-oriented extensions; and, Various wizards and builders to make development easier.

For new users, these multiple personalities can be a source of enormous frustration. The problem is that each personality is based on a different set of assumptions and a different view of computing. For instance,
y

the relational database personality expects you to view your application as sets

of data;
y

the procedural programming personality expects you to view your application

as commands to be executed sequentially;

17

The object-oriented personality expects you to view your application as

objects, which encapsulate state and behavior information. Microsoft makes no effort to provide an overall logical integration of these Personalities (indeed, it is unlikely that such integration is possible). Instead, it is up to you as a developer to pick and choose the best approach to implementing your application. Since there are often several vastly different ways to implement a particular feature in Access, recognizing the different personalities and exploiting the best features (and avoiding the pitfalls) of each are important skills for Access developers. The advantage of these multiple personalities is that it is possible to use Access to learn about an enormous range of information systems concepts without having to interact with a large number of single-personality tools, for example:
y y y

Oracle for relational databases PowerBuilder for rapid applications development, Small Talk for object-oriented programming.

Keep this advantage in mind as we switch back and forth between personalities and different computing paradigms.

18

3.2 DATABASE DESIGN

19

3.2 DATABASE DESIGN

A decade ago, database was unique to large corporations, which had deployed mainframes. Today it is recognized as a standard of Management Information System and is available for virtually to all operational users. These users have programs that handle their own data with no data integration or sharing or common data across applications. In a database environment, common data is available and used by several users. Instead of each program managing its own data across applications, data is shared with authorized users with the database software managing the data as an entity.

A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. The general objective is to make information access easy, quick, inexpensive and flexible for the user.

Database design minimizes the artificiality embedded in using separate files. The primary objectives are fast response time to inquire, more information at low cost, control of redundancy, clarity are ease of use data and program independence, accuracy and integrity of the system, fast recovery, privacy and security of information and availability of powerful end user language.

In database design, several views of data must be considered along with the persons who use them. In addition to data structuring where relationships are reflected between and within entities, we need to identify the application programs logical view of data within overall logical data structure.

The logical view is what the data look like regardless of how they are stored. The physical view is the data exists in physical storage. It deals with how data are stored, accessed or related to other data in storage. It shows four views of data - three logical and one physical. The logical views are the user view, the programmers view are the overall logical view.

20

TABLE STRUCTURE: TABLE NAME: CUSTOMER This table is used to store the details of the customer. The customer table Contains Customer ID, Customer Name, Address Details, Mobile Number, City, Country and Email Address.
S no. 1. 2. 3. 4. 5. 6. FIELD NAME CustID CustName cAddress cSex cMail-id cCity cCountry FIELD TYPE Number Text Text Text Text Text Text DESCRIPTION Customer ID Customer Name Customer Address Customer Sex Customer e-mail ID Customer City Customer Country

Validation: 1. CustID cannot be null. 2. CustName cannot be null. 3. Address for communication cannot be null. 4. Customer Sex cannot be null. 5. Mail-Id should be entered. 6. cCity cannot be null. 7. cCountry cannot be null.

TABLE NAME: UPDATE ORDER

S no. 1.

FIELD NAME

FIELD TYPE

DESCRIPTION

Item No Item Name NoOfItems

Number Text Number

Item Number Item Name NoOfItems

2. 3.

Validation: 1. ItemNo Cannot be null. 21

2. ItemName cannot be null. 3. NoOfItems cannot be null.

22

Feasibility Study: The feasibility study is usually carried out by a group of people who are familiar with the information system techniques, understand the part of the business or organization that will be involved or affected by the project and are skilled in system analysis and design process. People typically responsible for feasibility

assessment and experienced analysts or managers. There are many aspects in the feasibility study portion of the preliminary investigation. They are listed as under;

Technical Feasibility

A study of the function, performance and constraints that may affect the ability to achieve an acceptable system. This is concerned with specifying equipment and software that will successfully satisfy the user requirement.  The technical needs of the system may vary considerably, but might include  The facility to produce outputs in a given time.  Response time under certain conditions.  Ability to process a certain volume of transaction at a particular speed.  Facility to communicate data to a distant location. In examining technical feasibility, configuration of the system is given more importance than the actual make of the hardware. The configuration must give the complete picture about the system's requirements. At the feasibility stage, it is desirable that two or three different configurations will be pursued that satisfies the key technical requirements but which represent different levels of ambition and cost.

 This feasibility is usually carried out to find out whether  The necessary technology exists to do what is suggested.  The proposed equipment has the technical capacity to hold the data required to use the new system.

 The proposed system will provide adequate responses to inquire, regardless of the number of location of users.  The system can be expanded if developed.  There are technical guarantees of accuracy, reliability and security. Economical Feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. It is commonly known as cost benefit analysis. An evaluation of the development cost was weighed against the ultimate income or benefit derived from the developed system or product. If benefits outweigh costs, a decision is taken to design and implement the system. Otherwise, further justification or alternative in the proposed system will have to be made if it has to be approved. This is an ongoing effort that improves in accuracy at each phase of the system life cycle.

A system that can be developed technically and that will be used if installed must still be good investment for the organization. Financial benefits must equal the costs. Analysts during preliminary investigation to estimate raise the financial and economic questions.

 The cost of conducting a full systems investigation  The cost of hardware and software for the class of application being considered  The benefits in the form of reduced costs or fewer costly errors  The cost if nothing changes (the proposed system is not developed) Operational Feasibility

Proposed projects are beneficial only if they can be turned into information system that will meet organizations operating requirement. This feasibility test asks

if the system will work when it is developed and installed. It is mainly related to human organizational and political aspects. The points to be considered are,

 What changes must be brought with the system?  What organizational structures are disturbed?  What new skills will be required?  Do the existing staff members have these skills?  If not, can they be trained in due course of time?  Generally project will not be rejected simply because of poor operational feasibility, but such considerations are likely to critically affect the nature and scope of the eventual recommendations.  It also facilitated to find out whether,  There are sufficient supports for the project form management.  There are current business methods acceptable to the users.  The users were involved in the planning and development of the project.  The proposed system will cause any harm or procedure poorer results in any respect or area.

Alternatives

An evaluation of alternative approaches to the development of the system or product is studied. Among the most important information contained in the feasibility study is the cost-benefit analysis, which is the economic justification for a computerbased system project. Cost benefit analysis delineates costs for project development and weighs them against the tangible and intangible benefits of a system.

After having a thorough feasibility study, it was found that the product is feasible to be developed.

It is a determination of whether a proposed project will be acceptable to management. If management does not accept a project or gives a negligible support to it; the analyst will tend to view the project as a non-feasible one. With the active

involment of Finance Manager, Regional Office, the package was development, hence Management feasibility exists. Legal Feasibility Legal feasibility is the determination of any infringement, violation, or liability that could result from development of the system. Although in some instances the project might appear sound, on closer investigation it may be found to infringe on several legal areas.

Time feasibility Time feasibility is a determination of whether a proposed project can be implemented fully within a stipulated time frame. If a project takes too much time it is likely to be rejected. Alternatives

An evaluation of alternative approaches to the development of the system or product is studied. Among the most important information contained in the feasibility study is the cost-benefit analysis, which is the economic justification for a computerbased system project. Cost benefit analysis delineates costs for project development and weighs them against the tangible and intangible benefits of a system. After having a thorough feasibility study, it was found that the product is feasible to be developed.

Software Engineering Paradigm Normalization is one of the software engineering paradigms applied in simplifying the project. Normalization theory is built around the concept of normal forms. Normalization reduces redundancy. Redundancy is unnecessary repetition of data. Normalization theory is based on the fundamental notion of Functional Dependency.

There are four levels of Normalization.  FIRST NORMAL FORM  SECOND NORMAL FORM  THIRD NORMAL FORM  FOURTH NORMAL FORM First Normal Form

A relational schema R is in First Normal Form (1NF) if the domain of all attributes of R is atomic. A domain is atomic if elements of the domain are considered to be indivisible units.

Second Normal Form

A relational schema R is in Second Normal Form (2NF) if it is in 1NF and each attribute A in R must meet one of the following criteria.  It appears in a candidate key.  It is not partially dependent on a candidate key. Third Normal Form

A relational schema R is in the Third Normal Form (3NF) with respect to a set F of functional dependencies if it is in 2NF and there are no non-prime-attributes A in R for which A is transitively dependent on key for R.

Data Model

The data model consists of three interrelated pieces of information. They are data objects, the attributes that describe the data object and the relationships that connect the data objects to one another. A data object is a representation of almost any composite information that must be understood by software. Composite

information means something that has a number of different properties or attributes. For example, a dimension (incorporating height, width and depth) could be defined as a data object. One or more of the attributes must be defined as an identifier. That is, the identifier attribute becomes a Key when an instance of a data object is to be found. Data objects are connected to one another in a variety of different ways. For example, consider a person and a car as two data objects. In the phrase The person owns the Car, the relationship between the two data object is owns.

Types of Relationships

There are four types of relationships. They are

One-to-One (1 : 1) An occurrence or A can relate to one and only one occurrence of B, and an occurrence of B can relate to only one occurrence of A.

One-to-Many (1 : N) One occurrence of A can relate to one or many occurrence of B, but an occurrence of B can relate to only one occurrence of A

Many-to-One (N : 1) An occurrence of A can relate to only one occurrence of B, but an occurrence of B can relate to one or more occurrence of A.

Many-to-Many (N : N) An occurrence of A can relate to one or more occurrences of B and an occurrence of B can relate to one or more occurrences of A.

3.3 DATA FLOW DIAGRAM

3.3 DATAFLOW DIAGRAM: Data flow Diagram (DFD) is the way of expressing system requirement in graphical form. A Data Flow Diagram is also known as Bubble Chart has the purpose of clarifying system requirement and identifying major transformation that will become programs in system design. It is the starting form of design phase that functionally decomposes the requirement specification down to the lowest level of details.

In a Data Flow Diagram, there are four symbols:

A Square defines the source or destination of system data. An arrow identifies data flow. A circle represents a process that incoming data flow into Outgoing data flow. An open Rectangle is a data store.

Level 0

CUSTOMER
PRODUCTION MANAGAMENT SYSTEM

ADMIN

Level 1

User Name
PRODUCTION MANAGAMENT SYSTEM

MAIN MENU

Pass Word

LEVEL 1.1

CUSTOMER

MAIN MENU

PRODUCTION MANAGAMENT SYSTEM

ADMIN

LEVEL 1.2:

CUSTOMER

PRODUCTION MANAGAMENT SYSTEM

REGISTER CUSTOMER DETAILS

ORDER ITEM

LEVEL 1.3:

CUSTOMER DETAILS

ADMIN

PRODUCTION MANAGAMENT SYSTEM

UPDATE ORDER

UPDATE ITEM

System Design - ER Diagram

The overall logical structure of a database can be expressed graphically by a entity Relationship diagram. A diagram consists of the following components Rectangle - which represents entity sets Elipse - which represent attributes Diamonds which represent relationship sets Lines -which link attributes to entity sets and entity sets to relationship sets

4. IMPLEMENTATION

4.1 SYSTEM REQUIREMENT

HARDWARE REQUIREMENT

CPU RAM HARDDISK

PENTIUM III 128 MB 20 GB

FLOPPY DISK MONITOR KEYBOARD

1.44 MB SAMSUNG COLOR MONITOR 106 STANDARDS

SOFTWARE REQUIREMENT

OPERATING SYSTEM BACKEND FRONTEND

WINDOWS 98 ORACLE 8.0 VISUAL BASIC 6.0

4.2 SOURCE CODE

LOGIN FORM: Dim dtmTest As Date Private Sub Command1_Click() If Text1.Text = "" Then

MsgBox "Login ID cannot be empty" Text1.SetFocus Else If Text2.Text = "" Then MsgBox "Password cannot be empty" Text2.SetFocus Else If Text1.Text <> "customer" And Text1.Text <> "admin" Then MsgBox "Login ID is wrong" Text1.SetFocus Else If Text2.Text <> "password" Then MsgBox "Password is wrong" Text2.SetFocus End If End If If Text1.Text = "admin" And Text2.Text = "password" Then luser = "admin" Form7.Show End If If Text1.Text = "customer" And Text2.Text = "password" Then luser = "customer" Form7.Show End If End If End If End Sub

Private Sub Command2_Click() End End Sub

Private Sub Form_Load() Me.WindowState = 2 End Sub

Private Sub Timer1_Timer() Label4.Caption = TimeValue(Now) Label5.Caption = DateValue(Now) If Label3.Left > -1320 Then Label3.Left = Label3.Left - 100 ElseIf Label3.Left <= -1320 Then Label3.Left = 14500 End If End Sub

MAIN MENU: Private Sub Form_Load() Me.WindowState = 2 If luser = "customer" Then mnuAdmin.Enabled = False End If End Sub

Private Sub mnuCustDetails_Click() Form3.Show End Sub

Private Sub mnuExit_Click() End End Sub

Private Sub mnuExit1_Click() End

End Sub

Private Sub mnuNewItem_Click() Form4.Show End Sub

Private Sub mnuOrderItem_Click() Form5.Show End Sub

Private Sub mnuRegCust_Click() Form2.Show End Sub

Private Sub mnuUpdateItem_Click() Form6.Show End Sub

Private Sub munNewItem_Click() Form4.Show End Sub

CUSTOMER FORM: Dim con_cust As Connection Dim com_cust As Command Dim rstCust As Recordset Private Sub Command1_Click() Text1.Text = "" Text2.Text = ""

Text3.Text = "" Text4.Text = "" Text5.Text = "" Option1.Value = False Option2.Value = False End Sub

Private Sub Command2_Click() Dim sex As String If Text1.Text = "" Then MsgBox "Customer ID cannot be empty!!" Text1.SetFocus Else If Text2.Text = "" Then MsgBox "Customer Name cannot be empty!!" Text2.SetFocus Else If Text3.Text = "" Then MsgBox "Please enter the Address" Text3.SetFocus Else If Text4.Text = "" Then MsgBox "Please enter the City" Text4.SetFocus Else If Text5.Text = "" Then MsgBox "Please enter the Country" Text5.SetFocus Else rstCust.AddNew rstCust!CustId = Text1.Text rstCust!CustName = Text2.Text

If Option1.Value = True Then rstCust!cSex = "Male" Else If Option2.Value = True Then rstCust!cSex = "Female" End If End If rstCust!cAddress = Text3.Text rstCust!cCity = Text4.Text rstCust!cCountry = Text5.Text rstCust.Update MsgBox "Customer details are saved!" End If End If End If End If End If

End Sub

Private Sub Command3_Click() Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" Option1.Value = False Option2.Value = False End Sub

Private Sub Command4_Click() Unload Me

End Sub

Private Sub Form_Load() Me.WindowState = 2 Option1.Value = False Option2.Value = False Set con_cust = New Connection Set com_cust = New Command Set rstCust = New Recordset rstCust.CursorLocation = adUseServer rstCust.LockType = adLockOptimistic rstCust.CursorType = adOpenDynamic con_cust.Provider = "Microsoft.Jet.OLEDB.4.0" con_cust.ConnectionString = "User ID = Admin;Password=;" & "Data Source=D:\Source\ProdDb.mdb;" con_cust.Open com_cust.ActiveConnection = con_cust rstCust.Open "select * from customer", con_cust

End Sub

ORDER ITEM: Dim con_orderitem As Connection Dim com_orderitem As Command Dim rstOrderitem As Recordset Private Sub Command1_Click() Dim a As String a = List1.Text

rstOrderitem.MoveFirst Do While Not rstOrderitem.EOF If a = rstOrderitem!itemName Then If Val(Text1.Text) > rstOrderitem!noOfItems Then MsgBox "Required number of items not exist" Else rstOrderitem!noOfItems = rstOrderitem!noOfItems - Val(Text1.Text) MsgBox "Item Purchased! Your item will be delivered soon!" End If End If rstOrderitem.MoveNext Loop End Sub

Private Sub Command2_Click() Unload Me End Sub

Private Sub Form_Load() Me.WindowState = 2 Set con_orderitem = New Connection Set com_orderitem = New Command Set rstOrderitem = New Recordset rstOrderitem.CursorLocation = adUseServer rstOrderitem.LockType = adLockOptimistic rstOrderitem.CursorType = adOpenDynamic con_orderitem.Provider = "Microsoft.Jet.OLEDB.4.0" con_orderitem.ConnectionString = "User ID = Admin;Password=;" & "Data Source=D:\Source\ProdDb.mdb;" con_orderitem.Open com_orderitem.ActiveConnection = con_orderitem rstOrderitem.Open "select * from cOrder", con_orderitem

Do While Not rstOrderitem.EOF List1.AddItem rstOrderitem!itemName rstOrderitem.MoveNext Loop End Sub

CUSTOMER DETAILS:

Dim con_cust_d As Connection Dim com_cust_d As Command Dim rstCust_d As Recordset Private Sub Command1_Click() Unload Me End Sub

Private Sub Form_Load() Me.WindowState = 2 Option1.Value = False Option2.Value = False Text1.Enabled = False Text2.Enabled = False Text3.Enabled = False Text4.Enabled = False Option1.Enabled = False Option2.Enabled = False Set con_cust_d = New Connection Set com_cust_d = New Command Set rstCust_d = New Recordset

rstCust_d.CursorLocation = adUseServer rstCust_d.LockType = adLockOptimistic rstCust_d.CursorType = adOpenDynamic con_cust_d.Provider = "Microsoft.Jet.OLEDB.4.0" con_cust_d.ConnectionString = "User ID = Admin;Password=;" & "Data Source=D:\Source\ProdDb.mdb;" con_cust_d.Open com_cust_d.ActiveConnection = con_cust_d rstCust_d.Open "select * from customer", con_cust_d Do While Not rstCust_d.EOF List1.AddItem rstCust_d!CustId rstCust_d.MoveNext Loop End Sub Private Sub List1_Click() Dim a As String a = List1.Text rstCust_d.MoveFirst Do While Not rstCust_d.EOF If a = rstCust_d!CustId Then Text1.Text = rstCust_d!CustName If rstCust_d!cSex = "Male" Then Option1.Value = True Else Option2.Value = True End If Text2.Text = rstCust_d!cAddress Text3.Text = rstCust_d!cCity Text4.Text = rstCust_d!cCountry End If rstCust_d.MoveNext Loop

End Sub

UPDATE ORDER:

Dim con_order As Connection Dim com_order As Command Dim rstOrder As Recordset Private Sub Command1_Click() If Text1.Text = "" Then MsgBox "Item No cannot be empty" Text1.SetFocus Else If Text2.Text = "" Then MsgBox "Item Name cannot be empty" Text2.SetFocus Else If Text3.Text = "" Then MsgBox "No of Item value cannot be empty" Text3.SetFocus Else rstOrder.AddNew rstOrder!itemNo = Text1.Text rstOrder!itemName = Text2.Text rstOrder!noOfItems = Text3.Text rstOrder.Update MsgBox "Item Details are saved !" End If End If End If End Sub

Private Sub Command2_Click() Unload Me End Sub

Private Sub Form_Load() Me.WindowState = 2 Set con_order = New Connection Set com_order = New Command Set rstOrder = New Recordset rstOrder.CursorLocation = adUseServer rstOrder.LockType = adLockOptimistic rstOrder.CursorType = adOpenDynamic con_order.Provider = "Microsoft.Jet.OLEDB.4.0" con_order.ConnectionString = "User ID = Admin;Password=;" & "Data Source=D:\Source\ProdDb.mdb;" con_order.Open com_order.ActiveConnection = con_order rstOrder.Open "select * from cOrder", con_order End Sub

UPDATE ITEM:

Dim con_uorderitem As Connection Dim com_uorderitem As Command Dim rstuOrderitem As Recordset Private Sub Command1_Click() Dim a As String a = List1.Text rstuOrderitem.MoveFirst Do While Not rstuOrderitem.EOF

If a = rstuOrderitem!itemName Then rstuOrderitem!noOfItems = rstuOrderitem!noOfItems + Text2.Text MsgBox "Item detail is updated" End If rstuOrderitem.MoveNext Loop End Sub

Private Sub Command2_Click() Unload Me End Sub

Private Sub Form_Load() Me.WindowState = 2 Text1.Enabled = False Set con_uorderitem = New Connection Set com_uorderitem = New Command Set rstuOrderitem = New Recordset rstuOrderitem.CursorLocation = adUseServer rstuOrderitem.LockType = adLockOptimistic rstuOrderitem.CursorType = adOpenDynamic con_uorderitem.Provider = "Microsoft.Jet.OLEDB.4.0" con_uorderitem.ConnectionString = "User ID = Admin;Password=;" & "Data Source=D:\Source\ProdDb.mdb;" con_uorderitem.Open com_uorderitem.ActiveConnection = con_uorderitem rstuOrderitem.Open "select * from cOrder", con_uorderitem Do While Not rstuOrderitem.EOF List1.AddItem rstuOrderitem!itemName rstuOrderitem.MoveNext Loop End Sub

Private Sub List1_Click() Dim a As String a = List1.Text rstuOrderitem.MoveFirst Do While Not rstuOrderitem.EOF If a = rstuOrderitem!itemName Then Text1.Text = rstuOrderitem!itemNo End If rstuOrderitem.MoveNext Loop End Sub

Code Efficiency

In Visual Basic user interfaces are easy to use and easy to learn. Visual Basic was selected as the front-end tool and Oracle was selected as the back-end tool. This is because,

 Visual Basic is user friendly.  Visual Basic is a Graphical User Interface (GUI).  Visual Basic supports Object Oriented Programming Structure (OOPS) concepts.

One of the principal advantages of a Visual Basic is that programmer need not write code to display the required component. The list of available components are displayed. The programmer picks up the required component for this list. The component can be moved, resized and even deleted, if so required. restriction in the number of controls that can be placed this way. There is no

Moreover, since the programmer is creating the user interface visually, he can align, move or size the components as required without having to resort to writing

code. The interface components provided by the Visual Basic has some code built into them. For example, a button knows when it has been clicked upon. In the case of conventional programming tools, the programmer has to write code to determine the component that has been clicked and then execute the appropriate code.

5. CONCLUSION

5. CONCLUSION
Future Scope of the Project

The PPC is a Graphics User Interface Software User Friendly On Line Monitoring of each order status

Knowing the Process details for each product Analyzing Pending Orders Monitoring the Product movements Working Cost Analyzing for Executing each order

BIBLIOGRAPHY

Bibliography

 Visual Basic 6.0 by Steve Brown  Visual Basic 6.0 Programming Bible by Eric A.Smith,Valor Whisler, Hank Marquis

 Visual Basic 6.0 Programming Secrets by Harold Davis

 Visual Basic 5.0 Developer's Handbook by Evangelos Pertroutsos, Kevin Hough

 Visual Basic 6.0 by Cary Cornell  Visual Basic 6 by Peter Norton  VB6(Doing Objects in VB6.0) by Deborah Kurata  Software Engineering by Roger S. Pressman

ANNEXTURE

(a)SCREEN SHOTS

Common Entry Screen Formats For All Modules

Keeping in mind the users who are novices at their work, the screen formats have been designed in such a way that almost all the entry screen of the Masters Menu are kept in a similar fashion to the utmost possible way. The command buttons of Add, Delete, Edit, Save and Exit enable the users to easily navigate between and update records without much difficulty.

LOGIN FORM: The user can log into the system using the username and the password allotted to him by the system administrator, for better control of the resources of the system

MAIN MENU FOR CUSTOMER:

Once the user is authenticated, the main splash screen of PRODUCTION MANAGEMENT SYSTEM of the company is presented along with the menu bar displaying the various functionalities and transaction details of the Production Monitoring System.

CUSTOMER FORM: From the main screen on clicking the Register Customer Details command on the Customer Master Menu Command we are taken to this particular screen where the information regarding customers are updated and added. The address and other contact details of the customers are shown explicitly enabling the user to enter and read the details without much difficulty.

ORDER ITEM: From the main screen on clicking the Order Item command on the customer Master Menu Command we are taken to this particular screen where the information is ordered regarding products that are used for the production.

MAIN MENU FOR ADMINISTRATOR:

CUSTOMER DETAILS: From the main screen on clicking the display customer details command on the Master Menu Admin Command we are taken to this particular screen where the information regarding customer of the company is displayed.

UPDATE ORDER: From the main screen on clicking the Add new item command on the Master Menu Command we are taken to this particular screen where the information regarding Products of the company is updated and added.

UPDATE EXISTING ITEM: From the main screen on clicking the Update existing item command on the Master Admin Menu Command we are taken to this particular screen where the information regarding the existing Products of the company is updated and added.

(b)Reports

CUSTOMER DETAILS REPORT:

ORDER ITEM REPORT: