19-05-2012, 01:52 PM
Requirements Specification
Requirements Specification.doc (Size: 186 KB / Downloads: 327)
1.1 Purpose
The purpose of this document is to familiarize reader with software, which is developed by Dream Team Corporation. Specification describes all hardware and software requirements for product, behavior of it and its components. Software Requirements Specification (SRS) allows to verify the customer that all his requirements are observed and implemented correctly by developer.
The intended audience for the SRS reading consists of system end-users (patrons), customer engineers, software developers (defined by Ian Sommerville for system requirements)[1].
1.2 Scope
The Dream Team Corporation was invited to develop College Library Management System for National Innovation Foundation (N.I.F). The software will reflect all the requirements defined by the customer.
College Library Management System will allow to perform all necessary procedures for librarians and patrons. According to customer requirements the software to be developed will consist of three databases:
Item’s database (books, journals, magazines, newspapers, diploma thesis, etc)
Patron’s database
a small Access-based database with information about digital items, that College has (software, music) integrated with Item’s database
LMS will also provide all necessary services for databases such as creating, deleting, updating and searching information. Patrons will be able to access to the library site (web-based) through the Internet or through the library’s LAN-connected computers, scattered throughout the library for sending request, receiving information about current status of the books or renewing them. The design of product interface to be developed will be supported by Microsoft IE, Netscape Navigator and Opera browsers. User interfaces will be ergonomical and easy-to-use.
1.3 Abbreviations
• LMS – Library management system
• SRS – Software requirements specification
• PC – Personal Computer
• HDD - Hard Disc Drive
• RAM – Random Access Memory
• LUT – Lappeenranta University of Technology
• IE – Microsoft Internet Explorer
1.4 Client, Customer and other Stakeholders
1.4.1 The client is the person/s who pay for the development, and owner of the delivered system.
National Innovation Foundation became the Dream Team Corporation’s client in this project. The N.I.F will receive the final acceptance of the system, and thus must be satisfied with the developed system or not.
All client remarks will be improved immediately. Product deliverables have appropriated project schedule, approved by the client.
1.4.2 The customer is the person/s who will buy the product from the client.
In our case, the roles of the client and the customer are filled by the same company.
1.4.3 Stakeholders include:
End - Users (detailed in section 1.5)
Customer
Project Manager
Requirements Engineer
System Designer
System Tester
System Administrator
Configuration Manager
Viewpoints
This project consists of several stakeholders, which were defined above. According to Ian Sommerville’s article ‘Viewpoints for requirements elicitation: a practical approach’ [2] software requirements can be described by using PREview model. The viewpoint model is deliberately flexible and informal. Viewpoints can be adapted to specific organizational practice and standards as can the notations used to describe system requirements. Viewpoints may be used during the early stages of a requirements engineering process as a structuring mechanism for requirements elicitation and analysis. Identifying viewpoints and organizing information around them at this stage reduces the possibility that critical information will be missed during requirements elicitation and provides a traceability.
Implementation environment of the current system
This part of the specification will provide enough information about the environment for the designers to make the product successfully interact with its surrounding technology.
Here will be shown a diagram, with some kind of icon to represent each separate device or person (processor) and interfaces between the processors
FUNCTIONAL REQUIREMENTS
3.1 The Scope of the Work
At the beginning of October 2002 the Dream Team Corporation was represented a task to develop a College Library Management System by National Innovation Foundation (N.I.F). Software to be developed should be provide all necessary action for library staff and patrons
The Scope of the Product
Features provided by the library management system:
1. Store necessary information about items in the library:
- Author;
- Item’s title;
- Call number;
- Published place;
- Year of publication
- Location in the library;
- Number of copies
- Current status
- Keywords
2. Allow a search item by author, title or keywords
3. System will provide librarian to add, modify, and remove items to/from the library database, and check availability of the item.
4. System will allow patron to get information about his/her status after authorization procedures:
- User name
- User address
- Student number
- Number and information about checked out items
- Requested items information
5. Notification by e-mail automatically after item’s overdue.
6. Possibility to search, renew and order items though the Internet after authorization procedures.
7. Possibility to search and request items in the interlibrary loans, online databases through Internet.