Software project management project beautyspa store management application

Introduction Project name: Beauty&Spa Store Management Application Client: A Beauty&Spa store B.. Project Management 3 days 01/09/2021 03/09/2021 Requirement gathering 6 days 06/09/20

Software project management

Project: Beauty&Spa Store Management Application

Class: E18CN02 Group 6

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

I) Member’s distribution:

1 Đỗ Xuân Hi u ế SOW and project charter document

Configuration management document

Scheduling

Human resource management documet Quality management document Power point creating

Risk management document Communication management document Presenting

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- -use and to 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

Client: A Beauty&Spa store

User: Employees of the store

Business adviser: Store owner

It helps the manager to manage all information of bills, customer, employee, service and control product in warehouse

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

▪ View detail revenue of each service

• Statistic by imported products

Project Management 3 days 01/09/2021 03/09/2021

Requirement gathering 6 days 06/09/2021 13/09/2021

- 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

Project Manager Project Sponsor Client

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)

8

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.5 Package diagram (3 days)

3.2.6 Deployment diagram (3 days)

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)

10 IV) Scheduling:

V) Risk management:

1) List of risk with general information:

WBS

1

Software cannot be installed suitable ly with client's side Project Sponsor 6.1

Set up environment for

13 Argument between members which cannot be solve in short time Team Manager 3.0 Design and analysis B

15

18

implementation, Design and

24

Product is leaked and sold illegally

Team Manager/

26 Document and product are not synchronized Project Sponsor 6.1 Record user instructions S

28 Fire accident causing destruction of all computers storing project PM 4.0 implementation W/B

2) Risk analysis:

1 Software cannot be installed suitable ly

16

13 Argument between members which

21 A change in requirement causes the huge

17

23 Customer tends to refuse approving the

product of project

25 Some application is accused of not having

26 Document and product are not

28 Fire accident causing destruction of all

3) Risk Mitigation:

1 Software cannot be installed suitable ly

with client's side

Developer Team Planned

18

2 Scope is required to be wider at the end Contain

- Discuss with team about this

- Assess the difficulty of this request for the bargain with client

- Meet client to bargain, give our offer, the increasing in payment or what we can do for their request

3 System does not perform like client think Contain

- Ask client what they does not satisfy

- Assess the problem with team

- 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,…)

- 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

5 Client wants the price to be lower Contain

- Use the contract to bargain with client

- If the price is reasonable, we can agree with some 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

- Have a meet with team to gain new knowledge about tools and solution can solve the problem

PM and Team

19

- 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

7 Customer lacks of resources Establish

Developer Team Planned

- -schedule re

- Assess whether some work can be reduced

- If updating consumes too much time, we need to inform to client about the increasing of time

9 Added time to train employee Ignore/Accept

- Have a meet with team to figure out the way to recover the data as soon as possible

- Re-schedule

- we need to inform to client about the increasing of time if lots of time can be consumed

10 Losing information while updating Ignore/Accept

- Have a meet with team to figure out the way to recover the data as soon as possible

- Re-schedule

20

- we need to inform to client about the increasing of time if lots of time can be consumed

11 Requirement grows uncontrollablely Contain

- have a meet with the team to know how difficult the requests are

- If the request is simple, deal with it

- If the request is complicated, we have to deal with client to remove it or increase the cost and time for it

Project Sponsor

12 Problem cannot be solved Ignore/Accept

- if a team cannot silve, we will have to ask any help from other source to solve the proble as much as possible

- Bargain with client can be neccessay if cost is increased to solve the problem

- 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

PM and Team

13 Argument between members which

cannot be solve in short time Contain

- Have a meeting among team members to assess the problem

- Every member will give their opinion about the 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

Team Manager Planned

21

14 Deliverables are not completed in time Contain

- Have a meet with team to figure out the way to recover the data as soon as possible

- Re-schedule

- we need to inform to client about the increasing of time if lots of time can be consumed

15 System develops in wrong direction Avoid

- Focusing on testing and supervising in the work of analysis and design to not let it out of scope

