Software Requirements Specification

For

Asset Management System

(A.M.S)

Prepared by: Akhil Batch

Company: Akhil Reddy Technologies

Date: 17 - 03- 2015

Table of Contents

Table of Contents............................................................................................................................ i

Revision History............................................................................................................................. ii

1. Introduction.............................................................................................................................. 1

1.1 Purpose................................................................................................................................. 1

1.2 Document Conventions........................................................................................................ 1

1.3 Intended Audience and Reading Suggestions........................................................................ 1

1.4 Project Scope........................................................................................................................ 1

1.5 References............................................................................................................................ 1

2. Overall Description.................................................................................................................. 2

2.1 Product Perspective.............................................................................................................. 2

2.2 Product Features................................................................................................................... 2

2.3 User Classes and Characteristics........................................................................................... 3

2.4 Operating Environment......................................................................................................... 3

2.5 Design and Implementation Constraints................................................................................ 3

2.6 User Documentation............................................................................................................. 3

2.7 Assumptions and Dependencies........................................................................................... 4

3. System Features....................................................................................................................... 5

3.1 Asset Management................................................................................................................ 5

3.2 Asset Process...................................................................................................................... 6

3.3 Analysis…………………………………………………………………………………….8

4. External Interface Requirements........................................................................................... 9

4.1 User Interfaces..................................................................................................................... 9

4.2 Hardware Interfaces........................................................................................................... 16

4.3 Software Interfaces............................................................................................................. 16

4.4 Communications Interfaces................................................................................................ 16

5. Other Nonfunctional Requirements..................................................................................... 17

5.1 Performance Requirements................................................................................................. 17

5.2 Safety Requirements........................................................................................................... 17

5.3 Security Requirements........................................................................................................ 17

5.4 Software Quality Attributes................................................................................................ 17

6. Other Requirements.............................................................................................................. 18

Appendix A: Analysis Models..................................................................................................... 19

Appendix B: Issues List............................................................................................................... 20

Revision History

Name	Date	Reason For Changes	Version

1. Introduction

1.1 Purpose

Asset Management System is a systematic plan for and ongoing oversight of the management of one or more housing project(s) in furtherance of the projects’ goals and the organization’s mission.

How to manage?

1. Plan: orderly, detailed method linking the various parts of the whole system, formulated

beforehand to attain some object.

2. Conduct: supervise by using one’s skills and knowledge (to conduct a sales campaign)

3. Direct: delegate and issue general orders or instructions; implies less supervision of

actual details (e.g., to direct construction of a dam)

4. Control: implies firm direction by regulation or restraint

5. Generally, good management involves the ability to:

Observe the situation
Analyze the data
Diagnose problems
Prioritize the problems
Know and apply the appropriate remedy for the diagnosed problems

1.2 Intended Audience and Reading Suggestions

This document is intended for:-

· Client

· Project Manager

· Developers

· Test managers

· Test engineers

· Technical writers

· Users

Documentation writers

This document also contains details about the scope of the project, the hardware and software requirements and the overall description of the project.

AMS is complete software that helps you maintain records of assets. All events pertaining to an asset can be recorded in AMS, for example transferring, sale, disposal, adding, depreciation, etc. Recording annual maintenance contracts, warranties and insurance details help generating timely alerts for proper management of assets. Printing of reports and maintaining record of physical verification. This software can be used to keep track of all your company assets, including furniture, office equipment, computers and many more.

Create your new Asset Tag which helps in unique identification
Use view option to see assets grouped by different fields such as vendor, manufacturer, by status.
Track maintenance, repair history and other expenses.
Calculate Monthly and Annual Depreciation Tables.
Use the Find/Search Asset option for finding assets and its details.
Includes many useful reports.
Can import spreadsheet and/or CSV files
Internet links to each record.
Automatically track changes in Asset assignment or Location

1.4 References

2. Overall Description

2.1 Product Perspective

The AMS is designed specifically for the client to maintain their asset register and perform all associated accounting functions for assets. The system consists of a series of menu screens that the user completed to carry out the various accounting transactions and related calculations. A full set of reports could be produced at any time, both for the current financial year and the prior year. A detailed audit trail shall be maintained and all transactions were time-stamped.

2.2 Product Features:

The major functions of this product are:

· It keeps track on overall activities done on an asset.

· It eliminates paper work and organizes records.

· It keeps track of all the operations being carried out pertaining to an asset including addition, updation to which the task is assigned to etc.

· It helps in computing depreciation of assets.

