UAUT lLibrary SRS dDocument

UNITED AFRICAN UNIVERSITY OF TANZANIA
Department of Engineering and Information Technology
(COEIT)
Requirements Specification
College Library Management System
Version 1.0
Requirements Engineers: Shaban Rashid Kimokole
Evody Chalamila
Allen Akiledi
Brown Charles
Bedda Nyerere
Mpoki Chengerela
Supervisor: Dr. Ireneus Kagashe

Requirements Specification v1.0
Group III Third Year Software Engineering 17.01.2019
Table of Contents
REQUIREMENTS SPECIFICATION.................................................................................................1
REQUIREMENTS SPECIFICATION.................................................................................................1
College Library Management System.................................................................................................1
1. PROJECT DRIVERS.........................................................................................................................3
1. PROJECT DRIVERS.........................................................................................................................3
1.1 Purpose...........................................................................................................................................3
1.2 Scope..............................................................................................................................................4
1.3 Abbreviations.................................................................................................................................4
1.4 Client, Customer and other Stakeholders.......................................................................................5
SRS identifies each type of stakeholder:.............................................................................................5
1.5 Users of the Product.......................................................................................................................7
2. PROJECT CONSTRAINTS............................................................................................................12
2. PROJECT CONSTRAINTS............................................................................................................12
2.1 Mandated Constraints..................................................................................................................12
2.2 Implementation environment of the current system....................................................................13
2.3 Partner applications......................................................................................................................14
2.4 Schedule ......................................................................................................................................14
2.5 Budget..........................................................................................................................................15
3. FUNCTIONAL REQUIREMENTS................................................................................................15
3. FUNCTIONAL REQUIREMENTS................................................................................................15
3.1 The Scope of the Work................................................................................................................15
3.2 The Scope of the Product.............................................................................................................15
3.3 Functional requirements...............................................................................................................16
4. NON - FUNCTIONAL REQUIREMENTS....................................................................................17
4. NON - FUNCTIONAL REQUIREMENTS....................................................................................17
4.1 Look and Feel Requirements.......................................................................................................17
The ULM interfaces will the same for patrons and librarians based on C++/Java application.
Differences will depend on users’ functions. Patrons will have simple version of ULM without add,
remove and modify possibilities.........................................................................................................17
The ULM interface for system administrator will include C++/Java application, Command Line,
System files.........................................................................................................................................17
Web interface. This interface will provide search, request and renew procedures, connection with
other online databases. Web interface should work correctly in different browsers. .......................17
4.2 Usability Requirements................................................................................................................17
4.3 Performance Requirements..........................................................................................................18
Any interface between a user and ULM should have a maximum response time of 5 seconds........18
4.4 Operational Requirements...........................................................................................................18
2

The ULM should be used on any PC-compatible workstations with 50Mbytes free space on HDD
for library workstations (80Gbytes for server) and 32Mbytes RAM for library workstations
(256Mbytes for server).......................................................................................................................18
The ULM should be correctly implemented in different Internet browsers......................................18
The ULM should correctly interface if MS Access applications and MS SQL Server.....................18
4.5 Maintainability and Portability Requirements.............................................................................18
Changes (new patrons addition, password changes, database changes) must be verified once per
day at least...........................................................................................................................................18
The ULM should provide automatically notification to patrons by e-mail about item’s overdue,
reservation results, availability of reserved item and etc ..................................................................18
The ULM is expected to run under Windows 7 or higher ................................................................18
4.6 Security Requirements.................................................................................................................18
The ULM should provide databases’ modification only for librarians and system administrator
after authorization procedures.............................................................................................................18
Access to the ULM is permitted only for College student and staff after authorization procedures.18
4.7 Legal Requirements.....................................................................................................................19
Personal information should be protected..........................................................................................19
5.PROJECT ISSUES ...........................................................................................................................19
5.PROJECT ISSUES ...........................................................................................................................19
5.1 Open Issues..................................................................................................................................19
5.2 User’s Documentation and Training............................................................................................19
5.3 Waiting Room..............................................................................................................................19
6. REFERENCES: ..............................................................................................................................19
6. REFERENCES: ..............................................................................................................................19
7. APPENDIX 1. SYSTEM MODELS................................................................................................19
7. APPENDIX 1. SYSTEM MODELS................................................................................................19
Scenarios............................................................................................................................................19
1. PROJECT DRIVERS
1.1 Purpose
The purpose of this document is to familiarize reader with software, which is developed by
Group Three 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.
3

