Faculty of Software Engineering Department

Final Project
Project Report

Project Supervisor:
Respected Sir. Sharukh
Project Team
BSEM-F17-114 (M-Zia-ul-haq)

Project Report
1
 [Library Management System]

Change Record
Author(s) Version Date Notes Supervisor’s
Signature
M-Zia-ul-haq 1.0 Purposal
M-Zia-ul-haq 2.0 Specification

APPROVAL

PROJECT SUPERVISOR:

Comments:

2
 Name: ______________________________

Date: _______________________________ Signature: __________________________

PROJECT MANAGER

Comments: ___________________________________________________________________

_____________________________________________________________________________

Date: _______________________________ Signature: __________________________

HEAD OF THE DEPARTMENT

Comments: ___________________________________________________________________

_____________________________________________________________________________

Date: _______________________________ Signature: __________________________

Dedication

3
 This work is dedicated to my . . . . . .

Acknowledgements

We take this occasion to thank God, almighty for blessing us with his grace
and taking our endeavor to a successful culmination. We extend our sincere
and heartfelt thanks to our esteemed guide, Mam Fatima, for providing us
with the right guidance. We would like to thank the other faculty members
also, at this occasion. Last but not the least, we would like to thank our friends
and class fellows for the support and encouragement they have given us
during our work.

Executive Summary

LMS is an integrated application system that manages reference materials

such as books, serials and research papers, members and backroom
processing such as acquisitions, cataloguing, circulation, inventory control etc.
more effectively and efficiently in secured platform.
To provide better services to the industry. To improve on the security issues
whereby risk area such as stolen items, long overdue borrowing, system
downtime, system crash etc. can be managed effectively in secured
environment. To provide more time in other priority areas such as content
development and info search assistance.

Table of Contents
Dedication...................................................................................................................................3

4
Acknowledgements ................................................................................................................... i4
Executive Summary .................................................................................................................. iv
Table of Contents ........................................................................................................................v
List of Figures .............................................................................................................................6
List of Tables ..............................................................................................................................6
Chapter 1 .................................................................................... Error! Bookmark not defined.
Introduction ................................................................................ Error! Bookmark not defined.
1.1. Background................................................................... Error! Bookmark not defined.
1.2. Motivations and Challenges .......................................... Error! Bookmark not defined.
1.3. Goals and Objectives .................................................... Error! Bookmark not defined.
1.4. Literature Review/Existing Solutions ............................ Error! Bookmark not defined.
1.5. Gap Analysis................................................................. Error! Bookmark not defined.
1.6. Proposed Solution ......................................................... Error! Bookmark not defined.
1.7. Project Plan ................................................................... Error! Bookmark not defined.
1.7.1. Work Breakdown Structure ....................................... Error! Bookmark not defined.
1.7.2. Roles & Responsibility Matrix................................... Error! Bookmark not defined.
1.7.3. Gantt Chart ................................................................ Error! Bookmark not defined.
1.8. Report Outline .............................................................. Error! Bookmark not defined.
Chapter 2 .................................................................................... Error! Bookmark not defined.
Software Requirement Specifications .......................................... Error! Bookmark not defined.
2.1. Introduction .................................................................. Error! Bookmark not defined.
2.1.1. Purpose ..................................................................... Error! Bookmark not defined.
2.1.2. Document Conventions ............................................. Error! Bookmark not defined.
2.1.3. Intended Audience and Reading Suggestions ............. Error! Bookmark not defined.
2.1.4. Product Scope............................................................ Error! Bookmark not defined.
2.1.5. References ................................................................. Error! Bookmark not defined.
2.2. Overall Description ....................................................... Error! Bookmark not defined.
2.2.1. Product Perspective ................................................... Error! Bookmark not defined.
2.2.2. Product Functions ...................................................... Error! Bookmark not defined.
2.2.3. User Classes and Characteristics ................................ Error! Bookmark not defined.
2.2.4. Operating Environment ............................................. Error! Bookmark not defined.
2.2.5. Design and Implementation Constraints ..................... Error! Bookmark not defined.
2.2.6. User Documentation .................................................. Error! Bookmark not defined.
2.2.7. Assumptions and Dependencies ................................. Error! Bookmark not defined.
2.3. External Interface Requirements ................................... Error! Bookmark not defined.
2.3.1. User Interfaces .......................................................... Error! Bookmark not defined.
2.3.2. Hardware Interfaces................................................... Error! Bookmark not defined.
2.3.3. Software Interfaces .................................................... Error! Bookmark not defined.
2.3.4. Communications Interfaces ....................................... Error! Bookmark not defined.
2.4. System Features ............................................................ Error! Bookmark not defined.
2.4.1. System Feature 1 ....................................................... Error! Bookmark not defined.
2.4.1.1. Description and Priority ......................................... Error! Bookmark not defined.
2.4.1.2. Stimulus/Response Sequences ................................ Error! Bookmark not defined.
2.4.1.3. Functional Requirements........................................ Error! Bookmark not defined.
2.4.2. System Feature 2 ....................................................... Error! Bookmark not defined.
2.4.2.1. Description and Priority ......................................... Error! Bookmark not defined.

