45
C.M.S GOVT.GIRLS POLYTECHNIC DAURALA, MEERUT COMPUTER SCIENCE ENGINEERING TRAINING PROJECT REPORT SESSION 2012-2013 PRINCIPAL MR.RAMJI LAL HEAD OF GROUP OF NAME:

Project Report

Embed Size (px)

Citation preview

Page 1: Project Report

C.M.S GOVT.GIRLS POLYTECHNICDAURALA, MEERUT

COMPUTER SCIENCE ENGINEERING

TRAINING PROJECT REPORT

SESSION 2012-2013PRINCIPAL

MR.RAMJI LAL

HEAD OF GROUP OF NAME: DEPARTMENT Shivani yadav,

Kirti SrivastavaMr.Sanjay kumar

Page 2: Project Report

PROJECT REPORT

ON

A

PROJECT

REPORT

Submitted in partial fulfillment of the requirement for award of the Diploma

IN

COMPUTER SCIENCE ENGINEERING

SESSION-2012-2013 Submitted by

Shivani yadav,kirti srivastava

Page 3: Project Report

PROJECT REPORT

Page 4: Project Report

A Project on

Inventory

Management System

Page 5: Project Report

Table of Contents

S.No. Title Page No.

01. Acknowledgement 01

02. Certificate 02

03. Objective of Project 03

04. Project Specifications 04

05. Scope of Future Applications 06

06. Systems Analysis 08

07. Module wise Functionality 12

08. Introduction to Project 12

09. Tools Used and Environment 13

10. Analysis and Design of Reports 14

11. Implementation 17

12. Coding 26

13. Bibliography 63

Page 6: Project Report

ACKNOWLEDGEMENT

Page 7: Project Report

This not a one month works. We express thanks to the following individual whom contribution in various ways for the complete competition our project. The successful culmination of our efforts. Reminds of our indebtedness to words our venerated guide by Mr.motilal pandey for this valuable guidance and thought providing in encouragement throughout the year.We thank full to Mr. Ankit singh katiyar for this valuable advice in the hour of need providing the request facilities for the completion of the practical work.We are also thank full to all the faculty member of the department my friends of Computer science Engineer. C.M.S. Govt. Girls Polytechnic Daurala for their valuable suggestion and help provided to us time to time.

Page 8: Project Report

CERTIFICATE

Page 9: Project Report

This is to certify that Nidhi dubey and Archana sharma students of final year Information technology engineer of this institute has successfully completed the 28 days sumeer training in our organization from 20th june’12 to 18th june’12.During this training period they have completed the project on “INVENTORY MANAGEMENT SYSTEM” in core java technology under the guidance of our project manager Mr.Ankit Singh Katiyar.In this period they were an active member of the team project.

PROJECT MANAGER: Ankit singh katiyar

Objective of the Project

Page 10: Project Report

This is a inventory managemnet system can be used for for handling the records

in a small shop. This system could be used in the shop where the products is to

be maintained for example the sale report,purchase report etc..

In this model I will make two class files. One of them will act as a login form which

will be responsible for login of the authorised user only. This file will be saved as

“Welc.java”. The other class file that I will create will be responsible for the master

page where all informations can be maintained such as sale reprt ,purchase

report ,sale date ,purchase date , through which the owner of the shop can keep

the inventory updated.

In this application, the user will have to make enteries about the products this will

get stored in the databese and can be fetched according the requirements.

Page 11: Project Report

Project Specifications

Project Category

This project can be placed in the category of an Application Software that works on

a stand alone machine.

Tools and Environment (Platform & Language) to be used

Language used for this application is JAVA 2. It is an Object Oriented language. It

is platform independent and best suited for the Internet. As this is a Chat Client

Server application, so different users might run this application on different

platforms, because JAVA, unlike C and C++, is a platform independent language.

It could be run on any kind of platform. Here we have used JAVA’s built-in classes

with which the code becomes very compact and easy to be understood. Due to its

feature of inheritance, it becomes easy to develop the applications.

There are number of built-in classes in JAVA which do the specific work and

therefore we don’t need to write the whole code by ourselves. We only have to

inherit those classes and everything will be done. JAVA is also considered to be

the safe language over the net.

JAVA is a platform independent language i.e., it could be run on any kind of

platform. In this application one can not tell before hand that which client will be

using what platform. So with JAVA being platform independent language it

becomes quite simple. Unlike any other programming language JAVA produces

the byte codes. This code can be interpreted on any system that have a JAVA

Page 12: Project Report

Virtual Machine environment installed, which enables JAVA to create cross-

