BCS 051 (INTRODUCTION TO SOFTWARE ENGINEERING)

Question 1:
Develop SRS as per IEEE standard for Library Information System. Make assumptions
wherever necessary.
Answer:
1. Introduction
1.1 Purpose
The main objective of this document is to illustrate the requirements of the project Library
Management system, The document gives the detailed description of the both functional
and non-functional requirements proposed by the client. The purpose of this project is to
provide a friendly environment to maintain the details of books and library members. The
main purpose of this project is to maintain easy circulation system using computers and to
provide different reports. This project describes the hardware and software interface
requirements using ER diagrams and UML diagrams
1.2 Document Conventions Entire document should be justified.
Convention for Main title
• Font face: Times New Roman
• Font style: Bold
• Font Size: 14
> Convention for Sub title
• Font face: Times New Roman

• Font style: Bold

• Font Size: 12 Convention for body
• Font face: Times New Roman
Font Size: 12

1.3 Scope of Development Project Library Management System is basically updating the
manual library system into an internet-based application so that the users can know the
details of their accounts, availability of books and maximum limit for borrowing. The project
is specifically designed for the use of librarians and library users. The product will work as a
complete user interface for library management process and library usage from ordinary
users. Library Management System can be used by any existing or new library to manage its
books and book borrowing, insertion and monitoring It is especially useful for any
educational institute where modifications in the content can be done easily according to
requirements The project can be easily implemented under various situations, We can add
new features as and when we require, making reusability possible as there is flexibility in all
the modules The language used for developing the project is Java as it is quite advantageous
than other languages in terms of performance, tools available, cross platform compatibility,
libraries, cost freely available and development process,

1.4 Definitions, Acronyms and Abbreviations

JAVA-> platform independence
SQL> Structured query Language
ER > Entity Relationship
UML Unified Modeling Language
IDE-> Integrated Development Environment
SRS Software Requirement Specification
ISBN-> International Standard Book Number
IEEE Institute of Electrical and Electronics Engineer

1.5 References Books

• Software Requirements and Specifications:
A Lexicon of Practice, Principles and Prejudices (ACM Press) by Michael Jackson
• Software Requirements (Microsoft Second Edition By Karl E. Wiegers Software
Engineering: A Practitioner's Approach Fifth Edition By Roger S. Pressman)

Websites
• http://www.slideshare.net/
• http://ebookily.net/locsrs-library-management system/
2. Overall Descriptions
2.1 Product Perspective
Use Case Diagram of Library Management System

This is a broad level diagram of the project showing a basic overview. The users can be
either staff or student. This System will provide a search functionality to facilitate the
search of resources. This search will be based on various categories viz. book name or
the ISBN. Further the library staff personnel can add/update the resources and the
resource users from the system. The users of the system can request
issue/renew/return of books for which they would have to follow certain criteria

2.2Product Function
Entity Relationship Diagram of Library Management System
The Online Library System provides online real time information about the books available
in the Library and the user information. The main purpose of this project is to reduce the
manual work. This software is capable of managing Book Issues, Returns,
Calculating/Managing Fine, Generating various Reports for Record-Keeping according to end
user requirements. The Librarian will act as the administrator to control members and
manage books. The members status of issue/return is maintained in the library database.
The member's details can be fetched by the librarian from the database as and when
required. The valid members are also allowed to view their account information
2.3 User Classes and Characteristics
The system provides different types of services based on the type of users Member
Librarian). The Librarian will be acting as the controller and he will have all the privileges of
an administrator. The member can be either a student or staff of the university who will be
accessing the Library online.
The features that are available to the Librarian are:
• A librarian can issue a book to the member,
• Can view the different categories of books available in the Library
• Can view the List Of books available in ach category
• Can take the book returned from students
• Add books and their information to the database
• Edit the information of existing books
• Can check the report of the existing books
• Can check the report of the issue books
• Can access all the accounts of the students
The features that are available to the Members are:
• Can view the different categories of books available
• Can view the List of books available in each category
• Can own an account in the library.
• Can view the books issued to him Can put a request for a new book
• Can view the history of books issued to him previously
• Can search for a particular book

2.4 Operating Environment

