+ All Categories
Home > Documents > Product Master Maintenance System

Product Master Maintenance System

Date post: 24-Jan-2016
Upload: brinda
View: 8 times
Download: 0 times
Share this document with a friend
Popular Tags:
of 68 /68
1. INTRODUCTION 1.1 Product Master Maintenance System –An Overview: The Product Master Maintenance System is an Organization based application program designed for effective functioning of the web based maintenance system of products produced in a manufacturing industry. It is a client server based application that can be accessed by a selected group of sub dealers. This system can be used for maintaining all the details related to a product like Product hierarchy, product/sub-components attributes (cost/size/weight etc.) and details of the authorized sub-dealers available. This System developed should have purchase, sales and stock details that are maintained for an organization in a web based system. The products that are to be purchased and to be sold to the sub-dealers are maintained here. Deriving the details from Purchase product details and Sales product details and maintenance of the stock for product. It also involves the faults in the purchased product and the products that are to be replaced also been given. Stock entry forms are used to update the databases. The sale form can be used to view the sales details. The company return form can be used to show the details of defective products. Item details can be used to show the current status of the stock. 1.2 Objectives of the Project
Page 1: Product Master Maintenance System


1.1 Product Master Maintenance System –An Overview:

The Product Master Maintenance System is an Organization based application program

designed for effective functioning of the web based maintenance system of products produced in

a manufacturing industry. It is a client server based application that can be accessed by a selected

group of sub dealers. This system can be used for maintaining all the details related to a product

like Product hierarchy, product/sub-components attributes (cost/size/weight etc.) and details of

the authorized sub-dealers available.

This System developed should have purchase, sales and stock details that are maintained

for an organization in a web based system. The products that are to be purchased and to be sold

to the sub-dealers are maintained here. Deriving the details from Purchase product details and

Sales product details and maintenance of the stock for product. It also involves the faults in the

purchased product and the products that are to be replaced also been given. Stock entry forms are

used to update the databases. The sale form can be used to view the sales details. The company

return form can be used to show the details of defective products. Item details can be used to

show the current status of the stock.

1.2 Objectives of the Project

The objective of the project is to design and develop a new strategy for Product Master

Maintenance System of an organization. The system is used to store and retrieve the products

and update the products, view the sales details, status of the stock, and hot products available,

etc... The system has user-friendly layout of screens making it very simple to use. It is a

completely web-based system that can be run on companies Internet. It can be made available on

an organization allowing authorized sub dealers to access the system. This project helps dealer to

analyze the products that been utilized and not utilized by the sub dealers.

Page 2: Product Master Maintenance System



The existing system is developed in Visual Basic as front end and oracle 8i as back end.

This system fails in accuracy, efficiency and it is really a tedious task to maintain properly. At

present managing expense is really complicated in the organization. A great deal of effort is

required for maintaining up-to-date information of task assigning and effort capturing. The

system fails in security as the user process vary with their work.

Selected problems

No way to view the status of the stock.

System cannot upload and download.

System does not have mail process.

Navigation menus are not properly designed.

User interactive area is tedious

Inconvenient, cumbersome and it is time consuming process.

Redundancy is high and less efficient.

Not secure and reliable

More man power is needed and Chance of data loss is more

Page 3: Product Master Maintenance System


System Analysis is a management technique, which helps in designing a new system or

improving an existing system. System Analysis is the process of gathering and interpreting facts,

diagnosing problems, using information to recommend improvements to the system. There are

four basic elements of system analysis-Output, Input, Files, processes. For computerization of

any system, the existing system must be thoroughly being understood to determine “how the

computer can be best used to make its operation most effective”.


The proposed system rectifies most of the problem in the present system. The most

important aspect of the new system is that flexible to incorporate changes. Data validation is

done during data entry itself so that the errors are minimized. To upgrade the process we

included some features in the proposed system. We provide the separate login for every user.

User can access anywhere inside the organization. In this system we are capturing the required

designs of the employees. The status of every process can be shown in this system. The existing

system is not convenient for the user. If the system crashes the data will be loss.


Software solution is an IT solution provider for a dynamic environment where business

and technology strategies converge. Their approach focuses on new ways of business combining

IT innovation and adoption while also leveraging an organization and new products or service

and to implement prudent business and technology strategies in today’s environment. The

benefits of the proposed system are,

The data is more secure.

The user can access the webpage from anywhere

It is an integrated system so that the data can be shared and updated easily.

This application avoids the burden in deploying in each client machines.

It is a platform independent. Support and maintenance of the system is easier

Page 4: Product Master Maintenance System


The transactions related to products In, products Out and returns are maintained manually

at present along with maintaining details of the customers and the suppliers. All these are to be

automated as web based system and an application is required to relate all of them relatively and

logically so that the current system can be replaced and accepted without major changes and


