Inventory management

system for college

1. Introduction
This section introduces the project and also the reasons for the production of
an SRS. It
also contains definitions, acronyms and abbreviations used throughout the
document.

1.1 Purpose:
This document states the requirements for an interactive database system to
be agreed
upon between the client for the college and supplier. Further details can be
found
in the Software Project Management Plan. The client is management officier
of college. The intended audience of this document is Team Respect, the
project guide the markers and assessors.

1.2 Contact details

1.2.1Team Respect
The team can be contacted:

1.VIA E-MAIL nishtha garg: komalgarg81@yahoo.co.in

2.through the piet college computers depatment

1.3 objective
The Objective of the Project is to design an Inventory Management system for college
which will manage the stock of different products and items. The
application will contain module like stock Information of different products category,
available stock, price of different items etc. One can also extract any reports relating
to purchase and Sale. The inventory management will have all the
categories, subcategories, items, Stock details and reports.The existing system is a
manual system in such a system the inventory is managed by some predictions not on
actual numbers, either the ordered material are too less or too much. This leads to
either piling up of inventory or running out of stock. This problem with the existing
system demanded an inventory management application.
The responsibility of the new system would be: - Keeping inventory management a
cost down which is crucial to competitive advantage. Inventory Management
Application shall help college slash inventory costs by providing tighter control of
stock levels. The application would enable price-rules setting based on the product
and items. Inventory Management Application shall provide intelligent control over
inventory replenishment, helping ensure that you have enough on hand to fill
anticipated orders, but keep excess stock to a minimum.

1.4 Scope
The product will be used exclusively by poornima institute of engineering and
technology
college inventory management application is going to be build keeping the
commercial aspects of the college. The application will have different Category
of Products, Sub category of Products and items. This application will also have
transaction details and reports. The administrator of this application will have right to
create product, add items delete items etc. The application will provide information
on available stock of the products. The category will be tagged with subcategory.
Again the subcategories are tagged with different items in the respective category and
rate of the item.

1.5 Definitions, Acronyms and

Abbreviations
1.5.1 Definitions
1. Account
An account is the details of any monies owed to the college by a
manager/administrator

2. Stock
A supply of goods or materials available for sale or use
.
3. Database Member
Either a student, teacher, class or inventory entry in the database system.

4. Inventory
A storage of items which are for sale through the collegel.

5. Inventory Item
An item, which is currently for sale, details of which are stored in the
database.

6. Teacher
A teacher is defined as being employed by the school to teach students of
different
levels.
7.item
an individual article or unit

. 1.5.2 Acronyms
1. CPU
Central Processing Unit

2. GUI
Graphical User Interface

3. HTML
Hypertext Markup Language, a standard language for writing web sites.

4.piet
poornima imstitute of engineering and technology

2. general description:

2.1 project functions

• This application shall keep detailed information about product stock.

• save time wasted on repetitive data entry
• attain 100% data entry accuracy
• Single administrator of the system.
• Reduced paper work
• Faster order Fills
• streamlined data entry
• manage inventory by your own rules
• unlimited roles and permissions
• better time management
• no double entry
• automatically track landed cost for any product
• Improve billing accuracy by eliminating data entry errors caused by manual
entry
• Eliminate inventory receiving errors through automated receiving process
• Automate the Physical Inventory process

2.2 refrences
1. bridge school management system
2. boyanika,textile & handloom department, govt. of orrisa

3.http://www.orell.in/campus-erp/inventory-management-system.html

4.school management system features pdf

5.schoolmanager pdf

2.3 project constraints

Hardware Constraints
The design team will allow for mouse control of functionality which does not
require
text input.
.
Software Constraints
1. The development of the system will be constrained by the availability of
required
software such as compilers and development tools.
2. The availability of these tools will be governed by the college.
3. The most recent versions of software development tools may not be
installed at
the college

2.4 Requirements Prioritisation

The requirements will be prioritised in the following way:

1. Requirements will be split into Functional and Non-functional.

2. Each of these will be ranked as either Core (1st priority) or Optional(2nd
priority).
3. The Optional functionality will then be prioritised into:
(a) Highly Desirable - These requirements will be the first optional
requirements
to be implemented if time allows.
(b) Desirable - These requirements will be implemented only after all highly
desirable requirements have been implemented and tested.
The system will be considered satisfactorily completed after all Core
requirements
have been implemented and tested.
2.4.1 functional requirements:

1.Administrative Features
These features will allow manipulation of the underlying databases of the
system.

2. login
The system will provide functionality to allow the user to log in to the system
with a
username and password.

3.Add Inventory Item

The system will provide functionality to add a new inventory item into the
system
database. The user will enter into the system the following information
related to an
inventory item:
1. Item name
2. Item description
3. Supplier (Could be a company or individual)
4. Cost Price
5. Sale Price
6. purchase date
7. bill no.
8. purchase rate
9. items consumed
10. item in hand
11. item's configuration (if an electronic gadget)

4.Add Supplier
The system will provide functionality to add a supplier to the supplier list. The
user
will enter into the system the following information related to a supplier:
1. Supplier name
2. Items they supply
3. Retail prices of items
4. Discounts for bulk buying
5. Contact details
6 . address

5.Edit Details
The system will provide functionality to allow the user to edit the details of
any
database member.

6. Delete Database Member

The system will provide functionality to delete a database member and all
their details
from the database.
7.Edit Supplier List
The system will provide functionality to allow the user to edit the supplier list,
which
will contain details:
1. Supplier name
2. Items they supply
3. Retail prices
4. Discounts for bulk buying
5. Contact Details

8.List Unpaid Accounts

The system will provide functionality to display the details of all unpaid
accounts. The
information displayed will be:
1. Name of Account
2. Amount Owing
3. When it is/was due

Optional Requirements
The following requirements are optional and will be implemented only after
all core
requirements have been satisfied. Optional requirements do not have to be
satisfied
for the system to be satisfactorily completed.

2.4.2 Non-functional Requirements

Non-functional requirements are those which specify how the system will be
implemented.
These requirements include constraints on design and implementation. All
non-functional requirements are considered to be core requirements.

1. Interface Requirements
The following requirements apply to the communication of the system with
outside
entities and within itself.

External Interfaces
An external interface is defined as being a mode of communication with
entities which
are external to the system being developed. Examples of such entities are
users and
hardware.

User Interfaces
1. All interaction between the user and the system is to be through a
graphical user
interface (GUI).
2. All features are to be accessed through buttons that are to appear in
structured
menus.
3. The user is to communicate to the system through the use of a mouse and
keyboard.
.
4. View Profile Interface
This will display the details of either a student, teacher, class or inventory
item
and will provide access to functionalities described in Table 2. See section 3
for
a full description of functions in Tables 1 and 2.
Note: The interface descriptions may change slightly during the design phase
of
the software lifecycle.

Hardware Interfaces

1. The software is expected to operate on a personal computer with the

following
minimum hardware characteristics:
(a) Intel Celeron 1000MHZ CPU
(b) 32MB RAM
(c) 1 gigabyte free disk space
2. The software is to interact with a mouse and keyboard, which are to be the
sources of user input.
3. Interaction with the computer’s default printing device is also a necessary
core
hardware interface requirement, however the specifications of the printing
hardware
are not essential to the design of the software.

Software Interfaces

Following are details of specific software that will be interfaced with:

(a) Software name: Windows
Version: XP
Source: Microsoft
(b) Software name: Excel
Version: 2000
Source: Microsoft

Internal Interfaces
The following interfacing is required within the system:
1. Interfacing between the database and the user interfaces.
2.Security Requirements
The system is to provide a login feature which will be password activated.
Users will
be allocated a username and a password. This will allow only users with a
username
and password to access the system.

3. Implementation Constraints
The system will be implemented to allow for the possibility of making parts or
all of
the system available for use on the web at a later date.

2. Quality System Attributes

The following requirements relate to the quality of the system being
produced.

Availability
This system will only be available on the manager's personal lap-top, 24
hours a day.
Should the user leave the programme running whilst sitting at the lap-top,
data will
remain in memory, unless edited, and the system will remain in the state in
which the
user left it.

Security
There will be a login to the lap-top, requiring a username and password. The
software
will only be available to people who have been able to log on to the computer
through
the Microsoft Windows XP security system already on the computer.

Operability
The system will allow the user to operate it with a mouse, unless input is
required from
the keyboard. This is to allow the manager to have one hand free to hold
small children.

Learnability
The system will be delivered with a user manual which will detail the use of
the system
to the manager. Team Respect will also provide a tutorial for the manager if
the client wishes at system delivery time.