The intended audience for the SRS reading consists of system end-users (patrons), customer
engineers, software developers.
1.2 Scope
The Group Three was invited to develop College Library Management System for UAUT
Library. The software will reflect all the requirements defined by the customer.
UAUT College Library Management System (ULM) 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
ULM 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 ergonomically and easy-to-use.
1.3 Abbreviations
• ULM – UAUT Library management system
• SRS – Software requirements specification
• PC – Personal Computer
• HDD - Hard Disc Drive
• RAM – Random Access Memory
• IE – Microsoft Internet Explorer
4

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.
UAUT Library became the Group Three’s client in this project. The UAUT 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
SRS identifies each type of stakeholder:
Table 1. End - Users
Stakeholder Identification End - Users (librarians, patrons), College Library
Knowledge needed by the
project
Basic knowledge of Microsoft Windows-based interfaces, Internet
browser’s interfaces.
Necessary degree of
stakeholder’s involvement
Low. End – Users are not involved in software development, just in
some kinds of sociological surveys
Degree of influence for that
stakeholder
High. Software to be developed to satisfy first of all the End-Users.
5

Table 2. Customer
Stakeholder Identification Customer (UAUT)
project
Customer’s requirements, Project plan, business modeling and
forecasting.
Necessary degree of
Middle. Customer supervises project, establishes budget
stakeholder
High. Software development process may be canceled by Customer.
Table 3. Project Manager
Stakeholder Identification Project Manager, The Group Three
project
Project plan creating, computer skills.
Necessary degree of
High. Project Manager supervises project, establishes team, provides
deadlines, and negotiates with customer.
stakeholder
High. All development process requires constant control and decision
making from Project Manager,
Table 4. Requirements Engineer
Stakeholder Identification Requirements Engineer, The Group Three
project
SRS creating, computer skills.
Necessary degree of
High. Requirements Engineer summarizes requirements provided by
customer, updates them.
stakeholder
Middle. Requirements Engineer defines SRS under strict Customer
and Project Manager control
Table 5. System Designer
Stakeholder Identification System Designer, The Group Three
project
Computer-based Design tools, Internet technologies
Necessary degree of
High. System Designer defines all software interfaces, how the
product will look like, providing success of product from the End –
Users point of view.
stakeholder
Low. System Designer will not use product to be developed in
appropriate way.
Table 6. System Tester
Stakeholder Identification System Tester, The Group Three
Knowledge needed by the Computer-based Testing tools, Internet technologies, Testing
6

project requirements and specifications.
Necessary degree of
Middle. System Tester is looking for mistakes in software and verify
product’s possibilities.
stakeholder
Low. System Tester will not use product to be developed in
appropriate way.
Table 7. System Administrator
Stakeholder Identification System Administrator, College staff
project
Strong computer skills, Internet and network technologies.
Necessary degree of
Low. System Administrator is not involved in software development
process.
stakeholder
Middle. System Administrator will maintain and install product.
Table 8. Configuration Manager
Stakeholder Identification Configuration Manager, The Group Three
project
Computer-based Testing tools, Internet technologies, Testing
requirements and specifications.
Necessary degree of
High. Configuration Manager responsible for project repository,
project web pages.
stakeholder
Middle. Configuration Manager must follow job description and
deadlines, to prove his/her quality.
1.5 Users of the Product
1.5.1 The Users of the Product
Potential Users of the College ULM are librarians and patrons.
7

