C1SE.19 ProjectPlan SRS v2.0

International School
Capstone Project 1
CMU-SE 450
Project Plan
Version 2.0
Date: 10/10/2023
Smart Recruitment System

Submitted by
Dat, Nguyen Thanh
Thang, Nguyen Tran Anh
Khoa, Doan Ngoc Anh
Quang, Tran Minh
Approved by
Nguyen Tan Thuan
Proposal Review Panel Representative:

Name Signature Date
Capstone Project 1 - Mentor:

Name Signature Date
PROJECT INFORMATION
Project SRS
acronym
Project Title Smart Recruitment System
Start Date 19 Sep 2023 End Date 10 Dec 2023
Lead Institution International School, Duy Tan University

Project Mentor Thuan, Nguyen Tan, M.Sc.
Scrum master / Dat, Nguyen Thanh
Project Leader Email: nguyendat16111210@gmail.com
& contact Tel: 0352694246
details
ID: 26211242012
Partner Duy Tan University
Organization
Project Web
URL
Team members Name Email Tel
26211329003 Thang, anhthang2529@gmail.com 0869132529
Nguyen Tran
Anh
26211242069 Khoa, Doan 12.doanngocanhkhoa125@gm 0389876510

Ngoc Anh ail.com
24211208176 Quang, Tran quangyoung.tranminh@gmail 0329398805

Minh .com
REVISION HISTORY
Version Date Comments Author Approval
1.0 5/10/2023 Initial Release All members
2.0 10/10/2023 Initial Release All members X
TABLE OF CONTENTS
1. Project Overview.....................................................................................................1
1.1 Project Description................................................................................................1
1.2 Purpose and Scope................................................................................................1
1.2.1 Purpose...............................................................................................................1
1.2.2 Scope..................................................................................................................1
1.3 Assumptions and Constraints................................................................................1
1.4 Project Objectives.................................................................................................2
1.4.1 Standard Objectives............................................................................................2
1.4.2 Specific Objectives.............................................................................................3
1.5 Critical Dependencies............................................................................................3
1.6 Project Risk...........................................................................................................3
2 Project Development Approach...............................................................................4
2.1 Technical Process..................................................................................................4
2.1.1 Reasons for selecting..........................................................................................4
2.1.2 Agile Methodology............................................................................................4
2.2 Quality Management.............................................................................................6
2.3 Unit Testing Strategy............................................................................................8
2.4 Integration Testing Strategy..................................................................................9
2.5 System Testing Strategy........................................................................................9
3 Estimation.................................................................................................................9
3.1 Size........................................................................................................................9
3.3 Schedule..............................................................................................................11
3.3 Resource..............................................................................................................39
3.4 Infrastructure.......................................................................................................39
3.5 Training Plan.......................................................................................................40
3.6 Finance................................................................................................................40
4 Project Organization...............................................................................................41
4.1 Organization Structure........................................................................................41
4.2 Project Team.......................................................................................................42
5 Communication & Reporting.................................................................................42
6 Configuration Management....................................................................................43
7 Security Aspects.....................................................................................................43
Project Plan v2.0 - SRS
1. Project Overview
1.1 Project Description
Project code SRS Contract type Fixed price
Customer 2nd Customer

Project Level Group Project rank A
Group Team SE19 Division
Project Type External Project Manager/ Dat, Nguyen

Scrum master Thanh
Project Category Development Business domain
Application type Commercial Product
1.2 Purpose and Scope

1.2.1 Purpose
Build a smart job search application with CV creation feature. In addition, the
application also develops the feature to merge employers and candidates
Providing solutions to job search needs and saving time for employers and
recruiters.
Identify resources, time, budget, implement actual projects and ensure on
schedule and budget.
1.2.2 Scope
Providing job search solutions for employers, helping users create CVs easily.
A place to help employers post job content and vacancies so users can apply.
Detect the match between employers and applicants to help make recruitment
more effective
1.3 Assumptions and Constraints
No Description Note
Assumptions
1 Nodejs version v18.8.0 (or above) and lower version not supported. Scope
Customer reviewers will get seven days to approve a milestone External
2 document. If no comments are received within this time period, it Interfaces
will be considered as approved.
Constraints
1 The project is developed within 24 weeks and quarterly deployed on Schedule
Page | 1
the market.
2 The project shall conform to security requirements specified by the Security
customer
3 The product operates at a high level of performance and has a page Quality
load of no more than 5 seconds.
5 The project will be implemented by a team including 4 members Resources
6 The financial estimation for the project is at a budget limit of $5000 Budget
1.4 Project Objectives