- Have some periodic meeting to analyze the work of 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 transfer the work to the substitution as soon as posible

- Reschedule to make sure the work transfering does not affect too much the deadline

Team Manager Planned

18 Too much useless time during project Contain

- Watch schedule to know which work can be taken

22

- Have a meet with team to collect and understand the ambiguty

- Conatct with client to figure these out to inform the team later

20 Requirement cannot be understood Contain

- Have a meet with team to collect and understand the ambiguty

- Conatct with client to figure these out to inform the team later

21

A change in requirement causes the huge

- Assess the problem

- 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

- Assess the delay and bargain with client to increase the time for project if necessary

23

Customer tends to refuse approving the

- Focus on contract when project is created

- Try to consider some rules and constraints to avoid this proble

Project Sponsor

25 Some application is accused of not

- When use an availabe application from another source, must consider the copyright Project Sponsor Planned

23

- Always assess the tools and applications' copyright when the team member gives any tools and apps to apply to the project

26 Document and product are not

- have a review after a document is completed

- Perform the system following the documet to make sure the document is right before deliver to client

Team Manager Planned

27 Too many errors in system Establish

contingency

- Separate program to many parts to supervise easily to test and find errors easier or create a system of errors

to compare and find easier

- Build some standard and structure of coding and documents to avoid errors and be easy to transfer and follow the work

Team Manager Planned

28 Fire accident causing destruction of all

computers storing project

Establish contingency

- Always prepare another server or side to restore

- update the back-up after each milestone

- Depend on the importance of the project, high security need to be considered

Developer Team Planned

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 Target of

communication

Tools and documents

of communication Detailed actions

Making the deal and negotiation

- Understand each other's ideas and points

- Reaching the deal that can satisfy both as soon

as possible not to affect the process of project

- Documents: SOW and contract made by lawyers and experts

- Tool: Microsoft Team app

- If there is any problem in the deal, PM or client will contact to each other to arrange a meeting

to negotiation and understand the problems

- If cannot meet directly because

of some issue, can apply online meeting (Microsoft Team)

Ambiguity from members in project

- Figure out the ambiguity to meet the requirement of client

- Documets: lists of ambiguous part and questions from member of project

- Tool: Google Email, Microsoft Team

- Questions will be sent by PM

to client by email

-Make sure clients will answer in

a time range, if out of this time range, should contact with other ways like by phone

- If the question is a lot and hard

to understand, a meeting should

be made

Reviewing product

- Give client clear view about the completion of the deliverables and product

- Getting the comment

of client about the satisfaction and disatisfaction of client

- Documents: the report after each phase (Analysis, Designing, Coding)

- Tool: Google Email, Microsoft Team

- In a review after each phase,

PM will give client a report of the phase and explain for client Then, client will review to give the comment about what is good and what need to be changed

- The communication will be made by email if there are just a few of problems but if there are too many issues, the meeting should be made offline or online

b) Communication between PM and teams in project:

Topic of communication Target of communication

Tools and documents of communication

Detailed actions

Ambiguity in work, A requirement

that cannot be dealed

- PM understands the ambiguity and problems

of other members

- Tool: email, github, Microsoft Team

- A file will be created with github to share the questions about ambiguity and problems

- PM will read questions and make sure understand them If not, PM will contact to members

by email or discuss these in a meeting

- PM should have a small meeting occasionally to make sure ambiguity not be missed

26

c) Communication among teams:

Topic of communication Target of communication

Tools and documents of communication

Detailed actions

Transfering the work

- the work from the front phase can be understood

by the team which work

in the behind phase

- Document: the report from the front phase

- Tool: Email, Microsoft Team

- A report of the front phase will

be given to the team enrolling in the process of the project

- If there is any confusion in the report, the teams will contact with each other through mail or create a meeting to deal with it

Fixing faults during testing

- the development team can fix the faults given from testers in the right way

- Tool: github, email, Microsoft team

- A file will be created with github to share the faults and problems

- developers will read problems and make sure understand and be able to fix them If not, developers will contact to testers

by email or discuss these in a meeting