Contents
STATIONERY MANAGEMENT SYSTEM........................................................................................................... 2
PURPOSE ................................................................................................................................................... 2
PLATFORM USED FOR IMPLEMENTATION ............................................................................................. 2
FUNCTIONAL REQUIREMENTS OF THE PROJECT ...................................................................................... 2
STATIONERY MANAGEMENT SYSTEM
PURPOSE
This project is aimed at developing a tool for tracking the stationery request for the GIS group.
PLATFORM USED FOR IMPLEMENTATION
The system will be developed using swings/awt as the front end and the Microsoft access as the
back end and middle layer of pure java classes.
Application Tier (AWT/Swing)
Middle Tier (Java Classes) + JDBC
Database Layer
(MS Access)
___________________________________________________________________
FUNCTIONAL REQUIREMENTS OF THE PROJECT
There will be registered people in the system, with two Role Types Approver and Requester.
An approver will also be a requester.
1. A REQUESTER should be able to :
- Apply for new stationery request.
- View his/her report.
REQUEST
GENERATION
REQUESTER
VIEW MY
REPORT
------------------------------------------------------------------------------------------------------------------------------2.
-
An APPROVER should be able to:
Approve the request for item allocation.
View report history for all the users.
Cancellation of requests.
Manage Inventory.
INVENTORY ACCESS
DDADA
ADMIN
APPROVAL FOR
ITEM ALLOCATION
VIEW HISTORY
FOR ALL USERS
CANCELLATION