1.4.1 Standard Objectives
Metrics Unit Committed Note

Start Date dd-mmm-yy 05-09-2023
End Date dd-mmm-yy 12-12-2023
Duration days 100 days
Maximum Team Size Person 4 Person
Billable Effort Person-day 21,5 days
Number of work hours per day for Person-hour 4 hours

one engineer
Target
Metrics Unit LSL Average USL Basic for
setting Goals
Quality
Customer Refer to Gx Target in
Satisfaction Point the year 2020,
8.5 9 9.5 5% higher than
previous project (A
project)
Leakage Wdef/UCP
Process NC/Ob
Compliance
Cost
Page | 2
Effort Efficiency % 70 80 90
Correction Cost % 60 65 70
Delivery
Timeliness % 85 90 95
Requirement
80 85 90
Completeness %
1.4.2 Specific Objectives

Based on human resources, time and budget, we will build a system that uses
intelligent algorithms to detect compatibility between candidates and employers.
The system operates with high performance and is safe for users.
User security data is encrypted and stored carefully to avoid data loss.
The system implemented by the project team minimizes errors and controls risks
well.
1.5 Critical Dependencies
No Dependency Expected delivery date Note
1 SRS 25-Sep-2023 Legacy system
2 VNPay system 25-Sep-2023 External System
3 Firebase storage Cloud 25-Sep-2023 External System
4 Mapbox 25-Sep-2023 External System
5 Google 25-Sep-2023 External System
6 Facebook 25-Sep-2023 External System
1.6 Project Risk
Risk Description Probab Impact I*P Mitigation
ility Strategy
Incorrect Developing the product 4 5 20 Discuss and
requirements which does not accord communicate
with the requirements frequently with
Stakeholders
Estimate working Actual working time is 3 5 15 Review old tasks and
time not enough to finish a evaluations to estimate
task compared to the for the new task.
estimated previous time Replan for each sprint.
Page | 3
People Team member who is ill, 3 3 9 Notify the scrum

has health problems, or master (or ask a
busy colleague to help
you)
Complete the assigned
tasks when possible
Lack of technical Detect harmful content in 2 4 8 Spend a lot of time for
experiences the video is a difficult learning and training
technique that all
members need to research
and develop.
Team Team members can 4 2 8 Conduct a meeting to
Communication conflict with each other share knowledge,
while discussing experience and
something related to the learning methods
project
2 Project Development Approach

2.1 Technical Process
2.1.1 Reasons for selecting
To keep up with today's increasingly changing technology trends, we
want a truly flexible and easy project development model to adapt to that change.
Our project will develop more new features in the future. We will continuously
update and apply new technologies that increase the attractiveness and
intelligence of the application.
Currently, our team is a small team with little experience in project
development. Therefore, we cannot avoid problems that arise in the software
development stages and requirements can be changed to be more suitable. For the
traditional model that requires managerial skills and high accuracy, it will not suit
our team. Applying Agile Scrum model will help us to solve these problems,
bring a lot of experience and best performance for project development.
2.1.2 Agile Methodology
Agile software development refers to a group of software development
methodologies based on iterative development, where requirements and solutions
evolve through collaboration between self-organizing cross-functional teams.
Agile software development is more than frameworks such as Scrum,
Extreme Programming, or Feature-Driven Development (FDD).
Agile software development is more than practices such as pair
programming, test-driven development, stand-ups, planning sessions, and sprints.
Page | 4
Agile software development is an umbrella term for a set of frameworks

and practices based on the values and principles expressed in the Manifesto for
Agile Software Development and the 12 Principles behind it. When you approach
software development in a particular manner, it’s generally good to live by these
values and principles and use them to help figure out the right things to do given
your particular context.
2.1.3 Scrum Process
About Scrum:
Scrum is a subset of Agile. It is a lightweight process framework for agile
development, and the most widely-used one.
Page | 5
Scrum is most often used to manage complex software and product