Table 8. Librarians
User name College Librarians
User role To maintain College ULM (add, delete, renew items and update
databases)
Subject matter
experience
Master. College had the same management system in card-based
form. All features of the old database are presented in new
software product
Technological
experience
Journeyman*, as less. Basic computer skills are obligatory.
Intellectual
abilities/disabilities
Middle intellectual abilities
Age group Adult age 25-65 (65 years old- is a pension age)
Table 9. Patrons
User name Library patrons
User role To use the College ULM System in practice (from library or any
place, where Internet connection is available)
Subject matter
experience
May ranges from novice to master.
Technological
experience
May ranges from novice to master, but basic computer skills and
Internet working experience are obligatory.
Intellectual
abilities/disabilities
May range in wide band
Age group 16-65 (College students, professors, teachers, other staff)
*) - journeyman, some kind of human experience degree, it’s situated between novice and master
1.5.2 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
8

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 mechanism for linking
requirements with their sources. Let us define the following model of stating a
viewpoint PREview:
The viewpoint name.
The viewpoint focus.
The viewpoint concerns.
The viewpoint sources.
The viewpoint requirements.
Table 10: Patrons viewpoint
Name Patron
Focus Searching, lending, requesting and renewing library items
Concerns To familiarize patron with software functions
Source Requirements specification from the Customer
Requirements
 search for the books and other items
 renew books and other items
 browse catalogs
 reserve unavailable items
 subscribe for info about new acquisitions
 access to other databases (interlibrary loans, online
databases)
Table 11: Project manager viewpoint
Name Project manager
Focus Team establishment, project plan creating, control software
development process, follow schedule provided by the Customer
Concerns College ULM creation according to deadlines
Source Job description
Requirements  Follows deadlines and budget
9

 Responsible for all deliverables
 Easy communication with team and the Customer
 All project stages should be fully documented
 MS Word
 Internet connection
 MS IE, Netscape or Opera browsers
Table 12: Requirements engineer viewpoint
Name Requirements engineer
Focus
Requirements specification creating, customer interviewing,
collect and specify requirements
Concerns Constantly updating SRS accordingly customer’s requirements
Source Requirements specification from the Customer
Requirements
 Requirements from patrons, Customer and team members
should be prepared
 Requirements should be clear, complete and consistent
 MS Word
Table 13: System Designer viewpoint
Name System Designer
Focus Design user interfaces, creation of design specification document
Concerns Formal design
Source Project plan, requirements specification from the Customer
10

Requirements
 Clear and complete SRS
 Adobe Photoshop
 MS Word
Table 14: System Tester viewpoint
Name System Tester
Focus
Design testing strategies, creation testing documents, realize test
cases
Concerns Validation of software quality
Source
Requirements specification from the Customer
ISO 9001 Standards
Requirements
 Knowledge of software to be tested
 Testing tools
 MS Word
Table 15: System Administrator viewpoint
Name System Administrator
Focus Database installation, maintenance of College ULM
Concerns College ULM maintenance and troubleshooting
11

Source Inner SRS from Requirement Engineer, Internet and LAN specifications
Requirements
 Licensed software with automatically update tools
 MS Word;
Table16: Configuration Manager viewpoint
Name Configuration Manager
Focus Configuration and change management, project repository control, project
web-pages maintenance and follow calendar of events
Concerns Change control to achieve Quality assurance required by the Customer
Source Inner company’s SRS
Job description
Requirements
 All hardware and software should be available
 Adobe Acrobat Reader
2. PROJECT CONSTRAINTS
2.1 Mandated Constraints
Next items must be used to verify software:
i. For user home PC and library workstation
Hardware
 PC with PentiumΙ processor and higher
 50Mbytes free space on HDD
 32Mbytes RAM
Software
 MS Windows 7 or higher
 Mac OSX 10.10.0 or higher
 MS IE, Netscape or Opera browsers with Java2 support