5
 2.4.2.2. Stimulus/Response Sequences ................................ Error! Bookmark not defined.
2.4.2.3. Functional Requirements........................................ Error! Bookmark not defined.
2.4.3. System Feature 3 (and so on) ..................................... Error! Bookmark not defined.
2.5. Other Nonfunctional Requirements ............................... Error! Bookmark not defined.
2.5.1. Performance Requirements ........................................ Error! Bookmark not defined.
2.5.2. Safety Requirements .................................................. Error! Bookmark not defined.
2.5.3. Security Requirements ............................................... Error! Bookmark not defined.
2.5.4. Software Quality Attributes ....................................... Error! Bookmark not defined.
2.5.5. Business Rules .......................................................... Error! Bookmark not defined.
2.6. Other Requirements ...................................................... Error! Bookmark not defined.
Chapter 3 .................................................................................... Error! Bookmark not defined.
Use Case Analysis ....................................................................... Error! Bookmark not defined.
3.1. Use Case Model ............................................................ Error! Bookmark not defined.
3.2. Fully Dressed Use Cases ............................................... Error! Bookmark not defined.
Chapter 4 .................................................................................... Error! Bookmark not defined.
System Design ............................................................................ Error! Bookmark not defined.
4.1. Architecture Diagram .................................................... Error! Bookmark not defined.
4.2. Domain Model .............................................................. Error! Bookmark not defined.
4.3. Entity Relationship Diagram with data dictionary ......... Error! Bookmark not defined.
4.4. Class Diagram............................................................... Error! Bookmark not defined.
4.5. Sequence / Collaboration Diagram ................................ Error! Bookmark not defined.
4.6. Operation contracts ....................................................... Error! Bookmark not defined.
4.7. Activity Diagram .......................................................... Error! Bookmark not defined.
4.8. State Transition Diagram............................................... Error! Bookmark not defined.
4.9. Component Diagram ..................................................... Error! Bookmark not defined.
4.10. Deployment Diagram ................................................ Error! Bookmark not defined.
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1] .......... Error!
Bookmark not defined.
Chapter 5 .................................................................................... Error! Bookmark not defined.
Implementation ........................................................................... Error! Bookmark not defined.
5.1. Important Flow Control/Pseudo codes ........................... Error! Bookmark not defined.
5.2. Components, Libraries, Web Services and stubs ............ Error! Bookmark not defined.
5.3. Deployment Environment ............................................. Error! Bookmark not defined.
5.4. Tools and Techniques ................................................... Error! Bookmark not defined.
5.5. Best Practices / Coding Standards ................................. Error! Bookmark not defined.
5.6. Version Control ............................................................ Error! Bookmark not defined.
Appendices ................................................................................. Error! Bookmark not defined.
Appendix A: Information / Promotional Material ........................ Error! Bookmark not defined.
Reference and Bibliography ........................................................ Error! Bookmark not defined.
Index ........................................................................................... Error! Bookmark not defined.

List of Figures