development, using iterative and incremental practices. Scrum significantly
increases productivity and reduces time to benefits relative to classic “waterfall”
processes. Scrum processes enable organizations to adjust smoothly to rapidly-
changing requirements and produce a product that meets evolving business goals.
An agile Scrum process benefits the organization by helping it to
 Increase the quality of the deliverable
 Cope better with change (and expect the changes)
 Provide better estimates while spending less time creating them
 Be more in control of the project schedule and state
2.2 Quality Management
2.2.1 Estimates of Defects to be detected
Pre-release review defects
Process Planned found by review Actual found by review
Requirement 13 10
Design 10 0
Coding 50 25
Other 10 5
Total 73 40
Pre-release test defects

Process Planned found by review Actual found by review
Requirement 13 10
Design 10 0
Coding 50 25
Other 10 5
Total 73 40
2.2.2 Strategy for Meeting Quality Objectives
Page | 6
Strategy Expected Benefits
Page | 7
Do defect prevention using the standard 15–25% reduction in defect

defect prevention guidelines and process; injection rate and about 5%
use standards developed in JavaScript for improvement in productivity
coding.
Group review of program specs for first Improvement in quality as overall
few/logically complex use cases. defect removal efficiency will
Group review of design docs/first time- improve; some benefits in
generated code by project leader, developer, productivity as defects will be
and one consultant. detected early
Introduction of RUP methodology and Approximately 5% reduction in

implementing the project in iterations. defect injection rate and 1%
Milestone analysis and defect prevention improvement in overall
exercise will be done after each Iteration. productivity
2.2.3 Quality Control
Review Item Type of Review Reviewer When
Proposal Group review Thuan Nguyen, Dat Initial
Nguyen, Khoa Doan,
Thang Nguyen,
Quang Tran
Project plan Project Group review Thuan Nguyen, Dat End of Initiation stage
schedule Group review Nguyen, Khoa Doan,
Test Plan One-person review Thang Nguyen,
Quang Tran
Business analysis and Group review Thuan Nguyen, Dat End of 90%
requirements Nguyen, Khoa Doan, requirements
specification document, Thang Nguyen,
Use Case catalog Quang Tran
Design document, Group review Thuan Nguyen, Dat End of 90% design
object model Nguyen, Khoa Doan,
Thang Nguyen,
Quang Tran
Stage plans One-person review Thuan Nguyen, Dat Beginning of each stage
Nguyen, Khoa Doan,
Thang Nguyen,
Quang Tran
Complex/first specsincl Group review Thuan Nguyen, Dat End of detailed design
diagrams time test Nguyen, Khoa Doan,
Generaed cases Thang Nguyen,
Page | 8
program interactive Quang Tran

Code Group review Thuan Nguyen, Dat After coding for first
Nguyen, Khoa Doan, few programs
Thang Nguyen,
Quang Tran
2.2.4 Measurements Program

Data to be Purpose Responsible When
collected
Size: No. of Early estimate project cost PM/SM At the end of stages
KLOC/ FP
Effort: No. Calculate project effort for Team members Daily
person-day scheduling
Quality: No. Early evaluate product quality and Reviewer, Right after the
defects detected the feasibility of the project Tester review/test
Schedule Divide work and allocate resources PM/SM Weekly and at the end
properly, ensure the project is of stages
completed on time and on budget
2.3 Unit Testing Strategy

Grey Box:
− It is a combination of a Black Box and White Box testing. It is the type of
testing in which tester aware with internal functionality of a method or unit but
not in a more deep level like white box testing. In this, the user partially aware
of the internal functionality of a system.
− Write test cases before fixing the defect and independent of each other.
− Write cases to verify behavior, also write test cases to ensure the performance
of the code
− Execute test cases continuously and frequently.
− Using tool: Install and run Jest for writing unit test in NodeJS
Isolation of a code
− Isolate function to test it more rigorously. Isolate code to do Automated Unit
Testing in a better way. Isolating functions/code helps to do testing in a good
way. It helps to reveal dependencies between functions of code.
2.4 Integration Testing Strategy
Page | 9
Bottom up Strategy:
− The components below are first written and these are integrated first. The
integration happens from bottom to top. If the calling component is yet to be
developed, it is replaced by a specially written component called a Drive
− When we finish each product backlog, we test it out before we finish.
Bigbang Strategy:
− All components are put together at the same time, there is no order, except all
are integrated at the same time.
− Towards the end of the project, we started to apply this tactic to test the entire
application.
2.5 System Testing Strategy
Automation strategy:
− Automation Testing or Test Automation is a software testing technique that
performs using special automated testing software tools to execute a test case
suite.
− The automation testing software can also enter test data into the System Under
Test, compare expected and actual results and generate detailed test reports.
Software Test Automation demands considerable investments of money and
resources.
− Testing tools: Katalon Studio.
Customer testing(Beta testing) strategy:
− Beta testing is a type of user acceptance testing where the product team gives
a nearly finished product to a group of target users to evaluate product
performance in the real world.
− We are rolling out a beta app on the Google Store early on for testing. After
that, we gathered all the feedback and improved our system.
3 Estimation
3.1 Size
(1 point = 2 hours)
All of the Functions Pointy
Authentication (Candidate, Employer, Admin) 18
Dashboard View (Admin, Employer) 16
Page | 10
Manage Job (Employer, Admin) 18