ii. For Server
Hardware
12

 PC with Pentium ΙV and higher
 256Mbytes RAM or higher
 80Gbytes free space on HDD
Software
 MS SQL server and MS Access (Database server)
 MS Internet Information Server (Web server)
 Java Development Kit 1.2 and higher
 Development environment – Java2 programming language
2.2 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.
Library workstation Remote PC
Web - Interface
13

Integrated Databases
2.3 Partner applications
There are some applications that are not part of the product but with which the product will
collaborate. This section can be completed, by including written descriptions, models or
references to other specifications.
 ISO/OSI model
 TCP/IP specifications
 LAN’s specifications
 SMTP/POP e-mail protocols description
The physical work environment constrains the way that work is done. The product should
overcome whatever difficulties exist, however you might consider a redesign of the workplace
as an alternative to having the product compensate for it.
2.4 Schedule
The Schedule is presented by the Project Manager, strictly followed by the Group Three and is
proved by the Customer. The project was started at the beginning of the October.
Deliverable Deadline Time Extended Objective
Project Plan December 20, 2018 10:00 NO Reached
Requirements
documentation
December 20, 2018 10:00 NO Reached
Implementation
Plan
December 26, 2018 12:00 YES
Project binder December 31, 2018 12:00 YES
14

2.5 Budget
Budget is not completely assigned to the Project.
3. FUNCTIONAL REQUIREMENTS
3.1 The Scope of the Work
At the beginning of November, 2018 the Group Three was represented a task to develop a
College Library Management System by UAUT Library. Software to be developed should be
provide all necessary action for library staff and patrons.
There are several motivations to order new computer-based College ULM:
1. To modernize College Library database, where data was stored in a card-based catalog
2. To optimize librarians’ work and time
3. To join small Access-based database, where library has stored information about digital
items (software, music)
4. To expand services of library and patron’s possibilities
5. To check ability of commercial using of library management systems.
The ULM will allow remote access to library database via Internet only for patrons after
authorization procedures. The patrons could search, renew items, and send requests. The
College ULM will provide remote access to other databases (interlibrary loans, online
databases).
3.2 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;
15

- 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.
3.3 Functional requirements
Functional requirements are the following:
1. The ULM should store all information about librarians and patrons, their access keys,
priority and etc.
2. The ULM should store all information about items and patrons in two separated databases
3. The ULM allow searching items by author, title or keywords
4. The ULM should support 500 patrons and 1000 requests/min simultaneously.
16

5. The ULM should allow librarians to add, delete and modify items in database, and check
availability of the items.
6. The ULM should generate request’s reports for librarians every day, on base of which
librarians could make decisions about acquiring or retirement the item
7. The ULM should create notification and send to patrons by e-mail automatically after
item’s overdue
8. The ULM should allow patrons to get their personal information and status.
9. The ULM should provide to search, request and renew items either from the library
computers (ULM application) or from outside the library through College site(web-based)
though the Internet.
10. The ULM should provide access to previous Access-based database, online databases
11. The ULM will be integrated with other colleges and universities and allow interlibrary
loans
4. NON - FUNCTIONAL REQUIREMENTS
4.1 Look and Feel Requirements
According to the Customer requirements, the College ULM should include following interfaces:
 The ULM interfaces will the same for patrons and librarians based on C++/Java
application. Differences will depend on users’ functions. Patrons will have simple version of
ULM without add, remove and modify possibilities.
 The ULM interface for system administrator will include C++/Java application,
Command Line, System files
 Web interface. This interface will provide search, request and renew
procedures, connection with other online databases. Web interface should work correctly in
different browsers.
4.2 Usability Requirements
As it was mentioned above, product’s users are an adults, that’s why there are no special
requirements to simplicity of system.
 Ergonomically and clear interface
 The interface should contain prompts and help to avoid making mistakes
17

 The product should be used by people with no training
4.3 Performance Requirements
 Any interface between a user and ULM should have a maximum response time
