PROJECT ENTITLED

ONLINE REQUISITION SYSTEM

INTRODUCTION
The Project titled “E-Requisition System” is the implementation of the management’s stock
policies in a manner that assures the goals of stock management are met. A Requisition is a
request for something, especially a formal written request on pre-printed form. An online
requisition is an electronic document, which can be originated by the requester and then using
the company workflow or hierarchy rules, can be submitted to the subsequent levels, until it is
approved. It contains the description, quantity and specification of the goods or services to be
purchased. Online requisition is simple computer software which eases the supply and demand of
the stock e.g. in college stationary like marker, paper roll for printer, duster, sports utilities etc
required by different departments of the University. It is an intermediate which smoothens the
facilities of requesting, placing orders, getting confirmation and receiving the orders. It is better
in every respect than the existing manual working system, including counting and monitoring of
stock items: recording and retrieval of items, storage location, recording changes to stock, and
anticipating stock needs, including stock handling requirements. It manages the flow of
materials, effectively utilize people and equipment. The project E-REQUISITION is aimed at
reducing the work load of clerks, HODs, teaching, non-teaching faculty etc .It helps the students,
teachers etc to request for the various things they need .Besides requesting, it also will serve as a
medium for student or faculty to file complaints. The key thing here is that the identity of a
person who has registered a complaint will be hidden thus will provide a good privacy and will
not affect the personal life of an individual.

1
 Overview of Online Requisition

A Requisition is a request for something, especially a formal written request on pre-printed form.
In our project Online Requisition System; Admin is the main user of our system who has got
privileges over all other users. He can login to the system after that he can add departments to the
University, he can add members to the different departments, and he can also update
Departments and User details. Then in our project, Clerk is the other user who can login to the
system and creates the requisition by adding new items, after that the requisition is forwarded to
the HOD, where the HOD can login to the system and can view the orders sent by the Clerk. If
he feels the number of items in the order are either more or less than he can edit the number of
items, after that he approves the requisition. Then the requisition is forwarded to the Store
Incharge where he can login to the system and checks the requisition sent by the HOD, after that
the Store Incharge checks if all those items of the requisition are present in the stock then he
approves the order and if any item is not present in the stock then that item is moved into the
queue until the next requisition is sent by the department. At last the Clerk login to the system
and receives the order from the store.

This System has following components:

 Create Departments.
 Provide User Name And Password.
 Add Suppliers and Items.
 Allocate Items to Departments.
 Process Requisition send by Departments.

2
 METHODOLOGY
Our group members include Faizan Khalid Mir (05-ITE-2013), Shabir-Ur-Rashid (12-ITE-
2013), Muneeb Manzoor Bhat (14-ITE-2013) and Umar Farooq Mir (34-ITE-2013). By the time
our major project phase1 started, we discussed about lot of projects and came up with the project
E-REQUISITION SYSTEM. Following is the methodology and different stages of planning for
system development:

Planning and requirement analysis: In this phase we decided to plan about the system
requirements, user interfaces, hardware interfaces, software interfaces & memory constraints.
Also we planned to discuss about the Design constraints which include operations of our project,
functional requirements, performance requirements etc.

Defining requirements: After the planning and requirement analysis, this phase starts and in
this phase we decided to document and define the software requirements and get them approved
from the guide.

Designing phase: This phase will start after defining the requirements and in this phase
requirement analysis will play a major part in designing and developing and required software.

Coding phase: After the completion of design phase, the most important and exhilarative phase
(coding phase) starts. Coding here is done as per the design as it provides life to the developed
design. Different high level programming languages such as C++, HTML, and ASP.NET etc are
used. The programming language is chosen with respect the type of software to be developed.

Testing phase: This phase is the subset of all above phases. It is the only stage of the software
where defects are reported, tracked, fixed or retested.

3
Following table summarizes the methodology phase where the boxes with black colour indicate
various steps to be followed at the respective time:

Oct- Nov- Dec- Jan- Feb- Mar- Apr- May-

2016 2016 2016 2017 2017 2017 2017 2017

Requirement

Analysis

Defining

Requirements

Design

Coding

Testing

Documentation

4
  Goals & objectives:
 To generate various reports.

• To maintain communication timely and accurately.

• Efficient and controlled information handling. Ease of use and interactive user
interface.

• To provide secure, reliable, portable and convenient atmosphere for both

administrator as well as for users.

• To make the system efficient as well as optimize the use of staff.

• To provide multiuser options, comprehensive security as per user module and

create backup vendors with ease.

5
  Existing System and its Limitations:

The existing system is manual, thus it must have few drawbacks. As we know the manual
system is fully based on paper work. Sometimes the requisition made on those papers can
be misplaced while moving from department to the store or vice versa. . It is hard to
maintain the record of all requisitions of the University on the paper because sometimes
the leisure’s that holds the record of those all requisitions can also be misplaced, or can
be victim of any natural disaster like fire etc. The repetition of same requisition can also
take place. In order to understand the Existing System fully we will go through its
drawbacks. Some of the drawbacks of the existing system are categorized as under:

• Paper Work/Wastage: In manual system, there is extensive paper work as every record
is maintained in papers, manually has number of flaws like slow, time consuming etc.

• Complexity: Since the current system is manual, the complexities are there whenever any
modification is done. e.g.; transfers data records from one person to another.

• Lack of Reusability: The current System doesn’t support reusability.

• Redundancy: A lot of information and work is repeated in the manual system without
any necessity.

• Time Consuming: The humans can’t work as fast as computer can, the manual system
becomes slow and time consuming.

• Human Error: Whenever humans are working, the associated errors are also present
there e.g.; typing errors, arithmetic errors and boredom.

• Search Problems: Searching for records in manual system is always poor and difficult.

• Security Problem: The security of a lot of documents, which are paper based, is difficult
may be in terms of illegal access or manipulation by malicious personals or by accidents.

6
Software and Hardware Requirements

 Software Requirements:

Developing Language:

 Asp.Net, CSS, JavaScript, bootstrap.

Database:

 MS SQL

Operating System:

 Windows, Linux, Macintosh

 Hardware Requirements :

Processor:

 Intel Dual Core Processor.

Processor speed:

 Minimum 2.0 GHz

RAM:

 Minimum 1GB.

Hard Disk:

 Minimum 40GB.

7
 Bibliography

 www.wikipedia.com
 www.webreq.com.au
 www.slingshotsoftware.com/content/products/requisition-
management
 www.redkitesystems.com/on-line-requisition.html