INDIVIUAL ASSIGNMENT

LIBRARY MANAGEMENT SYSTEM

CT038-3-2-OODJ
OBJECT-ORIENTED DEVELOPMENT WITH JAVA
NP2F1701IT
HAND OUT DATE: 28 August 2017
HAND IN DATE: 31 October 2017
WEIGHTAGE: 50%

LAXMAN GHALAN
(NP000036)

INSTRUCTIONS TO CANDIDATES
1. Submit your assignment to the administration counter.
2. Students are advised to underpin their answers with the use of references (sites
using the Harvard Name System of Referencing)
3. Late submission will be awarded zero (0) unless Extenuating Circumstances
(EC) are upheld
4. Cases of plagiarism will be penalized
5. The assignment should be bound in an appropriate style (Comb Bound or
Stapled)
6. Where the assignment should be submitted in both hardcopy and softcopy, the
softcopy of the written assignment and source code (where appropriate) should
be on a CD in an envelope/ CD cover and attached to the hardcopy.
7. You must obtain 50% overall to pass this module
Table of Contents
1. Introduction .................................................................................................................. 3
2. Objective ....................................................................................................................... 2
3. Description and Justification of Design........................................................................ 2
3.1 Use Case Diagram ................................................................................................. 3
3.2 Activity Diagram ................................................................................................... 4
3.3 Class Diagram ....................................................................................................... 4
4. Implementation of Code ............................................................................................... 6
5. Additional Features....................................................................................................... 6
6. Conclusion .................................................................................................................... 9
References .......................................................................................................................... 10
Appendix ............................................................................................................................ 11
Appendix I: Marking Grid ............................................................................................. 11
List of Figures
Figure 1: Use Case Diagram ................................................................................................ 3
Figure 2: Activity Diagram .................................................................................................. 4
1. Introduction
Knowledgecia is a new public library in a modern city. It is planned to develop a Library
Management System (LMS) for knowledgecia. The LMS provides functionalities to
support the librarys books management. The LMS provides the ability to store records
about the full list of the owned books by the library, Books status (Available or Borrowed).
In addition, it supports a range of services including the adding of new titles to the librarys
books list, Deleting, modifying book information, searching for a book title, Check-in a
book, Check-out a book, and Reporting. The users of this system are administrators,
Librarians, and guests (Librarys visitors).

Besides, a supporting document is needed to reflect that the design utilises object oriented
programming concepts.

1
2. Objective
Develop the practical ability to describe, justify, and implement an object-oriented
system.

Research and present a contemporary object-oriented topic.

2
3. Description and Justification of Design
3.1 Use Case Diagram

System Panels

Book List

Create

Delete

Modify

Librarian
Check-in

Admin
Check out

Making Report

Search

Viewing
Guest

Figure 1: Use Case Diagram

Above is the use case diagram of the LMS. The LMS provides primarily; books
management services. The system can be access by three types of users (actors);
administrators, librarians, and the library visitors (guests). Among these, Guest can access
the LMS, where they can search and view the books as show in the above figure.

Admin has authority to perform all the activities from the system. Only admin has the
authority to control the system panel, where administrative panel, librarian panel, and guest
panel are mentioned.

Librarian is the actor who will have almost all the authority to use function except system
panel, create and delete.

3
 3.2 Activity Diagram

Figure 2: Activity Diagram

Represented figure is about the activity diagram where it shows how the activity will be
taken place in the system. When visitors visit the library then the process starts. Guest uses
the system and search for the desired book to see if the book is available or not. In log in
section when the librarian logs in the librarian will be able to add books and students, search
books, check-in, check-out, report and update the book information. Similarly, when the
admin logs in the admin will be able to see all the panel and have same function of librarian
with additional function of creating and deleting accounts and deleting books record.

4
 3.3 Class Diagram

Figure 3: Class Diagram

Above class diagram represents the static view of an application. IT describes the
attributes and operations of a class and also the constraints imposed on the system. Class
diagram above shows a collection of classes, interfaces, associations, collaborations, and
constraints.

The user class is the parent class which is inherited by the librarian and administrator class.
the student and the book class have the relation of issue. Similarly, the book and the
librarian have the relation of issue.

5
4. Implementation of Code

public class StudentInfo extends Student {

private boolean isstudetAvilable;

public StudentInfo (boolean isStudentAvailable) {

this. isstudetAvilable = isstudetAvilable;
}
}

The above code shows the implementation of the following OOP concepts:

Inheritance
The StudentInfo class is inheriting the features of Student class.

Encapsulation
The private keyword before the isStudentAvailable indicates the use of encapsulation

5. Additional Features
Fine system is the additional features in this system which will be calculated automatically.

6
Sample Output

Figure 4:Home Page

The above screen shot is home the initial page of the system in which student can search
the book according to the id and name.

Figure 5:Log In Page

The log in page of the system accepts log in from librarian and admin. If the new account
is to be created click register button.

7
 Figure 6:ManageBooks Page
This is the part where librarian can edit, view and add books details.

Figure 7:Reports Page

This is the report part to see the student and books details.

8
 Figure 8: Home Page

6. Conclusion
From a proper analysis of positive points and constraints on the component, it can be safely
concluded that the product is a highly efficient GUI based component. This application
works properly and meets all user requirements. The maintenance of the record is made
efficient, as all the records are stored in file, through which data can be retrieved easily.
The computerization of the library Management System will not improve the efficiency but
also reduces human stress.

9
References
SmartDraw, 2017. SmartDraw. [Online]
Available at: https://www.smartdraw.com/use-case-diagram/
[Accessed 29 10 2017].
Tutorials Point, 2017. Tutorials Point. [Online]
Available at: https://www.tutorialspoint.com/uml/uml_activity_diagram.htm
[Accessed 29 10 2017].

10
 Appendix
Appendix I: Marking Grid

Program Solution and Research Report (30%) Individual

Diagramming (60%) Assignment
Jitendra
Sharma
(NP000033)
Criteria Marks Criteria: Marks
Allocated Allocated

Requirement Analysis: 30% Report Structure: 10%

- Use case diagram Professional

- Activity diagram Report Format

- Class diagram References

Implementation: 30% Program Documentation: 20%

- User Login Object oriented

Authentication implementation codes
- Books management and any additional
and user panels functions
- Reporting

Presentation (10%)

Ability to answer questions addressed by the lecturer 10%

pertaining to the work done and presented

11