The application should provide quick access to the records maintained and must reveal

the important reviews about the business so that the growth can be easily compared and should

provide with the various reports showing the related details so that the important decisions could

be taken easily.


The feasibility of the project is analyzed in analysis phase and business proposal is put

forth with a very general plan for the project and some cost estimates. During system analysis the

feasibility study of the proposed system is to be carried out. This is to ensure that the proposed

system is not a burden to the company. For feasibility analysis, some understanding of the major

requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

Economical feasibility

Technical feasibility

Social feasibility


This study is carried out to check the economic impact that the system will have on the

organization. The amount of fund that the company can pour into the research and development

of the system is limited. The expenditures must be justified. Thus the developed system as well

within the budget and this was achieved because most of the technologies used are freely

available. Only the customized products had to be purchased.

Page 5: Product Master Maintenance System


This study is carried out to check the technical feasibility, that is, the technical

requirements of the system. Any system developed must not have a high demand on the available

technical resources. This will lead to high demands on the available technical resources. This

will lead to high demands being placed on the client. The developed system must have a modest

requirement, as only minimal or null changes are required for implementing this system.


The aspect of study is to check the level of acceptance of the system by the user. This

includes the process of training the user to use the system efficiently. The user must not feel

threatened by the system, instead must accept it as a necessity.

The level of acceptance by the users solely depends on the methods that are employed to

educate the user about the system and to make him familiar with it. His level of confidence must

be raised so that he is also able to make some constructive criticism, which is welcomed, as he is

the final user of the system.


Top-down and bottom-up are strategies of information processing and knowledge

ordering, mostly involving software, but also other humanistic and scientific theories (see

systemic). In practice, they can be seen as a style of thinking and teaching. In many cases top-

down is used as a synonym of analysis or decomposition, and bottom-up of synthesis. The

Product Management System incorporates the following aspects.

Product Details



Product Details:

In this module it has the information of the Products, its features like size, color,

compatibility, etc.. and it will be stored in to the database.

Page 6: Product Master Maintenance System

Order Product:

This module is used to make orders by viewing the product details and to know the

products been utilized and which are not utilized.


Reports are viewed whenever the sub dealer wants to know the information. Reports need

to be created with good care. Reports are generated from the Product list, Authorizer list, login

list, order list.



Three Tier Architecture

Three-tier architecture introduces a server (or an "agent") between the client and the

server. The role of the agent is manifold. It can provide translation services (as in adapting a

legacy application on a mainframe to a client/server environment), metering services (as in

acting as a transaction monitor to limit the number of simultaneous requests to a given server), or

intelligent agent services as in mapping a request to a number of different servers, collating the

results, and returning a single response to the client.

Employee Performance Management uses the 3-tier application is a program, which is

organized into three major disjunctive layers. These layers are,

Presentation layer (Front end)

Business layer (Logical)

Data layer (Backend)

Page 7: Product Master Maintenance System

Three Tier Architecture

Application layer

Application layer is the form which provides the user interface to either programmer of

end user. Programmer uses this layer for designing purpose and to get or set the data back and


Business layer

This layer is a class which we use to write the function which works as a mediator to

transfer the data from Application or presentation layer or data layer. In the three tier architecture

we never let the data access layer to interact with the presentation layer.

Data Access Layer

This layer is also a class which we use to get or set the data to the database back and

forth. This layer only interacts with the database. We write the database queries or use stored

procedures to access the data from the database or to perform any operation to the database.


The development and availability of Internet technology has resulted in an upsurge of

Intranets within these Organizations. It is now relatively easy for someone with an understanding

of the technology and XML to create web pages, and implement a server to host them. As their

Page 8: Product Master Maintenance System

experience increases they may also become able to produce graphics to enhance the site, and

more complicated and functional navigation.

2.2.3 Hardware specification

Processor : Pentium-III

Main Memory : 2 GB

Hard Disk : 20 GB

2.2.4 Software Environment

Front End : ASP.NET

Operating System : Windows-XP

Back End : MySQL

Introduction to Frame Work

A software framework, in computer programming, is an abstraction in which common

code providing generic functionality can be selectively overridden or specialized by user code

providing specific functionality. Frameworks are a special case of software libraries in that they

are reusable abstractions of code wrapped in a well-defined API, yet they contain some key

distinguishing features that separate them from normal libraries.

Introduction to .Net framework

Visual studio .Net is a complete set of development tools for building ASP Web

applications, XML Web services, desktop applications and mobile applications. Visual

Basic .Net, Visual C++ .Net, and visual c# .Net all use the same integrated development

environment (IDE) which allows them to share tools and facilities in the creation of mixed-

language solutions.


ASP.NET is an object-oriented computer language that can be viewed as an evolution of

Microsoft’s Visual Basic (VB) implemented on the Microsoft .net framework. Its introduction

