1.

Introduction
1.1 Purpose:
We know stock management is one of the necessary tasks that need to be carried out in an organization. Therefore every organization needs good software that would help the organization to maintain the stocks in an efficient, easy and time saving way. This project fulfils all the above requirements of an organization.

1.2 Intended Audience and Reading Suggestions:

This document is intended for the referral of the following section of readers: Developers Project Managers Users Testers Documentation Writers

1.3 Project Scope:

This project of Fixed Asset Management System is to be integrated with the existing College Management System. This will be added as a feature of CMS that will provide better management facilities for the stock manager and aims at the proper management of the assets of the college.

1.4 References:
This document includes the following references: User Flow Diagram

 Data Flow Diagram Data Model Diagram (E-R Diagram) Various User Interfaces

2. Overall Description
2.1 Product Perspective:
This product is going to be implemented for the first time in required area. Using this product, we can use a computer for the management, which would take very long time while doing it manually. It helps in maintaining the whole systematic order. It takes less time to maintain an item using computer rather than maintaining it in the register, manually.

2.2 Product Features:

The product contents are Item Category Stock issue Stock receive Stock maintenance Stock quotation Item:Each object may be tangible or intangible stored in store is known as Item. The item section contains all information about the goods that are stored in the store house of an organization. The section is also responsible for the generation of details about the stock present in the store house. So, the table is maintained in such a way that the generation of information will be easier and the store manager can know the item list in the store easily within a short time.

Category:All the items are divided into some categories. It is maintained in category section. In this section, the similar items are stored under the same category. Stock Issue:Stock issue section describes all the details about the issue and order of stock to different department within the organization. In this section we maintain to which department what item is issued and how much stocks are remaining after issuing. Stocks Receive:Stock Receive section is used to store all the details of the items that are being purchased from the supplier. It also gives an idea to the user about the stocks which are already present. It provides the user with detailed and updated information about the date and amount of stocks received. Stock Maintenance:It is the stock maintenance section in which we mention that when an item gets damaged then to whom it is sent and for which purpose. Here we also mention that whether the warranty of the item exists or not and on which date it is sent for servicing. Stock Quotation:When an organization requires particular items (products) for them, then at that time the purchase manager of the organization send a letter to the company for the requirement of items.

2.3 User Classes and Characteristics

This project will be used mainly by the warehouse manager or the person in charge of the strong room, who needs to be given a brief training for using this software before using it.

2.4 Operating Environment

This project of Fixed Asset Management System is aimed to be working on the following environment: Operating System Windows XP or higher. Framework 2.0 or higher 1GB free storage space (Minimum) 128 MB RAM (Minimum)

2.5 User Documentation

After the completion of the project, the user will be provided with a User Manual along with the product for his/her help in using the product efficiently and productively.

3. System Features
This section illustrates organizing the functional requirements for the product by the system features, the major services provided by the product.

3.1 Quotation Receive and Order:

3.1.1 Description:The main carried out here is the entry of the received quotations and then selecting the best one among all the quotations and finally, placing the order. 3.1.2 Stimulus/Response Sequences:-

User enters the received quotation data. Program gives the list of list of quotations ordered by the best one
first.

User selects any quotations according to his/her requirements. Program sends an e-mail to the selected organization and also
prints the order placed.

3.2 New Item Entry:

3.2.1 Description:The main function carried out here is the entry of the new item types that are bought and also includes the entry of the new category to which the item belongs. 3.2.2 Stimulus/Response Sequences:-

User enters the new item once. Then he/she enters the category to which it belongs by selecting it. If the category is also new then the user enters the name of the new
category.

Program then saves the data in the database and provides new item
codes and category codes as per the requirement.

3.3 Goods Receive:

3.3.1 Description:The main function carried out here is the entry of the goods that are received after placing the order.

3.3.2 Stimulus/Response Sequences: User enters the received item name and all other required data. Program then saves the data in the database.

3.4 Goods Issue:

3.4.1 Description:-

The main function carried out here is the entry of the goods that are issued from the stock to various departments in the organization.
3.4.2 Stimulus/Response Sequences: User enters the issued item name and all other required data. Program then saves the data in the database. After the return of the material, the user again enters the return is done or not what amount.

3.5 Goods Maintenance:

3.5.1 Description:The main function carried out here is the entry of the goods that are damaged and are sent outside the organization for the repair work.

3.5.2 Stimulus/Response Sequences: User enters the sent item name and all other required data. Program then saves the data in the database. After the return of the material, the again enters the return is done or not.

4. External Interface Requirements

4.1 User Interfaces:
The user interfaces are to be prepared using the platform of vb.Net (Visual Studio 2008). The standards that will be used for the designing of the interfaces are as follows: Text boxes o Border style = fixed single Buttons o Font Size = 11, bold o Style = Times New Roman Forms o Back Colour = 255,255,192 Labels o Font Size = 10, bold o Style = Times New roman

4.2 Software Interfaces:

The interfaces are connected to the database that stores all the details that are required for the working of the project as per the user requirement. The database is prepared using MS Access 2007.

5. Other Non-functional Requirements

5.1 Performance Requirements:
The project of Fixed Asset Management System will be having the following business logic which has been decided after consulting with the user that is the manager of the college. The contents of the data stored are according to the fields that are being maintained in the register, manually. The quotations are to be evaluated and arranged in an order showing the best one first. The software should provide the user with daily, weekly, monthly or yearly transactions as requested by the user. During the time of low availability of an item in the stock, it provides the user with the options to either send for a request or not. While requesting for an item, it should send an e-mail instantly to the concerned address. While checking the transactions, it should also show the opening balance. When a quotation is selected after evaluation, it should send the order to the concerned address via e-mail after taking the order details from the user.

5.2 Security Requirements:

For the security reasons, the user authentications are to be given as follows:

 Purchase Manager o Quotation section o Order section Warehouse Manager o Goods Receive section o Goods Issue section o Goods Maintenance section o New Item Entry Section