of 5 seconds
 The response should be fast enough to avoid users’ response collisions
 The ULM should be available for use 24 hours per day, 365 days per year.
 The ULM should support 500 patrons and 1000 requests/min simultaneously
4.4 Operational Requirements
 The ULM should be used on any PC-compatible workstations with 50Mbytes
free space on HDD for library workstations (80Gbytes for server) and 32Mbytes RAM for
library workstations (256Mbytes for server)
 The ULM should be correctly implemented in different Internet browsers
 The ULM should correctly interface if MS Access applications and MS SQL
Server
4.5 Maintainability and Portability Requirements
 Changes (new patrons addition, password changes, database changes) must be
verified once per day at least
 The ULM should provide automatically notification to patrons by e-mail about
item’s overdue, reservation results, availability of reserved item and etc
 The ULM is expected to run under Windows 7 or higher
4.6 Security Requirements
 The ULM should provide databases’ modification only for librarians and
system administrator after authorization procedures
 Access to the ULM is permitted only for College student and staff after
authorization procedures
18

4.7 Legal Requirements
 Personal information should be protected
 The ULM should comply with quality assurance standards
5. PROJECT ISSUES
5.1 Open Issues
Requirements elicitation haven’t yet completed, thus SRS are constantly updated by
Requirements Engineer.
5.2 User’s Documentation and Training
User documentation is under construction now and will be available accordingly to schedule.
System Designer will present guide of User’s Interfaces.
5.3 Waiting Room
Requirements that will not be part of the agreed product. These requirements might be included
in future versions of the product.
6. REFERENCES:
[1] Google.com
[2] UAUT Librarian
7. APPENDIX 1. System Models
Scenarios
The following stages describe main scenarios performed by the ULM:
- Login to the system;
19

- Add, Remove, Modify item;
- Check item for availability;
- Add, Remove, Modify user information;
- Overdue report generating;
- Search item;
- View information;
- Renew book.
Scenario 1
Name Login (Open program)
Actors Patron or Librarian
Preconditions
Existence of database and correctly installed web based server,
knowledge of standard Windows environment
Description
Library user or Librarian opens program using browser, to logon to
system he/she must enter username and password.
End Result Opened program, user see logon page.
Scenario 2
Name Add, Remove, Modify item
Actors Librarian
Preconditions
Existence of database and correctly installed web based server, user
logged on with librarian privileges.
Description
Librarian using web interface adds, removes or modifies (e.g. quantity)
information about item
End Result Added, Removed or Modified information about item in database
20

Scenario 3
Name Check for availability
Actors Librarian, patrons
Preconditions
logged on with librarian privileges or patrons’ rights.
Description
Through web interface librarian using item call number searches if this
item is available
End Result Returned status of item
Scenario 4
Name Add, Remove, Modify user information
Actors Librarian, System Administrator
Preconditions
Description
Using web interface forms for librarian or system administrator to add,
remove or modify information about user
End Result Added, Removed or Modified information about user in database
Scenario 5
Name Generate overdue report
Actors Librarian, the ULM
Preconditions
Description
Librarian defines overdue period for every category of item using web
interface or installed college ULM
End Result List of users and overdue items
Scenario 6
Name Search item
Actors Patron or Librarian
Preconditions
logged on to system.
Description
Patron or Librarian using web interface searches for item using author or
item’s title.
End Result List of found items are shown
21

Scenario 7
Name View information
Actors Patron
Preconditions
logged on to system.
Description
Paron using web interface view his/her status (User name, address,
number of taken books, requested items)
End Result User information are shown
Scenario 8
Name Renew item
Actors Patron
Preconditions
logged on to system, at least one item taken.
Description
User selects items he/she want to renew, using Renew button he/she
renews selected items
End Result Status are shown (renewed or not)
22

UAUT lLibrary SRS dDocument

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Similar to UAUT lLibrary SRS dDocument

Similar to UAUT lLibrary SRS dDocument (20)

Recently uploaded

Recently uploaded (20)

UAUT lLibrary SRS dDocument