Manage Candidate (Admin, Employer) 18
Manage Employer (Admin) 16
Manage Category Job (Admin) 16
Analysis CV and Recommendation (Employer) 30
Contact Message (Candidate, Employer) 18
Search, Filter, and View Job(Candidate) 16
Apply Job (Candidate) 16
Write CV Online (Candidate) 30
Job Recommendation (Candidate) 30
3.2 Effort
The Effort estimation
Total Sprint 1 Sprint 2 Sprint 3 Sprint 4
Total %
Activity budgeted budget
/Process Effort ed
Usage Effort USD % USD % USD % USD %
(USD) Usage
(%)
Requireme
315.7$ 5 80.68 2 78.57 1 78.16 1 78.38 1
nt
Design 358.3$ 10 90.38 3 90.27 3 89.35 2 89.38 2
Coding 1276.5$ 25 320.5 7 310.6 5 322.1 6 323.1 7
Testing 695$ 18 137.77 5 171.67 4 173.87 4 175.77 5
Deploymen
419.1$ 12 104.7 3 104.7 3 104.7 3 104.7 3
t
Support for
Acceptance 328.8$ 5 81.2 1 81.2 1 84.2 2 82.2 1
Test
Project
301.7$ 5 74.43 1 74.59 1 77.43 2 75.33 1
Planning
Project
227.6$ 5 56.69 1 56.23 1 56.57 1 58.12 2
monitoring
Quality
457.2$ 7 102.3 1 118.3 2 118.3 2 118.1 2
Asurance
Page | 11
Training 220.1$ 8 55.05 2 55.02 2 55.02 2 55.02 2
Total 4600$ 100 1139 26 1141 23 1159 25 1160 26
3.3 Schedule
3.3.1 Project Milestone & Deliverable
Deployment App
3.3.2 Work Breakdown Structure
Page | 12
Page | 13
3.1.3 Detailed Schedule

No. Task Name Duratio Start Finish Assign to
n (Days)
I. Initial 3 04/09/2023 06/09/2023 All Member
1. Discuss project ideal 1 04/09/2023 04/09/2023 All Member
2. Gathering 1 05/09/2023 05/09/2023 All Member

Requirement
3. Create Proposal 1 06/09/2023 06/09/2023 All Member

Document
II. Start Up 15 07/09/2023 21/09/2023 All Member
1. Project Kick Off 1 07/09/2023 07/09/2023 All Member

Meeting
2. Create Document for 14 08/09/2023 21/09/2023 All Member

project
2.1. Create Project Plan 7 08/09/2023 14/09/2023 All Member

document
2.2. Create Product 2 15/09/2023 16/09/2023 Đạt

Backlog document
2.3. Create User Story 2 17/09/2023 18/09/2023 Khoa

document
2.4. Create Database 2 17/09/2023 18/09/2023 Đạt

document
2.5. Create User Interface 2 15/09/2023 16/09/2023 Thắng

document
2.6. Create Architecture 4 15/09/2023 18/09/2023 Đạt, Quang

document
2.7. Pre-study 1 19/09/2023 19/09/2023 All Member
2.8. Project kick off 1 20/09/2023 20/09/2023 All Member

meeting
III. Development 80 22/09/2023 10/12/2023 All Member
Page | 30
1. Sprint 1 20 22/09/2023 11/10/2023 All Member
1.1 Sprint Planning 1 22/09/2023 22/09/2023 All Member