· AMS can automatically create log entries describing any changes in status, transfer.

· It helps to create various reports.

· It helps in maintaining Assets Register.

· Interact with different company assets.

Process Flow Diagram

Pre Event

Post Event

Event Creation

Event process

Analysis

Database

Process Flow

Data Flow

2.3 User Classes and Features

This application has three classes of users, namely

Administrator: The primary duty of the administrator is to create and manage the all the events, to give privileges to employee for different events and also manage the clients.

Employees: Involved in management and tracking of various asset details

Clients: They are the companies who are benefited by this software for overall management of their assets.

User Features

· Browse / View / Search Employees, Assets and Parts

· New Employee (via Register)

· Update Your Own Employee Details

· Employee History

· New Requisition

· New Request For Quote

· New Supplier

· Update Requisition or RFQ

· Deactivate/Activate Requisition or RFQ

· Timesheets Import/Update/Delete

· New Asset (depreciated in derived version)

· Request Transfers (including postdated)

· Sign In / Sign Out of General Assets and Surplus

· Asset Calendar / History

· Assets and Parts Report (HTML Spreadsheet - Import into Excel)

· Sign Out Report

· Confirmation Report (without e-mail capability)

· Print

· Help

Administrator Features

· Update Any Employees Details

· Change Employee Access Level or Reset Password

· Update Asset

· Approve and Perform Transfers

· Erase Employees, Assets, Parts and Sign Outs

· Add/Remove Parts

· Add/Remove Projects

· Add/Remove IPs (depreciated in derived version)

· Employees Report (HTML Spreadsheet - Import into Excel)

· Timesheets Report

· IP Report (depreciated in derived version)

· Confirmation Report (with e-mail capability)

· Setup (On First Run Only)

· Importing Employees, Assets and Timesheets from a spreadsheet or database

2.4 Operating Environment

Software requirements:

Operating System: Windows XP

Front End: J2EE Components ( JSP, XML, Struts, Swings, EJB)

Back end: Oracle9i

Client: IE 4.0 and above , Mozilla Firefox, Netscape navigator

Server: Apache Tomcat 5.5.20 (Web server)

Hardware requirements:

At least 1GB of Hard disk space

128 MB RAM

Processor: P II or above

2.5 User Documentation

Software Requirements Specification.
Test plan
Use case
Test case
Requirements Traceability Matrix
Defect Report

3. System Features

ASM keeps track of all your company assets, including furniture, office equipment, computers and more

Create your own Asset tags.
Track assets, maintenance, repair history and other expenses.
Calculate Monthly and Annual Depreciation Tables.
Use the search option to find missing assets.
Includes many useful reports.
Attach images, files and Internet links to each record.
Automatically track changes in Asset assignment or Location and Handles multiple locations.

Import CSV files and Microsoft Excel spreadsheet data into Asset Management.

3.1 Asset Management

3.1.1 Description and Priority

This process handles the adding, deleting, updating, transferring, auditing, maintaining history of assets, suppliers, parts, employees,surplus, retired and locations

3.1.2 Stimulus/Response Sequences

a. Login Module: Every user enters through login page which checks for user validity and allows the user to navigate

User Action : - User types valid username and password.

System Response: - Validates the username and password and it permits further processing

User Action : - User types invalid username or password.

System Response: - An Error Message will be displayed

User Action : - User Click

System response : - Home page open

b. We Manage: This is the main page which gives all the information about AMS

c. Assets:

· This module gives complete description about all the assets managed.

· It displays the types of assets present and the supplier associated with it.

· Each asset can be uniquely identified using asset _tag

· The details of the current owner of the asset is displayed

· An employee is assigned to manage the processing of asset

d. Retired:

· These are the assets which are disposable whose lifetime is expired

· Retired asset name, Date of disposal, Model, Registration Number and description shall be displayed

· These disposable assets can proceed for sale which is profitable

· The sale information of retired assets will be maintained

e. Surplus

· An asset currently not in use becomes surplus

· When an asset becomes surplus these are the operations performed

· Employee requests an Asset Transfer to Surplus on the system

· Administrator approves the request

· Employee receives a confirmation message

· Employee or third party moves asset into storage

· To reassign an asset, searching is carried out and it is transferred to assets and an employee is assigned again to manage it

f. Parts

Parts are the components of the existing product
This module gives description about the parts such as category, total products, total part and total cost
Each part has part_tag for unique identification, Number of parts used, Number of parts left, total part and total cost and also gives supplier details

g. Employees