Page 9: Product Master Maintenance System

has been controversial, as significant changes were made that broke backward compatibility with

older versions and caused a rift within developer community.

The great majority of ASP.NET developers use Visual Studio .Net as their integrated

development environment (IDE).Sharp Develop provides an open-source alternative Idealize

all .NET languages, programs written in ASP.NET require the .NET Framework to execute.

Whether ASP.NET should be considered as just another version of Visual Basic or a

completely different language is a topic of debate. This is not obvious, as once the methods that

have been moved around and which can be automatically converted are accounted for, the basic

syntax of the language has not seen many “breaking” changes, just additions to support new

features like structured exception handling and short circuited expressions. One simple change

that can be confusing to previous users is that of integer and long data types, which have each

doubled in length; a 16-bit integer is known as a short in VB.NET, While Integer and Long are

32 and 64 bits respectively. Similarly, the Windows Forms GUI editor is very similar in style and

function to the Visual Basic form editor.


MySQL is a relational database system. If you can believe many diehard MySQL fans,

MySQL is faster, more reliable, and cheaper -- or, simply put, better -- than any other database

system (including commercial systems such as Oracle and DB2). Many MySQL opponents

continue to challenge this viewpoint, going even so far as to assert that MySQL is not even a

relational database system.

Features of MySQL

The following list shows the most important properties of MySQL. This section is

directed to the reader who already has some knowledge of relational databases. We will use

some terminology from the relational database world without defining our terms exactly. On the

other hand, the explanations should make it possible for database novices to understand to some

extent what we are talking about.

Client/Server Architecture

MySQL is a client/server system. There is a database server and arbitrarily many clients

who communicate with the server; that is, they query data, save changes, etc. The clients can run

Page 10: Product Master Maintenance System

on the same computer as the server or on another computer (communication via a local network

or the Internet).

SQL compatibility

MySQL supports as its database language -- as its name suggests – SQL (Structured

Query Language). SQL is a standardized language for querying and updating data and for the

administration of a database. There are several SQL dialects (about as many as there are database

systems). MySQL adheres to the current SQL standard (at the moment SQL:2003), although

with significant restrictions and a large number of extensions.

Platform independence

It is not only client applications that run under a variety of operating systems; MySQL

itself (that is, the server) can be executed under a number of operating systems. The most

important are Apple Macintosh OS X, Linux, Microsoft Windows, and the countless Unix

variants, such as AIX, BSDI, FreeBSD, HP-UX, OpenBSD, Net BSD, SGI Iris, and Sun Solaris.

Page 11: Product Master Maintenance System


Software cost is related to many variables such as Human, Technical, Environment and

Effort applied to develop it. The estimates of cost depend, on our ability to estimate and evaluate

several factors, given below.

Number of user inputs

Number of user output

Experience and ability of the project personnel

The quality of software development environment

The degree to which software components can be reused

Man Day = 120.0 Function Points / 2.0 = 60days

Man Hours = 60 * 2 = 120 hr

Let us see how to compute the man power estimation and the cost estimation of the

project “Product Master Maintenance system” is. The computation is described briefly below.

Man Power Estimation

Phase Time Taken

User Requirement Specification 10

Project Planning 10

System Requirement Specification 10

Architectural Design Document 20

Detailed Design Document 10

Coding 30

Testing 5

Page 12: Product Master Maintenance System

Total 120

Cost Estimation

Cost for 1 Hour = 200.00 Indian Rupees (Rs)

Total Cost = 120 Hrs * 200.00

Cost = 24,000 Rupees

2.4 Final Outline of the Proposed System

The proposed system overcomes all the drawbacks of the existing system. A system study

help to analyze the present system in its full dimension, it recommends the need for a new

system, at it put handle the inefficiencies of a present system. The proposed system can be easy

to view, easy to modify, easy to see the process of each stage.

The Master purchase, sales and stock will be maintained. The stock details of dealers

which includes the amount of stock available, the stock is to be purchased, the date or the time it

is being bought or delivered, the amount, Sales details of master to sub-dealers (i.e.) How much

products has been sold to sub-dealers, total amount and what are products yet to sold, master

purchase details are maintained in this project. The whole economic status is being improved

properly if stock, sales and purchase details are maintained.

Some of the significant accrued benefits include,

Better data and reports help in taking a better decision.

Dealers can use the tool in efficient manner.

Have consistency across the whole organization.

Better quality feedback leads to better performance is achieved.

Page 13: Product Master Maintenance System


3.1 Fundamental design concepts

Although the degree of interest in each concept has varied over the year, each has

stood the test of time. Each provides the software designer with a foundation from which more

sophisticated design methods can be applied. Fundamental design concepts provide the necessary

framework for “getting it right”.

A software design is a meaningful engineering representation of some Software