platform programs.

JAVA is designed for the distributed environment of the internet, because it

handles TCP/IP protocol. It is also very robust because, the programmer does not

have to worry about the memory allocation or memory deallocation, that is

automatically done by the JAVA Runtime Environment (JRE). Exceptions and

errors are also handled by the JRE.

Platform used to make this application is JAVA Runtime Environment. To run this

application we use Java Virtual Machine.

Page 13: Project Report

Scope of Future Application

Inventory management system is a very useful tool for business organisation it

affects the business a lot by providing them an automated tool to handle all the

records and important da.

With this application one can keep track of all the records of his shop.User can

maintain the information such number of products available in the store. He can

maintain the profit or loss on aparticular item and provides an easy way to maintain

information about the sources through which the product is to be purchased or

sale.

Further, this application can be modified to be compared with the other ERP

systems such as Tally erp,Marg(a medical related Erp),Hospital Erp which are

present in the market. Moreover, it could also be improved to support the financial

calculations. This could be done by using the classes of advance JAVA.

This application can be further improved for the purpose of a big Company, in

which many depatments can be handled with this package. One more feature can

be added to this application, that is it can be extended to support the distributed

system so that the business can be organised in one place. Then the new user will

be given a kind of password so that in future if that client wants to the application

will ask for the password to check the authentication of the user.

Page 14: Project Report

With the help of Hibernate (Advance JAVA), this code could be further improved so

that it could be used over internet for the same purpose.

Page 15: Project Report

System Analysis

The Process Logic

The Inventory Management System is initiated by a user by providing his login

credentials user first sends a login request to be connected with the database of

the inventory and then fetch the records present in the database.

Validation Check

The Inventory Management System is initiated by a user by providing his login

credentials user first sends a login request to be connected with the database of

the inventory and then fetch the records present in the database.

Feasibility Study

This project is worth implementing because of many points of views; technical,

economical as well as operational. As we know that chatting is gaining popularity

day by day not only for the purpose of time passing, an entertainment but for the

sake of professional use also. Since it can be used at the places where it is not

possible for the users at different locations to meet frequently and talk time to time

as and whenever required. At such times chatting proves to be very much useful

and important. Now let us see how feasible the implementation of the Inventory

management system project is.

Technical Feasibility

As far as an organization is concerned, we know that it is not possible for all the

employees or the users to interact physically with each other to discuss technical

or other matters. Moreover, if it is possible too, then it is very time consuming to

Page 16: Project Report

arrange the meetings and organize each and every thing formally. In such

situations it is very feasible technically to chat with the desired person only and at

the specific tpoic only. There mey be some misuses but that’s part of life.

Echonomic Feasiblity

Whenever anything is planned to be developed, the first question, that arises

in the minds of the project leaders as well as the programmers, is that if it is

worth developing the project. If it is so, how much time, money and labour is

required for the implementation of the project. Labour indicates the

manpower involved in the development process of the project. Apart from

the cost of the project, it is also sought that if it will be able to gain some

profit or not. Because nobody will be desirous to develop the project if there

is no benefit promised.

This aspect of feasibility study also helps the cost estimation of the project

and is a vital part of the feasibility report. This feasibility report is produced

by the system analyst before the management committee so that they can

decide whether to proceed or not to proceed towards the development

process of the project. If this phase is passed, a major hurdle is cleared.

Because this phase give the green signal for the design phase.

Operational Feasibility

As we know that chatting provides us an easy way to communicate between

two persons, it also saves the time from many point of views. First of all,

when anything has to be discussed among some persons, it is not always

Page 17: Project Report

possible to arrange time specifically for the same due to their respectibe

busy schedules.

Secondly, we don’t have to leave our desks while chatting, but in most of the

cases we can continue woorking on our system at the same time while we

are chatting with the other users.

Thirdly, this system can also avail the status of the items available in the

database matters.

Thus we can see that the project on the chat client / server is feasible to be

developed from the operational point of view too.

Page 18: Project Report

Context Data Flow Diagram ( 0 Level DFD )

Login WindowWelcome FrameProvide credentials to open master form

Master Form1. Purchase2. Sale3. Reprt

Purchase Frame that display information about the items purchased

Sale Frame that display information about the items sold

Report FrameThat generates reports such as sale, purchase etc.

DATABASE

Page 19: Project Report

Modulewise Functionality

1. Database Connection Establishment Process

This process receives the connect request from user with his/hers login-

identification. The process then forwards these input parameters to the process 2

(Master Frame) to check whether the specified user is valid or not. Whatever is the

