Difference between revisions of "SMT483G1: Anly.io Project Management"
Jump to navigation
Jump to search
Stsze.2017 (talk | contribs) (Created page with "===Project Plan=== {| class="wikitable" |- ! End of Week !! Milestone !! Features !! |- | 1 || Discuss Specifications and Logistics with Sponsor<br>Show UI/UX Mockup to Spo...") |
Stsze.2017 (talk | contribs) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ===Project Plan | + | <!--HEADER--> |
| + | |||
| + | <!--/HEADER--> | ||
| + | |||
| + | <!--MENU--> | ||
| + | <!--rax--> | ||
| + | {|style="background-color:#AC3E3B ; color:#FFFFFF; padding: 5 0 5 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0"| | ||
| + | | style="padding-top:2em; font-size:100%; background-color:#b19cd9 ; text-align:center; color:#FF9633 " width="10%" | | ||
| + | [[SMT483G1: Anly.io |<font color="#FFFFFF" size=2.5 family ="Roboto"><b>HOME<b></font>]] | ||
| + | |||
| + | |||
| + | | style="padding:0.1em; font-size:100%; background-color:#b19cd9 ; text-align:center; color:#000000" width="10%" | | ||
| + | [[SMT483G1: Anly.io Project Overview |<font color="#FFFFFF" size=2.5 family ="Roboto"><b>PROJECT OVERVIEW</b></font>]] | ||
| + | |||
| + | | style="padding:0.1em; font-size:100%; background-color:#6a0dad ; text-align:center; color:#000000" width="10%" | | ||
| + | [[SMT483G1: Anly.io Project Management|<font color="#FFFFFF" size=2.5 family ="Roboto"><b>PROJECT MANAGEMENT</b></font>]] | ||
| + | |||
| + | | style="padding:0.1em; font-size:100%; background-color:#b19cd9 ; text-align:center; color:#000000" width="10%" | | ||
| + | [[SMT483G1: Anly.io Documentation |<font color="#FFFFFF" size=2.5 family="Roboto"><b>DOCUMENTATION</b></font>]] | ||
| + | |} | ||
| + | <!--/MENU--> | ||
| + | |||
| + | |||
| + | ==Project Plan== | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
| − | ! End of Week !! Milestone !! Features !! | + | ! End of Week !! Milestone !! Features !! Progress |
|- | |- | ||
| − | | 1 || Discuss Specifications and Logistics with Sponsor<br>Show UI/UX Mockup to Sponsor (7 Jan)<br>Design UI/UX || Main Page || | + | | 1 || Discuss Specifications and Logistics with Sponsor<br>Show UI/UX Mockup to Sponsor (7 Jan)<br>Design UI/UX || Main Page || Done |
|- | |- | ||
| − | | 2 || Develop Front-end<br>Develop Back-end || Game || | + | | 2 || Develop Front-end<br>Develop Back-end || Game || Game is delayed |
|- | |- | ||
| − | | 3 || Develop Back-end || Login and administration || | + | | 3 || Develop Back-end || Login and administration || Login and administration done <br> Shifted from Azure to AWS |
|- | |- | ||
| − | | 4 || Showcase a Minimum Viable Product to Sponsor (31 Jan) || || | + | | 4 || Showcase a Minimum Viable Product to Sponsor (31 Jan) || || Sponsor changed to Victoria School <br> Meeting on 4/2 |
|- | |- | ||
| − | | 5 || User Acceptance Test (1st round) (3-9 Feb) || || | + | | 5 || User Acceptance Test (1st round) (3-9 Feb) || || Shifted to Week 10 (10 Mar) |
|- | |- | ||
| − | | 6 || Refine usability || Complete | + | | 6 || Refine usability || Complete “Quests” <br> Develop Buffer Feature || Done |
|- | |- | ||
| − | | 7 || Mid-term Presentation and Report || || | + | | 7 || Mid-term Presentation and Report || || Done |
|- | |- | ||
| − | | 8 || User Acceptance Test (2nd round) (24-29 Feb) || || | + | | 8 || User Acceptance Test (2nd round) (24-29 Feb) || || Shifted to Week 13 |
|- | |- | ||
| − | | 9 || Refine usability || || | + | | 9 || Refine usability <br> Updated: Refine game UI, develop leaderboard frontend || || In progress |
|- | |- | ||
| − | | 10 || Deploy to Cloud <br> Go Live || || | + | | 10 || Deploy to Cloud <br> Go Live <br> Updated: UAT 1 at VS <br> UAT 2 at RVHS || || Done |
|- | |- | ||
| − | | 11 || User Acceptance Test (3rd round) (16-22 Mar) || || | + | | 11 || User Acceptance Test (3rd round) (16-22 Mar) <br> Updated: Analytics Dashboard UI || || Shifted to Week 13 |
|- | |- | ||
| − | | 12 || Refine Usability <br> CI/CD <br> Prepare Demo and Presentation || || | + | | 12 || Refine Usability <br> CI/CD <br> Prepare Demo and Presentation <br> Updated: Analytics Dashboard Backend and Frontend || || |
|- | |- | ||
| − | | 13 || Develop Business Model and Go-to Market Strategy <br> CI/CD <br> Prepare Report || || | + | | 13 || Develop Business Model and Go-to Market Strategy <br> CI/CD <br> Prepare Report <br> Updated: UAT 3 at VS (cancelled) || || |
|- | |- | ||
| − | | 14 || Final Presentation || || | + | | 14 || Meeting with teachers to demo teaching dashboard <br> Final Presentation || || |
|- | |- | ||
| 15 || Report Submission || || | | 15 || Report Submission || || | ||
|} | |} | ||
| − | === | + | ==Risks and Assumptions== |
| + | ===Assumptions=== | ||
| + | 1. Teachers are willing to try teaching using games<br> | ||
| + | 2. A cloud-based system by subscription is suitable for MOE's requirements in terms of security and | ||
| + | cost-effectiveness<br> | ||
| + | 3. A single platform is able to meet the learning needs of both IP, express and normal stream students<br> | ||
| + | ===Risks=== | ||
| + | 1. Schedule backlog due to fundamental changes required after user testing<br> | ||
| + | Mitigation: plan schedule with buffer to cater for overrun<br> | ||
| + | 2. Data privacy risk from collecting student and staff details<br> | ||
| + | Mitigation: encrypt student details and other important information when storing them on cloud platform<br> | ||
| + | 3. Insufficient product validation for commercialisation<br> | ||
| + | Mitigation: conduct user acceptance tests on a variety of schools with mix of IP, express and normal stream<br> | ||
| + | students to ensure good product fit<br> | ||
| + | |||
| + | ==Resources== | ||
| + | ===Technology=== | ||
| + | a. Stack (Alpha Build)<br> | ||
| + | i. Front-end: Angular 8 Framework<br> | ||
| + | ii. Back-end: Flask Framework (Monolith for now)<br> | ||
| + | iii. DB: PostgreSQL RDB<br> | ||
| + | iv. Authentication: Basic Access Authentication + JWT + LocalStorage<br> | ||
| + | b. Unit Testing: unittest (If time permits)<br> | ||
| + | c. Project Management and System Architecture<br> | ||
| + | i. Source Code Management: Gitlab<br> | ||
| + | ii. Containerization: Docker<br> | ||
| + | iii. CI/CD: Gitlab<br> | ||
| + | iv. Hosting: AWS EB/EC2<br> | ||
| + | |||
| + | ===Self-study For Software Engineering=== | ||
| + | a. System Architectural Development and Design<br> | ||
| + | b. Angular 8<br> | ||
| + | c. Flask (incl. Unit Tests)<br> | ||
| + | |||
| + | ===Financial Costs=== | ||
| + | a. Hosting with AWS<br> | ||
| + | b. Trip money to and from the schools<br> | ||
| + | |||
| + | ===Temporal Costs=== | ||
| + | a. Testing with students<br> | ||
| + | b. Meeting client<br> | ||
| + | c. Meeting supervisor<br> | ||
| + | |||
| + | ===Manpower Costs=== | ||
| + | a. Developers (us)<br> | ||
| + | b. Testers (students)<br> | ||
Latest revision as of 18:54, 27 March 2020
|
|
Contents
Project Plan
| End of Week | Milestone | Features | Progress |
|---|---|---|---|
| 1 | Discuss Specifications and Logistics with Sponsor Show UI/UX Mockup to Sponsor (7 Jan) Design UI/UX |
Main Page | Done |
| 2 | Develop Front-end Develop Back-end |
Game | Game is delayed |
| 3 | Develop Back-end | Login and administration | Login and administration done Shifted from Azure to AWS |
| 4 | Showcase a Minimum Viable Product to Sponsor (31 Jan) | Sponsor changed to Victoria School Meeting on 4/2 | |
| 5 | User Acceptance Test (1st round) (3-9 Feb) | Shifted to Week 10 (10 Mar) | |
| 6 | Refine usability | Complete “Quests” Develop Buffer Feature |
Done |
| 7 | Mid-term Presentation and Report | Done | |
| 8 | User Acceptance Test (2nd round) (24-29 Feb) | Shifted to Week 13 | |
| 9 | Refine usability Updated: Refine game UI, develop leaderboard frontend |
In progress | |
| 10 | Deploy to Cloud Go Live Updated: UAT 1 at VS UAT 2 at RVHS |
Done | |
| 11 | User Acceptance Test (3rd round) (16-22 Mar) Updated: Analytics Dashboard UI |
Shifted to Week 13 | |
| 12 | Refine Usability CI/CD Prepare Demo and Presentation Updated: Analytics Dashboard Backend and Frontend |
||
| 13 | Develop Business Model and Go-to Market Strategy CI/CD Prepare Report Updated: UAT 3 at VS (cancelled) |
||
| 14 | Meeting with teachers to demo teaching dashboard Final Presentation |
||
| 15 | Report Submission |
Risks and Assumptions
Assumptions
1. Teachers are willing to try teaching using games
2. A cloud-based system by subscription is suitable for MOE's requirements in terms of security and
cost-effectiveness
3. A single platform is able to meet the learning needs of both IP, express and normal stream students
Risks
1. Schedule backlog due to fundamental changes required after user testing
Mitigation: plan schedule with buffer to cater for overrun
2. Data privacy risk from collecting student and staff details
Mitigation: encrypt student details and other important information when storing them on cloud platform
3. Insufficient product validation for commercialisation
Mitigation: conduct user acceptance tests on a variety of schools with mix of IP, express and normal stream
students to ensure good product fit
Resources
Technology
a. Stack (Alpha Build)
i. Front-end: Angular 8 Framework
ii. Back-end: Flask Framework (Monolith for now)
iii. DB: PostgreSQL RDB
iv. Authentication: Basic Access Authentication + JWT + LocalStorage
b. Unit Testing: unittest (If time permits)
c. Project Management and System Architecture
i. Source Code Management: Gitlab
ii. Containerization: Docker
iii. CI/CD: Gitlab
iv. Hosting: AWS EB/EC2
Self-study For Software Engineering
a. System Architectural Development and Design
b. Angular 8
c. Flask (incl. Unit Tests)
Financial Costs
a. Hosting with AWS
b. Trip money to and from the schools
Temporal Costs
a. Testing with students
b. Meeting client
c. Meeting supervisor
Manpower Costs
a. Developers (us)
b. Testers (students)
