2009-10

DOCUMEN
T
INVENTORY SYSTEM

SUBMITTED BY | UMESH SHAKYA (CS)

NITIN SWAROOP (CS)
 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

 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

 Acknowledgement

Every endeavor we understand takes an indomitable urge,

perseverance, and proper guidance especially when it is most
needed. Internally motivated to undertake some appreciable work as
our degree project, we came to undertake the project. Unsure
though but with a hope and then we were introduced to these
project work to be completed, initially when we had hardly ever
thought of, the kind of work we were going to do

We would like to use this opportunity to thank with gratitude our

respected Director Sir.
In addition, we would like to thank Mrs. Shivani Singh of IMS for their
motivation to take
this endeavor and perform.

Here we think from the core, everybody who has helped us at

work when it started as an unknown ocean to swim though, we need
more then sense of words. In true sense, besides our guides we are
indebted to our friends at IMS for their constant help and invaluable
contribution on all occasion when they were most needed. Again, we
find the opportunity to acknowledge our regards and thanks to our
family members who have been true support behind us.

NI
TIN SWAROOP (CS)

UMESH SHAKYA
(CS)
 Table of Contents

MODULES

In order to design our proposed project, we are going to break

into following function module:

1. INVENTORY ADMINISTRATOR

2. AGENT
 DECLARATION

Both of us as a technical team of our proposed project declared at

all the above detail module are in preliminary stage, suppose to
change if required further.

( NITIN SWAROOP )
( UMESH SHAKYA )
 INITIAL
PHASE
( USE CASE TOOL )

USE CASE 1: (Initial case)

1. Use Case Name: INVENTORY ADMINISTRATOR

2. Author: NITIN , UMESH

 3. Actor:
a) Proposed Project
b) 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 required
field of operation .

6. Pre Condition: Not any.

7. Post Condition: Not any.

USE CASE 2: (Initial case)

1. Use Case Name: AGENT
2. Author: NITIN, UMESH

3. Actor:
a) Proposed Project
b) AGENT

4. Brief Description:
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.

7. Post Condition: Not any.

 SYSTEM
ANALYSIS
( USE CASE TOOL )

USE CASE 1:
(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 flight
infomations 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 password

Password is wrong.
Wrong item no.
 7. Pre Condition: Not any.

8. Post Condition: Not any.

USE CASE 2:

(Analysis case)
1. Use Case Name: Agent
2. Author: NITIN , UMESH

3. Actor:
a) Proposed project.
b) Agent

4. Brief Description:
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..
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 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

8. Post Condition: Not any.

 SYSTEM
DESIGN
( USE CASE TOOL )
USE CASE 1:

(Design 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 flight
infomations 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 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.

9. Alternative Flow Of Events:
Enter the password
Password is wrong.

Wrong item no.

10. Pre Condition: Not any.

11. Post Condition: Not any.

USE CASE 2:
(Design case)
1. Use Case Name: Agent
2. Author: NITIN , UMESH
3. Actor:
a) Proposed project.
b) Agent

4. Brief Description:
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..

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 exit from the system he may select EXIT.

6. Alternative Flow Of Events:

Enter the password
Password is wrong.
Wrong item no.

7. Precondition: Not any

8. Post Condition: Not any

OUTPUT
(SCREEN SHOTS)

HOME
NEW RECORD
DISPLAY

SEARCH
UPDATION

DELETE
 ANALYSIS

EXIT SCREEN
WRONG PASSWORD

EXITING
CODING