CSE (5th Semester), TMSL SPMP

Software Project Management Plan for “Library

Management System”
1. Introduction
This Library Management system will be an automated one. The users
would be able to submit or borrow books from the library and the
assigned Authority will be able to review it and assign the books as per
their need. The users can choose the books of their choice by selecting the
authors and the categories. So, this would increase the Authority’s
productivity by simplifying the process of reviewing and granting the
books. This product provides the complete solution to the Automated
Library Management process.

I. Project Overview

This project is to create a prototype Library Management System. It is an online

application like a virtual library on the Internet where users can borrow books
and can also return them in time. There are also features to extend the time
period of any issued books. And also payment section is there. Where all the
due late fines and charges will be estimated and taken from the user. The Admin
section holds different functionalities than the users. The admin can search for
any user details, also see and update the database as per his/her need.

II. Project Deliverables

1. Preliminary Project Plan 01.10.2021

2. Requirements Specification 10.10.2021
3. Analysis [Object model, Dynamic model, and User interface] 17.10.2021
4. Architecture Specification 26.10.2021
5. Component/Object Specification 09.11.2021
6. Source Code 18.11.2021 - 31.11.2021
7. Test Plan 01.12.2021 - 07.12.2021
8. Final Product Demo 08.12.2021 - 12.12.2021

III. Evolution of this document

This document will be updated as the project progresses. Updates should be

expected in the following sections:
i. References - https://nevonprojects.com/e-library-project
https://www.iitms.co.in/mopac-library-management-app.html
ii. Definitions, acronyms, and abbreviations –
Database – Collection of data that are either entered by user or
administrator.

@ESC501 Page 1 of 9
CSE (5th Semester), TMSL SPMP

Authority – The people in charge of the library (the librarians)

User – The people who will be using the application.

iii. Organizational Structure will be updated as the team leaders are

assigned for each phase.
iv. Technical Process - this section will be revised appropriately as the
requirements and design decisions become clearer.
v. Schedule – as the project progresses, the schedule will be updated
accordingly.

Revision History
Revision Date Updated By Update Comments
0.1 01.09.2021 Ayandip Roy First Draft
0.2 10.09.2021 Spandan Basu Second Draft/Final Draft

IV. References

i. Team Website
http://wwwis.win.tue.nl/2M390/projects/spingrid/spmp.pdf
ii. Project Scope
http://wwwis.win.tue.nl/2M390/projects/spingrid/spmp.pdf
iii. Case Studies
• http://allrecipes.com/recipe/10926/cake-mix-cookies-iv/
• http://www.costco.com/cakes-cookies.html
• http://www.cakescookiesandcraftsshop.co.uk/

V. Definitions, Acronyms, and Abbreviations

i. UML - Unified Modeling Language

ii. AD - Architectural Design
iii. ADD - Architectural Design Document
iv. ATP - Acceptance Test Plan Client Monitor, Agent or Submitter
v. CM - Configuration Management
vi. Customer - TradeK Cake House
vii. DD - Detailed Design
viii. DDD - Detailed Design Document
ix. ITP - Integration Test Plan Monitor Application that either monitors
dispatchers
x. PM - Project Manager
xi. QAM - Quality Assurance Manager
xii. SCMP - Software Configuration Management Plan
xiii. SM - Senior Management SPMP Software Project Management Plan
(this document)
xiv. SQA - Software Quality Assurance
xv. SQAP - Software Quality Assurance Plan

@ESC501 Page 2 of 9
CSE (5th Semester), TMSL SPMP

xvi. SR - Software Requirements

xvii. SRD - Software Requirements Document
xviii. STD - Software Transfer Document
xix. STP - Software Test Plan Submitter Application that submits jobs to
dispatchers
xx. SUM - Software User Manual
xxi. SVVP - Software Verification and Validation Plan
xxii. TBD – To Be Decided
xxiii. TR - Transfer Phase
xxiv. UR - User Requirements
xxv. URD - User Requirements Document
xxvi. UTP - Unit Test Plan
xxvii. VPM -Vice Project Manager
xxviii. VQAM - Vice Quality Assurance Manager

2. Project Organization

I. Process Model

The process used for this project will be a V-model such that each stage of the
model allows us to do testing after completing a phases. Referring to the
diagram below, each phase is tested after completion.

@ESC501 Page 3 of 9
CSE (5th Semester), TMSL SPMP

II. Organizational Structure

Team Members –
i)Ayandip Roy
ii)Spandan Basu
Organization/
Name Contact Information
Position

ITech Project [email protected]

Ayandip Roy
Manager 09051001800
[email protected]
ITech Business
Sayantan Roy 09468847142
Analyst

Days Deliverable Team Leader Deliverable Description

9 1 Ayandip Roy Project Plan
7 2 Spandan Basu Requirements Specification
9 3 Sayantan Roy Analysis
13 4 Rajarshi Monadal Architecture Specification
9 5 Kamalika Hazar Component/Object Specification
14 6 Rohit Chakroborty Source Code
7 7 Arghya Roy Test Plan
5 8 Entire Team Final Deliverable

III. Organizational Boundaries and Interfaces

Team leaders throughout each development of the phases will be responsible for
coordinating team meetings, updates, communications, and team deliverables.

IV. Project Responsibilities

