UNIVERSITY OF INFORMATION TECHNOLOGY

FACULTY OF SOFTWARE ENGINEERING

----- -----

Project name: Clothing Shop Website.

Major: Software Engineering.

Course: Microsoft .NET.

Instructor: Nguyen Thi Thanh Truc.

Group member: Nguyen Quang Truong – 20522089.

Nguyen Nhat Truong – 20522086.

TP.HCM, tháng 06 năm 2023

Table of Contents
I. Record of Changes................................................................................................................................3
II. Project Management Plan....................................................................................................................4
1. Overview..........................................................................................................................................4
1.1 Scope & Estimation....................................................................................................................4
1.2 Project Objectives......................................................................................................................4
1.3 Project Risks...............................................................................................................................4
2. Management Approach....................................................................................................................5
2.1 Project Process...........................................................................................................................5
2.2 Quality Management..................................................................................................................5
2.3 Training Plan..............................................................................................................................5
3. Project Deliverables.........................................................................................................................5
4. Responsibility Assignments.............................................................................................................5
5. Project Communications..................................................................................................................6
6. Configuration Management..............................................................................................................6
6.1 Document Management.............................................................................................................6
6.2 Source Code Management.........................................................................................................6
6.3 Tools & Infrastructures..............................................................................................................6
I. Record of Changes
Date A* In charge Change Description
M, D

*A - Added M - Modified D - Deleted

II. Project Management Plan
1. Overview
1.1 Scope & Estimation

Est. Effort
Complexit
# WBS Item (man-
y
days)
1 Login 81

1.1 Login and remember account Medium 5

1.2 Log out Medium 5

2 Product Interaction

2.1 Add product Medium 7

2.2 Update Product High 12
2.2 Delete Product Medium 7
2.3 Detail Product Medium 7
3 Order Medium 9
3.1 Confirm order Medium 8
3.2 Payment High 14
4 User
4.1 User information Medium 7
Total Estimated Effort (man-days) 81
1.2 Project Objectives

Test No. of % of
# Testing Stage Notes
Coverage Defects Defect
1 Reviewing N/A 2 10% Code review completed, addressed 2 defects.

2 Unit Test 85% 3 5% Achieved high coverage, 3 minor defects found.

3 Integration Test 75% 5 8% Identified and resolved 5 integration issues.

4 System Test 90% 2 3% Comprehensive system testing; minimal defects.

5 Acceptance Test 95% 1 1% Nearly full coverage; addressed 1 minor issue.

1.3 Project Risks

 Possibilit
# Risk Description Impact Response Plans
y
Third-Party API
1 High Medium Regular communication, backup plans.
Integration Delay
Insufficient User
2 Acceptance Medium Low Allocate ample UAT time, involve stakeholders.
Testing (UAT)
Security
3 High Medium Regular security audits, encryption.
Vulnerabilities
Changes in E-
4 commerce Medium Low Stay informed, maintain flexibility.
Regulations
Server Downtime
5 or Performance High Medium Load testing, scalable infrastructure.
Issues

2. Management Approach
Managing and implementing a project requires a systematic and well-organized
approach. Here's a general outline of the approach you might take:
Define Objectives:

 Clearly state project goals aligned with organizational strategy.

Create Plan:

 Develop a concise project plan with tasks, timelines, and resources.

Build Team:

 Assemble skilled team with defined roles and responsibilities.

Communicate:

 Establish a strong communication plan to engage stakeholders.

Manage Risks:

 Identify and mitigate risks, with contingency plans in place.

Budget and Allocate Resources:

 Develop a budget, allocate resources efficiently.

Execute:

 Implement the plan, monitor progress, and ensure quality.

Quality Assurance:

 Conduct regular reviews and testing for quality assurance.

Change Management:
  Handle changes with a structured change management process.

Monitor and Report:

 Track project status, report regularly to stakeholders.

Closure and Evaluation:

 Complete deliverables, conduct project evaluation.

Documentation:

 Maintain thorough project documentation.

Continuous Improvement:

 Gather feedback, implement lessons learned for improvement.

2.1 Project Process

2.2 Quality Management
To enhance project quality and achieve quality objectives, an effective quality management
approach is crucial. Here's a concise approach integrating defect prevention, reviewing, and
testing phases:

1. Defect Prevention:
 Proactive Planning: Identify potential issues in requirements and design.
 Training: Equip the team with necessary skills to prevent common pitfalls.
 Continuous Improvement: Implement feedback loops for ongoing process