Meeting
1.2 Create Sprint Backlog 1 23/09/2023 23/09/2023 Khoa

for Sprint 1
1.3 Create Test Plan 1 24/09/2023 24/09/2023 Quang

document for Sprint 1
1.4 Design UI 2 25/09/2023 26/09/2023 All Member
1.4.1 Design UI for 1 25/09/2023 25/09/2023 Đạt

Dashboard View
(Admin)
1.4.2 Design UI for 1 25/09/2023 25/09/2023 Thắng

Manage User
1.4.3 Design UI for 1 25/09/2023 25/09/2023 Khoa

Manage Employer
1.4.4 Design UI for 1 25/09/2023 25/09/2023 Quang

Manage Candidate
1.4.5 Design UI for 1 26/09/2023 26/09/2023 Đạt

Manage Resume

Manage Job Category

Manage Transaction

Manage Job Listings
1.4.9 Design UI for Evaluate 0.5 26/09/2023 26/09/2023 Khoa, Thắng

suitable job
1.4.10 Design UI for job 0.5 26/09/2023 26/09/2023 Đạt, Quang

recommend
1.5 Code 10 27/09/2023 06/10/2023 All Member
1.5.1 [Frontend] Dashboard 3 27/09/2023 29/09/2023 Thắng,Quang
Page | 31
View Page (Admin)
1.5.2 [Frontend] Manage 2 30/09/2023 01/10/2023 Thắng

User Page
1.5.3 [Frontend] Manage 3 30/09/2023 02/10/2023 Quang

Employer Page

Candidate Page

Job Category Page

Transaction Page

Job Listings Page
1.5.8 [Frontend] Evaluate 1 06/10/2023 06/10/2023 Thắng

suitable job
1.5.9 [Frontend] job 1 06/10/2023 06/10/2023 Quang

recommend
1.5.10 [Backend] 2 27/09/2023 28/09/2023 Khoa, Đạt

Authentication and
Authorization
1.5.11 [Backend] Dashboard 2 29/09/2023 30/09/2023 Khoa, Đạt

View Page (Admin)
1.5.12 [Backend] Manage 2 01/10/2023 02/10/2023 Khoa

User Page
1.5.13 [Backend] Manage 2 01/10/2023 02/10/2023 Đạt

Employer Page

Candidate Page

Transaction Page

Job Category Page
Page | 32

Job Listings Page
1.5.18 [Backend] Evaluate 1 06/10/2023 06/10/2023 Khoa

suitable job
1.5.19 [Backend] job 1 06/10/2023 06/10/2023 Đạt

recommend
1.6 Testing & Fix Bug 3 07/10/2023 09/10/2023 All Member
1.7 Release Sprint 1 2 10/10/2023 11/10/2023 All Member
1.7.1 Sprint 1 Review 1 10/10/2023 10/10/2023 All Member

Meeting
1.7.2 Sprint 1 Retrospective 1 11/10/2023 11/10/2023 All Member
2 Sprint 2 20 12/10/2023 31/10/2023 All Member
2.1 Sprint Planning 1 12/10/2023 12/10/2023 Thắng, Đạt

Meeting

for Sprint 2


Register Employer
Page
2.4.2 Design UI for 1 15/10/2023 15/10/2023 Đạt

Dashboard View
(Employer)

Candidate Page

Manage Resume
(Employer)

Manage Job Posting
Page | 33
Page
2.4.6 Design UI for 1 16/10/2023 16/10/2023 Đạt

Manage Interview
Schedule Page
(Employer)

Manage CV &
Candidate Page Page
2.4.8 Design UI for Contact 1 16/10/2023 16/10/2023 Quang

Message Page
2.5 Code 10 17/10/2023 26/10/2023 All Member
2.5.1 [Frontend] Register 3 17/10/2023 19/10/2023 Quang

Employer Page
2.5.2 [Frontend] Dashboard 4 17/10/2023 20/10/2023 Thắng

View (Employer)

Job Posting Page

CV & Candidate Page
2.5.5 [Frontend] Message 3 24/10/2023 26/10/2023 Quang

Page
2.5.6 [Frontend] Profile 3 24/10/2023 26/10/2023 Thắng

Employer Page
2.5.7 [Backend] Register 3 17/10/2023 19/10/2023 Khoa

Employer Page
2.5.8 [Backend] Dashboard 4 17/10/2023 20/10/2023 Đạt