For the most vital responsibilities per phase of each team members, please refer
to segment 2.2. Ultimately the project team is responsible for the successful
delivery of the product. The team member tasks per deliverable according to
expertise and the phases are as given below:
1. Project Plan – Whole Team
2. Requirements Specification –Spandan Basu
3. Analysis – Sayantan Roy
4. Architecture Specification – Rajarshi Mondal
5. Component/Object Specification – Kamalika Hazra
6. Source Code – Rohit Chakroborty
7. Test Plan – Arghya Roy

@ESC501 Page 4 of 9
CSE (5th Semester), TMSL SPMP

8. Final Deliverable – Entire Team

Organization/
Name Role/Responsibilities
Position
• Managing and leading the
project team.
• Developing and maintaining
a detailed project plan.
• Monitoring project progress
ITech Project and performance.
Ayandip Roy
Manager • Managing project evaluation
and dissemination activities.
• Develop corrective actions
when necessary.
• Prepare reports on project
plans, status, progress, risks,
deadlines and resource
requirements.
Sayantan Roy
ITech Business • Develop and perform work
flow analysis to find out the
difficulties in reaching
Analyst goals.
• Provide project cost
estimates.
• Propose effective design
solutions to meet project
goals.
• Prepare design layouts and
Rajarshi Mondal ITech Designer
sketches according to
company design standards.
• Keeping of records and files.
• Documentation of daily
Robert Ferguson activities.
• Making kick-off meeting
reports.
ITech Staff
• In-charge of materials
needed for team building
activities.

@ESC501 Page 5 of 9
CSE (5th Semester), TMSL SPMP

3. Managerial Process

I. Management Objectives and Priorities

The management objective is to observe all features of the library management

system and to ensure that all students and faculties are using this software very
smoothly. The PM and QAM work together to achieve this by respectively
checking that progress is made as planned and monitoring the quality of the
product at various stages.

II. Assumptions, Dependencies, and Constraints

In this project plan, a number of factors are taken into account. The following
list shows the way milestones on various project phases have been scheduled:

• The team budget of 5 persons x 365 hours = 1825 hours

• The project deadline is on December 12th.
• The final presentation is on December 12th.
• The peer evaluation deadline is on December 8th.
• Other days the weekends holiday is closed (October 3rd, October 10th, October
17th, October 24th, October 31th, November 7th, November 14th, November 21th,
November 28th, December 5th).

NOTE: Due to the deadline of 12th December 2021, running out of time will
have its reflection on the product, and not on the duration of the project. By
assigning a priority to every user requirement, a selection can be made of user
requirements that may be dropped out if time runs out.

III. Risk Management

This section mentions any potential risks for the project. Also, schedules or
methods are defined to prevent or to reduce the risks as below:

i. Technology risk
ii. People risk
iii. Financial risk
iv. Market risk
v. Structure/process risk

The following are the possible risks to be encountered during the development of
the project and how they can be prevented.
1. Miscommunication
Prevention: Team members should not hesitate to ask and
re‐ask questions if things are unclear. Team members should

@ESC501 Page 6 of 9
CSE (5th Semester), TMSL SPMP

have a written copy of the tasks assigned to them every

meeting.
Correction: When it becomes clear that miscommunication is
causing problems, the team members should gather in a
meeting to clear things up.

2. Time shortage
Prevention: Care is taken to plan enough spare time.
Correction: When tasks fail to be finished in time or when they
are finished earlier than planned the project planning is
adjusted
3. Illness or absence of team members
Prevention: Team members should warn their team leader or
the PM timely before a planned period of absence.
Correction: Work can be taken over quickly by someone else
or be distributed among the team members if a person gets ill.

Monitoring and Controlling Mechanisms:

The monitoring of progress is done by the PM using the following means:
Project Kick-off Meetings
The project group meetings take place within the class
room or through chat. These meetings are meant to inform each
other of the progress made on various tasks and to assign new
tasks.

Progress Report
Progress report is done every Friday. This is meant to
inform and show the progress in the development of the project
and how things are going.

IV. Monitoring and Controlling Mechanisms

The monitoring of progress is done by the PM using the following means:

i. Weekly project status meetings
ii. Shared document repository
iii. Project tracking by MS project plan
iv. Tracking utilizing baselines in MS project

4. Technical Process

I. Methods, Tools, and Techniques

The project will be implemented utilizing V-model methodology, and tools such
as Dreamweaver, Microsoft Project, Star UML, Java, MySQL, QTP, and Load
Runner will be utilized. The risks for each category are listed to complete the

@ESC501 Page 7 of 9
CSE (5th Semester), TMSL SPMP

project successfully. For each risk, a description, a probability of occurrence,

the associated action and the impact of the risk are given.

II. Software Documentation

Documentation such as Project Charter, Business Requirement Document,

Functional Specification document, Cost Benefit Analysis, Technical
Specification document, Detail Design Document, Test Plan, Implementation
Plan, Detailed Project Report, and Benefit Realization document.

III. Project Support Functions

All project support documents will be completed in applicable phases.

5. Work Elements, Schedule, and Budget

I. The project is accounted for project resources, technologies and tools required
to whole analysis, implementation, and test of the application.
II. The project lead will be rotated for each phase within 5 team members.
III. The document for all phases will be revised in subsequent phases if applicable.

Budget and Resource Allocation

Salary 80,000.00
Office Operations/Supplies/Equipment/Consumables 40,000.00
Miscellaneous 10,000.00
Total Rs. 130,000.00

Schedule

@ESC501 Page 8 of 9
CSE (5th Semester), TMSL SPMP

@ESC501 Page 9 of 9