1.1 Caption of first figure of first chapter 6

6
1.2
Caption of second
figure of first chapter 7
2.1 Caption of first figure of second chapter 14
2.2 Caption of second figure of second chapter 22
2.3 Caption of third figure of second chapter 26
5.1 Caption of first figure of fifth chapter 49
5.2 Caption of second figure of fifth chapter 49

List of Tables

1.1 label of first table of first chapter 6

1.2 label of second table of first chapter 7
2.1 label of first table of second chapter 14
2.2 label of second table of second chapter 22
2.3 label of third table of second chapter 26
5.1 label of first table of fifth chapter 49
5.2 label of second table of fifth chapter 49

C hapter#1 Introduction

7
Abstract:
In Information Technology one of the most important developments in recent years is that of
manual systems are being replaced by online automated web-based management systems.
Registers and Pens in any organization are replaced by Computer Systems. In the race of this
“Digital (Computerized) World” starting from a small organization to a large size organization
everyone is opting computerize systems for faster and secure access of data. Using Computerized
system has a lot of benefits that in modern days we can’t ignore. System Analysis and Design is
an area where we find in detail how a computerized system is being built and how it works. An
effective management system is a crucial factor in successful working of Automated Library
Management System in a school. Until recently, they must work through such inefficient and
potentially error-prone means as processing manuals, just to gather up the information and to
work smoothly. And that’s before they’ve passed it on to the students and faculties of Automated
Library Management System, where it was re-entered, hopefully with accuracy.
Background of Project:
Library Management system is an application refer to other library system and is suitable to use
by small and medium size library. It is use by librarian and library admin to manage the library
using a computerized system. The system was designed to help librarian record every book
transaction so that the problem such as file missing will not happened again.
Introduction:
Library Management System is an application which refers to library systems which are
generally small or medium in size. It is used by librarian to manage the library using a
computerized system
where he/she can record various transactions like issue of books, return of books, addition of
new books, addition of new students etc. Books and student maintenance modules are also
included in this system which would keep track of the students using the library and a detailed
description about the books a library contains. With this computerized system there will be no
loss of book record or member record which generally happens when a non-computerized
system is used. All these modules can help librarian to manage the library with more
convenience and in a more efficient way as compared to library systems which are not
computerized.
Motivations and Challenges:
Motivation: Libraries are essential in a process of giving citizens access to knowledge. In digital
times they are needed more than ever before. In our country, library systems are written that’s
why we make a great use of paper. By making paper we cut trees. It is very harmful for our
environment. For our environment, we take this step to reduce this.
Challenges:
Work with database.
Make a runnable jar File.
Make jar file to exe File.
UMl design.

8
Working with java GUI and Swim.
Scope of 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 remaining time 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. The
project aims and objectives that will be achieved after completion of this project are discussed in
this subchapter.
• Online book issue
• Request column for librarian for providing new books
• A separate column for digital library
• Student login page where student can find books issued by him/her and date of return.
• A search column to search availability of books
• A teacher login page where teacher can add any events being organized in the college
• and important suggestions regarding books.
• Online notice board about the workshop.
Literature Review:
Though a variety of software’s are available in software market, but only few of these are fully
compatible with Web. This is a review of the research on library automation software and their
compatibility with the recent advancement of Web as an interface used for accessing the
software in www environment. It also focuses on the growth and development of library
automation software way back to their origin. It also discussed standards, both in terms of library
and Web technology. Finally, the topic on Web interface used in library management software
system (LMSs) is covered including the technological implication, Web-based technical services,
security issue, database used and evaluation of LMS.
PROBLEMS OF THE EXISTING SYSTEM:
 Existing system does not have any facility of teacher’s login or student login whereas
proposed system will have a facility of student login as well as teacher’s login.
 Existing system does not have a facility of online reservation of books whereas proposed
system has a facility of online reservation of books.
 Existing system does not have any facility of online notice board where description of
workshops happening in our college as well as nearby colleges is being provided.
 Existing system does not have any option of lectures notes uploaded by teachers whereas
proposed system will have this facility.
 Existing system does not have any facility to generate student reports as well book issue