View (Employer)

Job Posting Page
(Employer)

CV & Candidate Page
(Employer)
Page | 34
2.5.11 [Backend] Message 3 24/10/2023 26/10/2023 Khoa

Page (Employer)
2.5.12 [Backend] Profile 3 24/10/2023 26/10/2023 Đạt

Employer Page

Meeting
3. Sprint 3 20 1/11/2023 20/11/2023 All Member
3.1 Sprint Planning 1 1/11/2023 1/11/2023 Thắng, Khoa

Meeting

for Sprint 3

3.4.1 Design UI for Login 1 04/11/2023 04/11/2023 Thắng

Page

Register Page
3.4.3 Design UI for Profile 1 04/11/2023 04/11/2023 Đạt

Page

Category Page
3.4.5 Design UI for Job 1 05/11/2023 05/11/2023 All Member

Home Page
3.5 Code 10 06/11/2023 15/11/2023 All Member
3.5.1 [Frontend] Login 2 06/11/2023 07/11/2023 Quang

Page
Page | 35
3.5.2 [Frontend] Register 2 08/11/2023 09/11/2023 Quang

Page

profile Page
3.5.4 [Frontend] Home 6 10/11/2023 15/11/2023 Quang

Page
3.5.5 [Frontend] Job 7 09/11/2023 15/11/2023 Thắng

Category Page

profile Page
3.5.7 [Backend] Home 4 06/11/2023 09/11/2023 Đạt

Page
3.5.8 [Backend] Job 6 10/11/2023 15/11/2023 Khoa,Đạt

Category Page

Meeting
4 Sprint 4 20 21/11/2023 10/12/2023 All Member
4.1 Sprint Planning 1 21/11/2023 21/11/2023 All Member

Meeting

for Sprint 4

4.4.1 Design UI for Job 1 24/11/2023 24/11/2023 Thắng

Wish List Page
4.4.2 Design UI for 1 24/11/2023 24/11/2023 Đạt
Page | 36
Company Profile
Page

Schedule Interview
Page

Resume & CV Online
Page
4.5 Code 10 26/11/2023 05/12/2023 All Member
4.5.1 [Frontend] Job Wish 2 26/11/2023 27/11/2023 Quang

List Page
4.5.2 [Frontend] Company 2 28/11/2023 29/11/2023 Quang

Profile Page
4.5.3 [Frontend] Schedule 2 26/11/2023 27/11/2023 Thắng

Interview Page
4.5.4 [Frontend] Resume & 6 30/11/2023 05/12/2023 Quang,

CV Online Page Thắng
4.5.5 [Backend] Job Wish 2 26/11/2023 27/11/2023 Khoa

List Page
4.5.6 [Backend] Company 2 28/11/2023 29/11/2023 Khoa

Profile Page
4.5.7 [Backend] Schedule 2 26/11/2023 27/11/2023 Đạt

Interview Page
4.5.8 [Backend] Resume & 6 30/11/2023 05/12/2023 Khoa, Đạt

CV Online Page and
ChatBot

Meeting
IV. Project's Meeting 1 11/12/2023 11/12/2023 All Member
Page | 37
V. Final Release 1 12/12/2023 12/12/2023 All Member

3.1.4 Project Schedule
The detail project schedule is available in here The Project Schedule is weekly
updated by the Project Manager.
No. Activity Start date Responsible Note
Defect Prevention
1 Sprint 1 22/09/2023 All members
Quality Control
1 Review: Work Product 1 10/10/2023 Mentor - Team members
Project Tracking
1 Sprint Plan Meeting 22/09/2023 Mentor - Team members
2 Sprint 1 Review Meeting 10/10/2023 Mentor - Team members
9 Final Plan Meeting 12/12/203 Mentor - Team members
10 Final Release Meeting 12/12/2023 Mentor - Team members
QA
Deliverable 1 10/10/2023 Mentor - Team members
Page | 38
Baseline audit: Startup 12/12/2023 Mentor - Team members

Baseline audit: Wrap-up 12/12/2023 Mentor - Team members
3.3 Resource
Specified as in the section Project Team
3.4 Infrastructure
Expected
Work/Product Purpose Availability by Note
Development Environment
Window 10, 11 Operating System Initiation stage
Visual Studio Code Initiation stage
MongoDB DBMS Initiation stage
JavaScript Development language for Initiation stage