enhancement.
2. Reviewing:
 Code Reviews: Conduct regular code reviews to catch issues early.
 Design Reviews: Evaluate system design to ensure alignment with
requirements.
 Requirements Reviews: Verify that requirements are clear, complete, and
testable.
3. Unit Testing:
 Comprehensive Testing: Develop and execute thorough unit tests for each
module.
 Automation: Automate unit tests to ensure repeatability and efficiency.
 Code Coverage: Strive for high code coverage to identify untested areas.
4. Integration Testing:
 Data Integrity: Verify data consistency and integrity between integrated
components.
 Interface Testing: Ensure seamless communication and data exchange.
 Scenario Testing: Test various scenarios to validate integrated functionalities.
5. System Testing:
 End-to-End Testing: Verify system functionality in a real-world
environment.
 Performance Testing: Assess system responsiveness, scalability, and
stability.
 Security Testing: Identify and address potential vulnerabilities and risks.
6. Continuous Monitoring and Feedback:
  Monitoring Tools: Implement tools for real-time monitoring.
 User Feedback: Gather feedback from end-users to identify improvements.
 Root Cause Analysis: Conduct thorough analyses of defects for continuous
learning.

By integrating these quality approaches, you establish a comprehensive framework for defect
prevention, thorough reviewing, and effective testing throughout the project lifecycle. This
approach enhances the likelihood of meeting and exceeding project quality objectives.

2.3 Training Plan

When, Waiver
Training Area Participants
Duration Criteria
Java Spring Boot Mandatory
Git, Github Mandatory

3. Project Deliverables
# Deliverable Due Date Notes

1 … dd/MM/yyyy …

4. Responsibility Assignments
D~Do; R~Review; S~Support; I~Informed; <blank>- Omitted Quang Truong
NhatTruong

Responsibility

Project Planning & Tracking D R

Prepare Project Introduction Document S D
Prepare SRS Document (Overview Part)
Prepare SRS Document (User Requirements)
Prepare Project Management Plan D R
Prepare Project Final Report S D
Prepare Project Weekly Report D R
Prepare Unit Test Report S D
Prepare Test Report S D

5. Project Communications
Communication Item Who/ Purpose When, Type, Tool,
 Target Frequency Method(s)

6. Configuration Management
6.1 Document Management
To manage project documents and versions effectively:

1. Centralized Repository:
 Establish a centralized document repository for easy access.
2. Version Control:
 Implement version control to track changes and ensure document
integrity.
3. Naming Conventions:
 Enforce clear naming conventions for easy identification of documents.
4. Document Ownership:
 Assign ownership to individuals for each document to ensure
accountability.
5. Access Controls:
 Set access controls to restrict document modification rights based on
roles.
6. Change Requests:
 Require change requests for document modifications, ensuring proper
approvals.
7. Regular Audits:
 Conduct regular audits to verify document accuracy and relevance.
8. Communication:
 Communicate changes promptly to relevant stakeholders.
9. Backup Procedures:
 Implement regular backup procedures to safeguard against data loss.
10. Training:
 Provide training on document management processes to the project
team.

6.2 Source Code Management

To manage project source codes and their changes/versions:

1. Version Control System (VCS):

 Implement a robust version control system (e.g., Git) for tracking
changes and maintaining code history.
2. Branching Strategy:
  Define a clear branching strategy to manage parallel development
efforts and feature releases.
3. Code Reviews:
 Enforce regular code reviews to ensure quality, adherence to coding
standards, and knowledge sharing.
4. Automated Builds:
 Set up automated build processes to catch integration issues early in
the development lifecycle.
5. Continuous Integration (CI):
 Implement CI practices to automatically test and integrate code
changes into the main repository.
6. Deployment Automation:
 Automate deployment processes to ensure consistency and reliability in
releasing new versions.
7. Tagging Releases:
 Use tagging to mark specific releases, making it easy to reference and
roll back to specific versions.
8. Documentation:
 Maintain clear documentation for coding standards, versioning
practices, and development workflows.
9. Access Controls:
 Define access controls to restrict code modifications based on roles and
responsibilities.
10. Communication Channels:
 Establish effective communication channels to notify team members of
code changes and updates promptly.

6.3 Tools & Infrastructures

Category Tools / Infrastructure
Technology HTML, CSS (FrontEnd), C#; NET (BackEnd)
Database MySQL
IDEs/Editors Visual Studio Code
Diagramming StarUML, DrawIO
Documentation Ms Office, Google Docs/Sheets/Slides
Version Control Github (Source Codes), Google Drive (Documents)
Project management GitLab (Tasks, Defects)