product that is to be built. A design can be traced to the customer’s requirements and can be

assessed for quality against predefined criteria.

During the design process the software requirements model is transformed into

design models that describe the details of the data structures, system architecture, interface, and

components. Each design product is reviewed for quality before moving to the next phase of

software development.

3.2 Design Notations

3.2.1 Data flow diagram

Analysis model help us to understand the relationship between different

components in the system design. Analysis model shows user more clearly, how a system will

function. This is the first technical representation of a system. The analysis is modeling must

achieve three primary objectives.

To establish a basis for creation of software design.

To describe what the user requires.

To define a set of requirement that can be validated once the software is built Data

Flow Diagram.

Page 14: Product Master Maintenance System

A Data Flow Diagram is a graphical technique that depicts information flow and

transforms that are applied as data move from input to output. The DFD is used to represent

increasing information flow and functional details. A level 0 DFD, also called a fundamental

system model or a Context Model, represents the entire software elements as a bubble with input

and output indicated by incoming and outgoing arrows respectively. Additional process and

information flow parts are represented in the next level i.e., Level 1 DFD. Each of the processes

represented at Level 1 are sub functions of overall system depicted in the Context Model. Any

processes, which are complex in Level 1, will be further represented into sub functions in the

next Level, i.e., in level 2.

Basic DFD symbols:

To Construct a Data Flow Diagram, we use



Open End Box



An arrow identifies the data flow in motion. It is a pipeline through which information is

flown like the rectangle in the Flow Chart.

Data may flow a source to a processor and from a data store or process. An arrow line depicts the

flow, with the arrowhead pointing in the direction of flow.


Circle stands for process that converts the data into information

A process represents transformation where incoming data flow is changed into outgoing flows.


Page 15: Product Master Maintenance System

A Rectangle defines a source or destination of system data. A source is a person or a part of

organization, which enters or receives information from the system but is considered to be

outside the context of the data flow model.

Open End Box

An Open End Box represents a data store, data at rest or temporary reposition of data.

A graphical picture of the logical steps and sequence involved in a procedure or a program is

called a flow chart. Unlike detailed flow chart, Data Flow Diagram does not supply detailed

description of the modules but graphically describes a system’s data how the data interact with

the system.

Six rules for considering the Data flow Diagram

Arrows should not cross each other

Squares, circles and Data Store must have names

Decomposed data flow squares and circles can have the same names.

Choose meaningful names for data flow

Draw all data flows around the outside of the diagram.

Page 16: Product Master Maintenance System

Level 0 DFD:


Receive AcknowledgementReceive Return Product

Order GoodsSend Goods

Receive goodsAccept Order

Product Master Maintenance



Sales Product



Send Invoice

Receive Payment Receive Invoice


Send Acknowledgement Return Product

Page 17: Product Master Maintenance System

Level 1 DFD:

Sales Product

Product Details

Valid sub-dealer

Product Details

Login DataLogin Process

Purchase Product Details

Sub-Dealer Data

Sub-Dealer Sub-Dealer/DealerRegiste


Valid Admin

Orders product

Sales Details

Product Store Order



Invalid Order

Make Order

Sales Order Details


Product Details

Verify Shipping


Order Details


Page 18: Product Master Maintenance System


Level 2 DFD:

Sub-DealerShipment Order

View Sales Details

Return Product

Sub-Dealer Data

Product Details

Valid sub-dealer

Purchase Product Details


Valid Admin

Sales Details

Product Store Order

Invalid Order

Make Order

Sales Order Details




Login DataLogin Process


Return Product Details

Return Product

Product Details

View Order

Return Product

Receive Acknowledgement

Accept Acknowledgement

Send Acknowledgement

Accept Return Product

Receive Return Product

Store Order

Return Product


Page 19: Product Master Maintenance System


3.2.2. Structure Chart

A structure chart is a design tool, constructed of squares representing the different

modules in the system, and lines that connect them. The lines represent the connection and or

ownership between activities and sub activities as they are used in organization charts.

Programmers use a structure chart to build a program in a manner similar to how an architect

uses a blueprint to build a house. In the design stage, the chart is drawn and used as a way for the

client and the various software designers to communicate.

Structure Chart is used to show the hierarchical arrangement of the modules in a Product

Management System. Each rectangular box in the structure chart represents a form and module.

The names of the forms are written inside the box. An arrow joins two forms that have an

invocation relationship.

A structure chart depicts

the size and complexity of the system, and

number of readily identifiable functions and modules within each function and

whether each identifiable function is a manageable entity or should be broken

down into smaller components

The module and forms in the Product Master Maintenance System represents in the

below structure chart.

Page 20: Product Master Maintenance System






















Page 21: Product Master Maintenance System


The relation upon the system is structure through a conceptual ER-Diagram, which not only

