Software project management project beautyspa store management application
Bạn đang xem bản rút gọn của tài liệu. Xem và tải ngay bản đầy đủ của tài liệu tại đây (1.85 MB, 43 trang )
Software project management
Project: Beauty&Spa Store Management Application
Class: E18CN02
Group 6
Member:
- Dương Hồng Vũ
- Hồng Duy Đạt
- Ngơ Đăng Thái
- Đỗ Xn Hiếu
download by :
Table of Contents
I) Member’s distribution: .............................................................................................................................. 2
II) SOW and project charter:......................................................................................................................... 3
III) WBS: ...................................................................................................................................................... 7
IV) Scheduling: ........................................................................................................................................... 10
V) Risk management: ................................................................................................................................. 14
VI) Communication management: .............................................................................................................. 24
VII) Human resource management: ........................................................................................................... 27
VIII) Quality management: ......................................................................................................................... 32
IX) Configuration management: ................................................................................................................. 34
1
download by :
I) Member’s distribution:
STT
Name
1
Đỗ Xuân Hiếu
2
Hoàng Duy Đạt
Work
SOW and project charter document
Configuration management document
WBS
Scheduling
Human resource management documet
3
Ngô Đăng Thái
Quality management document
Power point creating
Risk management document
4
Dương Hoàng Vũ
Communication management document
Presenting
download by :
II) SOW and project charter:
1) Statement of work (SOW):
Statement of Work
A. Introduction
Project name: Beauty&Spa Store Management Application
Client: A Beauty&Spa store
B. Objectives
This project will construct an application which will be installed in employee computer
and running on web browser. This application will have GUI that easy-to-use and
provide functions that make store management easier, reduce the workload for manager,
more convenient and more exactly.
C. Scope Of Work
Arcording to customer’s requirement above, propose an application with following
feature:
-
This is a web application which will be internally used inside a store.
This application could be installed on many computers of the store employees.
However, the database is stocked on the store server
This application supports the management for only one store.
Only used by 2 types of employees
• Store manager
• Receptionist
-
Include:
• Import product management
• Check in
• Payment
• Statistic by revenue
• Statistics by imported products
-
Not include:
• Infrastructure management
• Working days management
• News showing
3
download by :
• Internet connection
The project is expected to start in 01/09/2021 and complete in 01/12/2021.
2) Project charter:
Project Charter
1. Project Overall
Project name: Beauty&Spa Store Management Application
Project manager:
Date of Project Authorization: 01/09/2021
Stakeholder:
Sponsor: VNPT
Client: A Beauty&Spa store
User: Employees of the store
Business adviser: Store owner
Project Team:
No.
1
2
3
4
Role
PM
BA
Developer
Tester
Number
1
2
8
4
2. Project Objective
This project will construct an application which will be installed in employee
computer and running on web browser. This application will have GUI that easyto-use and provide functions that make store management easier, reduce the
workload for manager, more convenient and more exactly.
It helps the manager to manage all information of bills, customer, employee, service
and control product in warehouse.
4
download by :
It also provide functions which help receptionist to do counter staff like receive
customers and make a payment automatically.
3. Project Scope – Deliverables
- Web application with following functions:
• Import product management
▪ Search engine
▪ Add/edit/delete
▪ Print out invoice
• Check in
▪ Search engine
▪ Add/edit/delete
• Payment
▪ Search engine
▪ Payment
▪ Print out invoice
• Statistic by revenue
▪ Statistic
▪ Order by date
▪ Order by money
▪ View detail revenue of each service
• Statistic by imported products
▪ Statistic
▪ Order by date
▪ Order by amount
▪ View detail imported product of each product
- Not include:
• Infrastructure management
• Working days management
• News showing
• Internet connection
- Instruction
- Install database system to store’s server
- Install environment
- Maintenance
5
download by :
4. Project Schedule
Event
Estimated time Projected Date Completed
Comment
Date
Project Management
3 days
01/09/2021
03/09/2021
Requirement gathering
6 days
06/09/2021
13/09/2021
Analysis
13 days
14/09/2021
30/09/2021
Design
21 days
01/10/2021
29/10/2021
Implementation
12 days
01/11/2021
16/11/2021
Testing
6 days
17/11/2021
24/11/2021
Deployement
2 days
25/11/2021
30/11/2021
- The first version will be release and implement on store employee’s computer on
01/12/2021
5.
-
Assumptions
This will be a web-based application
System will run on existing networking and computer resources
The front-end will be built using Angular 10
The back-end will be built using Spring framework
Our in-house development team will do the work
All import data will be available in JSON format
We will partner with a third-party company to create the security system
Database Management System will be MySQL Server
6. Project Approval & Signatures
Name
Title
Project Manager
Project Sponsor
Client
Signature
Date
6
download by :
III) WBS:
WBS
0.0 Beauty&Spa Store Management Application
1.0 Project Management (3 days)
2.0 Requirement gathering
2.1 Unified Modeling Language (3 days)
3.0 Design and Analysis
3.1 Analysis
3.1.1 UML Structure Diagrams (3 days)
3.1.2 Making scenario (3 days)
3.1.3 Static analysis (3 days)
3.1.3.1 Entity class (3 days)
3.1.3.2 Module class diagram
3.1.3.2.1 Create class diagram for manager’s modules (2 days)
3.1.3.2.2 Create class diagram for receptionist’s modules (2 days)
3.1.3.2.3 Create class diagram for client’s modules(2 days )
3.1.4 Dynamic analysic
3.1.4.1 Sequence diagram
3.1.4.1.1 Create Sequence diagram for manager’s modules (2 days)
3.1.4.1.2 Create Sequence diagram for receptionist’s modules (2 days)
3.1.4.1.3 Create Sequence diagram for client’s modules(2 days )
3.1.4.2 State diagram
download by :
3.1.4.2.1 Create State diagram for manager’s modules (2 days)
3.1.4.2.2 Create State diagram for receptionist’s modules (2 days)
3.1.4.2.3 Create State diagram for client’s modules(2 days )
3.1.5 Review (1 days)
3.2 Design
3.2.1 Class diagram
3.2.1.1 Design class diagram for System(2 days)
3.2.1.2 Design class diagram for manager’s modules (2 days)
3.2.1.3 Design class diagram for receptionist’s modules (2 days)
3.2.1.4 Design class diagram for client’s modules(2 days )
3.2.2 Database diagram (3 days)
3.2.3 Static design
3.2.3.1 Interface design
3.2.3.1.1 Design interface for manager’s modules (2 days)
3.2.3.1.2 Design interface for receptionist’s modules (2 days)
3.2.3.1.3 Design interface for client’s modules(2 days )
3.2.4 Dynamic design
3.2.4.1 Activity diagram (3 days)
3.2.4.2 Sequence diagram
3.2.4.2.1 Sequence diagram for manager’s modules (2 days)
3.2.4.2.2 Sequence diagram for receptionist’s modules (2 days)
3.2.4.2.3 Sequence diagram for client’s modules(2 days )
8
download by :
3.2.5 Package diagram (3 days)
3.2.6 Deployment diagram (3 days)
3.2.7. Review(1 days)
4.0 Implementation
4.1 Frontend
4.1.1 Create HTML (3 days)
4.2 Backend
4.2.1 Database implementation (3 days)
4.2.2 Java development
4.2.2.1 Code module for manager’s modules (3 days)
4.2.2.2 Code module for receptionist’s modules (3 days)
4.2.2.3 Code module for client’s modules (3 days)
4.3 Review
4.3.1 JUnit test (3 days)
5.0 Testing
5.1 Black box test case (3 days)
6.0 Deployement
6.1 Set up environment for customer(2 days)
6.2 Record user instructions (2 days)
9
download by :
IV) Scheduling:
10
download by :
11
download by :
download by :
13
download by :
V) Risk management:
1) List of risk with general information:
ID
1
Risk Event
Owner
WBS
WBS Name
Number
Area of impact
Set up environment for
Software cannot be installed suitablely with client's side
Project Sponsor
6.1
customer
W/B
2
Scope is required to be wider at the end
PM
4.3
Review
W/B/S
3
System does not perform like client think
PM
4.3
Review
W/S
4
Supplier exceeds budget
PM
3.2.6
Deployment diagram
W/S
5
Client wants the price to be lower
PM
4.3
Review
B/S
6
Unavailable resources
Project Sponsor
3.2.6
Deployment diagram
B
7
Customer lacks of resources
PM
3.2.6
Deployment diagram
B
8
Added time to update
Team Manager
4.0
implementation
B
9
Added time to train employee
Team Manager
4.0
implementation
B
10
Losing information while updating
Team Manager
4.0
implementation
B
11
Requirement grows uncontrollablely
PM
3.2.6
Deployment diagram
B
12
Problem cannot be solved
Team Manager
4.0
implementation
W/B
13
Argument between members which cannot be solve in short time
Team Manager
3.0
Design and analysis
B
download by :
14
Deliverables are not completed in time
Team Manager
4.0
implementation
S
15
System develops in wrong direction
Project Sponsor
4.3
Review
W
16
Some requirements are wrong or missed
Project Sponsor
4.3
Review
B/S
17
An important member quits unexpectedly
Team Manager
4.0
implementation
B/S
Too much useless time during project
Team Manager
4.0, 3.0
19
Scope is not clear
PM
20
Requirement cannot be understood
21
A change in requirement causes the huge change in project
22
23
18
24
implementation, Design and
analysis
B
3.2.6
Deployment diagram
S
PM
3.2.6
Deployment diagram
S
PM
4.3
Review
B/S
Consulting delays
PM
3.2.7
Review
B/S
Customer tends to refuse approving the product of project
PM
4.3
Review
W/B
Team Manager/
Product is leaked and sold illegally
PM
3.0
Design and analysis
W/B
25
Some application is accused of not having copyright
Project Sponsor
4.3
Review
W/B/S
26
Document and product are not synchronized
Project Sponsor
6.1
Record user instructions
S
27
Too many errors in system
Team Manager
4.3
Review
B
28
Fire accident causing destruction of all computers storing project
PM
4.0
implementation
W/B
29
Server is hacked and all project is lost
PM
4.0
implementation
W/B
2) Risk analysis:
ID
1
Risk Event
Software cannot be installed suitablely
with client's side
Probable Impact Date
25/11/2021
Risk Probability
Medium
Risk Impact
High
15
download by :
Severity
High
Rank
20
2
Scope is required to be wider at the end
13/11/2021
Low
High
Medium
28
3
System does not perform like client think
13/11/2021
High
High
High
19
4
Supplier exceeds budget
27/10/2021
High
High
High
5
5
Client wants the price to be lower
13/11/2021
High
Medium
High
6
6
Unavailable resources
27/10/2021
Medium
Medium
Medium
21
7
Customer lacks of resources
27/10/2021
High
Medium
High
7
8
Added time to update
5/11/2021
Medium
Medium
Medium
25
9
Added time to train employee
5/11/2021
Medium
Medium
Medium
26
10
Losing information while updating
5/11/2021
Medium
High
High
18
11
Requirement grows uncontrollablely
12
Problem cannot be solved
13
Argument between members which
cannot be solve in short time
27/10/2021
High
High
High
17
5/11/2021
Medium
High
High
8
16/9/2021
Very High
Medium
High
9
5/11/2021
High
High
High
22
4
14
Deliverables are not completed in time
15
System develops in wrong direction
13/11/2021
Low
Very High
High
16
Some requirements are wrong or missed
13/11/2021
Very High
High
Very High
1
17
An important member quits unexpectedly
5/11/2021
Medium
High
High
16
18
Too much useless time during project
16/9/2021
Very High
Medium
High
15
19
Scope is not clear
27/10/2021
Very High
High
Very High
2
20
Requirement cannot be understood
27/10/2021
Very High
High
Very High
3
13/11/2021
High
High
HIgh
14
27/10/2021
High
Medium
High
10
21
22
A change in requirement causes the huge
change in project
Consulting delays
16
download by :
23
24
25
26
27
28
29
Customer tends to refuse approving the
product of project
Product is leaked and sold illegally
Some application is accused of not having
copyright
Document and product are not
synchronized
Too many errors in system
Fire accident causing destruction of all
computers storing project
Server is hacked and all project is lost
13/11/2021
Low
Very High
High
11
16/9/2021
Low
Very High
High
12
13/11/2021
Low
High
Medium
27
29/11/2021
Medium
Low
Medium
29
13/11/2021
High
High
High
13
5/11/2021
Low
Very High
High
23
5/11/2021
Low
Very High
High
24
3) Risk Mitigation:
ID
Mitigation
Risk event
Mitigation Task
Strategy
Responsible
Status
- Arrange a meeting between customer and installing
team to ask about the system of client.
- In the meeting, customer and client will discuss about
1
Software cannot be installed suitablely
with client's side
Avoid
the system installed.
- If something is hard to understood, there will be a
need for team to come to client's place to study the
client's side system properly to avoid this problem
17
download by :
Developer Team
Planned
- Discuss with team about this.
- Assess the difficulty of this request for the bargain
2
Scope is required to be wider at the end
Contain
with client.
PM
Planned
PM
Planned
PM
Planned
PM
Planned
- Meet client to bargain, give our offer, the increasing in
payment or what we can do for their request.
- Ask client what they does not satisfy.
- Assess the problem with team
3
System does not perform like client think
Contain
- If it is simple, fix it, else try to satisfy them with some
speech as much as you can
- Have a meeting with team to figure out what is
needed to reduce the cost (available tools, open
source,…)
4
Supplier exceeds budget
Contain
- Have a meeting with client to bargain with them as
much as possible, try to offer client some new service
that the team can add to the deliverables in order to
make the bargain more reasonable.
- Use the contract to bargain with client.
- If the price is reasonable, we can agree with some
5
Client wants the price to be lower
Contain
percentage, else we have to say something reasonable
to make sure both satisfy, we can recevie our profit
while not lose any client in the future
6
Unavailable resources
Contain
- Have a meet with team to gain new knowledge about
PM and Team
tools and solution can solve the problem.
Manager
18
download by :
Planned
- If the tool, the new application is able to cause cost
increasing, we can have a meet client to baragin, give
them some reason to accept the problem
- Arrange a meeting between customer and installing
team to ask about the system of client.
- In the meeting, customer and client will discuss about
7
Customer lacks of resources
Establish
contingency
the system installed.
Developer Team
Planned
PM
Planned
PM
Planned
PM
Planned
- If something is hard to understood, there will be a
need for team to come to client's place to study the
client's side system properly to avoid this problem
- re-schedule.
- Assess whether some work can be reduced.
8
Added time to update
Ignore/Accept
- If updating consumes too much time, we need to
inform to client about the increasing of time.
- Have a meet with team to figure out the way to
recover the data as soon as possible.
9
Added time to train employee
Ignore/Accept
- Re-schedule.
- we need to inform to client about the increasing of
time if lots of time can be consumed.
- Have a meet with team to figure out the way to
10 Losing information while updating
Ignore/Accept
recover the data as soon as possible.
- Re-schedule.
19
download by :
- we need to inform to client about the increasing of
time if lots of time can be consumed.
- have a meet with the team to know how difficult the
requests are.
11 Requirement grows uncontrollablely
Contain
- If the request is simple, deal with it.
- If the request is complicated, we have to deal with
Project Sponsor
and PM
Planned
client to remove it or increase the cost and time for it.
- if a team cannot silve, we will have to ask any help
from other source to solve the proble as much as
possible.
12 Problem cannot be solved
Ignore/Accept
- Bargain with client can be neccessay if cost is
PM and Team
increased to solve the problem.
Manager
Planned
- If the problem is too hard, we can consider to drop the
project or deal with client to change the direction
where we can solve the problem.
- Have a meeting among team members to assess the
problem.
- Every member will give their opinion about the
13
Argument between members which
cannot be solve in short time
Contain
argument to persuade their idea.
- Team leader will decide which idea is right or wrong
and analyze ideas.
- Vote is needed if arguement cannot be solved easily.
20
download by :
Team Manager
Planned
- Have a meet with team to figure out the way to
recover the data as soon as possible.
14 Deliverables are not completed in time
Contain
- Re-schedule.
PM
Planned
- we need to inform to client about the increasing of
time if lots of time can be consumed.
- Focusing on testing and supervising in the work of
analysis and design to not let it out of scope.
15 System develops in wrong direction
Avoid
- Have some periodic meeting to analyze the work of
Team Manager
and PM
team.
Planned
- Ambiguty is highly alerted among team.
- Focusing on testing and supervising in the work of
analysis and design to not let it out of scope.
16 Some requirements are wrong or missed
Establish
- Have some periodic meeting to analyze the work of
contingency
Team Manager
and PM
Planned
team.
- Ambiguty is highly alerted among team.
- Always have a substitution for an important position.
- when a member quits, we have to ask him/her to
17
An important member quits
Establish
unexpectedly
contingency
transfer the work to the substitution as soon as posible.
Team Manager
Planned
Team Manager
Planned
- Reschedule to make sure the work transfering does
not affect too much the deadline.
- Watch schedule to know which work can be taken
18 Too much useless time during project
Contain
parallelly by team
21
download by :
- Have a meet with team to collect and understand the
ambiguty.
19 Scope is not clear
Contain
- Conatct with client to figure these out to inform the
PM
Planned
PM
Planned
PM
Planned
PM
Planned
PM
Planned
team later.
- Have a meet with team to collect and understand the
ambiguty.
20 Requirement cannot be understood
Contain
- Conatct with client to figure these out to inform the
team later.
- Assess the problem.
21
A change in requirement causes the huge
change in project
Contain
- Have a meet with client to bargain about the
increasing in cost and time
- Watch schedule to know which work can be taken
parallelly during the delay to avoid lots of dead time.
22 Consulting delays
Ignore/Accept
- Assess the delay and bargain with client to increase
the time for project if necessary
- Focus on contract when project is created
23
Customer tends to refuse approving the
product of project
Avoid
- Try to consider some rules and constraints to avoid
this proble.
- Always assess the product and prepare security and
24 Product is leaked and sold illegally
25
Some application is accused of not
having copyright
Establish
contingency
authorization for the project to avoid when it is
initialized
Project Sponsor
and PM
Planned
- When use an availabe application from another
Avoid
source, must consider the copyright.
22
download by :
Project Sponsor
Planned
- Always assess the tools and applications' copyright
when the team member gives any tools and apps to
apply to the project.
- have a review after a document is completed.
26
Document and product are not
synchronized
Contain
- Perform the system following the documet to make
Team Manager
Planned
Team Manager
Planned
PM
Planned
Developer Team
Planned
sure the document is right before deliver to client.
- Separate program to many parts to supervise easily to
test and find errors easier or create a system of errors
27 Too many errors in system
Establish
to compare and find easier.
contingency
- Build some standard and structure of coding and
documents to avoid errors and be easy to transfer and
follow the work.
- Always prepare another server or side to restore back-
28
Fire accident causing destruction of all
Establish
computers storing project
contingency
up
- update the back-up after each milestone.
- Always prepare another server or side to restore backup
29 Server is hacked and all project is lost
Establish
contingency
- update the back-up after each milestone.
- Depend on the importance of the project, high security
need to be considered.
23
download by :
VI) Communication management:
1) General rules in communication of project:
- In Project, because of the small size of a task, when telling about the completion
of a task, the answer is just having completed (100%) or not completing (0%).
- When meeting ambiguity during requirement gathering, analysis, designing and
coding, must confirm it with PM, do not do the task with understaning when not be
sure because it can cause the wrong direction of entire project.
2) Detailed description of communication in project:
a) Communication between PM and Client:
Topic of communication
Making the deal and negotiation
Target of
communication
- Understand each
Tools and documents
of communication
- Documents: SOW
- If there is any problem in the
other's ideas and points
and contract made by
deal, PM or client will contact to
- Reaching the deal that
lawyers and experts.
each other to arrange a meeting
can satisfy both as soon
- Tool: Microsoft
to negotiation and understand the
as possible not to affect
Team app.
problems.
the process of project
Detailed actions
- If cannot meet directly because
of some issue, can apply online
meeting (Microsoft Team)
Ambiguity from members in project
- Figure out the
- Documets: lists of
- Questions will be sent by PM
ambiguity to meet the
ambiguous part and
to client by email.
requirement of client
questions from
-Make sure clients will answer in
member of project.
a time range, if out of this time
- Tool: Google Email, range, should contact with other
Microsoft Team.
ways like by phone.
- If the question is a lot and hard
to understand, a meeting should
be made.
download by :
