“Software Project Plan Document”

Library Management System

Software Project Management
Course project
Instructor
Syed Affan Ahmed
 Table of Contents

1. Revision control sheet...........................................................................................................1

2. Project Abstract......................................................................................................................1
3. Project Charter....................................................................................................................... 1
4. Software Requirement Specification...............................................................................1-3
4.1 Functional and Nonfunctional
Requirements…………………………………………………………………….4-6
4.2 Project Features……………………………………….
……………………………………………………………………….7-8
4.3 Use case
Diagram………………………………………………………………………………………………………………9
4.4 Class
Diagram……………………………………………………………………………………………………………………..10

5. Table of Activities with proper predecessor...................................................................8-9

5.1 Project Network
Diagram………………………………………………………………………………………………….10

6. RMMM Plan....................................................................................................................... 8-9

7. Risk Sheet............................................................................................................................. 10
8. Acceptance Sheet.................................................................................................................16
1. Revision Control Sheet: predecessor
Name Date Reason for Version
Change
Hamna Meraj 10-08-2022 1.0

2. Project Abstract:

This report was about the design of a library website or library online page. A library member
wants to design a website. This makes the website comfortable for people of all ages. It also
increases the library's customer base. Fewer page numbers to make it easier for users to find
difficult books. It is open 24 hours a day, even on public holidays. This improves the standards of
the library. Developing the website took him 40 days and cost him about $15,000 to complete the
project. This project will guide you through the website design process. The project consists of
three steps. A project overview describes budgets, schedules, dependencies, deliverables,
constraints, descriptions, and goals. A work breakdown structure describes the activities that
occur during a project. This allows the project team to work efficiently. A Gantt chart provides a
clearer timeline for all project activities and project milestones. Risk requirements such as user
requirements, stakeholders, and members of the library requirements. If the web doesn't meet
your requirements, that's also the problem. The project team should also focus on maintaining
the website and using technology for all ages.

3. Project Charter:
It gives the overall information about the project like with the budget, time, description, objectives,
goals, exclusions, benefits, dependencies, assumptions and constraints.

Project Name: Digital Library Project Manager: Hamna Meraj

 Description:
 Redesign the site architecture and improve the fundability and usability.
 Redesign the homepage with a new look.
 Implement the new system to maintenance
 Implement the new design that meet the standard and requirements of the library.
 Implement the new management system to control the activities on the website
Objective/s: Goals:
• User-centered redesign • Provide great user experience and navigation
• Reduction in size system.
• Architectural overhaul • Clear idea to maintain and develop the
• Updated and intuitive navigation structure activities of the website.
• Accessibility compliance • The website will be design according to the
Coherent content strategy user needs and requirements.
• Meeting the library standard and
requirements.

Deliverables: Exclusions:
• Providing the manufacturing information. • Providing the training to the public about the
• Information about the security systems. website.
• Compliant with accessibility requirements. • After completed the project, they must set
their own management team.
Benefits expected: Dependencies: • Before launch the security
• less duplication system, first giving the information about the
• Easy to update the information on website system and giving training about it like how to
• Smaller (easily find information) control that issue with the system. • Need to
• Easily manageable like the new content the upload the high-tech system to secure that
added in the website.
• Less dead content and less out of date content

Assumptions: • The budget control overall Constraints: • The project must be completed in
project expenses. • The set of project goal and given time frame work. • Website must design
objects are achievable and help to finish project with limited colour schema • The content must
successfully. • All the required skills in the be properly categories • Weekly meeting must
project development are available. • All with the key stakeholders. • Maintain the
stakeholders are contributing in the project and confidence in the project team. Also valued the
help to assist the project. individual requirements.
Timeframe:40 days Budget: nearly$15,000

Team Member : Date Approved: 10-08-2022

Hamna Meraj

4. Software Requirements Specification:

class Address:

public class Address {

private String streetAddress;
private String city;
private String state;
private String zipCode;
private String country;
}

class Person:

public class Person {

private String name;
private Address address;
private String email;
private String phone;
}

