https://wiki.smu.edu.sg/is480/api.php?action=feedcontributions&user=Choryi.poon.2012&feedformat=atomIS480 - User contributions [en-gb]2024-03-29T06:45:00ZUser contributionsMediaWiki 1.33.1https://wiki.smu.edu.sg/is480/index.php?title=File:Final(v1).pdf&diff=256209File:Final(v1).pdf2016-04-20T23:50:58Z<p>Choryi.poon.2012: Choryi.poon.2012 uploaded a new version of &quot;File:Final(v1).pdf&quot;</p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=256163IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-20T14:23:57Z<p>Choryi.poon.2012: /* Deployed Website Link */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[https://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br><br />
[[Image:Tech complex1.png|600px|center]]<br><br />
[[Image:Gem ruby finals.jpg|200px|center]]<br><br />
[[Image:Gem ruby finals2.jpg|600px|center]]<br><br />
<br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=256162IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-20T14:23:40Z<p>Choryi.poon.2012: /* Final Slides */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Final(v1).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br><br />
[[Image:Tech complex1.png|600px|center]]<br><br />
[[Image:Gem ruby finals.jpg|200px|center]]<br><br />
[[Image:Gem ruby finals2.jpg|600px|center]]<br><br />
<br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Final(v1).pdf&diff=256161File:Final(v1).pdf2016-04-20T14:23:24Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=256064IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-19T07:54:33Z<p>Choryi.poon.2012: /* Technical Complexity */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br><br />
[[Image:Tech complex1.png|600px|center]]<br><br />
[[Image:Gem ruby finals.jpg|200px|center]]<br><br />
[[Image:Gem ruby finals2.jpg|600px|center]]<br><br />
<br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255434IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T11:46:27Z<p>Choryi.poon.2012: /* Technical Complexity 1: Assigning Code Usage */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
[[Image:Tech complex1.png|600px|left]]<br />
<br/><br />
[[Image:Gem ruby finals.jpg|200px|left]]<br />
<br/><br />
[[Image:Gem ruby finals2.jpg|600px|left]]<br />
<br/><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255426IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T11:36:28Z<p>Choryi.poon.2012: /* Technical Complexity 2: Generating PDF & Charts in PDF */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br /><br />
<br />
[[Image:Tech complex1.png|600px]]<br /><br />
[[Image:Gem ruby finals.jpg|200px]]<br /><br />
[[Image:Gem ruby finals2.jpg|600px]]<br /><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255422IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T11:29:06Z<p>Choryi.poon.2012: /* Technical Complexity 2: Generating PDF & Charts in PDF */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
[[Image:Tech complex1.png|600px|left]]<br />
<br/><br />
[[Image:Gem ruby finals.jpg|200px|left]]<br />
<br/><br />
[[Image:Gem ruby finals2.jpg|600px|left]]<br />
<br/><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255421IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T11:27:01Z<p>Choryi.poon.2012: /* Technical Complexity 2: Generating PDF */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF & Charts in PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
* Able to display graphs for reporting and display when generating report in pdf. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
<br>[[Image:Gem ruby finals.jpg|200px|left]]<br><br />
<br>[[Image:Gem ruby finals2.jpg|600px|left]]<br><br />
<br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
* Use of Squid gem and GoogleCharts to define data and formatting for charts, graphs and tables. Able to pass in different attributes as parameters. <br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br />
Squid and GoogleCharts make it easy to switch between graph/chart types. Easy to install & documentation is straightforward. However, important to think through purpose of graphic & choose the appropriate type. <br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Gem_ruby_finals2.jpg&diff=255418File:Gem ruby finals2.jpg2016-04-11T10:56:09Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Gem_ruby_finals.jpg&diff=255417File:Gem ruby finals.jpg2016-04-11T10:55:04Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255416IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T10:30:42Z<p>Choryi.poon.2012: /* Bug Metrics */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11 <br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 12 <br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs.<br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log Used the planned debugging time in the iteration. <br />
| style="text-align:center" | Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Project_Bug_Metrics&diff=255415IS480 Team wiki: 2015T2 Starteur Project Bug Metrics2016-04-11T10:18:49Z<p>Choryi.poon.2012: /* Bug Metric Score & Description */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|300px]]<br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START--><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="90%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Schedule | <span style="color:#3d3d3d">Schedule</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics | <span style="color:#3d3d3d">Schedule Metrics</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics | <span style="color:#3d3d3d">Bug Metrics</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management | <span style="color:#3d3d3d">Risk Management</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Change Management | <span style="color:#3d3d3d">Change Management</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--CONTENT START--> <br />
[[File:Bug metric title.jpg|center|800px]]<br />
[[File:(starteur-ed)Bugmetric1.PNG|center|800px]]<br />
[[File:(starteur-ed)Bugmetric2.PNG|center|800px]]<br />
[[File: Bug_metric3(starteur).jpg|center|800px]]<br />
<br />
<br><br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20pxl; font-face: Century Gothic"><font color=#ffffff>Bug Metric Score & Description</font></div>==<br />
[[File:(starteur)Bug metric chart.JPG|900px|center|link=]]<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | -<br />
| style="text-align:center" | -<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | Team stopped current development and resolved bugs immediately. 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | -<br />
| style="text-align:center" | -<br />
<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | -<br />
| style="text-align:center" | - <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated.<br />
| style="text-align:center" | Team stopped development to debug. 1 buffer day used for additional testing and debugging<br />
<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 0<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Iteration stopped midway and was incomplete. <br />
<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 2 critical bugs found. Unable to login to application after integration with Starteur side. Either able to login to Starteur or Starteur for Educators but not both due to conflicting gems. <br />
| style="text-align:center" | Team stopped all development to resolve bugs. <br />
<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 1 low bug and 1 critical bug found. Unable to generate group report and placement error. <br />
| style="text-align:center" | Team stopped all development to resolve bugs. <br />
<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in audit log <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 1 high bug found. Unable to generate page after sandbox transaction. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<!--CONTENT END--><br />
<!--CONTENT END--></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:(starteur)Bug_metric_chart.JPG&diff=255414File:(starteur)Bug metric chart.JPG2016-04-11T10:03:25Z<p>Choryi.poon.2012: Choryi.poon.2012 uploaded a new version of &quot;File:(starteur)Bug metric chart.JPG&quot;</p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255413IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:53:39Z<p>Choryi.poon.2012: /* Team's Reflections */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
#Learnt the importance of communication across ALL stakeholders in order to foster productivity and feedback to develop a better application <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255412IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:50:32Z<p>Choryi.poon.2012: /* Individual Reflections */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Finals(reflections).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Finals(reflections).jpg&diff=255411File:Finals(reflections).jpg2016-04-11T09:48:07Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255410IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:31:05Z<p>Choryi.poon.2012: /* Project Schedule */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur).jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255409IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:30:01Z<p>Choryi.poon.2012: /* Testing */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Location</b>: CHIJ St. Nicholas Girls', Reactor ARC <br/><br />
<b>Date & Time</b>: 14 April onwards <br/><br />
<b>No. of Participants</b>: 3 Educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255408IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:28:55Z<p>Choryi.poon.2012: /* Deliverables */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="3"| Testing<br />
|rowspan="3"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255407IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:28:29Z<p>Choryi.poon.2012: /* Deliverables */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=255406IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-11T09:24:27Z<p>Choryi.poon.2012: /* Project Schedule */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Actual(starteur.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Scheduleforfinals.jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. Schedule was adjusted according to changes in scope. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Scheduleforfinals.jpg&diff=255405File:Scheduleforfinals.jpg2016-04-11T09:21:31Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254185IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:37:10Z<p>Choryi.poon.2012: /* Project Schedule */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254184IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:37:02Z<p>Choryi.poon.2012: /* Deliverables */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 3|UAT 3]]<br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, Reactor ARC <br/><br />
<b>Date & Time</b>: 10 - 23 March 2016<br/><br />
<b>No. of Participants</b>: 3 educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Client management is crucial to a project. It is important to balance the team's capabilities and client's expectations of team. This will greatly help in managing scope of project and load of time. <br />
#Communication is important, be it with end-user, supervisor, client or within the project team. It will enable us to carry out tasks effectively and efficiently. <br />
#Hard work to carry out a project with the minimal number of teammates. But hard work & perseverance pays off. Planning ahead and being flexible helps too. <br />
<br />
===What did we do well?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users liked the interface and gave us positive feedback with regards to usability of functions <br />
* Engaged client actively. Was able to manage client's requests and business needs and keep scope from expanding out of control. <br />
<br />
===What can be improved?===<br />
* Better coordination with Starteur developers.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254183IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:35:50Z<p>Choryi.poon.2012: /* Team's Reflections */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, Reactor ARC <br/><br />
<b>Date & Time</b>: 10 - 23 March 2016<br/><br />
<b>No. of Participants</b>: 3 educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Client management is crucial to a project. It is important to balance the team's capabilities and client's expectations of team. This will greatly help in managing scope of project and load of time. <br />
#Communication is important, be it with end-user, supervisor, client or within the project team. It will enable us to carry out tasks effectively and efficiently. <br />
#Hard work to carry out a project with the minimal number of teammates. But hard work & perseverance pays off. Planning ahead and being flexible helps too. <br />
<br />
===What did we do well?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users liked the interface and gave us positive feedback with regards to usability of functions <br />
* Engaged client actively. Was able to manage client's requests and business needs and keep scope from expanding out of control. <br />
<br />
===What can be improved?===<br />
* Better coordination with Starteur developers.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254182IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:29:13Z<p>Choryi.poon.2012: /* Testing */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
===User Testing 3===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, Reactor ARC <br/><br />
<b>Date & Time</b>: 10 - 23 March 2016<br/><br />
<b>No. of Participants</b>: 3 educators <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 3|Click here to view our User Testing 3!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254180IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:25:18Z<p>Choryi.poon.2012: /* Project Schedule */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There were no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users. <br />
<br />
There were no major changes to the project schedule. Functions were added and removed within the schedule. UAT 4 was removed as Client's management team was unable to make it for the testing due to their busy schedule.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254179IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:20:33Z<p>Choryi.poon.2012: </p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254178IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-08T08:20:03Z<p>Choryi.poon.2012: </p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px|left]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254083IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-07T06:25:19Z<p>Choryi.poon.2012: /* Project Scope */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px|center]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px|center]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|| <br />
[[File:Scope(finals).jpg|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Scope(finals).jpg&diff=254082File:Scope(finals).jpg2016-04-07T06:24:50Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254075IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-07T06:01:54Z<p>Choryi.poon.2012: /* Project Risks */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px|center]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px|center]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254073IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-07T06:00:46Z<p>Choryi.poon.2012: /* Project Scope */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px|center]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px|center]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Removed multiple report <br />
| style="text-align:center" | -<br />
| style="text-align:center" | Post mid-term feedback: group would like to focus on functionalities that give the client most amount of value. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added Audit Log & Search Functionalities<br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions were requested by client after mid-terms. After evaluation, team agreed that it is feasible and valuable to client's business needs. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=254071IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-07T05:56:34Z<p>Choryi.poon.2012: /* Project Achievements */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px|center]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px|center]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=253996IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-06T05:52:37Z<p>Choryi.poon.2012: /* Project Progress Summary */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
[[Image: Project summary.jpg|500px|center]]<br />
<br />
==Project Challenges==<br />
[[Image: Project challenges.jpg|500px|center]]<br />
<br />
==Project Achievements==<br />
<b>urrent Sprint:C</b> 11 <br/><br />
<b>Sprint Duration:</b> 10 Feb 2016 - 17 Feb 2016 <br/><br />
<b>Major Milestone:</b> Midterm Presentation, Integration with Starteur <br/><br />
<br />
<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Project_challenges.jpg&diff=253995File:Project challenges.jpg2016-04-06T05:51:50Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:Project_summary.jpg&diff=253986File:Project summary.jpg2016-04-06T05:27:05Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=253982IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-06T05:13:26Z<p>Choryi.poon.2012: /* Midterm Slides */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Project Status==<br />
<br />
==Final Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
* Deployed application on <b>17 February 2016</b> <br />
* Completed <b>70%</b> of our development work as of 17 February 2016<br />
* <b>Added and removed</b> features to our scope since acceptance (see below)<br />
* <b>Change in schedule</b> since acceptance (see below) <br />
* Completed <b>2 user testings</b> with actual users before midterm <br />
* Confirmed <b>2 educators and 50 students</b> for UAT 3<br />
* In talks with <b>3 Professors and 1 institution</b> for UAT 3<br />
<br />
==Development Progress==<br />
<b>Current Sprint:</b> 11 <br/><br />
<b>Sprint Duration:</b> 10 Feb 2016 - 17 Feb 2016 <br/><br />
<b>Major Milestone:</b> Midterm Presentation, Integration with Starteur <br/><br />
<br />
<b>Upcoming Sprint:</b> 12 <br/><br />
<b>Sprint Duration:</b> 20 Feb 2016 - 7 Mar 2016 <br/><br />
<b>Features Involved:</b> <br />
* Group Report <br />
* Payment Gateway<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Project_Meeting_Minutes&diff=253981IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes2016-04-06T04:55:12Z<p>Choryi.poon.2012: /* Team Meeting Minutes */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|300px]]<br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START--><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="90%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Use Cases | <span style="color:#3d3d3d">Use Cases</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams | <span style="color:#3d3d3d">Technical Diagrams</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents | <span style="color:#3d3d3d">Design Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes | <span style="color:#3d3d3d">Meeting Minutes</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project User Testings | <span style="color:#3d3d3d">User Testings</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Project Documents | <span style="color:#3d3d3d">Project Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
<!--internal meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; line-height: 0.3em; text-indent: 15px;font-size:20px; font-weight: bold; font-face: Century Gothic"><font color=#ffffff>Team Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 24/08/2015<br />
| style="text-align:center" | [[Media:(starteur)TM1 240815.docx| Internal Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 10/09/2015<br />
| style="text-align:center" | [[Media:TM 10092015.docx| Internal Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 20/09/2015<br />
| style="text-align:center" | [[Media:TM 20092015.docx| Internal Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 26/09/2015<br />
| style="text-align:center" | [[Media:TM 26092015.docx| Internal Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 29/09/2015<br />
| style="text-align:center" | [[Media:TM 29092015(1).docx| Internal Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 03/10/2015<br />
| style="text-align:center" | [[Media:TM 03102015.docx| Internal Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 06/10/2015<br />
| style="text-align:center" | [[Media:TM 06102015.docx| Internal Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 09/10/2015<br />
| style="text-align:center" | [[Media:TM 09102015.docx| Internal Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 14/10/2015<br />
| style="text-align:center" | [[Media:TM 14102015.docx| Internal Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 18/10/2015<br />
| style="text-align:center" | [[Media:TM 18102015.docx| Internal Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 21/10/2015<br />
| style="text-align:center" | [[Media:TM 21102015.docx| Internal Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 31/10/2015<br />
| style="text-align:center" | [[Media:TM 31102015.docx| Internal Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 1/11/2015<br />
| style="text-align:center" | [[Media:TM 01112015.docx| Internal Meeting Minutes 13]]<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 11/11/2015<br />
| style="text-align:center" | [[Media:TM 11112015.docx| Internal Meeting Minutes 14]]<br />
|-<br />
| style="text-align:center" | 15<br />
| style="text-align:center" | 18/11/2015<br />
| style="text-align:center" | [[Media:TM 18112015.docx| Internal Meeting Minutes 15]]<br />
|-<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 25/11/2015<br />
| style="text-align:center" | [[Media:TM 25112015.docx| Internal Meeting Minutes 16]]<br />
|-<br />
| style="text-align:center" | 17<br />
| style="text-align:center" | 14/12/2015<br />
| style="text-align:center" | [[Media:TM 14122015.docx| Internal Meeting Minutes 17]]<br />
|-<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 28/12/2015<br />
| style="text-align:center" | [[Media:TM 28122015.docx| Internal Meeting Minutes 18]]<br />
|-<br />
| style="text-align:center" | 19<br />
| style="text-align:center" | 05/01/2016<br />
| style="text-align:center" | [[Media:TM 05012016.docx| Internal Meeting Minutes 19]]<br />
|-<br />
| style="text-align:center" | 20<br />
| style="text-align:center" | 16/01/2016<br />
| style="text-align:center" | [[Media:TM 16012016.docx| Internal Meeting Minutes 20]]<br />
|-<br />
| style="text-align:center" | 21<br />
| style="text-align:center" | 22/01/2016<br />
| style="text-align:center" | [[Media:TM 22012016.docx| Internal Meeting Minutes 21]]<br />
|-<br />
| style="text-align:center" | 22<br />
| style="text-align:center" | 29/01/2016<br />
| style="text-align:center" | [[Media:TM 29012016.docx| Internal Meeting Minutes 22]]<br />
|-<br />
| style="text-align:center" | 23<br />
| style="text-align:center" | 05/02/2016<br />
| style="text-align:center" | [[Media:TM 05022016.docx| Internal Meeting Minutes 23]]<br />
|-<br />
| style="text-align:center" | 24<br />
| style="text-align:center" | 12/02/2016<br />
| style="text-align:center" | [[Media:TM 12022016.docx| Internal Meeting Minutes 24]]<br />
|-<br />
| style="text-align:center" | 25<br />
| style="text-align:center" | 16/02/2016<br />
| style="text-align:center" | [[Media:TM 16022016.docx| Internal Meeting Minutes 25]]<br />
|-<br />
| style="text-align:center" | 26<br />
| style="text-align:center" | 23/02/2016<br />
| style="text-align:center" | [[Media:TM 23022016.docx| Internal Meeting Minutes 26]]<br />
|-<br />
| style="text-align:center" | 27<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 27]]<br />
|-<br />
| style="text-align:center" | 28<br />
| style="text-align:center" | 10/03/2016<br />
| style="text-align:center" | [[Media:TM 10032016.docx| Internal Meeting Minutes 28]]<br />
|-<br />
| style="text-align:center" | 29<br />
| style="text-align:center" | 19/03/2016<br />
| style="text-align:center" | [[Media:TM 19032016.docx| Internal Meeting Minutes 29]]<br />
|-<br />
| style="text-align:center" | 30<br />
| style="text-align:center" | 25/03/2016<br />
| style="text-align:center" | [[Media:TM 25032016.docx| Internal Meeting Minutes 230]]<br />
|-<br />
|}<br />
</div><br />
<br />
<br />
<!--Supervisor meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;font-size:20px; font-face: Century Gothic"><font color=#ffffff>Supervisor Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|- <br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 29/10/2015<br />
| style="text-align:center" | [[Media:Supervisor 29102015.docx| Supervisor Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 30/11/2015<br />
| style="text-align:center" | [[Media:SM 30112015.docx| Supervisor Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 13/01/2016<br />
| style="text-align:center" | [[Media:SM 13012016.docx| Supervisor Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 20/01/2016<br />
| style="text-align:center" | [[Media:SM 20012016.docx| Supervisor Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 27/01/2016<br />
| style="text-align:center" | [[Media:SM 27012016.docx| Supervisor Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 03/02/2016<br />
| style="text-align:center" | [[Media:SM 03022016.docx| Supervisor Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 10/02/2016<br />
| style="text-align:center" | [[Media:SM 10022016.docx| Supervisor Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 15/02/2016<br />
| style="text-align:center" | [[Media:SM 15022016.docx| Supervisor Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:SM 02032016.docx| Supervisor Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 09/03/2016<br />
| style="text-align:center" | [[Media:SM 09032016.docx| Supervisor Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 16/03/2016<br />
| style="text-align:center" | [[Media:SM 16032016.docx| Supervisor Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 23/03/2016<br />
| style="text-align:center" | [[Media:SM 23032016.docx| Supervisor Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 30/03/2016<br />
| style="text-align:center" | [[Media:SM 30032016.docx| Supervisor Meeting Minutes 13]]<br />
|-<br />
|}<br />
</div><br />
<br />
<br />
<!--Sponsor meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;font-face: Century Gothic;font-size:20px"><font color=#ffffff>Sponsor Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 3/09/2015<br />
| style="text-align:center" | [[Media:(starteur-ed)Client meeting.docx| Sponsor Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 14/09/2015<br />
| style="text-align:center" | [[Media:(starteur-ed)Client meeting 2.docx| Sponsor Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 28/09/2015<br />
| style="text-align:center" | [[Media:CM 28092015.docx| Sponsor Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 18/10/2015<br />
| style="text-align:center" | [[Media:CM 18102015.docx| Sponsor Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 31/10/2015<br />
| style="text-align:center" | [[Media:TM 31102015.docx| Sponsor Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 11/11/2015<br />
| style="text-align:center" | [[Media:TM 11112015.docx| Sponsor Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 18/11/2015<br />
| style="text-align:center" | [[Media:TM 18112015.docx| Sponsor Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 14/12/2015<br />
| style="text-align:center" | [[Media:TM 14122015.docx| Sponsor Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 28/12/2015<br />
| style="text-align:center" | [[Media:TM 28122015.docx| Sponsor Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 16/01/2016<br />
| style="text-align:center" | [[Media:CM 16012016.docx| Sponsor Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 22/01/2016<br />
| style="text-align:center" | [[Media:TM 22012016.docx| Sponsor Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 29/01/2016<br />
| style="text-align:center" | [[Media:TM 29012016.docx| Sponsor Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 05/02/2016<br />
| style="text-align:center" | [[Media:TM 05022016.docx| Sponsor Meeting Minutes 13]]<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 16/02/2016<br />
| style="text-align:center" | [[Media:TM 16022016.docx| Sponsor Meeting Minutes 14]]<br />
|-<br />
| style="text-align:center" | 15<br />
| style="text-align:center" | 23/02/2016<br />
| style="text-align:center" | [[Media:TM 23022016.docx| Sponsor Meeting Minutes 15]]<br />
|-<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:TM 03032016.docx| Sponsor Meeting Minutes 16]]<br />
|-<br />
| style="text-align:center" | 17<br />
| style="text-align:center" | 10/03/2016<br />
| style="text-align:center" | [[Media:TM 10032016.docx| Sponsor Meeting Minutes 17]]<br />
|-<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 25/03/2016<br />
| style="text-align:center" | [[Media:TM 25032016.docx| Sponsor Meeting Minutes 18]]<br />
|-<br />
|}<br />
</div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:TM_19032016.docx&diff=253980File:TM 19032016.docx2016-04-06T04:54:38Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Project_Meeting_Minutes&diff=253979IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes2016-04-06T04:53:52Z<p>Choryi.poon.2012: /* Sponsor Meeting Minutes */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|300px]]<br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START--><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="90%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Use Cases | <span style="color:#3d3d3d">Use Cases</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams | <span style="color:#3d3d3d">Technical Diagrams</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents | <span style="color:#3d3d3d">Design Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes | <span style="color:#3d3d3d">Meeting Minutes</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project User Testings | <span style="color:#3d3d3d">User Testings</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Project Documents | <span style="color:#3d3d3d">Project Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
<!--internal meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; line-height: 0.3em; text-indent: 15px;font-size:20px; font-weight: bold; font-face: Century Gothic"><font color=#ffffff>Team Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 24/08/2015<br />
| style="text-align:center" | [[Media:(starteur)TM1 240815.docx| Internal Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 10/09/2015<br />
| style="text-align:center" | [[Media:TM 10092015.docx| Internal Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 20/09/2015<br />
| style="text-align:center" | [[Media:TM 20092015.docx| Internal Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 26/09/2015<br />
| style="text-align:center" | [[Media:TM 26092015.docx| Internal Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 29/09/2015<br />
| style="text-align:center" | [[Media:TM 29092015(1).docx| Internal Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 03/10/2015<br />
| style="text-align:center" | [[Media:TM 03102015.docx| Internal Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 06/10/2015<br />
| style="text-align:center" | [[Media:TM 06102015.docx| Internal Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 09/10/2015<br />
| style="text-align:center" | [[Media:TM 09102015.docx| Internal Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 14/10/2015<br />
| style="text-align:center" | [[Media:TM 14102015.docx| Internal Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 18/10/2015<br />
| style="text-align:center" | [[Media:TM 18102015.docx| Internal Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 21/10/2015<br />
| style="text-align:center" | [[Media:TM 21102015.docx| Internal Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 31/10/2015<br />
| style="text-align:center" | [[Media:TM 31102015.docx| Internal Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 1/11/2015<br />
| style="text-align:center" | [[Media:TM 01112015.docx| Internal Meeting Minutes 13]]<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 11/11/2015<br />
| style="text-align:center" | [[Media:TM 11112015.docx| Internal Meeting Minutes 14]]<br />
|-<br />
| style="text-align:center" | 15<br />
| style="text-align:center" | 18/11/2015<br />
| style="text-align:center" | [[Media:TM 18112015.docx| Internal Meeting Minutes 15]]<br />
|-<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 25/11/2015<br />
| style="text-align:center" | [[Media:TM 25112015.docx| Internal Meeting Minutes 16]]<br />
|-<br />
| style="text-align:center" | 17<br />
| style="text-align:center" | 14/12/2015<br />
| style="text-align:center" | [[Media:TM 14122015.docx| Internal Meeting Minutes 17]]<br />
|-<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 28/12/2015<br />
| style="text-align:center" | [[Media:TM 28122015.docx| Internal Meeting Minutes 18]]<br />
|-<br />
| style="text-align:center" | 19<br />
| style="text-align:center" | 05/01/2016<br />
| style="text-align:center" | [[Media:TM 05012016.docx| Internal Meeting Minutes 19]]<br />
|-<br />
| style="text-align:center" | 20<br />
| style="text-align:center" | 16/01/2016<br />
| style="text-align:center" | [[Media:TM 16012016.docx| Internal Meeting Minutes 20]]<br />
|-<br />
| style="text-align:center" | 21<br />
| style="text-align:center" | 22/01/2016<br />
| style="text-align:center" | [[Media:TM 22012016.docx| Internal Meeting Minutes 21]]<br />
|-<br />
| style="text-align:center" | 22<br />
| style="text-align:center" | 29/01/2016<br />
| style="text-align:center" | [[Media:TM 29012016.docx| Internal Meeting Minutes 22]]<br />
|-<br />
| style="text-align:center" | 23<br />
| style="text-align:center" | 05/02/2016<br />
| style="text-align:center" | [[Media:TM 05022016.docx| Internal Meeting Minutes 23]]<br />
|-<br />
| style="text-align:center" | 24<br />
| style="text-align:center" | 12/02/2016<br />
| style="text-align:center" | [[Media:TM 12022016.docx| Internal Meeting Minutes 24]]<br />
|-<br />
| style="text-align:center" | 25<br />
| style="text-align:center" | 16/02/2016<br />
| style="text-align:center" | [[Media:TM 16022016.docx| Internal Meeting Minutes 25]]<br />
|-<br />
| style="text-align:center" | 26<br />
| style="text-align:center" | 23/02/2016<br />
| style="text-align:center" | [[Media:TM 23022016.docx| Internal Meeting Minutes 26]]<br />
|-<br />
| style="text-align:center" | 27<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 27]]<br />
|-<br />
| style="text-align:center" | 28<br />
| style="text-align:center" | <br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 28]]<br />
|-<br />
| style="text-align:center" | 29<br />
| style="text-align:center" | <br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 29]]<br />
|-<br />
| style="text-align:center" | 30<br />
| style="text-align:center" | 25/03/2016<br />
| style="text-align:center" | [[Media:TM 25032016.docx| Internal Meeting Minutes 230]]<br />
|-<br />
|}<br />
</div><br />
<br />
<br />
<!--Supervisor meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;font-size:20px; font-face: Century Gothic"><font color=#ffffff>Supervisor Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|- <br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 29/10/2015<br />
| style="text-align:center" | [[Media:Supervisor 29102015.docx| Supervisor Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 30/11/2015<br />
| style="text-align:center" | [[Media:SM 30112015.docx| Supervisor Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 13/01/2016<br />
| style="text-align:center" | [[Media:SM 13012016.docx| Supervisor Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 20/01/2016<br />
| style="text-align:center" | [[Media:SM 20012016.docx| Supervisor Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 27/01/2016<br />
| style="text-align:center" | [[Media:SM 27012016.docx| Supervisor Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 03/02/2016<br />
| style="text-align:center" | [[Media:SM 03022016.docx| Supervisor Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 10/02/2016<br />
| style="text-align:center" | [[Media:SM 10022016.docx| Supervisor Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 15/02/2016<br />
| style="text-align:center" | [[Media:SM 15022016.docx| Supervisor Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:SM 02032016.docx| Supervisor Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 09/03/2016<br />
| style="text-align:center" | [[Media:SM 09032016.docx| Supervisor Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 16/03/2016<br />
| style="text-align:center" | [[Media:SM 16032016.docx| Supervisor Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 23/03/2016<br />
| style="text-align:center" | [[Media:SM 23032016.docx| Supervisor Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 30/03/2016<br />
| style="text-align:center" | [[Media:SM 30032016.docx| Supervisor Meeting Minutes 13]]<br />
|-<br />
|}<br />
</div><br />
<br />
<br />
<!--Sponsor meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;font-face: Century Gothic;font-size:20px"><font color=#ffffff>Sponsor Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 3/09/2015<br />
| style="text-align:center" | [[Media:(starteur-ed)Client meeting.docx| Sponsor Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 14/09/2015<br />
| style="text-align:center" | [[Media:(starteur-ed)Client meeting 2.docx| Sponsor Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 28/09/2015<br />
| style="text-align:center" | [[Media:CM 28092015.docx| Sponsor Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 18/10/2015<br />
| style="text-align:center" | [[Media:CM 18102015.docx| Sponsor Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 31/10/2015<br />
| style="text-align:center" | [[Media:TM 31102015.docx| Sponsor Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 11/11/2015<br />
| style="text-align:center" | [[Media:TM 11112015.docx| Sponsor Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 18/11/2015<br />
| style="text-align:center" | [[Media:TM 18112015.docx| Sponsor Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 14/12/2015<br />
| style="text-align:center" | [[Media:TM 14122015.docx| Sponsor Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 28/12/2015<br />
| style="text-align:center" | [[Media:TM 28122015.docx| Sponsor Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 16/01/2016<br />
| style="text-align:center" | [[Media:CM 16012016.docx| Sponsor Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 22/01/2016<br />
| style="text-align:center" | [[Media:TM 22012016.docx| Sponsor Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 29/01/2016<br />
| style="text-align:center" | [[Media:TM 29012016.docx| Sponsor Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 05/02/2016<br />
| style="text-align:center" | [[Media:TM 05022016.docx| Sponsor Meeting Minutes 13]]<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 16/02/2016<br />
| style="text-align:center" | [[Media:TM 16022016.docx| Sponsor Meeting Minutes 14]]<br />
|-<br />
| style="text-align:center" | 15<br />
| style="text-align:center" | 23/02/2016<br />
| style="text-align:center" | [[Media:TM 23022016.docx| Sponsor Meeting Minutes 15]]<br />
|-<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:TM 03032016.docx| Sponsor Meeting Minutes 16]]<br />
|-<br />
| style="text-align:center" | 17<br />
| style="text-align:center" | 10/03/2016<br />
| style="text-align:center" | [[Media:TM 10032016.docx| Sponsor Meeting Minutes 17]]<br />
|-<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 25/03/2016<br />
| style="text-align:center" | [[Media:TM 25032016.docx| Sponsor Meeting Minutes 18]]<br />
|-<br />
|}<br />
</div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:TM_10032016.docx&diff=253978File:TM 10032016.docx2016-04-06T04:53:28Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Project_Meeting_Minutes&diff=253977IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes2016-04-06T04:20:19Z<p>Choryi.poon.2012: /* Supervisor Meeting Minutes */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|300px]]<br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START--><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="90%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Use Cases | <span style="color:#3d3d3d">Use Cases</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams | <span style="color:#3d3d3d">Technical Diagrams</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents | <span style="color:#3d3d3d">Design Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes | <span style="color:#3d3d3d">Meeting Minutes</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project User Testings | <span style="color:#3d3d3d">User Testings</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Project Documents | <span style="color:#3d3d3d">Project Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
<!--internal meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; line-height: 0.3em; text-indent: 15px;font-size:20px; font-weight: bold; font-face: Century Gothic"><font color=#ffffff>Team Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 24/08/2015<br />
| style="text-align:center" | [[Media:(starteur)TM1 240815.docx| Internal Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 10/09/2015<br />
| style="text-align:center" | [[Media:TM 10092015.docx| Internal Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 20/09/2015<br />
| style="text-align:center" | [[Media:TM 20092015.docx| Internal Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 26/09/2015<br />
| style="text-align:center" | [[Media:TM 26092015.docx| Internal Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 29/09/2015<br />
| style="text-align:center" | [[Media:TM 29092015(1).docx| Internal Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 03/10/2015<br />
| style="text-align:center" | [[Media:TM 03102015.docx| Internal Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 06/10/2015<br />
| style="text-align:center" | [[Media:TM 06102015.docx| Internal Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 09/10/2015<br />
| style="text-align:center" | [[Media:TM 09102015.docx| Internal Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 14/10/2015<br />
| style="text-align:center" | [[Media:TM 14102015.docx| Internal Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 18/10/2015<br />
| style="text-align:center" | [[Media:TM 18102015.docx| Internal Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 21/10/2015<br />
| style="text-align:center" | [[Media:TM 21102015.docx| Internal Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 31/10/2015<br />
| style="text-align:center" | [[Media:TM 31102015.docx| Internal Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 1/11/2015<br />
| style="text-align:center" | [[Media:TM 01112015.docx| Internal Meeting Minutes 13]]<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 11/11/2015<br />
| style="text-align:center" | [[Media:TM 11112015.docx| Internal Meeting Minutes 14]]<br />
|-<br />
| style="text-align:center" | 15<br />
| style="text-align:center" | 18/11/2015<br />
| style="text-align:center" | [[Media:TM 18112015.docx| Internal Meeting Minutes 15]]<br />
|-<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 25/11/2015<br />
| style="text-align:center" | [[Media:TM 25112015.docx| Internal Meeting Minutes 16]]<br />
|-<br />
| style="text-align:center" | 17<br />
| style="text-align:center" | 14/12/2015<br />
| style="text-align:center" | [[Media:TM 14122015.docx| Internal Meeting Minutes 17]]<br />
|-<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 28/12/2015<br />
| style="text-align:center" | [[Media:TM 28122015.docx| Internal Meeting Minutes 18]]<br />
|-<br />
| style="text-align:center" | 19<br />
| style="text-align:center" | 05/01/2016<br />
| style="text-align:center" | [[Media:TM 05012016.docx| Internal Meeting Minutes 19]]<br />
|-<br />
| style="text-align:center" | 20<br />
| style="text-align:center" | 16/01/2016<br />
| style="text-align:center" | [[Media:TM 16012016.docx| Internal Meeting Minutes 20]]<br />
|-<br />
| style="text-align:center" | 21<br />
| style="text-align:center" | 22/01/2016<br />
| style="text-align:center" | [[Media:TM 22012016.docx| Internal Meeting Minutes 21]]<br />
|-<br />
| style="text-align:center" | 22<br />
| style="text-align:center" | 29/01/2016<br />
| style="text-align:center" | [[Media:TM 29012016.docx| Internal Meeting Minutes 22]]<br />
|-<br />
| style="text-align:center" | 23<br />
| style="text-align:center" | 05/02/2016<br />
| style="text-align:center" | [[Media:TM 05022016.docx| Internal Meeting Minutes 23]]<br />
|-<br />
| style="text-align:center" | 24<br />
| style="text-align:center" | 12/02/2016<br />
| style="text-align:center" | [[Media:TM 12022016.docx| Internal Meeting Minutes 24]]<br />
|-<br />
| style="text-align:center" | 25<br />
| style="text-align:center" | 16/02/2016<br />
| style="text-align:center" | [[Media:TM 16022016.docx| Internal Meeting Minutes 25]]<br />
|-<br />
| style="text-align:center" | 26<br />
| style="text-align:center" | 23/02/2016<br />
| style="text-align:center" | [[Media:TM 23022016.docx| Internal Meeting Minutes 26]]<br />
|-<br />
| style="text-align:center" | 27<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 27]]<br />
|-<br />
| style="text-align:center" | 28<br />
| style="text-align:center" | <br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 28]]<br />
|-<br />
| style="text-align:center" | 29<br />
| style="text-align:center" | <br />
| style="text-align:center" | [[Media:TM 03032016.docx| Internal Meeting Minutes 29]]<br />
|-<br />
| style="text-align:center" | 30<br />
| style="text-align:center" | 25/03/2016<br />
| style="text-align:center" | [[Media:TM 25032016.docx| Internal Meeting Minutes 230]]<br />
|-<br />
|}<br />
</div><br />
<br />
<br />
<!--Supervisor meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;font-size:20px; font-face: Century Gothic"><font color=#ffffff>Supervisor Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|- <br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 29/10/2015<br />
| style="text-align:center" | [[Media:Supervisor 29102015.docx| Supervisor Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 30/11/2015<br />
| style="text-align:center" | [[Media:SM 30112015.docx| Supervisor Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 13/01/2016<br />
| style="text-align:center" | [[Media:SM 13012016.docx| Supervisor Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 20/01/2016<br />
| style="text-align:center" | [[Media:SM 20012016.docx| Supervisor Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 27/01/2016<br />
| style="text-align:center" | [[Media:SM 27012016.docx| Supervisor Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 03/02/2016<br />
| style="text-align:center" | [[Media:SM 03022016.docx| Supervisor Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 10/02/2016<br />
| style="text-align:center" | [[Media:SM 10022016.docx| Supervisor Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 15/02/2016<br />
| style="text-align:center" | [[Media:SM 15022016.docx| Supervisor Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:SM 02032016.docx| Supervisor Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 09/03/2016<br />
| style="text-align:center" | [[Media:SM 09032016.docx| Supervisor Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 16/03/2016<br />
| style="text-align:center" | [[Media:SM 16032016.docx| Supervisor Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 23/03/2016<br />
| style="text-align:center" | [[Media:SM 23032016.docx| Supervisor Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 30/03/2016<br />
| style="text-align:center" | [[Media:SM 30032016.docx| Supervisor Meeting Minutes 13]]<br />
|-<br />
|}<br />
</div><br />
<br />
<br />
<!--Sponsor meeting minutes--><br />
<div style="text-align: left; width:1080px; margin-left:auto; margin-right:auto; "><br />
<br />
==<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;font-face: Century Gothic;font-size:20px"><font color=#ffffff>Sponsor Meeting Minutes</font></div>==<br />
<br />
{| class="wikitable" <br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | No.<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999; font-face: Century Gothic" | Date<br />
! style="font-weight: text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:200px; border:1px solid #999; font-face: Century Gothic" | Minutes<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 3/09/2015<br />
| style="text-align:center" | [[Media:(starteur-ed)Client meeting.docx| Sponsor Meeting Minutes 1]]<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 14/09/2015<br />
| style="text-align:center" | [[Media:(starteur-ed)Client meeting 2.docx| Sponsor Meeting Minutes 2]]<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 28/09/2015<br />
| style="text-align:center" | [[Media:CM 28092015.docx| Sponsor Meeting Minutes 3]]<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 18/10/2015<br />
| style="text-align:center" | [[Media:CM 18102015.docx| Sponsor Meeting Minutes 4]]<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 31/10/2015<br />
| style="text-align:center" | [[Media:TM 31102015.docx| Sponsor Meeting Minutes 5]]<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 11/11/2015<br />
| style="text-align:center" | [[Media:TM 11112015.docx| Sponsor Meeting Minutes 6]]<br />
|-<br />
| style="text-align:center" | 7<br />
| style="text-align:center" | 18/11/2015<br />
| style="text-align:center" | [[Media:TM 18112015.docx| Sponsor Meeting Minutes 7]]<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 14/12/2015<br />
| style="text-align:center" | [[Media:TM 14122015.docx| Sponsor Meeting Minutes 8]]<br />
|-<br />
| style="text-align:center" | 9<br />
| style="text-align:center" | 28/12/2015<br />
| style="text-align:center" | [[Media:TM 28122015.docx| Sponsor Meeting Minutes 9]]<br />
|-<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 16/01/2016<br />
| style="text-align:center" | [[Media:CM 16012016.docx| Sponsor Meeting Minutes 10]]<br />
|-<br />
| style="text-align:center" | 11<br />
| style="text-align:center" | 22/01/2016<br />
| style="text-align:center" | [[Media:TM 22012016.docx| Sponsor Meeting Minutes 11]]<br />
|-<br />
| style="text-align:center" | 12<br />
| style="text-align:center" | 29/01/2016<br />
| style="text-align:center" | [[Media:TM 29012016.docx| Sponsor Meeting Minutes 12]]<br />
|-<br />
| style="text-align:center" | 13<br />
| style="text-align:center" | 05/02/2016<br />
| style="text-align:center" | [[Media:TM 05022016.docx| Sponsor Meeting Minutes 13]]<br />
|-<br />
| style="text-align:center" | 14<br />
| style="text-align:center" | 16/02/2016<br />
| style="text-align:center" | [[Media:TM 16022016.docx| Sponsor Meeting Minutes 14]]<br />
|-<br />
| style="text-align:center" | 15<br />
| style="text-align:center" | 23/02/2016<br />
| style="text-align:center" | [[Media:TM 23022016.docx| Sponsor Meeting Minutes 15]]<br />
|-<br />
| style="text-align:center" | 16<br />
| style="text-align:center" | 03/03/2016<br />
| style="text-align:center" | [[Media:TM 03032016.docx| Sponsor Meeting Minutes 16]]<br />
|-<br />
| style="text-align:center" | 17<br />
| style="text-align:center" | <br />
| style="text-align:center" | [[Media:TM 03032016.docx| Sponsor Meeting Minutes 17]]<br />
|-<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | <br />
| style="text-align:center" | [[Media:TM 03032016.docx| Sponsor Meeting Minutes 18]]<br />
|-<br />
| style="text-align:center" | 19<br />
| style="text-align:center" | 25/03/2016<br />
| style="text-align:center" | [[Media:TM 25032016.docx| Sponsor Meeting Minutes 19]]<br />
|-<br />
|}<br />
</div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:SM_30032016.docx&diff=253976File:SM 30032016.docx2016-04-06T04:19:37Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=253919IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-05T09:24:54Z<p>Choryi.poon.2012: /* Midterm Slides */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Project Status==<br />
<br />
==Midterm Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our final presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
* Deployed application on <b>17 February 2016</b> <br />
* Completed <b>70%</b> of our development work as of 17 February 2016<br />
* <b>Added and removed</b> features to our scope since acceptance (see below)<br />
* <b>Change in schedule</b> since acceptance (see below) <br />
* Completed <b>2 user testings</b> with actual users before midterm <br />
* Confirmed <b>2 educators and 50 students</b> for UAT 3<br />
* In talks with <b>3 Professors and 1 institution</b> for UAT 3<br />
<br />
==Development Progress==<br />
<b>Current Sprint:</b> 11 <br/><br />
<b>Sprint Duration:</b> 10 Feb 2016 - 17 Feb 2016 <br/><br />
<b>Major Milestone:</b> Midterm Presentation, Integration with Starteur <br/><br />
<br />
<b>Upcoming Sprint:</b> 12 <br/><br />
<b>Sprint Duration:</b> 20 Feb 2016 - 7 Mar 2016 <br/><br />
<b>Features Involved:</b> <br />
* Group Report <br />
* Payment Gateway<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_Final_Wiki&diff=253918IS480 Team wiki: 2015T2 Starteur Final Wiki2016-04-05T09:24:37Z<p>Choryi.poon.2012: /* Project Status */</p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|200px]]<br><br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Home |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START --><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="55%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Main Wiki | <span style="color:#3d3d3d">Main Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Midterm Wiki | <span style="color:#3d3d3d">Midterm Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Final Wiki | <span style="color:#3d3d3d">Final Wiki</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
{|style=" width="100%" cellspacing="0" border="0" |<br />
| style="font-size:100%; background-color:#FFFFFF; " width="10%" | <br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Progress Summary</font></div>=<br />
<br />
==Project Status==<br />
<br />
==Midterm Slides==<br />
Click [[Media: Midterm(final).pdf| here]] to download our midterm presentation slides!<br />
<br />
==Deployed Website Link==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Project Highlights==<br />
* Deployed application on <b>17 February 2016</b> <br />
* Completed <b>70%</b> of our development work as of 17 February 2016<br />
* <b>Added and removed</b> features to our scope since acceptance (see below)<br />
* <b>Change in schedule</b> since acceptance (see below) <br />
* Completed <b>2 user testings</b> with actual users before midterm <br />
* Confirmed <b>2 educators and 50 students</b> for UAT 3<br />
* In talks with <b>3 Professors and 1 institution</b> for UAT 3<br />
<br />
==Development Progress==<br />
<b>Current Sprint:</b> 11 <br/><br />
<b>Sprint Duration:</b> 10 Feb 2016 - 17 Feb 2016 <br/><br />
<b>Major Milestone:</b> Midterm Presentation, Integration with Starteur <br/><br />
<br />
<b>Upcoming Sprint:</b> 12 <br/><br />
<b>Sprint Duration:</b> 20 Feb 2016 - 7 Mar 2016 <br/><br />
<b>Features Involved:</b> <br />
* Group Report <br />
* Payment Gateway<br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Project Management</font></div>=<br />
<br />
==Project Scope==<br />
{| class="wikitable" border="1" align="center"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Planned<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Actual<br />
|-<br />
|<br />
[[File:Planned scope(starteur).png|center|800px]]<br />
|| <br />
[[File:Actual scope(starteur).png|center|850px]]<br />
|}<br />
<br />
<h4>Major Changes</h4><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Module<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:8%; border:1px solid #999" | Category<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:15%; border:1px solid #999" | Change/Removal/Addition <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Description<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:30%; border:1px solid #999" | Reason for change/removal/addition<br />
|-<br />
| style="text-align:center"| Educator Management <br />
| style="text-align:center"| Primary<br />
| style="text-align:center"| Change Track completion rate to Track status of access code <br />
| style="text-align:center"| Instead of tracking the completion rate of the Starteur Test, we will be tracking if students have been assigned an access code to the test, used their access code and if they have completed the Starteur test. <br />
| style="text-align:center"| Educators have reflected that they will need to know if their students have been assigned an access code to the test or not and if they have completed the test, so that they can send our test reminders. Knowing which part of the test the students are not, does not help them much or give them any information to work on. <br />
|-<br />
<br />
|-<br />
| style="text-align:center" | Notification<br />
| style="text-align:center" | Secondary<br />
| style="text-align:center" | Change of automated test reminder email to manual test reminder<br />
| style="text-align:center" | Instead of the web application automatically sending out an email reminder to students who have to completed the Starteur test, according to a particular threshold (e.g. 5 days later), educators will now have to manually use the application to send out a reminder. <br />
| style="text-align:center" | Educators prefer to have control over the frequency of sending out emails to their students and to control the threshold number of days. <br />
|- <br />
<br />
|-<br />
| style="text-align:center" | Group Report <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Removed Filter students in group<br />
| style="text-align:center" | -<br />
| style="text-align:center" | Educators have provided feedback during initial questionnaire that these 2 functions are of no relevance to them. They do not need to know the ranking of students as they are more broad-visioned and requires an overview of their students instead. They also prefer to see such results within the report instead. <br />
|-<br />
<br />
| style="text-align:center" | Payment Gateway <br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Shifted View Payment History and Generate Invoice in Educator Management to Payment Gateway <br />
| style="text-align:center" | -<br />
| style="text-align:center" | These 2 functions will only be fully completed when 3rd party payment integration is up. As such, we have shifted them there. <br />
|-<br />
<br />
| style="text-align:center" | Group Report<br />
| style="text-align:center" | Secondary <br />
| style="text-align:center" | Added Multiple Group Report <br />
| style="text-align:center" | Educators will now be able to view a report that consolidates results from more than 1 student group. <br />
| style="text-align:center" | Educators have reflected that they would like to view results from student cohorts, which means that they want to be able to combine multiple student groups to see how each academic year's cohort would differ in behavior. <br />
|-<br />
<br />
| style="text-align:center" | Client Administrator<br />
| style="text-align:center" | Tertiary<br />
| style="text-align:center" | Added transfer Ownership<br />
| style="text-align:center" | Administrator is able to transfer ownership of access code generated to another educator for promotion purposes.<br />
| style="text-align:center" | After discussing in detail with client, team decided to implement this function to allow client to use this as a promotion too. <br />
|-<br />
<br />
|}<br />
<br />
<br />
[[IS480 Team wiki: 2015T2 Starteur Project Change Management|View our Change Management Here!]]<br />
<br />
==Project Schedule==<br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Planned Schedule</font></div><br />
[[Image:Schedule(v1)031115.jpg|center|1200px]]<br />
<br><br />
<div style="background: #FFFFFF; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:16px; font-family:helvetica"><font color= #000000>Actual Schedule</font></div><br />
[[File:Actual(starteur).jpg|center|1200px]]<br />
<br />
<h4>Schedule Highlights</h4><br />
There are no major changes to the project schedule. Functions were shifted around within the schedule due to difficulties faced at the middle of the project (Iteration 9), required inputs from Starteur developers were not provided in time. The team postponed testing for Student & Batch Report functions to after Mid Terms Presentation as User Testing 3 due to changes in project schedule. Focus of User Testing 2 was changed to Client Administrator Module, with Reactor Industries' management team as target end-users.<br />
<br />
==Project Metrics==<br />
<br />
===Schedule Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|View our Schedule Metrics Here!]]<br><br />
<br />
[[File:Schedulemetric(chart).PNG|800px|center|link==]]<br />
<br />
<font size=3><b>Schedule Metric Highlights</b></font><br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Iteration<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Planned Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Actual Duration/days<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Schedule Metric Score<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:50%; border:1px solid #999" | Action<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:10%; border:1px solid #999" | Status<br />
<br />
|-<br />
| style="text-align:center"| 5<br />
| style="text-align:center"| 10<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| 0.91<br />
| style="text-align:center"| Our estimates are fairly accurate. Project schedule is on track. Difficulty in setting up email server for Starteur and it was exams period for SMU Term 1. As such, project was delayed. 1 buffer day used.<br />
| style="text-align:center"| Completed<br />
|-<br />
<br />
|-<br />
| style="text-align:center"| 9<br />
| style="text-align:center"| 14<br />
| style="text-align:center"| 11<br />
| style="text-align:center"| -<br />
| style="text-align:center"| Group report module was pushed back due to client's inability to provide algorithm on time. Supervisor was informed of change in schedule.<br />
| style="text-align:center"| Incomplete<br />
|-<br />
<br />
|}<br />
<br />
===Bug Metrics===<br />
[[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|View our Bug Metrics Here!]] <br><br />
[[File:(starteur)Bug metric chart.JPG|800px|center]]<br />
<br />
<font size=3><b>Bug Metric Highlights</b></font><br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Iteration<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Bug Score<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Summary of Bugs<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Action Taken<br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2 <br />
| style="text-align:center" | 2 low bugs found. Low bugs were related to displaying of individual batch page<br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | 2 medium bugs and 2 low bugs found. Medium bugs found in functionality to purchase access codes for test. Low bugs found in displaying tests in test store for purchase <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 3 low bugs found. Low bugs found in displaying of student name in batch. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 18<br />
| style="text-align:center" | 2 high bugs found. High bugs found in functionality to send access code to students in student group. Logic to send different types of code usage to different types of students (students who have a Starteur account and students who don't). <br />
| style="text-align:center" | 1 buffer day used for testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 8<br />
| style="text-align:center" | 10<br />
| style="text-align:center" | 2 low bugs found and 3 medium bugs found. Alignment of elements in individual student report and presenting all data on pdf generated. <br />
| style="text-align:center" | 1 buffer day used for additional testing and debugging. <br />
<br />
|-<br />
| style="text-align:center" | 10 <br />
| style="text-align:center" | 4<br />
| style="text-align:center" | 4 low bugs found. Alignment of elements in form to generate access codes, promotion code and discount code. <br />
| style="text-align:center" | Used the planned debugging time in the iteration. Team was able to fix all the bugs within the scheduled time.<br />
<br />
|}<br />
<br />
==Project Risks==<br />
<br><br />
[[Image: Starteur(midterm)Risk Table.jpg|center|650px]]<br />
===Activated Risks===<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Development Risk <br />
| style="text-align:center" | Starteur for Educators will require results from Starteur and is sharing same database as Starteur. Delays in Starteur may impact Starteur for Educators and may delay progress. Inconsistencies will compromise on user experience. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Starteur for Educators to specify their needs early to Starteur and client. Constant communication and updates from both sides. Schedule planned ahead with possible changes in mind as well as Starteur’s development schedule. Cut-off time to pull changes from Starteur development branch. <br />
<br />
|-<br />
| style="text-align:center" | Technical Risk <br />
| style="text-align:center" | RubyonRails is a new framework for development team other than Kia Yong who has experience working with it. As such, inexperience with the framework and insufficient learning time will delay development schedule and will affect quality of work produced. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team started learning RubyOnRails once project and technology has been confirmed. Daily updates on learning with screenshots of Codeacademy progress. Highly useful reference materials identified: Rails tutorial and Rails Casts. Kia Yong acting as a mentor for team and to implement best practices for coding<br />
<br />
|}<br />
<br />
===Potential Risks===<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Century Gothic"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Type of Risk<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Description<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Risk Level<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #00cdcd;color:#ecf0f1; width:100px; border:1px solid #999" | Mitigation<br />
<br />
|-<br />
| style="text-align:center" | Manpower Risk <br />
| style="text-align:center" | Pre-acceptance: 2 out of 4 members are on Leave of Absence for internships, thus meeting times are limited to evenings and weekends. 4 member FYP team as such manpower is limited as compared to teams with 6 members. <br />
| style="text-align:center" | C<br />
| style="text-align:center" | Team have been meeting for 2 weeknights/week and if required, weekend afternoons. Team to commit to at least 12hours/week for FYP. Ensure that project scope is reasonable within limits and tasks are also covered by another member to eliminate dependencies. Daily updates on work completed and remaining. <br />
<br />
|-<br />
| style="text-align:center" | Communication Risk<br />
| style="text-align:center" | Sponsor is juggling multiple roles and will be travelling for business trips and is participating in many projects and events. As such, Sponsor may not be available when needed and may cause a delay and be a bottleneck in communication and feedback from end-users. This will impact project development as well as UATs. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Slack communication tool setup between Starteur and Starteur for Educators development team. So that team has alternative contact if Sponsor is not available. UATs to be scheduled in advance and team will contact end-users themselves and arrange for UAT while keeping Sponsor in the loop. <br />
<br />
|-<br />
| style="text-align:center" | Scope Risk<br />
| style="text-align:center" | Sponsor may have difficulties pointing out what he wants due to this being a new project for him and for his company’s team. As such, sponsor may add possible functions according to his own reviews and needs. Scope creep will affect development schedule. <br />
| style="text-align:center" | B<br />
| style="text-align:center" | Transparent communication with sponsor on team’s development progress and capability. All changes to go through change management before making any decision. Expectations of client to be managed through meetings. <br />
<br />
|}<br />
==Technical Complexity==<br />
===Architecture Diagram===<br />
[[Image:Midterm archi.jpg|900px|center]]<br><br />
[[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams|View our architecture diagram for deployment to staging server here!]]<br />
<br />
===Technical Complexity 1: Assigning Code Usage ===<br />
<br />
<font size=2><b><u>Issue</u></b></font><br />
[[Image:Midterm complexity1(starteur).jpg|700px|center]]<br><br />
* A Starteur user (student) can have different states. <br />
* An Educator can potentially have users of mixed states <br />
* Every time an educator takes an action, e.g. Assign access codes, the logic has to take into account all possible relevant states the user might be at. <br />
* Compounded when your actions involve more than 1 such modal with multiple states.<br />
<br> <br />
<font size=2><b><u>Solution</u></b></font><br />
Important to figure out all the possible combinations and relevant actions to take. <br />
<br />
<font size=2><b><u>Implementation</u></b></font><br />
<br />
===Technical Complexity 2: Generating PDF===<br />
<font size=2><b><u>Issue</u></b></font><br />
* Multiple pages with variable content length, headers and footers.<br />
* A need to have a template to have a consistent look for all reports and to control how each page is rendered. <br />
* Displaying of dynamic content and setting a template for content. <br />
<br />
<font size=2><b><u>Solution</u></b></font><br />
<br>[[Image:Tech complex1.png|600px|center]]<br><br />
* Use of Prawn. Prawn is a full-featured gem with a nice DSL for creating PDF documents and integrating Prawn with Rails is straightforward. <br />
* Highly flexible PDF document generation system that allows us to specify where we want to display our content.<br />
<br />
<br />
<font size=2><b><u>Outcomes</u></b></font><br> <br />
Using a library like Prawn, content styling and positioning have to be done on our own using Prawn’s DSL. We would more control over how things are displayed and where pages break.<br><br />
Prawn supports image embedding and table drawing which will prove beneficial for the future Group Report Module should be there be a need for images and tables. <br />
<br/><br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Quality of Product</font></div>=<br />
<br />
==Deliverables==<br />
<br />
{| class="wikitable" border="1"<br />
|- style="background:#35404f; color:white" <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Stage <br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Specification<br />
! style="text-align: center; bold;background: #00cdcd;color:white; width:20px; border:1px solid #999" | Module<br />
|-<br />
|rowspan="7"| Project Management<br />
<br />
|| Minutes<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes| Meeting Minutes]]<br />
|- <br />
|| Project Schedule<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule|Project Schedule]]<br />
|- <br />
|| Project Scope<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Scope|Project Scope]]<br />
|- <br />
|rowspan="2"| Metrics<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Schedule Metrics|Schedule Metrics]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Bug Metrics|Bug Metrics]]<br />
|- <br />
|| Risks & Mitigations<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Risk Management|Risk Management]]<br />
|- <br />
|| Client & End-user Change Requests<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Change Management|Change Management]]<br />
|- <br />
<br />
|-<br />
|rowspan="3"| Analysis<br />
|rowspan="2"| Diagrams<br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Use_Cases Use-case Diagram]<br />
|- <br />
|| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_Starteur_Project_Technical_Diagrams ER Diagram]<br />
|- <br />
|| Market Research<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Market Research|Market Research]]<br />
|- <br />
<br />
|-<br />
|rowspan="1"| Design<br />
||Lo-Fidelity Prototype<br />
|| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents|Lo-Fidelity Prototype]]<br />
|- <br />
<br />
|rowspan="2"| Testing<br />
|rowspan="2"|User Test Plan and Results & Analysis<br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 1|UAT 1 ]]<br />
|- <br />
|| [[IS480 Team wiki: 2015T2 Starteur User Testing 2|UAT 2]]<br />
|- <br />
|}<br />
<br />
==Deployment==<br />
[http://starteur-ed.herokuapp.com/educators/sign-in Click here to explore our deployed site! ]<br />
<br />
==Testing==<br />
<br />
===User Testing 1===<br />
<b>Locations</b>: CHIJ St Nicholas Girls' School, SMU, Raffles Institution <br/><br />
<b>Date & Time</b>: 1st week of December 2015<br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 1|Click here to view our User Testing 1!]]<br />
<br />
===User Testing 2===<br />
<b>Location</b>: SMU <br/><br />
<b>Date & Time</b>: 13 February 2016 <br/><br />
<b>No. of Participants</b>: 4 <br/><br />
<b>Objectives</b>: <br/><br />
1. Verify that functionalities built are in line with user requirements<br/><br />
2. Determine if the user interface is intuitive<br/><br />
3. Gather feedback on current functionalities<br/><br />
4. Identify usability problems<br/><br />
<br />
[[IS480 Team wiki: 2015T2 Starteur User Testing 2|Click here to view our User Testing 2!!]]<br />
<br />
=<div style="background: #00cdcd; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em"><font color=#ffffff>Reflections</font></div>=<br />
<br />
==Team's Reflections==<br />
<font size=3><b>Team Reflection</b></font><br />
#Deeper insights of the behind-the-scenes in a learning management web application and the difficulties teachers and educators face when getting students to complete their assignments on time. <br />
#Gained real-life experience of a commercial project from scratch <br />
<br />
===What have we done well so far?===<br />
* Focused a lot on providing convenience and ease of use to our end-users when we design and build the app<br />
* As a result, both our client and the actual users like the product and gave us positive feedback<br />
* Kept close and constant contact with our end-users. Resulting in most of them agreeing to be participants for our User Testings or recommending other educators to be a part of our User Testings. <br />
<br />
===What can be improved?===<br />
* Be more assertive when seeking understanding from Starteur developers when requesting for inputs and integration efforts. <br />
* Do more in-depth research for front-end design and seek feedback from all stakeholders before moving ahead with changes. <br />
<br />
===How will we do better?===<br />
* Managing our schedule and Starteur's development schedule closely while constantly reminding everyone of the tasks at hand and ahead. <br />
* Development rules with Starteur's developer and strict enforcements. <br />
* 1 month before our final presentation, we will halt all development from Starteur's side so that we are given ample time to deal with their changes and to prevent any last minute changes on their end. <br />
* For any design implementations that we are unsure of, must come up with a few design and seek approval and feedback from relevant stakeholders before moving ahead.<br />
<br />
==Individual Reflections==<br />
<br><br />
[[Image:Midterm reflections (starteur).jpg|center|700px]]</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=IS480_Team_wiki:_2015T2_Starteur_User_Testing_3&diff=253917IS480 Team wiki: 2015T2 Starteur User Testing 32016-04-05T08:52:24Z<p>Choryi.poon.2012: </p>
<hr />
<div><!--Logo--><br />
[[Image:starteur.jpg|center|300px]]<br />
<br />
<!--MAIN HEADER--><br />
{|style="background-color:#FFFFFF; color:#FFFFFF; padding: 10 0 10 0;" width="100%" cellspacing="0" cellpadding="0" valign="top" border="0" |<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur |<font color="#33494C" size=3 face = 'Century Gothic'><b>HOME</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur About Us |<font color="#33494C" size=3 face = 'Century Gothic'><b>ABOUT US</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Overview |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT OVERVIEW</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#eafbf7; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Project Management |<font color="#33494C" size=3 face = 'Century Gothic'><b>PROJECT MANAGEMENT</b></font>]]<br />
<br />
| style="padding:0.1em; font-size:100%; background-color:#d8d8d8; text-align:center; color:#FFFFFF" width="10%" | <br />
[[IS480 Team wiki: 2015T2 Starteur Documentation |<font color="#33494C" size=3 face = 'Century Gothic'><b>DOCUMENTATION</b></font>]]<br />
|} <br />
<!--MAIN HEADER END--><br />
<br />
<!--SUB HEADER START--><br />
{| style="background-color:#ffffff; margin: 3px auto 0 auto" width="90%"<br />
|- <br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Use Cases | <span style="color:#3d3d3d">Use Cases</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Technical Diagrams | <span style="color:#3d3d3d">Technical Diagrams</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Design Documents | <span style="color:#3d3d3d">Design Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Meeting Minutes | <span style="color:#3d3d3d">Meeting Minutes</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #2e2e2e" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project User Testings | <span style="color:#3d3d3d">User Testings</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
<br />
! style="font-size:15px; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="150px"| [[IS480 Team wiki: 2015T2 Starteur Project Project Documents | <span style="color:#3d3d3d">Project Documents</span>]]<br />
! style="font-size:15px; font-face: Century Gothic; text-align: center; border-top:solid #ffffff; border-bottom:solid #ffffff" width="20px"|<br />
|}<br />
<!--SUB HEADER END--><br />
<br />
<!--MAIN CONTENT--><br />
==<div style="background: #354b60; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#ffffff>Venue</font></div>==<br />
* Location: CHIJ St Nicholas Girls' School, Reactor ARC <br />
* Date: 14 - 23 Mar 2016 <br />
* Time: - <br />
<br />
==<div style="background: #354b60; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#ffffff>Objectives</font></div>==<br />
* Verify that functionalities built are in line with user requirements<br />
* Determine if the user interface is intuitive<br />
* Gather feedback on current functionalities<br />
* Identify usability problems<br />
<br />
==<div style="background: #354b60; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#ffffff>Participants</font></div>==<br />
* Number of educators: 4<br />
* Number of students: 80<br />
* Roles of participants: Head-of-Department, Academic Director, Personal Development Trainer<br />
<br />
<br />
<center><br />
</center><br />
<br />
==<div style="background: #354b60; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#ffffff>Tasks</font></div>==<br />
* Each of the users was given a list of tasks to complete. Click [[Media:(UAT3)Task Instructions.docx| here]] to download tasklist.<br />
* Before and after completing all the tasks, users are given a survey questionnaire to complete.<br />
<br />
==<div style="background: #354b60; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.08em;font-size:20px"><font color=#ffffff>Survey Results</font></div>==<br />
===Collated Task Score===<br />
Educators were asked to rate the ease of completing the task ( 1 - Very Easy, 5 - Very Difficult) <br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Roboto Lt"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:30px; border:1px solid #999" | Task<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 1<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 2<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 3<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 4<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Overall Mean<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:30px; border:1px solid #999" | Remark<br />
|-<br />
| style="text-align:center" | Task 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.5<br />
| style="text-align:center" | Nil<br />
<br />
|-<br />
| style="text-align:center" | Task 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.25<br />
| style="text-align:center" | Nil<br />
<br />
|-<br />
| style="text-align:center" | Task 3<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.25<br />
| style="text-align:center" | Nil<br />
<br />
|-<br />
| style="text-align:center" | Task 4<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2.5<br />
| style="text-align:center" | Nil<br />
<br />
|-<br />
| style="text-align:center" | Task 5<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | Nil<br />
|-<br />
| style="text-align:center" | Task 6<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1.5<br />
| style="text-align:center" | Nil<br />
|-<br />
| style="text-align:center" | Task 7<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | Nil<br />
|-<br />
| style="text-align:center" | Task 8<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.75<br />
| style="text-align:center" | Nil<br />
|-<br />
| style="text-align:center" | Task 9<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.25<br />
| style="text-align:center" | <br />
|-<br />
| style="text-align:center" | Task 10<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.5<br />
| style="text-align:center" | <br />
|-<br />
| style="text-align:center" | Task 11<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | <br />
|-<br />
| style="text-align:center" | Task 12<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 2.25<br />
| style="text-align:center" | h<br />
|-<br />
| style="text-align:center" | Task 13<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | 1.75<br />
| style="text-align:center" | <br />
|-<br />
</div><br />
<br />
[[File:UAT3 results.png|1000px|center|link=]]<br />
<br />
<br />
<div style="text-align: left; width:99%; margin-left:auto; margin-right:auto;"><br />
{| class="wikitable" width="100%" font-family="Roboto Lt"<br />
|-<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:30px; border:1px solid #999" | #<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:40px; border:1px solid #999" | Issue<br />
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:50px; border:1px solid #999" | Collated feedback<br />
<br />
|-<br />
| style="text-align:center" | 1<br />
| style="text-align:center" | Text size<br />
| style="text-align:center" | Layout of the pages is simple and easy to see, <br> However, the text is quite faint and the font size can be bigger. <br> Bigger font size<br> Current layout is nice but text can be bigger.<br> Bigger font size. <br />
<br />
|-<br />
| style="text-align:center" | 2<br />
| style="text-align:center" | Phrasing<br />
| style="text-align:center" | "Batch" is a little too definitive as teachers may only request a certain group of students to take the test. Consider changing to something less definitive and more generic. <br />
<br />
|-<br />
| style="text-align:center" | 3<br />
| style="text-align:center" | Success Messages<br />
| style="text-align:center" | Application is simple to use and straightforward but I would like to know where I am at in terms of the steps in using the application. <br> I think it would be good if I can know whether some stuff I am doing is correct or not. <br />
<br />
|-<br />
| style="text-align:center" | 4<br />
| style="text-align:center" | Lack of information hierarchy <br />
| style="text-align:center" | Everything is there on the page but I don't know where to look or what to focus on for certain stuff<br>I like the layout cause it is not confusing but it would be good if things are presented in a way that I can see certain important information. <br />
<br />
|-<br />
| style="text-align:center" | 5<br />
| style="text-align:center" | Validation<br />
| style="text-align:center" | Do you have certain password restrictions? <br> Any password limits and email verification? <br />
<br />
|-<br />
| style="text-align:center" | 6<br />
| style="text-align:center" | Any thing you will like to see in the application?<br />
| style="text-align:center" | A report for my cohort as well? It would be very insightful<br> It will be useful if I send the reminder myself. Because then I know how many days have passed since the reminder has been sent and send it again if necessary. I can control the frequency.<br> Allow me to send an email straight from this application. <br><br />
Include a report for a cohort so that I can submit it for analysis with the other Year Heads. <br><br />
|}<br />
</div><br />
<br />
<br />
===User Study Summary===<br />
* Overall, users find that the interface of the application has improved as compared to the previous version in UAT 1. It was a lot more intuitive. <br />
* Users are satisfied with most functions and find that functions were easy to use and suit their needs. <br />
* Users were satisfied with the report but feels that it needs more details/explanations. <br />
* Feedback from users were highly useful for report functions and fine-tuning functions.<br />
<br />
===User Study Takeaways===<br />
* Important to keep solutions simple for users, be it a complex function or a relatively simple one. <br />
* With users' feedback, we managed to zero in on functions that needs more work. <br />
* The user study allowed us to identify areas for improvement and to evaluate how our primary & secondary functions can be further improved. Comments on individual report will be directed back to Starteur's development team and comments on batch report will be used to improve the usability of the batch report to an educator.</div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:UAT3_results.png&diff=253916File:UAT3 results.png2016-04-05T08:48:52Z<p>Choryi.poon.2012: Choryi.poon.2012 uploaded a new version of &quot;File:UAT3 results.png&quot;</p>
<hr />
<div></div>Choryi.poon.2012https://wiki.smu.edu.sg/is480/index.php?title=File:UAT3_results.png&diff=253915File:UAT3 results.png2016-04-05T08:46:53Z<p>Choryi.poon.2012: </p>
<hr />
<div></div>Choryi.poon.2012