CMU-SE 303 Software Testing

Verification & Validation

PRODUCT BACKLOG DOCUMENT

LIBRARY MANAGEMENT

Submitted by

Long, Phan Hoang

Hieu, Hua Phu Minh
Tho, Nguyen Xuan
Tuan, Nguyen Manh
Tuong, Huynh Huu

Approved by
Trinh, Tran Thi Thuy M.Sc.

Proposal Review Panel Representative:

Name Signature Date

Group Project for Software Testing - Mentor:

Name Signature Date

LM(Group 6) Product Back Log Document v1.1

PROJECT INFORMATION

Project
TM
acronym

Project title

Start date 01– Aug – 2023 End Date ?? – ?? – 2023

Lead institution International School, Duy Tan University

Trinh, Tran Thi Thuy

Project mentor Email: thuytrinh85@gmail.com

Phone: 0795898823

Partner
Duy Tan University
organization

Scrum Master Long, Phan Hoang Hloeng.business@gmail.com 0946575102

Product owner Tho, Nguyen Xuan nguyenxuantho2003@gmail.com 0396038065

Hieu, Hua Phu Minh huahieu.cv@gmail.com 0901160328

Team members Tuan, Nguyen Manh mguyenmanhtuan@gmail.com 0782097162

Huynh, Huu Tuong Huynhhuutuong@dtu.edu.vn 0327979229

DOCUMENT NAME

Document Title User Story Document

Author(s) Long, Phan Hoang

Group 6 Page 2
LM(Group 6) Product Back Log Document v1.1

Tho, Nguyen Xuan

Role Product Owner, Team Member, Scrum Master
[LM]Product Backlog-
Date September 2, 2023 File name:
ver1.1.docx
URL
Access Project and CMU Program

REVISION HISTORY

Version Person(s) Date Description

Long, Phan Hoang Proceeding to Product Backlog
1.1 August 28, 2023
Tho, Nguyen Xuan Document

SIGNATURE
Document Approvals: The following signatures are required for approval of this document.
Signature:
Mentor Trinh, Tran Thi Thuy
Date:

Signature:
Project Leader Long, Phan Hoang
Date:

Signature:
Product Owner Tho, Nguyen Xuan
Date:

Signature:
Tuan, Nguyen Manh
Date:
Team Member(s)
Signature:
Hieu, Huu Phu Minh
Date:

Group 6 Page 3
LM(Group 6) Product Back Log Document v1.1

Signature:
Tuong, Huynh Huu
Date:

Group 6 Page 4
LM(Group 6) Product Back Log Document v1.1

Table of Contents
1. Introduction 6
1.1. Purpose 6
1.2. Scope 6
2. Product backlog 7
2.1. Product Backlog Items Diagram 7
2.2. Product Backlog Specification 7
2.3. Break down into Sprint Backlog 8
3. Constraint 10
4. Stack holders and user descriptions summary 10
5. References 11

Group 6 Page 5
LM(Group 6) Product Back Log Document v1.1

1. Introduction
The agile product backlog in Scrum is a prioritized features list, containing short
descriptions of all function desired in the product. When applying Scrum, it’s not
necessary to start a project with a lengthy, upfront effort to document all requirements.
Typically, a Scrum team and its product owner begin by writing down everything they
can think of for agile backlog prioritization. This agile product backlog is almost always
more than enough for a first sprint. The Scrum product backlog is then allowed to grow
and change as more is learned about the product and its clients.
1.1. Purpose

− In order to analyze the requirements for the "library management" project, this

document was created.

− The usecase design, development, and system testing phases of system

development use this document as input.

1.2. Scope

− List the user’s role.

− Write all the user’s requirements.

− List some main function of system.

− Short description of all the function desired in the product.

− Given the priority of each feature and function of the product.

Group 6 Page 6
 LM(Group 6) Product Back Log Document v1.1

2. Product backlog
2.1. Product Backlog Items Diagram

Figure 1. Product Backlog Items Diagram

2.2. Product Backlog Specification

Table 1. Product Backlog Specification

As
ID Theme I want to So that Priority
a/an

Access to the
I can use the system with
PB01 Login User system by my
my role
account

I can stop using the

Log out of the system. I can login after I
PB02 Logout User
system want to use the system
next time.

Menu

PB03 Form menu I want to show I can log out and use the
choices for menu options to access the
Group 6 Page 7
 LM(Group 6) Product Back Log Document v1.1

book management
function, reader
entering the
management function, and
function.
book borrowing and
returning management.

BOOK MANAGEMENT

I want to provide a I may enter information

list of books with about the book code, book
information that title, author's name, book
Form book
PB04 can be filled in to kind, publisher, year of
management
execute book publication, quantity, view
management the function buttons, and
operations. see the book list.

I may update the system's

