HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 spirITus Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 271: Line 271:
 
| 4
 
| 4
 
| 21
 
| 21
| 21
+
| 20
| 100%
+
| 105%
 
| None. We are on schedule.
 
| None. We are on schedule.
 
|-
 
|-
Line 290: Line 290:
 
|-
 
|-
 
| 7
 
| 7
| 14
 
| 14
 
| 100%
 
| None. We are on schedule.
 
|-
 
| 8
 
 
| 14
 
| 14
 
| 14
 
| 14

Revision as of 14:07, 24 February 2015

WELCOME TO

Official spirITus Logo.png


Home

 

About Team spirITus

 

Project Overview

 

Project Management

 

Project Documentation

 
Slides and Links
  • View our midterm presentation slides here!
  • Visit our deployed application here!

Login Credentials

Teacher Account
Username:
Password:
Guardian Account
Username:
Password:
Student Account
Username:
Password:

Project Progress Summary

Project Highlights

Unexpected events that have occurred:

  • One member was removed from the team as she did not met the prerequisite for IS480
  • Jeanne Tan resigned from DAS
  • Some change of requirements after the handover
  • List of changes:
    • "Contact us" communication feature instead of real-time chat function
    • Addition of SMS notification as a good to have additional functionality
    • Calendar function on Desktop was reconsidered and implemented after Sponsor Test 2
    • Took the December term break to learn php and understand the laravel framework
  • Some problem faced:
    • Learning curve for email function for notification was higher than expected
    • Technical complexities during integration

Schedule Updates

Number of planned iterations: 13
Number of iteration completed: 8

  • Current iteration: 9

Number of iterations left: 5
Complete Testing: 4

  • Acceptance
  • UAT 1
  • Sponsor Test 1
  • UAT 2
  • Sponsor Test 2

Milestones left: 4

  • Midterm
  • Poster
  • Finals
  • Poster Day
Project Management

Functionality and Scope

Functionalities Progress in Task completion
Primary 100%
Secondary 90%
Tertiary 80%
Good-to-have 30%

Functionalities achieved

Iteration Module Functions / Comments Confidence
1 Admin and accounts UI UI using jQuery mobile. Coincides with IDP 1
2 Account Module Teacher account can View, create and search 1
Parent Account UI for reports, events and chats 1
3 Accounts Module Creation of profiles. Entity profiling 1
Classroom Module Teachers can mark attendance, guardians can view child;s attendance 1
Feedback Module 1 Teachers can mark attendance, guardians can view child;s attendance 1
4 Feedback Module 1 Guardians can view child's education progress 1
Communication Module 1 Teachers and parents are able to send message to each other 1
Search and Filter Module Teachers can search for student by name 1
5 Accounts Module 1 Admin account have CRUD access, able to reset password 1
Classroom Module Teachers, students and guardians can view lessons/ scheduled plans 1
Communication Module 2 Teachers can create announcements for class. Guardian can get notifications on child's progress 1
Rewards Module Teachers can award points to students ans student can view their awarded points 1
6 Desktop rollout Desktop UI and Accounts CRUD implementation 1
Rewards Module Gamification techniques and concepts changes to make it more engaging. 1
Feedback Module 1 Teachers can generate student profile, attendance statistics including assessments 1
7 Forum Module All users can post queries in forum 1
Feedback Module 2 Student can view their attendance statistics 1
Teachers' dashboard showing class activities and student reports(Desktop) 1
8 Feedback Module 2 Teachers can opt to send generated reports to email accounts 1

Functionalities To Be Achieved

Iteration Module Functions / Comments
9 UI Enhancement UI Enhancement for Mobile and Desktop site
10 Security Security features to prevent spam to email accounts


Project Schedule

Our team has made very minimal changes to schedule, most of the changes were implemented during the planned iterations. The most notable changes were the change in functionality requirement, the communication module. Our client conducted their own trials and wanted a 'contact us' form for parents to communicate with the teachers. They also told us to focus more on the mobile development in December 2014 as they wanted to use our application in January for trials.

Planned Schedule

IS480 Timeline(New).png

Dated: December 2014

Actual Schedule