specifics the existential entities but also the standard relations through which the system exists

and the cardinalities that are necessary for the system state to continue.

The entity Relationship Diagram (ERD) depicts the relationship between the data objects.

The ERD is the notation that is used to conduct the date modeling activity the attributes of each

data object noted is the ERD can be described resign a data object descriptions. The set of

primary components that are identified by the ERD are

Data object



Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

Page 22: Product Master Maintenance System














Pname Nop
















Tax Tot

Make Paymen





StorePurchase Return


Page 23: Product Master Maintenance System

3.3 Design process

The design phase focuses on the detailed implementations of the system recommended in

the feasibility study. Emphasis is on translating performance specification into design

specification. The design phase is a translation from user-oriented document to a document to a

document oriented to the programmers or database personnel.

3.3.1 Data Structure Design

To design an application it is necessary to design a database file. These files are called

tables. After designing the output and input, tables must be organized according to the storage

needs of the back end used.

Normalization procedure is used to avoid duplication of data and to produce feasibility

necessary to support different functional requirements. In this project some fields are assigned as

primary key. The repeating data are removed and are placed in the corresponding entity. In the

master table primary key is assigned and this is referenced by the same field in the transaction

table which is assigned there as foreign key. Every non key attribute in this system are non-

transitively dependent on primary key. The records are retrieved by selecting the primary key.


It is a technique for designing relational database tables to minimize duplication of


The goals of normalization are,

Eliminating redundant data

Ensuring data dependencies make sense.






Page 24: Product Master Maintenance System

Types of Normalization are,

1. 1st Normal form

2. 2nd Normal form

3. 3rd Normal form

1st Normal form

A relation to be in 1NF, each column must contain only a single value and each

row must contain the same columns.

2nd Normal form

In order to be in Second Normal Form, a relation must first fulfill the

requirements to be in First Normal Form. Additionally, each nonkey attribute in the

relation must be functionally dependent upon the primary key.

3rd Normal form

In order to be in Third Normal Form, a relation must first fulfill the requirements

to be in Second Normal Form. Additionally, all attributes that are not dependent upon

the primary key must be eliminated.



Field Name Type Size Description PK/FK

Uname Varchar 30 Sub-dealer Name NOT NULL

Email Varchar 30 Sub-dealers emailed

Pass Varchar 30 Password NOT NULL

Cpass Varchar 20 Confirm Password

Gend Varchar 20 Gender of the sub-dealer

DOB Date - Date Of Birth

Scode Number - Generation of the Member ID PK

Page 25: Product Master Maintenance System

MSD_Product Details

Field Name Type Size Description PK/FK

Pid Varchar 10 Product ID PK

Pname Varchar 30 Product Name NOT NULL

Pfea Varchar 20 Features of product

Uprice Number - Unit Price of product

Qty Number - Quantity of the product

Pdis Varchar 50 Description of the Product

Stot Varchar 20 Sub Total of the product

MSD_Purchase Details

Field Name Type Size Description PK/FK

Pid Varchar 10 Product ID PK

Pname Varchar 30 Product Name NOT NULL

Nop Number - No of products

Pdis Varchar 20 Description\ of product

Price Number - Price of the product

Tax Number - Tax of the Product

Amt Number - Rate of the product

MSD_Purchase Return Details

Field Name Type Size Description PK/FK

Regid Varchar 5 Product ID PK

Page 26: Product Master Maintenance System

Pid Varchar 10 Product Name FK

Pdis Varchar 20 Description of product

Com Varchar 50 Comments of the product returned

Rdate Date 50 Returned date of the Product

MSD_Stock Details

Field Name Type Size Description PK/FK

Pur Number - Products Purchased PK

Sale Number - Products sold FK

Return Number - Returned of product

Pdis Varchar - Description of the product returned

Avail Number - Availability of the Product

MSD_Sales Details

Field Name Type Size Description PK/FK

Pid Varchar 5 Product ID FK

Pname Varchar 30 Product Name NOT NULL

Nop Varchar 20 No of products

Pdis Varchar 20 Description of product

Price Number - Price of the product

Tax Number - Tax of the Product

Tot Number 20 Total of the product sold

Baddr Varchar 20 Billing Address

Bcon Number 10 Billing Contact

Saddr Varchar 20 Shipping Address

Scon Number 50 Shipping Contact

Page 27: Product Master Maintenance System

3.3.2 Module Design

The project “Product Master Maintenance System” is divided into 5 modules. They are

as follows

Manufacturer Purchase details

Product entry

Sales details

Stock details

Purchase return details

Manufacturer Purchase Module

The Manufacturer purchase specifies all the details of the products that are bought from a

manufacturer in a bulk manner. These overall stock (i.e.), product details on the whole are

maintained by the dealer. These purchase details and stock details are maintained separately by