Web interface
JavaScript Development language for Initiation stage
Restful API
Hardware & Software
4 Personal Laptop Design, Develop and Initiation stage
emulation
Other Tools
Git, Github Source version control Definition stage
Postman API Testing Construction stage
Figma UI/UX Design Definition stage
Draw.io Diagramming Initiation stage
Trello Task tracking Initiation stage
3.5 Training Plan

Training Area Participants When, Waiver Criteria
Page | 39
Duratio
n
Technical
JavaScript Language All members 7 days If already trained
Detect harmful contents All members 10 hrs If already trained
ReactJS All members 10 days If already trained
NodeJS All members 10 days If already trained
Business domain
Banking All members 2 days
Process
Quality system All members 3 hrs If already trained
Configuration All members 2 hrs If already trained for
management(Git and bit CC. For others, on-the- job training
bucket tool)
Group review All members 4 hrs If already trained
Defect prevention All members 4.5 hrs Mandatory
Trello tool All members 1 day If already trained
Agile Scrum All members 2 hrs Mandatory
3.6 Finance
No. Criteria Price (USD) Amount Total (USD)
1 Working hour $2 2300 $ 4600
$ 4600
Description Amount Unit

Number of member 4 Person
Number of working per day 4 Hours
Number of work days per week 5 Days
The cost per member per week 20 USD
The number of working days 100 Days
Explain: Amount of working hours = 4 member * 4 hours * 100 days

4 Project Organization
Page | 40
4.1 Organization Structure

Role Responsibility Name
Scrum Master - Communicate the value of Scrum Dat,
Nguyen
- Teach the organization on Scrum to maximize business Thanh
value
- Preserve the integrity and spirit of the Scrum framework
- Serve as a coach and mentor to members of the Team
- Respectfully hold the Team, Product Owner and
Stakeholders accountable for their commitments
- Continually work with the Team and business to find and
implement improvements
- As a timekeeper
- Helping the team agree on what they can achieve during
each development sprint (or other period of time).
- Facilitating the daily standup (sometimes called the daily
scrum) and helping the team reach consensus on each of
the three questions.
- Helping the team continuously make progress on the
project by making sure each person is working on the right
tasks, helping to remove any obstacles to the team
members’ progress, and protecting the team from
distractions.
Product Owner - A spokesperson for the customer and needs to represent Khoa, Doan
them Ngoc Anh
- Gathers, manages, and prioritizes the product backlog.
- Has technical product knowledge or specific domain
expertise.
- Tracks progress towards the release of a product.
Developer - Responsible for quality All

- Responsible for delivering the potentially shippable members
product of the Application each sprint
- Report progress based on the remaining time
- Self-organized
- Owns the Sprint backlog
Page | 41
Mentor - Guide on the process. Thuan,

Nguyen
- Monitoring all activities of the Team. Tan
- Help with anything.
- Reviews project documents
- Reviews product
4.2 Project Team

Full Name Position
Thuan, Nguyen Tan Mentor
Dat, Nguyen Thanh Scrum Master, Dev-team
Khoa, Doan Ngoc Anh Product Owner, Dev-team

Thang, Nguyen Tran Anh Dev-team
Quang, Tran Minh Dev-team
5 Communication & Reporting

Audience / Topic / Frequency Method
Attendees Deliverable
Scrum Master, Members Daily meeting Daily Face to Face / Zoom
Meeting / Zalo Chat
Scrum Master, Members Sprint Planning When starting a sprint Zoom Meeting
Meeting
Scrum Master, Members, Sprint Review When finishing a Face to face, Zoom
Mentor Meeting sprint Meeting
Scrum Master, Members Sprint When the sprint Face to Face
Retrospective review finish
Scrum Master, Members Individual Meeting When need Face to Face, Zoom
Meeting, Message
Scrum Master, Members, Working report, Once a week Face to face
Mentor review problems
6 Configuration Management
<Refer to the CM plan or insert here the contents of the CM plan as appropriated>
7 Security Aspects
• The credential data is carefully secured by multi-layer encryption and data
Page | 42
integrity is ensured. Regularly back up system data.