IS480 Timeline caa 23022015.jpg

Dated: February 2015

Project Metrics

Schedule Metrics

SpirITus Schedule Metrics.jpg
Current Status: Good standing

Iteration Planned Days Actual Days Score Remarks / Actions Taken
1 35 35 100% None. We are on schedule
2 21 26 81% Reasons: Learning curve in learning new frameworks and integrating libraries result in slower than expected progress in development.

Extend iteration till the task is completed. Adjust the dates of the subsequent iteration to match the use of buffer days.

3 21 27 78% Reasons: All developers are still learning the new language and framework. Coupled with other academic commitments, the difficulty in developing back-end logic in 'attendance taking for student' in php resulted in the delay in task completion

Extend iteration till the task is completed. Adjust the dates of the subsequent iteration to match the use of buffer days.

4 21 20 105% None. We are on schedule.
5 14 15 93% Reasons: Zam left the group, reallocation of assigned work to other members.

Used one buffer day to complete planned functionality in iteration. No need for adjustment of scope.

6 14 16 88% Reasons: Jeanne left DAS, handover of management to Sree. There were also new suggestion of new functionality by the directors which led to some major change in the database structure.

Used two buffer days to complete planned functionality + new requirements in iteration. Extend iteration till the tasks are completed. Adjust the dates of the subsequent iteration to match the use of buffer days.

7 14 14 100% None. We are on schedule.


Bug Metrics

Bugsiteration.PNG Bugs metricsgraph.PNG

Iteration Low High Critical Total Score Actions Taken
1 0 0 0 0 No actions required.
2 1 0 0 1 Used debugging time to debug.
3 4 1 2 29 Used debugging time + one buffer day to debug.
4 1 3 1 26 Bugs were fixed during testing and debugging time. No buffer time required.
5 4 1 0 9 Bugs were fixed during testing and debugging time.
6 8 4 0 28 Used debugging time to debug. One outstanding UI bug to be fixed in later iteration due to low importance. Used one buffer day to debug.
7 4 1 1 19 Bugs were fixed during testing and debugging time.
8 5 4 0 25 Some UI bugs were found during Sponsor Test 2; used debugging time to debug.
9 1 1 1 16 Bugs were fixed during testing and debugging time.


Technical Complexity

S/N Technical Description Remarks
1 PDF Generation of reports Getting things displayed nicely in a single page in the pdf.Special symbols and font embedding issues. Transformation of database records data to the display format required.
2 Attendance taking Transformation of database records data to the display format required
3 Lesson Feedback and makeup There are many client changes as to how lesson feedback and make ups are to be recorded. Resulting in frequent database schema changes.
4 Laravel Framework This is the 1st time our team has used a web framework in application development. The learning curve is particularly steep as there are many components to learn and to pick up for development.


Risks

Risk Probability Impact Mitigation
Steep learning curve in exploring new frameworks and languages with 3rd party libraries, such as SMS integration and email notifications High High We will seek help from learning sessions and watching videos on the know-how to integrate it in our application. After much work about, we became more familiar with the use of such libraries and framework.
There were sudden change in requirement due to results analysis by client by their own trials, such as the communication method using the application High Medium We will seek advice from supervisor and inform her on the new changes. We proceed with the change if it does not delay the completion of the project.
Juggling other academic workload when the tasks in a particular workload is heavy. Medium Low We will seek advice from seniors and read up on best practices on how we can utilize the framework chosen to make coding less mundane. Working long hours into the night was prevalent as we try not to exceed the planned iteration days.



Quality of Product

Intermediate Deliverables

Stage Specification Relevant Links
Project Management Meeting Minutes Meeting Minutes
Schedule and Bug Metrics Metrics
Project Scope Scope / Functionalities
Analysis Architecture Diagrams Architecture Diagrams
ER Diagram ER Diagram
Use Case Use Case Diagram
Design Prototypes Prototypes
Testing User Acceptance Test & Sponsor Test Results Test Results


Reflection

Team Reflection

After spending so much time together coding, working and debugging, we have learnt a lot about each other's strengths and weaknesses, and how we use that knowledge to support each other. For example, ...