Inventory System - By Nitin n Umesh

8/8/2019 Inventory System - By Nitin n Umesh

1/30

2009-10

SUBMITTED BY | UMESH SHAKYA (CS)NITIN SWAROOP (CS)

DOCUMENT

INVENTORY SYSTEM


2/30

I.M.S. ENGINEERING COLLEGE

Ghaziabad

AIRLINES INFORMATION AND

MANAGEMENT SYSTEM

(AIMS)

Minor Project Submitted towards

partial fulfillment of the degree of

Bachelor of Engineering

Year 2009-2010

Department of COMPUTER

SCIENCE

Guided By: Mr. MANISH K. JHA


3/30

CERTIFICATE

This is to Certify that Mr. NITIN SWAROOP and Mr. UMESH

SHAKYA Working in a Group have satisfactorily completed the minor

project titled INVENTORY SYSTEM (IS) towards the partial

fulfillment of the degree in Bachelor of Engineering (COMPUTER

SCIENCE) Awarded by Uttar Pradesh Technical University (UPTU),

Lucknow for the academic year 2009-10.

GUIDED BY ,

Mr. MANISH K.JHA


4/30

Acknowledgement

Every endeavor we understand takes an indomitable urge,perseverance, and proper guidance especially when it is mostneeded. Internally motivated to undertake some appreciable work asour degree project, we came to undertake the project. Unsurethough but with a hope and then we were introduced to theseproject work to be completed, initially when we had hardly everthought of, the kind of work we were going to do

We would like to use this opportunity to thank with gratitude ourrespected Director Sir.In addition, we would like to thankMrs. Shivani Singh of IMS for their

motivation to takethis endeavor and perform.

Here we think from the core, everybody who has helped us atwork when it started as an unknown ocean to swim though, we needmore then sense of words. In true sense, besides our guides we areindebted to our friends at IMS for their constant help and invaluablecontribution on all occasion when they were most needed. Again, wefind the opportunity to acknowledge our regards and thanks to our

family members who have been true support behind us.

NITIN SWAROOP (CS)

UMESH SHAKYA(CS)


5/30

Table of Contents

MODULES

In order to design our proposed project, we are going to breakinto following function module:

1. INVENTORY ADMINISTRATOR

2. AGENT


6/30

DECLARATION

Both of us as a technical team of our proposed project declared atall the above detail module are in preliminary stage, suppose to

change if required further.

( NITIN SWAROOP )( UMESH SHAKYA )


7/30

INITIAL

PHASE( USE CASE TOOL )

USE CASE 1: (Initial case)

1. Use Case Name:INVENTORY ADMINISTRATOR

2. Author : NITIN , UMESH


8/30

3. Actor :a) Proposed Projectb) ADMIN

4. Brief Description :

The administrator may login and add/update/delete/analyse

infomations in the inventory system .5. Basic Flow Of Event :

The administrator may click and select the requiredfield of operation .

6. Pre Condition : Not any.

7. Post Condition : Not any.

USE CASE 2: (Initial case)1. Use Case Name:AGENT2. Author : NITIN, UMESH

3. Actor :a) Proposed Projectb) AGENT


The agent may login and add/update/delete ..

5. Basic Flow Of Event :The agent may click and select the required field of operation .

6. Pre Condition : Not any.



9/30

SYSTEM

ANALYSIS( USE CASE TOOL )

USE CASE 1:


10/30

(Analysis case)

1. Use Case Name:Administrator

2. Author: NITIN , UMESH

3. Actor:a) Proposed Project

b) Administrator

4. Brief Description:

The administrator may login and add/update/delete flightinfomations and records.

5. Basic Flow Of Event:

a

a) This case is initiated when the administrator wants to

login and add/update/delete /analyse records in the

inventory..

b) The proposed system produces the page after login.

c) Now he can select his desired operation to perform.d) If he wants to add a new item in the inventory he may

select ADD NEW RECORD.e) If he wants to see all the items in the inventory he may

select DISPLAY.f) If he wants to search any item in the record he may select

SEARCH.g) If he wants to update/modify any item in the record he

may select UPDATE.h) If he wants to delete any item in the record he may select

DELETE.i) If he wants to analyse the inventory n its current postion

he may select ANALYSIS.j) If he wants to exit from the system he may select EXIT.

6. Alternative Flow Of Events:

Enter the passwordPassword is wrong.Wrong item no.


11/30

7. Pre Condition: Not any.

8. Post Condition: Not any.

USE CASE 2:

(Analysis case)

1. Use Case Name : Agent2. Author: NITIN , UMESH

3. Actor :

a) Proposed project.b) Agent


The agent may login and add/update/delete reocrds .

5. Basic Flow Of Events:

a) This case is initiated when the agent wants to login and

add/update/delete items in the inventory..



select ADD NEW RECORD.e) If he wants to see all the items in the inventory he may

select DISPLAY.f) If he wants to search any item in the record he may select

SEARCH.g) If he wants to update/modify any item in the record he

may select UPDATE.h) If he wants to delete any item in the record he may select

DELETE.


12/30

i) If he wants to exit from the system he may select EXIT.

6. Alternative Flow Of Events :

Enter the user name.Enter the password.

Enter the 7 digit PNR no.

7. Precondition: Not any



13/30

SYSTEMDESIGN

( USE CASE TOOL )USE CASE 1:

(Design case)


14/30

1. Use Case Name:Administrator

2. Author: NITIN , UMESH

3. Actor:

a) Proposed Projectb) Administrator

4. Brief Description:

The administrator may login and add/update/delete flightinfomations and records.

5. Basic Flow Of Event:

a) This case is initiated when the administrator wants to

login and add/update/delete /analyse records in theinventory..



select ADD NEW RECORD.


15/30

e) If he wants to see all the items in the inventory he mayselect DISPLAY.

f) If he wants to search any item in the record he may selectSEARCH.


16/30

g) If he wants to update/modify any item in the record hemay select UPDATE.


17/30

h) If he wants to delete any item in the record he may selectDELETE.

i) If he wants to analyse the inventory n its current postionhe may select ANALYSIS.

j) If he wants to exit from the system he may select EXIT.


18/30

9. Alternative Flow Of Events:

Enter the passwordPassword is wrong.

Wrong item no.

10. Pre Condition: Not any.

11. Post Condition: Not any.

USE CASE 2:


19/30

(Design case)

1. Use Case Name : Agent2. Author: NITIN , UMESH3. Actor :

a) Proposed project.b) Agent


The agent may login and add/update/delete reocrds .

5. Basic Flow Of Events:

a) This case is initiated when the agent wants to login and

add/update/delete items in the inventory..


c) Now he can select his desired operation to perform.


20/30

d) If he wants to add a new item in the inventory he mayselect ADD NEW RECORD.

e) If he wants to see all the items in the inventory he mayselect DISPLAY.


21/30

f) If he wants to search any item in the record he may selectSEARCH.


22/30

g) If he wants to update/modify any item in the record hemay select UPDATE.

h) If he wants to delete any item in the record he may selectDELETE.


23/30

i) If he wants to exit from the system he may select EXIT.

6. Alternative Flow Of Events :

Enter the passwordPassword is wrong.Wrong item no.

7. Precondition: Not any

8. Post Condition : Not any


24/30

OUTPUT(SCREEN SHOTS)HOME


25/30

NEW RECORD


26/30

DISPLAY

SEARCH


27/30

UPDATION

DELETE


28/30

ANALYSIS

EXIT SCREEN


29/30

WRONG PASSWORD

EXITING


30/30

CODING

Inventory System - By Nitin n Umesh

Documents

Transcript of Inventory System - By Nitin n Umesh