Câu 1: Project Description
- Project title : Preschool Education Management System (PEMS)
- Project Purpose/ Objectives:
The purpose PEMS is support efficient management and monitoring of educational
activities in preschool. key object include:
+ Enable administration to manage classes, teacher, schedules teaching
material and staff information.
+ Supporting teacher in organizing class activites, attendance student in
class, manage curriculum in class, feedback student for parent.
+ Allowing parents to register their children, receive daily report,
timetable lesson, and view feedback child.
+ Generating reports related to student progress, attendane, health status
- Customer/ sponsor:
The primary customer and sponsor of this project include preschools, kindergartens,
and early childhood education centers seeking digital transformation in educational
management.
Project Milestones: Waterfall model
Requirement Gathering and Analysis (Week 1-2)
System Design( Week 3-4)
Development and Unit Testing (Week 5-10)
System Testing, Integration Testing and User Acceptance Testing(Week 11-12)
Deployment(Week 13-16)
- Success Criteria:
+ System Development:
The system must be successfully deployed on AWS Cloud by the end of the week 16,
achieving an uptime of at least 99% during the first month after go-live
+ Feature Completion:
100 % of Functional Requiremnet listed in the Functional Requirement Document
(FRD), must be implemented and completed in Week 12
+ System Performance:
The average page response time must be under 2 seconds during load testing with at
least 100 concurrent users by the end of week 12
+ Product quality:
At least 95% of all test cases must pass during System testing (Week 11)
There must be zero bug important type 1 and no more than three bug important type 2
before deployment phase
+ Training and User manual:
Conduct a minium of 2 training sessions for teachers and administration between
week 13 - 14
+ User Satisfaction:
Achive at least 85% user satisfaction (teachers and adminstators) in a survey
conducted one month after system launch
+ Budget and Timeline Completed:
Complete the project within the approved budget of 10,000 USD and no later on week
after the scheduled week 16 project completion date
Orther Project Constraints:
Cost: The project budget is 10,000 USD
Resources: The project team includes 3 developers, 1 tester, 2 designers, 2
business analyst. and a project manager working collaboratively to meet deadlines
Technology Stack:
Backend: Express JS
FrontEnd: React JS
Deployment Environment: AWS Cloud
Câu 2: Organization Type
- For the PEMS project, it is very important that teamworks closely together and
finishes the work on time. Because the project time is short (only 4 months), we
need a way to organize the team that helps everyone focus only on the project
- A projectized organization structure is the best choice for this project. In this
structure, all team members will work only for project. They will not have other
jobs, so they can focus 100% on the project tasks
- Reasons for choosing a projectized organization:
+ Full focus on the project :
Team members only work for this project. They do not work for other departments.
This helps them finish their work faster and better.
+ Fast and clear communication:
Because everyone belongs to the same project team, it is easier to talk, share
ideas, and solve problems quickly
+ Quick response to change:
If something changes during the project, the team can react fast without waiting
for approval from departments
+ Clear Roles and Responsibility:
Everyone knows exactly what they have to do. This make the team work effectively
and avoids confusion
Using a projectized organization structure will help the team complete the
Preschool Education Management System on time, with good quality, and meet all the
goals of the project.
Câu 3: Management Risk
1. Delay in Requirement Gathering
+ Describe Risk: BA cannot complete requirement collection on time
+ Impact: high
+ Probability: Medium
+ Mitigation plan: Schedile early meetings and regular follow-ups with stakeholders
+ Contingency Plan: Prioritize core requirement first, defer minor features if
needed
2. Lack of User Training
+ Describe Risk: Users (admin, teacher) find the system hard to use.
+ Impact: Medium
+ Probability: Medium
+ Mitigation plan: Prepare user guides, conduct simple training sessions before go-
live.
+ Contingency Plan: Provide hotline or support team for quick help after
deployment.
3. Technology Obsolescence
+ Describe Risk: NodeJS version in React and Express become outdated during project
development
+ Impact: Low
+ Probability: Medium
+ Mitigation plan: Use Long Term Support (LTS) version of frameworks.
+ Contingency Plan: Plan upgrade for next release if needed.