response of master frame, the user is informed about the connection status

accordingly.

Introduction to Proejct

This is a inventory management system can be used for for handling the records

in a small shop. This system could be used in the shop where the products is to

be maintained for example the sale report, purchase report etc..

In this model I will make two class files. One of them will act as a login form which

will be responsible for login of the authorized user only. This file will be saved as

“Welc.java”. The other class file that I will create will be responsible for the master

page where all information’s can be maintained such as sale report ,purchase

report ,sale date ,purchase date , through which the owner of the shop can keep

the inventory updated.

In this application, the user will have to make entries about the products this will

get stored in the database and can be fetched according the requirements.

Page 20: Project Report

Tools Used and Environment

Language used for this application is JAVA 2. It is an Object Oriented language. It

is platform independent and best suited for the Internet. As this is a Chat Client

server application so different users might run this application different platforms,

So JAVA unlike C and c++ is platform independent. It could be run on any kind of

platform. Here the we have used JAVA’s built in classes with which the code

becomes very compact and easy to understand .because of it’s inheritance feature

it becomes easy to develop the applications.

There are number of built in classes in JAVA which do the specific work we do not

have to write the code by ourselves. We only have to inherit those classes and

everything will be done. JAVA is also considered to be the safe language over the

net.

JAVA is a platform independent language i.e., it could be run on any kind of

platform .In this application one can not tell before hand that which client will be

using what platform. So with JAVA it becomes simple ,JAVA being platform

independent language .Unlike any other programming language JAVA produces

the byte codes. This code can be interpreted on any system that provides a JAVA

Virtual Machine which enables JAVA to create cross-platform programs.

JAVA is designed for the distributed environment of the internet, because it

handles TCP/IP protocols. It is also very robust because in this programmer does

not have to worry about the memory allocation or memory release, that is done by

the JRE .Exceptions and errors are also handled by the JAVA run time

environment. Platform used to make this application is Java Runtime Environment.

To run this application we use Java Virtual Machine.

Page 21: Project Report

Analyses and Design Report

Login Frame

We will create a class called Welc that implements the following GUI design:

As you can see, there are six components in this GUI. The main component is a

Label. The bottom component is a Button. There are two Button components on

the bottom that is Login and cancel. You will need to refer to Appendix C in the

textbook for instructions on how to use the text components.

1. Create the Welc class with six private attributes; one for each component. In

the constructor, initialize each of these component attributes: the text field

should be 50 columns wide, the login button should have the word "Enter" in

the display, and likewise for the cancel button.

1. Create a launchFrame method which constructs the layout of the

components. Feel free to use nested panels and any layout managers that

will help you construct the layout in the GUI design shown above.

2. Create the main method. This method will instantiate a new MenuApp object

and then call the launchFrame method.

First of all we will have to be clear about the outlook of the client window. For this

GUI window we will need two text field where the user will type the id and

password .

Page 22: Project Report

To let these function work we will be using event handling for the process:

1. Create an ActionListener which will Handle the events generated from clicking

the button when the Enter or cancel button is pressed. Use an inner class

to implement this because you will need access to the MenuApp’s private

attributes.

2. Create an ActionListener which will quit the program when the cancel button is

pressed.

3. Create a WindowListener which will quit the program when the close widget is

pressed on the frame.

4. Modify the launchFrame method to add instances of your listeners to the

appropriate components.

Point to be taken care of while handling events:

Have the listeners (inner classes) access the instance variables of their

containing class to refer to the components like the output textfield

Remember that you made the components instance variables in the

previous lab.

Also, don't forget to import the java.awt.event.* package.

The function of the send button will be to send the text from the text field to the text

area of all the visible GUI windows of all the clients .If the client wishes to end the

chatting then he will press the quit button which will close the GUI window .There

are also two menu items which will be displayed on the menu bar.

Page 23: Project Report

Then we will have to think about the placing of all the components on to the

window . For that we will use panels which will be placed on to the layout of type

Gridlayout. Text field will be placed at the south of the layout , text area will be

placed to the center of the layout, then we will make one panel which will contain

two buttons and a choicebox in a flowlayout fashion ,then this panel will be further

placed on to the right of gridlayout.

Master Frame

Here we will finish the "Chat Room" client program. This client will connect to

"Chat Server" so that the client is able to chat with the other clients.

1. To make this application In the launchFrame method, we need to make the

connection to the server (by making a socket connection).

2. Then we need to get streams (input and output) from the socket connection so

that we can send our messages to the server, and receive other messages

from the server.

3. Then we need to modify the actionPerformed method so that when the user