the dealer or admin.

Product Entry Module

The products that are purchased from the manufacturer are maintained in this module.

After purchasing products in bulk from the manufacturer makes the product entries in to this

form so that the products that are ready for sale are maintained efficiently.

Sales Module

Page 28: Product Master Maintenance System

This module maintains the details of products that are sold to a particular sub dealer and

the total sales made to all sub dealers. Here the sales Id and product code can be given to which

uniquely products can be identified. It also maintains the sales information of an item.

Stock Module

This module consists of all the product details like allot required product, issue product,

maintenance of the product for sales, remaining stock (products) after the purchase made by sub

dealer and delivery details. Overall stock estimation can be made from this page.

Purchase return Module

The products that are not satisfied by the sub dealers can be received or returned back

after some specified period of time like 10 days from the date of delivery. Also the products that

are checked and regained by the dealer. If the defect occurred in the purchase product it can be

returned back and added to the current stock details. And also involves all the sub dealer

payment made for the purchased products from the master through this web based system and

then in turn master provides an invoice to the sub dealers.

So in order to provide more efficient application we implement a web application which

will increase efficiency of the system and data is stored in database so accessing data is more


3.3.3 Input Design

The input design is the process of converting the user-oriented inputs in to the computer-

based format. For providing a good input design for the application easy data input and selection

features are adopted.

The input design requirements are user friendliness and consistent format. The input form

comprises of Login form, which play a major role in the project that screens the unauthorized

user entering into the system. The user name and password are given as input to login into the

system. The given below the Input screens.


Login Sub-Dealer

Product Details

Page 29: Product Master Maintenance System

Order product


Return Product


Description: New sub-dealers use this registration to enroll them and to select the product which

they want to sale in turn to customers.

Input: Enter the Name, Address, mobile no, email-id,Password,etc..

Process: Store the data in the table

Table: Tb_Registration Details


Login Form

Description: This form is used to login the users. The security has to enter the username and the


Input: Enter the username and password.

Process: Check the role based authentication for user by retrieving the username and password.

Table: Tb_Registration


Product Details

Description: Dealer stores the Product and its features needed.

Input: select the Product sub-dealer wants and continue shopping.

Process: Forward Product details to Order the products.

Table: Tb_Product_Details


Order Product

Description: By viewing the details of the products available the sub-dealer orders the product.

Input: Select the Product_id, Product_name,etc,..

Process: Orders the product by entering the quantity.

Page 30: Product Master Maintenance System

Table: Tb_Purchase_Detials.


Shipment Details

Description: Details of the Shipment and bill address are given

Input: User enters the Address of shipment and bill

Process: Forward the details to the internet banking.



Purchase Return

Input: Enters the product id, defect reason and name for returning it

Process: Product is returned by the sub-dealer



Page 31: Product Master Maintenance System

3.3.4 Output Design

The output design presents the manipulated data to the end user. The output design acts

as medium of communication to the user by providing the desired data that may be either a

stored data fetched from the database or may be manipulated result displayed to the user for

confirmation before it is stored into the database.

The quality output is one, which meets the requirements of the end user and presents the

information clarity. In any system results of processing are communicated to the users and to

other systems through outputs. The output design deals with determining how the information is

to be displayed for immediate need and also for the hard copy output. The given below the

output screens.

Page 32: Product Master Maintenance System


4.1 System Testing

System testing is a type of testing to confirm that all code modules work as specified, and

that the system as a whole performs adequately on the platform on which it will be deployed.

System testing should be performed by testers who are trained to plan, execute, and report on

application and system code. They should be aware of scenarios that might not occur to the end

user, like testing for null, negative, and format inconsistent values.

System testing of software or hardware is testing conducted on a complete, integrated

system to evaluate the system's compliance with its specified requirements. A tester should be

able to repeat the steps that caused an error. Test techniques include, but are not limited to, the

process of executing a program or application with the intent of finding software bugs.

4.1.1 Testing and Methodologies

We begin the testing process by developing a comprehensive plan to test the general

functionality and special features on a variety of platform combinations. Strict quality control

procedures are used. The process verifies that the application meets the requirements specified in

the system requirements document and is bug free.

At the end of each testing day, we prepare a summary of completed and failed test. And

the application is redeveloped and retested until every item is resolved. All changes and retesting

are tracked through spreadsheets. Applications are not allowed to launch until all identification

problem are fixed. Finally a report is prepared at the end of testing to show exactly what was

Page 33: Product Master Maintenance System

tested and to list the final outcomes. Our software testing methodology is applied in four distinct


Unit testing

Integration testing

Unit Testing

Unit testing is designed to test small pieces of functionality rather than the system as a

whole. This allows us to conduct the first round of testing to eliminate bugs before the other

major tests (i.e.) each module is tested individually. Unit testing is testing changes made in a

