asdsadasd

Requirements
Specification
College Library Management System
dasd

Requirements Engineer: Andasdsadasrey Paklin 0dsadasasdasdasd242566

E-mail: paklin@lut.fi

Supervisor: Yana dsadadasdsSelioukova

E-mail: Yana.Selioukova@lut.fi
asd
Jan das
E-mail: jan.voracek@lut.fi

Lappeenranta, Finland
2002

Table of Contents
1. PROJECT DRIVERS........................................................................................................................3
1.1 Purpose........................................................................................................................................3
1.2 Scope............................................................................................................................................3
1.3 Abbreviations.............................................................................................................................4
1.4 Client, Customer and other Stakeholders.........................................................................4
1.5 Users of the Product................................................................................................................7
1.5.1 The Users of the Product................................................................................................................7
1.5.2 Viewpoints........................................................................................................................................7
2. PROJECT CONSTRAINTS...........................................................................................................11
2.1 Mandated Constraints............................................................................................................11
The Dream Team Corporation, Requirements Specification v1.1 23.09.2020
010752000 Team project, Project-Based Software Engineering

2.2 Implementation environment of the current system.....................................................11

2.2.1 System Interface............................................................................................................................11
2.2.2 User Interface.................................................................................................................................14
2.3 Partner applications........................................................................................................15
2.4 Schedule....................................................................................................................................16
2.5 Budget........................................................................................................................................16
3. FUNCTIONAL REQUIREMENTS.................................................................................................16
3.1 The Scope of the Work..........................................................................................................16
3.2 The Scope of the Product.....................................................................................................17
3.3 Functional requirements.......................................................................................................18
4. NON - FUNCTIONAL REQUIREMENTS....................................................................................19
4.1 Look and Feel Requirements...............................................................................................19
4.2 Usability Requirements.........................................................................................................19
4.3 Performance Requirements.................................................................................................19
4.4 Operational Requirements....................................................................................................19
4.5 Maintainability and Portability Requirements.................................................................20
4.6 Security Requirements..........................................................................................................20
4.7 Legal Requirements...............................................................................................................20
5. PROJECT ISSUES........................................................................................................................20
5.1 Open Issues..............................................................................................................................20
5.2 User’s Documentation and Training..................................................................................20
5.3 Waiting Room...........................................................................................................................20
6. REFERENCES:...............................................................................................................................21
7. Appendix 1. System Models..........................................................................................................22

1. Project Drivers
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.

2
The Dream Team Corporation, Requirements Specification v1.1 23.09.2020
010752000 Team project, Project-Based Software Engineering

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

3
The Dream Team Corporation, Requirements Specification v1.1 23.09.2020
010752000 Team project, Project-Based Software Engineering

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

SRS identifies each type of stakeholder:

Table 1. End - Users

Stakeholder Identification End - Users (librarians, patrons), College Library
Knowledge needed by the Basic knowledge of Microsoft Windows-based interfaces, Internet
project browser’s interfaces.
Necessary degree of Low. End – Users are not involved in software development, just in
stakeholder’s involvement some kinds of sociological surveys
Degree of influence for that High. Software to be developed to satisfy first of all the End-Users.
stakeholder

Table 2. Customer
Stakeholder Identification Customer (National Innovation Foundation)
Knowledge needed by the Customer’s requirements, Project plan, business modeling and
project forecasting.

4
The Dream Team Corporation, Requirements Specification v1.1 23.09.2020
010752000 Team project, Project-Based Software Engineering

Necessary degree of Middle. Customer supervises project, establishes budget

stakeholder’s involvement
Degree of influence for that High. Software development process may be canceled by Customer.
stakeholder

Table 3. Project Manager

Stakeholder Identification Project Manager (Fabian GARRIDO-MARTINEZ), The Dream Team
Corporation
Knowledge needed by the Project plan creating, computer skills.
project
Necessary degree of High. Project Manager supervises project, establishes team, provides
stakeholder’s involvement deadlines, negotiates with customer.
Degree of influence for that High. All development process requires constant control and decision
stakeholder making from Project Manager,

Table 4. Requirements Engineer

Stakeholder Identification Requirements Engineer (Andrey Paklin), The Dream Team
Corporation
Knowledge needed by the SRS creating, computer skills.
project
Necessary degree of High. Requirements Engineer summarizes requirements provided by
stakeholder’s involvement customer, updates them.
Degree of influence for that Middle. Requirements Engineer defines SRS under strict Customer
stakeholder and Project Manager control

Table 5. System Designer

Stakeholder Identification System Designer (Konstantin Vlasenko), The Dream Team
Corporation
Knowledge needed by the Computer-based Design tools, Internet technologies
project
Necessary degree of High. System Designer defines all software interfaces, how the
stakeholder’s involvement product will look like, providing success of product from the End –
Users point of view.
Degree of influence for that Low. System Designer will not use product to be developed in
stakeholder appropriate way.
Table 6. System Tester
Stakeholder Identification System Tester (Alex Kanavin), The Dream Team Corporation
Knowledge needed by the Computer-based Testing tools, Internet technologies, Testing
project requirements and specifications.
Necessary degree of Middle. System Tester is looking for mistakes in software and verify
stakeholder’s involvement product’s possibilities.
Degree of influence for that Low. System Tester will not use product to be developed in
stakeholder appropriate way.

Table 7. System Administrator

5
The Dream Team Corporation, Requirements Specification v1.1 23.09.2020
010752000 Team project, Project-Based Software Engineering

Stakeholder Identification System Administrator, College staff

Knowledge needed by the Strong computer skills, Internet and network technologies.
project
Necessary degree of Low. System Administrator is not involved in software development
stakeholder’s involvement process.