reports whereas proposed system provides librarian with a tool to generate reports.
 Existing system does not have any facility for book request and suggestions whereas in
proposed system after logging in to their accounts student can request books as well as
provide suggestions to improve library.

9
Gap analysis:
Gap analysis is the method in which we see where we are known and where we will in future.
It’s called need analysis like what are specification of our project and which things we need to
add in our system for future needs. So, our system in on library management here in our project
here we are making web site for middle class libraries so need analysis is to increase our site
functionality and by adding some more different and necessary things in it. And make it able for
use of high-class libraries.
Proposed Solution:
The case study titled Library Management System is library management software for the
purpose of monitoring and controlling the transactions in library. This case study on the library
management system gives us the complete information about the library and the daily
transactions done in a Library. We need to maintain the record of new books and retrieve the
details of books available in the library which mainly focuses on basic operations in a library like
adding new member, new books, and updating new information, searching books and members
and facility to borrow and return books. It features a familiar and well thought-out, an attractive
user interface, combined with strong searching, insertion and reporting capabilities. The report
generation facility of library system helps to get a good idea of which are the books borrowed by
the members, makes users possible to generate hard copy.
Objectives of the system:
 Develop a system that can replace the manual library management system.
 Develop a database which stores user details and book details with reliable search
facility. Administrator, librarian, and users should have separate logins.
 Attractive user interface to navigate through the system with user friendly environment
for the users.
Word Break Down Structure:
The Work Breakdown Structure provides a clear picture of the items that are required to be
completed for the project work scope. It is arranged in a tree structure manner to show all sub-
sections required to be accomplished in each phase throughout the project.

10
 Roles & Responsibility Matrix:
WBS # WBS Deliverable Activity Activity to Duration Responsible Team
# Complete the (# of Member(s) & Role(s)
Deliverable Days)

1.0 Proposal 1.1 Gathering of data 6 Muhammad Ahsan

Document Eliminate our Muhammad Hussnain
mistakes Momal Ashfaq
2.0 5 Muhammad Ahsan
Part-2
Specification Muhammad Hussnain
Momal Ashfaq
1.2 Part-1 Front end and 7 Muhammad Ahsan
Documentation backend Muhammad Hussnain
Momal Ashfaq

1.3 Database 10 Muhammad Ahsan

Muhammad Hussnain
Momal Ashfaq

1.4 Documentation 30 Muhammad Ahsan

Muhammad Hussnain
Momal Ashfaq

Table1.1: Role of Responsibility Matrix

Gantt Chart:

11
 Report Outline
Ch2: In Ch. 2 we can define the features of our project and define functional and non-
functional requirements and internal and external interface of our project
Ch3: we can implementation and define actors and use case analysis in our project with the help
of diagrams.
Ch4 we can define our project through diagrams
Ch5 we can implement our project in this chapter and tell what tools and techniques are used?

C hapter#2

Purpose:
Software Requirement Specifications

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.
Improved customer service through greater access to accurate information.
Greater accountability and transparency in operations.
Scope:
Library Management System is basically updating the manual library system into a internet-
based application so that the users can know the details of their accounts, availability of books
and remaining time 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.

12
 Audience Definitions, Acronyms and Abbreviations:
Audience Definitions:
The intended readers of this document are the developers of the site, testers, library owners and
managers and coordinators. Any suggested changes on the requirements listed on this document
should be included in the last version of it so it can be a reference to developing and validating
teams.

References:
IEEE 830-1998 standard for writing SRS document. I Sommerville, Software Engineering 8th
ed, Addison-Wesley, 2007
Overall Description:
Product Perspective:
Library Management System is a replacement for the ordinary library management systems
which depend on paperwork for recording book and user’s information.
Product Functions:
Administrators:
 Admin should be able to insert, modify and delete books.
 Can accept or reject a new user according to the library policy or payment methods.
 Increase the period for borrowing a book for specific type or group of users.
 Can get the information (status report) of any member who has borrowed a book.
 Add and edit book categories and arrange books by categories.
 Add and edit authors and publisher’s information.
 Can send lateness warnings to people who have exceeded deadline date.
 Can record books returned by users.