· This module gives the information about all the employees who are active/inactive and their responsibilities in the organization

· Each employee is assigned the responsibilities of managing the assets like adding, updating, transferring, deleting, etc.,

h. Location

· Location gives the details as to where the assets are placed

· The details of the location such location number, location name, address and the employee_id who manages it will be given

i. Supplier

· This module gives the list of suppliers

· A supplier gives requisition for supply of product whose detail will be stored.

· When the requisition is processed, supplier gives the quotation.

· Once the quotation is approved further processing will take place

· Once the supplier supplies the details of the product – the product is assigned to the projects

j. Reports

· Various reports are generated accordingly such as Asset report, Summary part report, Employee report, Transfer report, verification report, IP report, Time sheet report, etc.,

k. Timesheets

· Time sheet is maintained for asset transfer which gives information such as start date, end date, assigned employee etc.,

l. Depreciation

· The cost of an asset decreases with respect to time which is Depreciation. It is calculated using depreciation rate for a particular asset according to company act.

· Methods used for depreciation are straight line method, WDV, reducing balance method

3.1.3 Functional Requirements

Assets Types

Retired Supplier

Surplus

Parts Active

AMS Employees Inactive

Location

Supplier Requisition

Reports RFQ

Timesheets Projects

Depreciation

4. External Interface Requirements

4.1 User Interfaces

Ø First time when the application is opened, the cursor should appear in the username text box.

Ø Help button will appear in every screen to guide the user.

Ø Here we used Shortcut keys like ctrl+h for help, ctrl+p for print, Alt+H for help, ctrl+H for history ‘TAB’ key for moving cursor to the next field etc.

Ø If the user enters any invalid input, a pop up message will appear to alert the user.

Ø The screen will follow the standard GUI format, and navigation rules.

Ø User interfaces are needed for almost all modules namely, User login, Event creation, Questionnaire creation, Questionnaire preview, Questionnaire display during the event, Display of textual and graphical reports, Etc.

4.2 Database Design

Screen Shots

1. Login

2. Main Menu

3. Assets

4. Asset-Type

5. Asset-supplier

6. Details

7. Update

8. Transfer

9. Signout

10. History

10. Audit

11. Date Management

12. Erase

13. Retired

14. Surplus

15. Parts

16. Parts—List & Details

18. Purchase Details of Parts

19. Employees

20. Locations

21. Suppliers

22. Suppliers Details

23. Purchase Details

24. Requisitions

25. Transfer Report

26. Depreciation

Depreciation Calculator

Cost Method Category Description Asset Tag Dep’n Rate

Period	2004	2005	2006	2007
1
2
3
4
5
6
7
8
9
10
11
12

Annual
Cumulative
Net

Period Beginning Period Ending Total Period

4.2 Hardware Interfaces

Ø The communications protocol used is HTTPS.

Ø The application should interact with printers (for the analysis (reports) part).

4.3 Software Interfaces

This software should interact with oracle8i database, Operating systems like Windows XP/2003/ME, Linux, Solaris, And all the standard support libraries. The communications will be based on the HTTPS and TCP/’IP protocol.

4.4 Communications Interfaces

The Client applications, which interact with this application can include IE 4.0 or above, Netscape navigator, Mozilla Firefox 2.0. The communications will be based on TCP/IP and HTTPS protocols.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The application is expected to have response time of 4milli seconds under normal load conditions.

The application is expected to handle a normal load of 1000 users per hour. And under double the load, the application is expected to have a response time of 10 milli seconds. This speed is justifiable when compared to the response time of common web applications.

5.2 Safety Requirements

The application should interact only with those web applications which have been digitally certified for security by standard certifying agencies. Prevent the interaction with third party applications from un-trustable sources.

5.3 Security Requirements

Firewalls are required to be used along with the application to safeguard the data. Certification for security is needed to be carried out for this application. Data transfer is to be made secure by encrypting the sent data. User name and password must be strengthened by setting ranges for user name and password. (e.g.,: between 6 and 15 characters).

5.4 Software Quality Attributes

1. Adaptability

2. Flexibility

3. Maintainability

4. Portability

5. Reliability

6. Reusability

7. Robustness

6. Other Requirements

This application is intended to be used by international users. International language and time standards are to be followed while developing the application. The application was to be registered under the patent and copyright laws.

Appendix B: Issues List

No issues till now.

AKHIL REDDY ONLINE SELENIUM TRAININGS

Friday, 7 August 2015

FUNCTIONAL REQUIREMENT SPECIFICATION(Real time)