• Research on network attack prevention solutions to ensure data security, avoid
being exploited and stolen data by hackers.
• Deploy project architecture with a high priority in security. Optimized
architectural solutions enable the deployment of data security with 99%
reliability.
• Social media, sharing and use of data must be approved by the end user and
verified by the organization's management.
REFERENCES
No Reference item Issued Date Source Note
1 Agile Scrum 04-Apr-21 https://www.atlassian.com/agile
https://www.cprime.com/resources/
what-is-agile-what-is-scrum/
https://www.agilealliance.org/
agile101/
The Scrum Framework by
International Scrum Institute
2 Software Standards 05-Apr-21 https://www.nws.noaa.gov/oh/hrl/
developers_docs/General_So
ftware_Standards.pdf
https://standards.ieee.org/standard/
12208-2017.html
https://sw-eng.larc.nasa.gov/
Page | 43

C1SE.19 ProjectPlan SRS v2.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C1SE.19 ProjectPlan SRS v2.0

Uploaded by

Copyright:

Available Formats

International School

Smart Recruitment System

Proposal Review Panel Representative:

Capstone Project 1 - Mentor:

Lead Institution International School, Duy Tan University

26211242069 Khoa, Doan 12.doanngocanhkhoa125@gm 0389876510

24211208176 Quang, Tran quangyoung.tranminh@gmail 0329398805

Customer 2nd Customer

Project Type External Project Manager/ Dat, Nguyen

Application type Commercial Product

1.2 Purpose and Scope

1.4 Project Objectives

Metrics Unit Committed Note

End Date dd-mmm-yy 12-12-2023

Duration days 100 days

Maximum Team Size Person 4 Person

Billable Effort Person-day 21,5 days

Number of work hours per day for Person-hour 4 hours

1.4.2 Specific Objectives

People Team member who is ill, 3 3 9 Notify the scrum

2 Project Development Approach

Agile software development is an umbrella term for a set of frameworks

2.1.3 Scrum Process

Scrum is most often used to manage complex software and product

Pre-release test defects

2.2.2 Strategy for Meeting Quality Objectives

Strategy Expected Benefits

Do defect prevention using the standard 15–25% reduction in defect

Introduction of RUP methodology and Approximately 5% reduction in

program interactive Quang Tran

2.2.4 Measurements Program

2.3 Unit Testing Strategy

2.4 Integration Testing Strategy

Manage Job (Employer, Admin) 18

Design 358.3$ 10 90.38 3 90.27 3 89.35 2 89.38 2

Coding 1276.5$ 25 320.5 7 310.6 5 322.1 6 323.1 7

Testing 695$ 18 137.77 5 171.67 4 173.87 4 175.77 5

Training 220.1$ 8 55.05 2 55.02 2 55.02 2 55.02 2

Total 4600$ 100 1139 26 1141 23 1159 25 1160 26

3.3.2 Work Breakdown Structure

3.1.3 Detailed Schedule

1. Discuss project ideal 1 04/09/2023 04/09/2023 All Member

2. Gathering 1 05/09/2023 05/09/2023 All Member

3. Create Proposal 1 06/09/2023 06/09/2023 All Member

II. Start Up 15 07/09/2023 21/09/2023 All Member

1. Project Kick Off 1 07/09/2023 07/09/2023 All Member

2. Create Document for 14 08/09/2023 21/09/2023 All Member

2.1. Create Project Plan 7 08/09/2023 14/09/2023 All Member

2.2. Create Product 2 15/09/2023 16/09/2023 Đạt

2.3. Create User Story 2 17/09/2023 18/09/2023 Khoa

2.4. Create Database 2 17/09/2023 18/09/2023 Đạt

2.5. Create User Interface 2 15/09/2023 16/09/2023 Thắng

2.6. Create Architecture 4 15/09/2023 18/09/2023 Đạt, Quang

2.7. Pre-study 1 19/09/2023 19/09/2023 All Member

2.8. Project kick off 1 20/09/2023 20/09/2023 All Member

III. Development 80 22/09/2023 10/12/2023 All Member

1. Sprint 1 20 22/09/2023 11/10/2023 All Member

1.1 Sprint Planning 1 22/09/2023 22/09/2023 All Member

1.2 Create Sprint Backlog 1 23/09/2023 23/09/2023 Khoa

1.3 Create Test Plan 1 24/09/2023 24/09/2023 Quang

1.4 Design UI 2 25/09/2023 26/09/2023 All Member

1.4.1 Design UI for 1 25/09/2023 25/09/2023 Đạt