Normal Users (Library Members):
 The member should be provided with the updated information about the books catalog.
 Members are given an access to check their account’s information and change it.
 Members can search through books by subject, title, authors or any information related to
the
 book.
 Can extend the period of borrowing books according to the library policy.
 The customer may suggest a book to be brought to the library book collection.

13
Operating 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, Mozilla Firefox with Flash
Player and JavaScript.
User Characteristics:
Users of this Library Management System are members, librarians and the administrators who
maintain the website. Members and librarians are assumed to have basic knowledge of
computers and Internet browsing. Administrators of the system should have more knowledge of
internal modules of the system and are able to rectify small problems that may arise due to disk
crashes, power failures and other catastrophes.
Design and Implementation Constraints:
 The information of all users, books and libraries must be stored in a database that is
accessible by the website.
 MS SQL Server will be used as SQL engine and database.
 The Online 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 to enter their online accounts and
do actions.
Assumptions and Dependencies:
 The product needs the following third-party products.
 Microsoft SQL server to store the database.
 ASP.net to develop the Product.
External Interfaces Requirements:
User Interfaces:
 Login Interface:
In case the user is not registered yet, he can enter the details and register. Which asks the user to
type his username and password? If the user entered either his username or password incorrectly
then an error message occurs.
 Search:
The member or librarian can enter the type of book he is looking for and the title he is interested
in them, then he can search for the required book by entering the book name.
 Categories view:
Categories view shows the books categories view with ability to Liberian to add/edit or delete
category from the list.
 Librarian’s Control Panel:
This control panel will allow librarians to add, confirm, or remove users; add, edit, or remove a
medium. And manage lending options.
 Hardware Interfaces:
Only the recommended configuration (basic requirements of a computer system) no other
specific hardware is required to run the software.

14
  Software Interfaces:
 Browser to load and view the web pages
 Operating System
User Requirement:
 The software provides good graphical interface for the user any administrator can operate
on the system performing the required task such as create, update, viewing the details of
the book.
 Allows user to view quick reports like Book Issues/Returned etc. in between particular
time.
 Stock verification in different criteria or according to different-different categories.
 Search facility based on different criteria in depth.
System requirements:
The system should prompt for the user and administrator to login to the application and for
proper input criteria.
Functional requirements:
1. Normal user: user login:
This feature used by the user to login into system. They are required to enter user id and
password before they can enter the system. The user id and password will be verified and if
invalid id is there user cannot enter the system.
 Functional requirements:
 user id is provided when they register
 The system must only allow user with valid id and password to enter the system
 The system performs authorization process which decides what user level can access to.
 The user must be able to logout after they finished using system.
2. Register new user:
This feature can be performed by all users to register new user to create account.
 Functional requirements:
 System must be able to verify information
 System must be able to delete information if information is wrong.
3. Register new book:
This feature allows to add new books to the library
 Functional requirements:
 System must be able to verify information
 System must be able to enter number of copies into table.
 System must be able to not allow two books having same book id.

4. Search book:
This feature is found in book maintenance part. we can search book based on book id, book
name publication or by author name.
 Functional requirements:

15
  System must be able to search the database based on select search type
 System must be able to filter book based on keyword entered
 System must be able to show the filtered book in table view
5. Issue books and return books:
This feature allows to issue and return books and view reports of book issued.
 Functional requirements
 System must be able to enter issue information in database.
 System must be able to update number of books.
 System must be able to search if book is available or not before issuing books System
should be able to enter issue and return date information.
6. Event addition:
This feature allows teacher and student to add information about various workshops being
conducted in college and colleges nearby.
 Functional requirements:
 System should be able to add detailed information about events.
 System should be able to display information on notice board available in the