The product will be operating in windows environment. The Library Management
System is a website and shall operate in all famous browsers, for a model we are
taking Microsoft Internet Explorer Google Chrome and Mozilla Firefox.Also it will be
compatible with the IE 6.0. Met of the features will be compatible with the Mozilla
Firefox & Opera 7.0 or higher version. The only requirement to use this online product
would be the internet connection. The hardware configuration include Hard Disk 40
GB, Monitor: 15" Color monitor, Keyboard 122 keys. The basic input devices required
are keyboard, mouse and output devices we monitor, printer etc.
2.5 Assumptions and Dependencies The assumptions are:
• The coding should be error free.
• The system should be user-friendly so that it is easy to use for the users.
• The information of all users, books and libraries must be stored in a database
accessible by the website.
• The system should have more storage capacity and provide fast access to the
database.
 • The system should provide search facility and support quick transactions.
• The Library System is running 24 hours a day.
• Users may access from any computer that has Internet browsing capabilities and an
Internet connection.
• Users must have their correct usernames and passwords s enter into their online
accounts and do actions.

The dependencies are:

• The specific hardware and software due to which the product will be run.
• On the basis of listing requirements and specification the project will be developed
and run
• The end users (admin) should have proper understanding of the product.
• The system should have the general report tired.
• The information of all the users must be stored in a database that is accessible by the
Library System.
• Any update regarding the book from the library is to be recorded to the database and
the data entered should be correct

2.6 Requirement Software Configuration

This software package is developed using java as front end which is supported by sun
microsystem, Microsoft SQL Server as the back end to store the database Operating System:
Windows NT, windows 98, Windows XP Language: Java Runtime Environment, Net beans
7.0.1 front end) Database: MS SQL Server (back end)

Hardware Configuration

Processor: Pentium(R)Đual-core CPU

Hard Disk: 40GB
RAM: 256 MB or more
2.7 Data Requirement

The inputs consist of the query to the database and the output consists of the solutions for
the query. The output also includes the user receiving the details of their accounts. In this
project the inputs will be the queries as fired by the users like create an account, selecting
books and putting into account. Now the output will be visible when the user requests the
server o get details of their account in the form of time, date and which books are currently
in the account.

3. External Interface Requirement

3.1 GUI

The software provides good graphical interface for the user and the administrator can
operate on the system, performing the required task such as create, update, viewing the
details of the book.
It allows user to view quick reports like Book Issued/Returned in between particular time. It
provides stock verification and search facility based on different criteria.
The user interface must be customizable by the administrator
All the modules provided with the software must fit into this graphical user interface and
accomplish to the standard defined.
The design should be simple and all the different interfaces should follow a standard
template.
The user interface should be able to interact with the user management module and a part
of the interface must be dedicated to the login/Logout module
Login Interface:
In case the user is not yet registered, he can enter the details and register to create his
account. Once his account is created he can 'Login' which asks the user to type his username
and password. If the user interact either his username or password incorrectly then an error
message appears.

Search:
The member or librarian can enter the type of book he is looking for and the title he is
interested then he can search for the required book by entering the book name

Categories View:
Categories view shows the categories of books available and provides ability to the librarian
to add edit or delete category from the list.

Librarian's Control Panel:

This control panel will allow libraries to add remove users, add, edit, or remove a resource
And manage lending options

4. System Features
• The users of the system should be provided the surety that their account is secure.
• User authentication and validation of members using their unique member ID Proper
monitoring by the administrator which includes updating account status, showing a
popup if the member attempts to sue number of books that exceed the provided by
the library policy, assigning fine to members who skip the date of return.
• Proper accountability which includes not allowing a member to see other account.
Only administrator will see and manage all member accounts
5. Other Non-functional Requirements
5.1 Performance Requirement
The proposed system that we are going to develop will be used as the Chief performance
system within the different campuses of the university which interact with the university
staff und students. Therefore, it is expected that the database would perform functionally all
the requirements that are specified by the university.
The performance of the system should he fast and accurate Library Management System
shall handle expected and unexpected errors in ways that prevent loss in information und
long downtime period. Thus it should have inbuilt error testing to identify invalid
username/password The system should be able to handle large amount of data. Thus it
should accommodate high number of books and users without any fault
5.2 Safety Requirement
The database may get crashed at any certain time due to virus or operating system failure,
Therefore, it is required to take the database backup so that the database is not lost. Proper
UPS/inverter facility should be there in case of power supply failure.