class BookReservation:
public class BookReservation {
private Date creationDate;
private ReservationStatus status;
private String bookItemBarcode;
private String memberId;

public static BookReservation fetchReservationDetails(String barcode);

}

class BookLending:

public class BookLending {

private Date creationDate;
private Date dueDate;
private Date returnDate;
private String bookItemBarcode;
private String memberId;

public static boolean lendBook(String barcode, String memberId);

public static BookLending fetchLendingDetails(String barcode);
}

class Fine:

public class Fine {

private Date creationDate;
private double bookItemBarcode;
private String memberId;

public static void collectFine(String memberId, long days) {}

}
class Book:
public abstract class Book {
private String ISBN;
private String title;
private String subject;
private String publisher;
private String language;
private int numberOfPages;
private List<Author> authors;
}

class BookItem:

public class BookItem extends Book {

private String barcode;
private boolean isReferenceOnly;
private Date borrowed;
private Date dueDate;
private double price;
private BookFormat format;
private BookStatus status;
private Date dateOfPurchase;
private Date publicationDate;
private Rack placedAt;

public boolean checkout(String memberId) {

if(bookItem.getIsReferenceOnly()) {
ShowError("This book is Reference only and can't be issued");
return false;
}
if(!BookLending.lendBook(this.getBarCode(), memberId)){
return false;
}
this.updateBookItemStatus(BookStatus.LOANED);
return true;
}
}

class Rack:

public class Rack {

private int number;
private String locationIdentifier;
}

4.1 Functional Requirement:

 Only authentic user must have the access to the system.

 Only the user must be able to provide the information related
to the library.
 Librarian must be able to:
 Provide the information regarding books.
 Add new book to the database.
 Update the number of books in database.
  Enter data of issued book in Database.
 Information of returned books.
 Collect Bills
 Check Feedback
 User must have the knowledge about the no of copies of a
book.
 Same Id’s for 2 or more books shall not be allowed.
 User must check if the book is available or not before issuing.
 User must enter issue and return date in database.
 The user must know the number of racks in the library
 User can search for the required books from database.

4.2 Non-Functional Requirements:

Performance

The Server would be able to perform desired tasks in reasonable

unit of time.

Reliability

The Server would perform desired tasks as expected. The system

does its work with more accuracy like user registration to the
system, user validation and authorization, book search and issue
operation, return status , and updating the database by
synchronizing between database and application.

Security

The system would provide access to only legitimate users. It will be

secure on network and only authorized person can use it.

Scalability

The proposed system would be scalable to support extended

number of users.

 Ease of Use

The proposed system would be user-friendly and would provide

Graphical User Interface (GUI).

Accessibility
The proposed system would be GUI-based desktop application
installed on computing root node (server) running the application.

 Maintainability

The proposed system would be easy to maintain and extend. Minor

modification to the system would not cause harm to the running
application.

4.3 Project Features:

 Login and Logout
 Books Add and Remove and Update.
 Feedback
 Billing
 Reservation of books
 Renew books
5. Table of Activities with proper predecessor

Task Days Predecessor

T1 ( Requirements) 4 -

T2( Contract Writing) 2 T1

T3( Concept planning) 3 T1

T4(Composite Designing) 5 T2 and T3

T5(Client Approval) 3 T4

T6( UI development) 5 T5

T7( Database Designing) 4 T5

T8(Testing UI) 3 T6

T9(Coding) 2 T6 and t7

T10( Testing system) 2 T8 and T9

Task Day Day Day Day Day Day Day Day Day Day Day Day Day Da Day Da Day Da Day Da Day Da Day Da Day
1 2 3 4 5 6 7 8 9 10 11 12 13 y 15 y 17 y 19 y 21 y 23 y 25
14 16 18 20 22 24
T1
T2
T3
T4
T5
T6
T7
T8
T9
T10
6.

7.

8. Acceptance Criteria:

Syed Affan Ahmed

Lecturer Cocis Department
PAF-KIET (Main Campus)

Dear Sir:
I am writing to confirm my Document as per requirement as a course project which you were assigned in this document, I
have complete software quality document with complete test cases and complete risk management report of Library
Management system. So, I want to approve this document from you.

Signature: _________
Date: _________