existing or new program to find out each module is found to be working satisfactorily

Test Cases using Unit Testing:- Login Module :

Test ID Test Condition

Test Description

Test Data

Actual Result Expected Result Final Result

LF_01 User enters the name

User enters characters as name

admin System accepts the data

System should accept the data


LF_02 User enters name

User does not enter the name

null System does not accepts the data

System shows error message


LF_05 User enters the password

User enters password and the data should be encrypted

***** System accepts the data

System should accept the data


LF_08 User enters user name and password

User enters the login fields and clicks “OK”

System accepts data

System should accept the data


Page 34: Product Master Maintenance System


Return Product Module:

Test ID Test Condition

Test Description

Test Data

Actual Result Expected Result

Final Result

RP_01 User enters Customer name

User enters characters as Customer name

Bharathi System accepts the data

System should accepts the data


RP_02 User enters Net amount

User enters net amount

100000 System accepts the data

System should accepts the data


RP_03 User enters Shipping address

User enters the address

12/b kannan street,chennai-08

System accepts the data

System should accepts the data


RP_04 User enters Contact No

User enters contact number


System accepts the data

System should accepts the data


RP_05 User enters Billing address

User enters the Billing address

14/r dd street,kerala-09

System accepts the data

System should accepts the data


RP_6 User enters Contact

User enters contact number


System accepts the

System should accepts the data


Page 35: Product Master Maintenance System

number data

Integration Testing

Integration testing is a type of testing in which software and/or hardware components are

combined and tested to confirm that they interact according to their requirements. Integration

testing can continue progressively until the entire system has been integrated.

It is also a software testing methodology used to test individual software components or

units of code to verify interaction between various software components and detect interface

defects. Components are tested as a single group or organized in an iterative manner. After the

integration testing has been performed on the components, they are readily available for system

testing. The following are the types of integration testing:

Top down Integration

Bottom-up Integration

Test case for Integration Testing:

Test ID Test Condition

Test Description

Test Data

Actual Result Expected Result

Final Result

IG_01 User enters Login Form credentials and click submit button

User clicks submit button to be directed to product details form



System accepts the data

System should accepts the data


Page 36: Product Master Maintenance System

IG_02 User clicks any of the product and clicks continue shopping

User clicks continue shopping to be directed to the ordering product by entering the quantity

10 System accepts the data

System should accepts the data


Validation Testing:

Tests to determine whether an implemented system fulfills its requirements. The

checking of data for correctness or for compliance with applicable standards, rules, and

conventions. Validation testing is used to validate the fields in the form. It mainly focuses on text

field and numeric field.

Numeric field validation:

The numeric field can contain only numbers from 0 to 9.

An entry of any character flashes an error messages.

The individual modules are checked for accuracy and what it has to perform

Text field validation:

The text field can contain only the number of characters lesser than or equal to its size.

The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect

entry always flashes an error message.

Test Case ID

Test Condition Actual Results Expected Results Pass/Fail

LF_01 Enter the characters in “It won’t allow you to “It won’t allow you to Pass

Page 37: Product Master Maintenance System

the product name field enter the Numeric Values.”

enter the numeric values.”

LF_02 Enter the Quantity in the Dropdown list Box.

“It won’t allow you to Enter Quantity.”

“It won’t allow you to Enter Quantity.”


4.2 Quality Assurance

We believed that testing should occur throughout the development process. We tested our

software against the specifications in the system requirement document using the scenarios

developed earlier in the project.

Testing is applied in four distinct phases—unit testing, integration testing, system testing,

acceptance testing. During the system test we designs and develops test cases to verify that

system requirements have been implemented and software works correctly. By this, we achieve

better objectivity in the quality of the product.

4.2.1 Generic Risks

A risk is a potential event with negative consequences that has not happened yet.

However a risk could also be defined as the event with unforeseen positive consequences. By

identifying the risks we can avoid failures and increase the success rate of our system. During the

risk management process, the following things were discussed. They are:

What are the risks in my project?

What can go wrong in my project?

What are important risks?

What shall we do to reduce severity or avoid risk?

What is the risk status?

What has to be changed?

4.3 System Implementation

Implementation is the stage of the project where the theoretical design is turned into a

working system. At this stage the main work load, the greatest upheaval and the major impact on

Page 38: Product Master Maintenance System

the existing system shifts to the user department. If the implementation is not carefully planned a

controlled it can cause and confusion.

Implementation includes all those activities that take place to convert from the old system

to the new one. The new system may be totally new, replacing an existing manual or automated

system or it may be a major modification to an existing system. Proper implementation is

essential to provide a reliable system to meet the organization requirements. Successful

implementation may not guarantee improvement in the organization using the new system, but

improper installation will prevent it.

The process of putting the developed system in actual use is called system

