System and Design Document for Online Library Management System

System and Design Document 1
Specification and Design Document
Name
Institution
Date

System and Design Document 2
Table of Contents
List of Figures..................................................................................................................................4
1.0 Specification Document........................................................................................................5
1.1 Executive Summary...............................................................................................................5
1.2 System Description................................................................................................................5
1.3 Scope......................................................................................................................................6
1.4 Feasibility analysis.................................................................................................................6
1.4.1 Technical Feasibility.......................................................................................................7
1.4.2 Economic Feasibility......................................................................................................8
1.4.3 Operational Feasibility....................................................................................................8
1.5 Requirements specification....................................................................................................9
1.5.1 Functional.......................................................................................................................9
1.5.2 Non-functional.........................................................................................................11
1.6 Constraints......................................................................................................................12
1.7 Use cases..............................................................................................................................13
1.7.1 Use case diagrams.........................................................................................................13
1.7.2 Use case descriptions....................................................................................................14
1.8 Context model......................................................................................................................16
1.9 Functional models................................................................................................................17
2.0 Design Document....................................................................................................................18
2.1 Architectural design.............................................................................................................18
2.2 Hardware specification........................................................................................................18
2.3 Class diagram.......................................................................................................................18
2.4 Interface design....................................................................................................................19

Specification and Design Document 3
2.4.1 Wireframe diagrams.....................................................................................................19
2.5 Business process models......................................................................................................20
2.6 Sequence diagrams..............................................................................................................21
2.7 Collaboration diagrams........................................................................................................24
2.8 State diagrams......................................................................................................................25
References......................................................................................................................................27

Specification and Design Document 4
List of Figures
Figure 1: Student use case.............................................................................................................14
Figure 2: Librarian use Case Diagram...........................................................................................14
Figure 3: Context Diagram............................................................................................................17
Figure 4: Dataflow diagram...........................................................................................................18
Figure 5: Class Diagram...............................................................................................................20
Figure 6: Wireframe Diagram.......................................................................................................21
Figure 7: General Sequence Diagram............................................................................................23
Figure 8: Book Borrow Sequence Diagram...................................................................................24
Figure 9: Book Return Sequence Diagram....................................................................................24
Figure 10: Book Issues Collaboration Diagram............................................................................25
Figure 11: Book Return Collaboration Diagram...........................................................................25
Figure 12: State Diagram...............................................................................................................26
Figure 13: Book State Diagram.....................................................................................................27
Figure 14: Librarian State Diagram...............................................................................................27

Specification and Design Document 5
1.0 Specification Document
1.1 Executive Summary
Because of the numerous issues being considered with the present Library management system
by the Victoria Institute of Technology, I made a totally new library administration framework
that can create the mechanized online framework for dealing with the library activities. It is
completely anchored framework that can be gotten to just by the checked client putting the client
name and secret key system. To alleviate the issues of ordinary and manual strategy for
reservation and appropriation of books to users from the library, the online Library Management
System has been made.
1.2 System Description
This library management system will be developed in Php and JavaScript and will run as a web
application. With this in mind, the overall application will be in the form of a website. The
database software used will be MySQL freely available on the internet at www.mysql.com and
can run on various platforms. The goal of the Victoria Institute project in mind is the
development of the library management system that will allow the performance of all the actions.
1.3 Scope
The developed system will be put to use within the Victoria Institute of Technology. The
software is planned to provide a well-managed set of books and other learning materials in the
university. The extent of Online Library Management System incorporates: Make particular item
clients dependent on their jobs and authorizations. Verify clients at their login. Give the rundown
of books the clients can obtain. Office to save books that are accessible.
1.4 Feasibility analysis
This is the practice in which the extension of the performance of a project can be analyzed. For a
proper evaluation, this study or rather an analysis is carried out in order to determine which of
the possible solutions can be considered for the accomplishment of any given task is practical for
each and every in a software setting.
1.4.1 Technical Feasibility
The technical feasibility is concerned with the determination of the hardware and the software set
in place to effectively for the fulfillment of the user prerequisite. The extensive work is

Specification and Design Document 6
influenced by the frameworks that included the office duty meant for creating the yields at any
given time, the time of response set to some specific conditions made, the ability for the software
to process a given volume of the information at a given specified speed and finally the facility
for the imparting process for the far-off areas, Agarwal et al (2015).
1.4.2 Economic Feasibility
For any proposed software project, the monetary value should be investigated by all means. For a
system to be fully viable, its economic value needs to be assessed every now and then to fully get
the all work within the planned budget plan, Nasution, M., & Ginting, M. (2018).
1.4.3 Operational Feasibility
With this type of feasibility study, the human being under control is considered whereby their
views on the authoritative life together with how they consider the system in a political manner.
The system to be developed should lie within these frameworks:
a) What are the possible changes that could be required in the design of the system
software?
b) The hierarchical structure that the system will utilize in its development.
c) The features that are new to the system
d) Considering the fact that the system will be developed in there any staff member with the
abilities on how best to make good use of the proposed system.
e) If otherwise, then is there enough time to allow the users to learn all the features of the
system.
1.5 Requirements specification
1.5.1 Functional
a) Adding library material
Input: the user enters all the required details of the system.
Output: a confirmation message is shown with the status of the added material.
Processing: the system checks for errors in the entered information.
b) Library membership
i. Registration