5.3 Security Requirement

• System will use secure database.
• Normal users can just read information but they cannot edit or modify anything
except their personal and some other information.
• System will have different types of users and every user has access constraints Proper
user authentication should be provided.
• No one should be able to hack user password.
• There should be separate accounts for admin and members such that no member can
access the database and only admin has the rights to update the database.

5.4 Requirement attributes

There may be multiple admins creating the project, all of them will have the right to create
changes to the system. But the members or other users cannot do changes The project
should be open source.
The Quality of the database is maintained in such a way so that it can be very user friendly
to all the users of the database The user be able to easily download and install the system.

5.5 Business Rules

A business rule is anything that captures and implements business policies and practices. A
rule can enforce business policy, make a decision or infer new data from existing data This
includes the rules and regulations that the System users should abide by. This includes the
cost of the project and the discount offers provided. The users should avoid illegal rules and
protocols. Neither admin nor member should cross the rules and regulations.
5.6 User Requirement
The users of the system are members and Librarian of the university who act as
administrator to maintain the system, The members are assumed to have basic knowledge
of the computers and internet browsing. The administrators of the system should have more
knowledge of the internals of the system and is able to rectify the small problems that may
arise due to disk crashes, power failures and other catastrophes to maintain the system. The
proper user interface, user manual. online help and the guide to install and maintain the
system must be sufficient to educate the users on how to use the system without any
problems, The admin provides certain facilities to the users in the form of
• Backup and Recovery
• Forgot Password
• Data migration ie. whenever user registers for the first time then the data is stored in
the server.
• Data replication i.e. If the data is lost in one branch, it is still stored with the server
• Auto Recovery ie. frequently auto saving the information.
• Maintaining files ie. File Organization.
• The server must be maintained regularly and it has to be updated from time to time.

6. Other Requirements

6.1 Data and Category Requirement

There are different categories of users namely teaching staff, Librarian, Admin, students etc.
Depending upon the category of user the access rights are decided It means if the user is an
administrator then he can be able to modify the data delete, append etc. All other users
except the Librarian only have the rights to retrieve the information about database.
Similarly there will be different categories of books available. According to the categories of
books their relevant data should be displayed. The categories and the data related to each
category should be coded in the particular format

6.2 Appendix

A: Admin, Abbreviation, Acronym, Assumptions

B: Books, Business rules
C: Class, Client, Conventions
D: Data requirement, Dependencies
G: GUL
K: Key
L: Library, Librarian
M: Member
N: Non-functional Requirement
O: Operating environment
P: Performance Perspective Purpose
R: Requirement. Requirement attributes
S: Safety. Scope. Security, System features
U: User, User class and characteristics, User requirement

6.3 Glossary

The following are the list of conventions and acronyms used in this document and the
project as well:
• Administrator: A login id representing a user with user administration privileges to the
software.
• User: A general login id assigned to most users Client Intended users for the software.
• SQL Structured Query Language: used to retrieve information from a database
• SQL Server: A server used to store data in an organized format.
• Layer: Represents a section of the project.
• User Interface Layer: The section of the assignment referring to what the user
interacts with directly Application Logic Layer.
The section of the assignment referring to the Web Server. This is where all computations
are completed Data Storage Layer The section of the assignment referring to where all
data is recorded.
Use Case: A broad level diagram of the project showing a basic overview
 Class diagram: It is a type of static structure diagram that describes the structure of a
system by showing the system's cases their attributes, and the relationships between the
classes.
• Interface: Something used to communicate across different mediums Unique Key
Used to differentiate entries in a database.

Question 2:
Develop Design Document for the System mentioned in Question no. I
Answer: A Library Management System is a software built to handle the primary
housekeeping functions of a library. Libraries rely on library management systems to
manage asset collections as well as relationships with their members. Library management
systems help libraries keep track of the books and their checkouts, as well as members’
subscriptions and profiles.

Library management systems also involve maintaining the database for entering new
books and recording books that have been borrowed with their respective due dates.
System Requirements:

We will focus on the following set of requirements while designing the Library
Management System:

1. Any library member should be able to search books by their title, author, subject
category as well by the publication date.

2. Each book will have a unique identification number and other details including a
rack number which will help to physically locate the book.

3. There could be more than one copy of a book, and library members should be able to
check-out and reserve any copy. We will call each copy of a book, a book item.

4. The system should be able to retrieve information like who took a particular book or
what are the books checked-out by a specific library member.

5. There should be a maximum limit (5) on how many books a member can check-out.

6. There should be a maximum limit (10) on how many days a member can keep a
book.

7. The system should be able to collect fines for books returned after the due date.

8. Members should be able to reserve books that are not currently available.

9. The system should be able to send notifications whenever the reserved books
become available, as well as when the book is not returned within the due date.

10.Each book and member card will have a unique barcode. The system will be able to
read barcodes from books and members’ library cards.

Use case diagram

#
We have three main actors in our system:

• Librarian: Mainly responsible for adding and modifying books, book items, and
users. The Librarian can also issue, reserve, and return book items.
• Member: All members can search the catalog, as well as check-out, reserve, renew,
and return a book.
• System: Mainly responsible for sending notifications for overdue books, canceled
reservations, etc.

Here are the top use cases of the Library Management System:
• Add/Remove/Edit book: To add, remove or modify a book or book item.
• Search catalog: To search books by title, author, subject or publication date.
• Register new account/cancel membership: To add a new member or cancel
the membership of an existing member.
• Check-out book: To borrow a book from the library.
• Reserve book: To reserve a book which is not currently available.
• Renew a book: To reborrow an already checked-out book.
 • Return a book: To return a book to the library which was issued to a member.

Class diagram

#
Here are the main classes of our Library Management System:
• Library: The central part of the organization for which this software has been
designed. It has attributes like ‘Name’ to distinguish it from any other libraries and
‘Address’ to describe its location.

• Book: The basic building block of the system. Every book will have ISBN, Title,
Subject, Publishers, etc.

• BookItem: Any book can have multiple copies, each copy will be considered a book
item in our system. Each book item will have a unique barcode.

• Account: We will have two types of accounts in the system, one will be a general
member, and the other will be a librarian.

• LibraryCard: Each library user will be issued a library card, which will be used to
identify users while issuing or returning books.

• BookReservation: Responsible for managing reservations against book items.

• BookLending: Manage the checking-out of book items.

• Catalog: Catalogs contain list of books sorted on certain criteria. Our system will
support searching through four catalogs: Title, Author, Subject, and Publish-date.

• Fine: This class will be responsible for calculating and collecting fines from library
members.

• Author: This class will encapsulate a book author.

• Rack: Books will be placed on racks. Each rack will be identified by a rack number
and will have a location identifier to describe the physical location of the rack in the
library.

• Notification: This class will take care of sending notifications to library members.
Activity diagrams#
Check-out a book: Any library member or librarian can perform this activity. Here are
the set of steps to check-out a book:
Return a book: Any library member or librarian can perform this activity. The system
will collect fines from members if they return books after the due date. Here are the steps
for returning a book:
Renew a book: While renewing (re-issuing) a book, the system will check for fines and
see if any other member has not reserved the same book, in that case the book item cannot
be renewed. Here are the different steps for renewing a book:
Question 3: What is Change Management? Explain the process of changing
requirements for a Software To be developed?
Answer:
Change management in software development involves tracking and managing changes to artifacts,
such as code and requirements. It's critical for effective application development. The below elements
have been identified from research as key elements of a successful change management process.

These elements are incorporated into Prosci’s 3-Phase Process. Prosci’s methodology and how to
apply it to achieve better outcomes.

Here are the nine elements of a successful change management process:

1. Readiness Assessments

Assessments are tools used by a change management team or project leader to assess the
organization's readiness to change. Readiness assessments can include organizational
assessments, culture and history assessments, employee assessments, sponsor assessments and
change assessments. Each tool provides the project team with insights into the challenges and
opportunities they may face during the change process. What to assess:

Assess the Scope of the Change:

• How big is this change?

• How many people are affected?

• Is it a gradual or radical change?

Assess the Readiness of the Organization Impacted by the Change:

• What is the value-system and background of the impacted groups?

• How much change is already going on?

• What type of resistance can be expected?

You will also need to assess the strengths of your change management team and change sponsors,
then take the first steps to enable them to effectively lead the change process.

2. Communication and Communication Planning

Many managers assume that if they communicate clearly with their employees, their job is done.
However, there are many reasons why employees may not hear or understand what their managers
are saying the first time around. In fact, you may have heard that messages need to be repeated five
to seven times before they are cemented into the minds of employees.

Three Components of Effective Communication

Effective communicators carefully consider three components:

1. The audience

2. What is communicated

3. When it is communicated

For example, the first step in managing change is building awareness around the need for change
and creating a desire among employees. Therefore, initial communications are typically designed to
create awareness around the business reasons for change and the risk of not changing. Likewise, at
each step in the process, communications should be designed to share the right messages at the
right time.

Communication planning, therefore, begins with a careful analysis of the audiences, key messages
and the timing for those messages. The change management team or project leaders must design a
communication plan that addresses the needs of frontline employees, supervisors and executives.
Each audience has particular needs for information based on their role in the implementation of the
change.
3. Sponsor Activities and Sponsor Roadmaps

Business leaders and executives play a critical sponsor role in times of change. The change
management team must develop a plan for sponsor activities and help key business leaders carry out
these plans. Research shows that sponsorship is the most important success factor.

Avoid Confusing the Notion of Sponsorship with Support

The CEO of the company may support your project, but that is not the same as sponsoring your
initiative. Sponsorship involves active and visible participation by senior business leaders throughout
the process, building a coalition of support among other leaders and communicating directly with
employees. Unfortunately, many executives do not know what this sponsorship looks like. A change
manager or project leader's role includes helping senior executives do the right things to sponsor the
project.

4. Change Management Training for Managers

Managers and supervisors play a key role in managing change. Ultimately, the manager has more
influence over an employee’s motivation to change than any other person. Unfortunately, managers
can be the most difficult group to convince of the need for change and can be a source of resistance.
It is vital for the change management team and executive sponsors to gain the support of managers
and supervisors. Individual change management activities should be used to help these managers
through the change process.

Once managers and supervisors are on board, the change management team must prepare a
strategy to equip managers to successfully coach their employees through the change. They will
need to provide training and guidance for managers, including how to use individual change
management tools with their employees.

5. Training Development and Delivery

Training is the cornerstone for building knowledge about the change and the required skills to
succeed in the future state. Ensuring impacted people receive the training they need at the right time
is a primary role of change management. This means training should only be delivered after steps
have been taken to ensure impacted employees have the awareness of the need for change and
desire to support the change. Change management and project team members will develop training
requirements based on the skills, knowledge and behaviors necessary to implement the change.
These training requirements will be the starting point for the training group or the project team to
develop and deliver training programs.

6. Resistance Management

Resistance from employees and managers is normal and can be proactively addressed. Persistent
resistance, however, can threaten a project. The change management team needs to identify,
understand and help leaders manage resistance throughout the organization. Resistance
management is the processes and tools used by managers and executives with the support of the
change team to manage employee resistance.
7. Employee Feedback and Corrective Action

Managing change is not a one way street; employee involvement is a necessary and integral part of
managing change. Feedback from employees as a change is being implemented is a key element of
the change management process. Change managers can analyze feedback and implement
corrective action based on this feedback to ensure full adoption of the changes.

8. Recognizing Success and Reinforcing Change

Early adoption, successes and long-term wins must be recognized and celebrated. Individual and
group recognition is a necessary component of change management in order to cement and reinforce
the change in the organization. Continued adoption needs to be monitored to ensure employees do
not slip back into their old ways of working.

9. After-Project Review

The final step in the change management process is the after-action review. It is at this point that you
can stand back from the entire program, evaluate successes and failures, and identify process
changes for the next project. This is part of the ongoing, continuous improvement of change
management for your organization and ultimately leads to change competency.

These elements comprise the areas or components of a change management program. Along with
the change management process, they create a system for managing change. Good project
managers apply these components effectively to ensure project success, avoid the loss of valued
employees and minimize the negative impact of the change on productivity and a company's
customers.