I'd want to enter database with information
information about such as book code, book
PB05 Add book User
a book into the name, author name, book
system. kind, publisher, year of
publication, and quantity.

From the system's

I'd like the system
Update database, I may change the
to provide me with
PB06 information User book title, author name,
information on a
of book book type, publisher, year
book.
of release, and quantity.

PB07 Delete book User I'd want to remove After reviewing the
material from a information, I may delete
book. the book information from

Group 6 Page 8
 LM(Group 6) Product Back Log Document v1.1

the database. I can't erase

the information if someone
is borrowing it.

I may locate book

information by entering
one or more of the
Book I'm looking for following book details:
PB08 User
Searching book information. book code, book title,
author name, book type,
publisher, and year of
release.

READER MANAGEMENT

I can enter reader

I want to display a information such as reader
list of readers, code, reader name, date of
where I can fill in birth, address, cccd
Form reader the necessary number, and phone
PB09
management information to number, as well as view
execute reader operation buttons for
management reader administration
operations. functions and a list of
readers' books.

PB10 Add reader User I'd like to include I may enter reader
some information information into the
from a reader. system's database, such as
reader code, reader name,
date of birth, address, cccd
number, and phone
Group 6 Page 9
 LM(Group 6) Product Back Log Document v1.1

number.

I may change reader

information from the
I'd want to change system's database, such as
Update data
PB11 User reader information reader name, date of birth,
of reader
in the system. address, citizen
identification number, and
phone number.

I have the ability to

I'd want to remove
PB12 Delete reader User remove reader information
reader information.
from the database.

I can access reader

information by entering
one or more of the
I'm looking for following information:
Searching
PB13 User information from reader code, reader name,
reader
readers. date of birth, address,
citizen identification
number, and phone
number.

BOOK BORROW MANAGEMENT

PB14 Form Book I'd want to show I may examine historical

Borrow the history of loan date, return due date,
Management borrowing dates, return date, reader code
payment due dates, information, borrow date,
return dates, and return date, borrow
where to enter amount, and search book

Group 6 Page 10
 LM(Group 6) Product Back Log Document v1.1

information to lend
code information.
books.

I want to show the

loan date history, I may access historical
return due date data on borrow dates,
Form Book
history, return date return due dates, return
PB15 Return
history, and where dates, reader code
Management
to put in information, and return
information to dates.
return the book.

I may search for loan

information by entering
the book code, and I can
Book I'd want to oversee
lend books by putting
PB16 Borrow User the lending of
information into the
Management books.
system's database such as
the reader code, loan date,
return date, and amount.

I can look up the reader's

loan and return date
Book Return I'd want to handle
PB17 User history and insert the
Management book returns.
return date data into the
system's database.

Table 2: Priority impact description

Impact Description

Group 6 Page 11
LM(Group 6) Product Back Log Document v1.1

1 Very high Must have

2 High Should have

3 Medium Could have

4 Low Won’t have

2.3. Break down into Sprint Backlog

Table 3. Breakdown into Sprint Backlog

No Task Name Time Duration Start

1 Initial

1 Gathering Requirement

1.1 Create Proposal Document

2 Start Up

2.1 Create documents for project

2.1 Project’s Kick-off Meeting

3 Development

3.1 Sprint 1

3.2 Sprint 2

3.3 Sprint 3

4 Project’s Retrospective Meeting

5 Final Release

Duration

3. Constraint
Group 6 Page 12
LM(Group 6) Product Back Log Document v1.1

Table 4. Constraint
Constraint Condition

Project completion time limit in 4 months so time to complete

Time
project be restricted

People constraint 5 people working together to finish the project

The integrated system Must be connected to Internet network to operate

Requirements According to Product owner’s Requirements

4. Stakeholders and user descriptions summary

Table 5. Stakeholders and User Descriptions Summary

Name Description Role

The Person who give the Provide information to develop the

Product Owner Requirement system. Make the decision to accept and
implement the project, do the unit test

This is the stakeholder Controlling, managing, monitoring,

who leading, manage the make sure the project complete on time,
Scrum Master
system development within budget, according to plan and
Team according to requirements

This is a stakeholder that Specifies the details of one or more a

works with the Analysts part of the system’s functionality by

Requirement to correctly translate describing one or the aspects of the

Analyzer requests or needs into requirements,

requirements to be used
This will include functional and non-
for design
functional

This is a stakeholder that Responsible for the software

Software

Group 6 Page 13
LM(Group 6) Product Back Log Document v1.1

is primary for leading the architecture, which includes the key

Architect system development technical decisions that constrain the
overall design for the project

This is a stakeholder that Implement the project

Coder
programs the software

5. References

Table 6. References
No Reference Note

https://www.lucidchart.com/blog/how-to-develop-a-product-backlog- How to create

1
in-agile product backlog

Product Backlog
2 https://www.atlassian.com/agile/scrum/backlogs
Example

Group 6 Page 14