homepage of Site.
Non-Functional Requirement:
1) Efficiency requirement:
When a library management system will be implemented librarian and user will easily acess
library as searching and book transaction will be very faster.
2) Reliability requirement:
The system should accurately perform member registration, member validation, report
generation, book transaction and search.
3) Usability requirement:
The system is designed for a user-friendly environment so that student and staff of library can
perform the various tasks easily and in an effective way.
4) Safety requirements:
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.
5) Security Requirements:
We are going to develop a secured database for the university 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 other than library staff only have the rights
to retrieve the information about database.
6) Hardware Constraints:
The system requires a database in order to store persistent data. The database should have backup
capabilities.
7) Error handling:
Library Management System shall handle expected and non-expected errors in ways that
prevent loss in information and long downtime period.

16
Software and hardware requirements:
This section describes the software and hardware requirements of the system
 Software requirements:
 Operating system: Windows 7 is used as the operating system as it is stable and
supports more features and is more user friendly
 Database MYSQL-MYSQL is used as database as it easy to maintain and retrieve
 records by simple queries which are in English language which are easy to understand
and easy to write.
 Development tools and Programming language- HTML is used to write the whole
code and develop webpages with CSS, java script for styling work and php for sever
side scripting.
 Hardware requirements:
 Intel core i5 2nd generation is used as a processor because it is fast than other
processors an provide reliable and stable and we can run our pc for longtime.
 By using this processor, we can keep on developing our project without any worries.
 Ram 1 GB is used as it will provide fast reading and writing capabilities and will in
turn support in processing.

C hapter#3 Use Case Analysis:

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.

17
18
C hapter No 4 System Design

Architectural Design

Domain Model:
Library Domain Model describes main classes and relationships which could be used during
analysis phase to better understand domain area for Integrated Library System (ILS), also known
as a Library Management System (LMS). Each physical library item - book, tape cassette, CD,
DVD, etc. could have its own item number. To support it, the items may be barcoded. The
purpose of barcoding is to provide a unique and scannable identifier that links the barcoded
physical item to the electronic record in the catalog. Barcode must be physically attached to the
item, and barcode number is entered into the corresponding field in the electronic item record.
Barcodes on library items could be replaced by RFID tags. The RFID tag can contain item's
identifier, title, material type, etc. It is read by an RFID reader, without the need to open a book
cover or CD/DVD case to scan it with barcode reader.

19
 Class Diagram:
Class diagram for library management system contains classes such as
 Book class
 librarian class
 Transaction class
 Member record class
 Bill class
Each class contains various attributes and methods (Functions) which call other class attributes
to share data.
 Book Class contains attributes such as author, book name, price status, rack no, edition.
And functions such as display book details, update status.
 librarian class contains attributes such as name, password and functions such as search
book, issue book, calculate fine, calculate bill.

20
 transaction class contains attributes such as transaction id, member id bill id date of issue
etc. and functions such as create transaction delete transaction
 Member record class contains attributes such as member id, type, date of issue, no of
books, etc. and functions such as increase book issue, decrease book issue, pay bill.
 Bill class contains attributes such as bill no, date, member, amount and functions such as
create bill, update bill.

21
 Sequence Diagram:
User login

22
Registration/signup

23
Issue of books:

24
Return of books:
Return with fine:

25
Return within due date:

Addition of new books:

26
Removal of old books:

Reservation of books:

27
Cancellation of previous registration:

Change password:

28
Activity Diagram:

29
C hapter 5 Implementation

This describes how the system works and how best computers together with other
resources may be applied to perform data storage, management and retrieval for
decision making. The requirement of this research work demands a web
programming language.
Future Scope:
Future scope of application:
This application can be easily implemented under various situations. We can add
new features as and when we require. Reusability is possible as and when require
in this application. There is flexibility in all the modules.
Software scope:
Extensibility: This software is extendable in ways that its original developers may
not expect. The following principles enhances extensibility like hide data structure,
avoid traversing multiple links or methods, avoid case statements on object type
and
distinguish public and private operations.
Reusability: Reusability is possible as and when require in this application. We
can update it next version. Reusable software reduces design, coding and testing
cost by amortizing effort over several designs. Reducing the amount of code also
simplifies understanding, which increases the likelihood that the code is correct.
We follow up both types of reusability: Sharing of newly written code within a
project and reuse of previously written code on new projects.

30