implementation. This includes all those activities that take place to convert from the old system

to the new system. The system can be implemented only after thorough testing is done and if it is

found to be working according to the specifications. The system personnel check the feasibility

of the system.

The system implementation has three main aspects. They are education and training,

system testing and changeover.

The method of implementation and the time scale to be adopted are found out initially.

Next the system is tested properly and the same time users are trained the new procedures.

4.3.1 Implementation Procedures

Implementation of software refers to the final installation of the package in its real

environment, to the satisfaction of the intended users and the operation of the system.

The active user must be aware of the benefits of using the system

Their confidence in the software is built up.

Proper guidance is imparted to the user so that he is comfortable in using the


The user must know that for viewing the result, the server program should be running

in the server. If the server object is not up running on the server, the actual processes

won’t take place.

4.3.2 User Training

Page 39: Product Master Maintenance System

Our entire system was developed very user friendly. No extra training was required to use

our system. Our system automatically guides (fully user guided) the user to give input and to

produce the output.

4.3.3 Operational Documentation

An online help which gives the clear idea about our system was attached with our system.

Whenever the user needs guidance he can get help from the help manual.

4.4 System Maintenance

The maintenance phase of the software cycle is the time in which a software product

performs useful work. After a system is successfully implemented, it should be maintained in a

proper manner. System maintenance is an important aspect in the software development life


The need for system maintenance is for it to make adaptable to the changes in the system

environment. There may be social, technical and other environmental changes, which affect a

system, which is being implemented. Software product enhancements may involve providing

new functional capabilities, improving user displays and mode of interaction, upgrading the

performance characteristics of the system.

Maintenance is actually implementation of the review plan as important as it is

programmers and analyst is to perform or identify with him or herself with the maintenance.

There are psychologically personality and professional reasons for this. Analyst and

programmers spend fair more time maintaining programmer then they do writing them

Maintenances account for 50-80% of total system development.

Page 40: Product Master Maintenance System


The project report entitled “PRODUCT MASTER MAINTENANCE SYSTEM" has

come to its final stage. The System is designed to meet all the requirements of the user. Mac

Rumors gives the facility to define the products in the organization and also allows the dealer to

track the products sold to the sub dealers. The system has been developed with much care that it

is free of errors and at the same time it is efficient and less time consuming . A good amount of

user- friendly features have been incorporated in this software “Product Management System”

and it is possible for any of the candidates to exploit features to get the maximum benefit.

Some special features of this project are:

It reduces the manpower to some extent

It reduces the time cost.

To provide an easy and efficient environment

To provide an easy user interactive area

To reduce the report generation required time

Page 41: Product Master Maintenance System


The software is left without proper and frequent maintenance will have to put in the bin

after a small duration of usage. In order to avoid this timely enhancement will be made to this

project so as keep the system update according to the user needs. In teams of technological

updating, steps will be taken to make this current developed “Product Management system”

compatible with the new versions of the software tools used so as to avoid the maximum possible

usage out of the system.

“Time will make changes …..” it’s true. MAC RUMORS is so flexible to change

according to the needs. Since the software is reusable and the modules are well formed it is easy

to make any changes easily. We are planning to add the facility for providing different levels of

performance tracking of employee services based on this performance.

Page 42: Product Master Maintenance System



Professional ASP.NET 3.5 AJAX ,Bill Evjen, Matt Gibbs, Dan Wahlin, Dave Reed, Publications Pap/Pas edition (March 4, 2008).

ASP.NET MVC 1.0 Website Programming: Problem - Design – Solution,Nick Berardi, Al Katawazi, Marco Bellinaso,Pap/Dig edition (March 4, 2008).

ASP.NET AJAX Programmer's Reference: with ASP.NET 2.0., Programmers Reference,Dr. ShahramKhosravi, Wrox Publications,3 edition (January 2, 2009).

The Zen of CSS Design,Dave Shea, O’Reilly Publications,Gold Edition

JavaScript: A Beginner’s Guide,John Pollock, TATA McGraw Hill, Gold Edition

JavaScript Programmer's Reference,Cliff Wootton, Wrox Publications,Har/Cdr edition (April 13, 2009)

Page 43: Product Master Maintenance System









Home Page

Page 44: Product Master Maintenance System

Registration Form

Page 45: Product Master Maintenance System

Login form

Page 46: Product Master Maintenance System

Sales Form

Page 47: Product Master Maintenance System

Order Product

Page 48: Product Master Maintenance System

Return Product

Admin Login Form

Page 49: Product Master Maintenance System

Admin Form

Page 50: Product Master Maintenance System


Page 51: Product Master Maintenance System

PMS Product Management System

ERD Entity Relationship diagram

DFD Data Flow Diagram

GUI Graphical User interface

SRS Software Requirement Specifications

SC Source Code