clicks the "send" button you send the text of the message to the server

(using the output stream) rather than putting it into the text area.

4. We also need to modify the action listener on the "input" text field to do the

same as above (send the message to the server).

Page 24: Project Report
Page 25: Project Report

Implementation

How to make the class

import java.awt.*;

import javax.swing.*;

import java.awt.event.*;

public class Welc extends Frame implements ActionListener

{

Toolkit t;

Image im;

Label l1,l2,l3;

TextField t1,t2;

Font f;

Button b1,b2;

Welc()

{

super("WELCOME TO INVERNTORY MANAGEMENT SYSTEM");

l1=new Label("Login ID ");

Page 26: Project Report

l2=new Label("Password.");

l3=new Label("Developed by : ABC Groups");

t1 = new TextField(20);

t2 = new TextField(20);

b1 = new Button("Enter");

b2 = new Button("Cancel");

General format of the class

import java.awt.*;

import java.awt.event.*;

import java.applet.*;

public class MenuApp extends Frame implements ActionListener

{

MenuBar mb;

Menu m1,m2,m3;

MenuItem i1,i2,i3,i4,i5,i6,i7,i8,i9,i10;

Page 27: Project Report

Toolkit toolkit;

Font fo = new Font("Courier New",1,30);

Image im;

Button b1 = new Button("M a s t e r F o r m");

Button b2 = new Button("P u r c h a s e F o r m");

Button b3 = new Button("S a l e F o r m");

Button b4 = new Button("P u r c h a s e R e p o r t ");

Button b5 = new Button("S a l e R e p o r t ");

public MenuApp()

{

super("Inventory Management System");

setup();

setLayout(null);

setBackground(new Color(142,175,251));

b1.setBackground(new Color(245,160,120));

b2.setBackground(new Color(245,160,120));

b3.setBackground(new Color(245,160,120));

b4.setBackground(new Color(245,160,120));

Page 28: Project Report

b5.setBackground(new Color(245,160,120));

b1.setForeground(Color.blue);

b2.setForeground(Color.blue);

b3.setForeground(Color.blue);

b4.setForeground(Color.blue);

b5.setForeground(Color.blue);

b1.setBounds(200,150,360,50);

b2.setBounds(200,220,360,50);

b3.setBounds(200,290,360,50);

b4.setBounds(200,360,360,50);

b5.setBounds(200,430,360,50);

b1.setFont(fo);

b2.setFont(fo);

b3.setFont(fo);

b4.setFont(fo);

b5.setFont(fo);

Page 29: Project Report

add(b1);

add(b2);

add(b3);

add(b4);

add(b5);

addWindowListener(new WindowAdapter()

{

public void windowClosing(WindowEvent e)

{

setVisible(false);

}

});

}

void setup()

{ mb = new MenuBar();

m1 = new Menu("File");

m2 = new Menu("Reports");

Page 30: Project Report

m3 = new Menu("Help");

i1 = new MenuItem("Master");

i2 = new MenuItem("Procurement");

i3 = new MenuItem("Sale");

i4 = new MenuItem("Exit");

i7 = new MenuItem("Sales Report");

i8 = new MenuItem("About");

i10 = new MenuItem("Purchase Report");

i1.addActionListener(this);

i2.addActionListener(this);

i3.addActionListener(this);

i4.addActionListener(this);

i7.addActionListener(this);

i8.addActionListener(this);

i10.addActionListener(this);

b1.addActionListener(this);

b2.addActionListener(this);

b3.addActionListener(this);

Page 31: Project Report

b4.addActionListener(this);

b5.addActionListener(this);

m1.add(i1);

m1.add(i2);

m1.add(i3);

m1.add(i4);

m2.add(i7);

m3.add(i8);

m2.add(i10);

mb.add(m1);

mb.add(m2);

mb.add(m3);

setMenuBar(mb);

setBounds(20,20,700,500);

setVisible(true);

Page 32: Project Report

}

public void actionPerformed(ActionEvent e)

{

Object o = e.getSource();

if(o==i1 || o==b1 )

new Mast2();

if(o==i2 || o==b2)

new Purc();

if(o==i3 || o==b3)

new Sale();

if(o==i4)

setVisible(false);

if(o==i7 || o==b5)

new dialog11();

if(o==i8)

new Help();

if(o==i10 || o==b4)

new dialog12();

Page 33: Project Report

}

public static void main(String aa[])

{

MenuApp a = new MenuApp();

}

}

Page 34: Project Report

Bibliography:

BRAINSOFT SOFTWARE PVT. LTD.