Graduation Project PROPOSAL DOCUMENT PRESCHOOL MANAGEMENT SYSTEM Mentor: MSc Huy Nguyen Dang Quang Project Team: Noodle Cup Team Members: Duong Nguyen Thi Thuy Tai Nguyen Van Thao Mai Thi Thu Hao Nguyen Chiem Proposal Version 1.2 | PMS PROJECT INFORMATION Project Acronym PMS Project Title Preschool Management System Start Date Feb 17, 2020 End Date Apr 22, 2020 Lead Institution
The Faculty of Information Technology, Duy Tan University Project Mentor MSc Huy Nguyen Dang Quang Project Manager MSc Huy Nguyen Dang Quang & Contact Details Email: huyndq@duytan.edu.vn Phone: 0935525354 Members
Duong Nguyen Thi nguyenthuyduong72018 0389121969 Thuy @gmail.com Tai Nguyen Van nguyenvantai22298@gm 0764466624 ail.com Hao Nguyen Chiem nguyenchiemhao2205@ 0365225603 gmail.com Thao Mai Thi Thu
maittthao1602@gmail.co 0343431856 m Page 2 of 21 Proposal Version 1.2 | PMS PROPOSAL DOCUMENT Document Title Proposal Document Reporting Feb 2020 Period Author(s) Duong Nguyen Thi Thuy KidsLand_Proposal_Version- Date Feb 17, 2020 Filename 1.2.docx Access Project and FIT program DOCUMENT HISTORY Version Person Date Description Duong Nguyen Thi Thuy Tai Nguyen Van 1.0 Feb 17, 2020 Draft Hao Nguyen Chiem Thao Mai Thi Thu Duong Nguyen Thi Thuy Update Master 1.1 Feb 17, 2020 Schedule and Tai Nguyen Van Architecture Diagram Update Architecture 1.2 Duong Nguyen Thi Thuy Feb 17, 2020 Diagram Page 3 of 21 Proposal Version 1.2 | PMS SIGNATURE MSc Huy Nguyen Dang Quang Date Mentor Duong Nguyen Thi Thuy Date Scrum Master Tai Nguyen Van Date Member Hao Nguyen Chiem Date Member Thao Mai Thi Thu Date Member Page 4 of 21 Proposal Version 1.2 | PMS Table of Contents I.
Introduction.................................................................................................................7
1. Purpose..................................................................................................................... 7
2. Scope........................................................................................................................ 7
3. References................................................................................................................ 8
II. Project Overview......................................................................................................... 9
1. Project Definition.....................................................................................................9
2. Business Needs........................................................................................................9
2.1. Business Problem.............................................................................................. 9
2.2. Business Needs................................................................................................10
III. Proposal Solution.....................................................................................................10
1. Project Goal........................................................................................................... 10
1.1. System Context................................................................................................11
1.2. Solution Description........................................................................................16
2. Technical Constraints.............................................................................................17
IV. Master Plan..............................................................................................................18
1. Master Schedule..................................................................................................... 18
2. Organization Management.....................................................................................19
2.1. Human Resource.............................................................................................19
2.2. Cost Estimation...............................................................................................20 Page 5 of 21 Proposal Version 1.2 | PMS Table
Table 1: References....................................................................................................... 8
Table 2: Master Schedule............................................................................................18
Table 3: Human Resource...........................................................................................19
Table 4: Detail Cost Estimation...................................................................................20 Figure
Figure 1: System Context Diagram.............................................................................11
Figure 2: Architecture Diagram Overview..................................................................14 Page 6 of 21 Proposal Version 1.2 | PMS I. Introduction 1. Purpose
The document provides an overview of the project includes the purpose and scope of project.
In addition, identifying business needs, problems or situation related to the
initialization and construction projects.
Provide solution for business needs and give the overview of system architecture.
Provide overview about resources, schedule, solution, and budget for the project. 2. Scope
This document provides an overview of project will be developed. It includes
overview of the product, overview of the process and overview of the project team.
This document provides a plan for each stage of software development process based
on Scrum process include start time, end time and number of working days. This is the
general plan and will be updated with detail of the software development process in the next document.
Proposal includes the introduction of solutions, determine the best way to develop
software that we make, the total estimated costs, payback period, break-even volume for the project. Page 7 of 21 Proposal Version 1.2 | PMS 3. References No. References Document Information Scrum
https://www.scrum.org/resources/what-is-scrum 1 Process https://stackoverflow.com/ https://www.codeproject.com/ https://aws.amazon.com/ https://dotnet.microsoft.com/ 2 Technical https://www.mongodb.com/ https://reactjs.org/ https://about.gitlab.com/ https://reactnative.dev/ https://shopeefood.vn/ 3 Information https:// baemin .vn/ http://quanlymamnon.edu.vn/ Page 8 of 21 Proposal Version 1.2 | PMS II. Project Overview 1. Project Definition
Building Mobile applications can perform child management functions at preschools.
This includes monitoring attendance and recognition child when entering the
classroom and notifying Parents what time the child is at school and notify the child's
activities to parents and parents. Parents update the child's situation for teachers
through the application. In addition, creating a contact book helps schools and parents
to keep an overall track on the learning situation of children. 2. Business Needs 2.1. Business Problem
Many schools, parents use for the purpose of monitoring children, but still not very
comfortable and know the activities that day of the child.
Today, it is quite common for buses to transport children from home to school, but no
one can guarantee that the school bus will take full advantage. The driver or teacher
may leave the child behind, resulting in many unfortunate events.
The methods of notifying children's learning, health and activities with parents are still manual.
The management of learning situations, tuition fees, activities is still manual and
backward, leading to difficulties in management and complexity if the school has
many students and many facilities. 2.2. Business Needs
Desiring to create a close relationship between the school and parents to monitor the
learning situation of children in the classroom, especially preschool.
Help the school to manage students and parents easily information, statistical reports quickly.
Quickly capture parental feedback and make timely adjustments (if needed).
Transparent information avoids misunderstandings between parents - teachers. Page 9 of 21 Proposal Version 1.2 | PMS
Ensuring accurate information about children, clearly identifying activities when
children are at school, saving time and increasing trust. III. Proposal Solution 1. Project Goal
Building a child management system in preschool, connecting and ensuring the
accuracy of interaction between parents and the school.
Users manipulate the system through mobile applications.
Automate the process of enrolling children in school with a face recognition system, improve accuracy and faster.
Connecting parents with the school, creating parent's satisfaction and trust with the school.
Easily manage facilities with aggregate reporting. Easily retrieve information anytime
the manager wants. Easily establish standards-based facilities that operate on the
system. Help the school manage and update teacher and student data easily. Page 10 of 21 Proposal Version 1.2 | PMS
1.1. Business Function Diagram Page 11 of 21 Proposal Version 1.2 | PMS
1.2. System Context Diagram Page 12 of 21 Proposal Version 1.2 | PMS
The "KidsLand" system with key features that meet business requirements includes For Students role include
Participating in attendance by standing in front of the camera for identification by the system. For Teachers role include
Attendance identifies children through the camera system.
Managing electronic contact book (adding information, updating, commenting,
assessing the learning situation of children in the contact book).
Managing children's activities (daily activities, comments, notifying parents of health situation). For Parents role include
Capture the information of children present in the classroom in time when
teachers make attendance of children through the camera system.
Feedback and exchange with teachers about learning and playing activities.
Registration of leave for children.
Subscribe to daily children's notifications. Following contacts book.
Managing young information (editing, updating child information). For Admin role include
Users management (create accounts, edit, delete users accounts).
Classes management (create class, edit, delete class).
Schedule Management (create class schedules, edit and delete class schedules). User authorization.
Managing the information of children and parents (add, update, edit, delete
information of children and parents). Page 13 of 21 Proposal Version 1.2 | PMS
Teacher management (add, delete, update teachers for each class).
Managing contact books (create, edit, delete, track contacts, inform children's health status).
Statistics (statistics on school days, day-off of children by week, month, health
statistics of children by month). Page 14 of 21 Proposal Version 1.2 | PMS
1.3. Architecture Overview Page 15 of 21 Proposal Version 1.2 | PMS :
Teachers use the app to take attendance. When the attendance of each child is
completed, at the same time on the parent application, you will immediately see
the information just confirmed by the notification. After the attendance has been
completed, the application will summarize the children who have been enrolled in
the list of the day, thereby knowing the number of school days and days off.
An application that teachers can use to monitor children in the class, update their
learning situation and activities in the contact book. See statistics of holidays,
school days of children, health status by week.
Parents use the app to view notifications about attendance for the day. Suggest a
day off for children, correct child information or notify the child's health status to
the teacher and see the child's contact book for the week on health status, the
number of school days, and days off, learning and activities.
Admin controls access to each object, manages accounts (Create accounts, edit,
delete accounts), manages classes (Create classes, edit, delete classes), manage
class schedules (Create a calendar, update, delete class schedule), manage teachers
(Add, update, delete teachers in each class), manage activities (Add, update),
create contact book, view information about children and parents, statistics of
holidays, school days of children, statistics of the health status of children in the week. Page 16 of 21 Proposal Version 1.2 | PMS
1.4. Solution Description
The centralized system solves two problems:
Manipulation of user data access.
Attendance function by face recognition.
Input: Information and data entered by the user.
Process: Application processing system to suit each different entry requirements.
Output: Returns the result of a user action taken.
The system uses AWS Rekognition service to develop face recognition attendance.
Rekognition helps users analyze images, integrate them into applications, helping
users easily find, identify and organize images.
Rekognition is based on proven Deep Learning technology, which is highly
accurate in the field of computer vision science.
Rekognition uses (Deep neural network models) to detect and label objects.
Training (Convolutional deep neural networks) require the cost of calculating and
requiring a high-speed hardware system. Therefore, using Rekognition saves
construction costs, training, maintaining and upgrading deep learning pipelines.
Rekognition is updated, upgraded, long-term supported by Amazon, stability in
image processing is maintained and quickly supported. Page 17 of 21 Proposal Version 1.2 | PMS 2. Technical Constraints
Tool develop: Visual Studio Code, VS Code, Postman, Chrome Develop Tool
Language: React JS, React Native, ASP.NET Core Database: MongoDB
Library: Amazon Web Service SDK, ASP.NET Core 3.1, MongoDB Driver, Json
web token, React Native Elements, React Native Base, Firebase Admin SDK ad Firebase Client SDK Manual test Resource: 04 people Budget: Limited
Time: The project must be completed within two-months frame
Environment: Windows, Android, Linux, Virtual Machine Page 18 of 21 Proposal Version 1.2 | PMS IV. Master Plan 1. Master Schedule No. Task name Duration Start Finish 1 Start Up Feb 03, 2020 Feb 18, 2020 1.1 Gathering Requirement 10 days Feb 03, 2020 Feb 14, 2020 1.2 Create Proposal Document 1 day Feb 17, 2020 Feb 17, 2020 1.3 Project Kick-off Meeting 3 days Feb 18, 2020 Feb 20, 2020 1.4 Make Project Plan Document 1 day Feb 21, 2020 Feb 21, 2020 2 Development Feb 24, 2020 Apr 22, 2020 2.1 Sprint 1 10 days Feb 24, 2020 Mar 06, 2020 2.2 Sprint 2 10 days Mar 09, 2020 Mar 20, 2020 2.3 Sprint 3 10 days Mar 23, 2020 Apr 04, 2020 2.4 Sprint 4 10 days Apr 06, 2020 Apr 17, 2020 3 Project’s Meeting 1 day Apr 20, 2020 Apr 20, 2020 4 Final Release 1 day Apr 22, 2020 Apr 22, 2020 Page 19 of 21 Proposal Version 1.2 | PMS 2. Organization Management 2.1. Human Resource TEAM INFORMATION Full Name Position Phone Email Huy Nguyen Dang 093552535 Mentor huyndq@duytan.edu.vn Quang 4 Duong Nguyen Thi Scrum 038912196 nguyenthuyduong72018@gmail.co Thuy Master 9 m Team 076446662 Tai Nguyen Van nguyenvantai22298@gmail.com member 4 Team 036522560 Hao Nguyen Chiem nguyenchiemhao2205@gmail.com member 3 Team 034343185 Thao Mai Thi Thu maittthao1602@gmail.com member 6 Page 20 of 21