HeaderSIS.jpg

Difference between revisions of "GenSHYFT Mid Term Wiki"

From IS480
Jump to navigation Jump to search
Line 36: Line 36:
  
 
===Project Highlights:===
 
===Project Highlights:===
* <b>Change in Requirements</b>
+
====<b>Change in Requirements</b>====
 
Actual Scope<br>
 
Actual Scope<br>
 
[[Image:GENSHYFT_IS480_SPCircle6.png|480px]]  
 
[[Image:GENSHYFT_IS480_SPCircle6.png|480px]]  

Revision as of 21:31, 17 February 2014

GENShYFT IS480 1314 Logo.jpg


Home   Project Overview   Project Management   Documentation   The Team



Project Progress Summary

Place your Final slides link and deployed site link here

For proposal, please see Requrements at the Project Deliverables. This will help us understand your scope. Note wiki policy here.

This page should NOT be too long. It should link to other pages in the IS480 team wiki. Do not repeat the proposal, midterm or other wiki information here. Highlight changes since midterm.

Describe the project progress briefly here. Is the project completed? Link to the final presentation slides and videos.

Project Highlights:

Change in Requirements

Actual Scope
GENSHYFT IS480 SPCircle6.png
Acceptance Scope
Genshyft acceptance scope.jpg

Below is a compiled list of requirement changes:

Feature Affected Previously Currently Change Management Action
Registration & Tracking Map that allows user to see the number of players registered with respect to each school. Added to scope, event ranking for event, display the people who have done mastery based coaching and purpose driven, badges, Events map, badges and levels completed. This requirement change will be taken into consideration after mid-terms as this requirement is recent (9/2) and team has yet to finish up the minimum requirements
Mastery-based Coaching Users would be able to resolve questions that they solved below their average performance in the past User should redo any question that they have attempted before on the Practice page This change was implemented as it was still early in the development process.
Mastery-based Coaching

Client will provide audio files and text captions for the Coaches

Client requested team to do up the audio files and text captions for the Coaches either personally or engage in professional services.

Team decided to do the files up personally instead as it would take longer time if it was done by professionals. This change was implemented as client did not have materials ready yet.

Mastery-based Coaching

Pictures of mentors will be images

Pictures of mentors in animated GIF format

This feature was taken into consideration as this was UI fix but requirement change was not of high importance

Mastery-based Coaching

On landing page, player select mentor, language and difficulty. Player will select as such for each Mastery coaching session.

On landing page, player only selects mentor and language. User does not need to select the difficulty.
If user has played a Mastery coaching session before, previously selected mentor and language will be the default mentor and language. Have the option "Continue", "Change Mentor" and "Change Language" for existing users of Mastery coaching.

This feature was taken into consideration as team was in the midst of developing this feature and it was of utmost priority since client wanted to show it to RP and IDA

Mastery-based Coaching

This option did not exist when signing off prototype View Paper Prototype

Client wants an admin page for Mastery-based coaching

This feature was not taken into consideration as team tried to develop it and realise feature is too complex to implement.

Mastery-based Coaching

When user starts the Mastery coaching session, user will be starting a new session

For each question,a new Mastery coaching session is launched.

This requirement change will be taken into consideration after mid-terms as this requirement is recent (9/2) and team has yet to finish up the minimum requirements

Purpose Driven Development UI discussed as such in prototype View Paper Prototype

UI changed after prototyping, client changed position of video and feedback. The buttons for the options to answer the feedback has been changed from slider to radio button and as of recent (9/2) normal button.

This change was implemented as it was mostly a UI issue.
Purpose Driven Development

This option did not exist when signing off prototype

Client wants a video gallery below (on the page that the user is viewing the video). It would indicate which videos are locked and unlocked. This translated into a change in the data structure.

This change is implemented because team assessed the requirement change and realised it would make sense for the video gallery to appear so that player knows the videos he has unlocked so far.

Purpose Driven Development

No Admin page was discussed during the paper prototype sign off

Client wants an Admin page where he can manage the videos to upload on the Purpose page. He wants to be able to copy and paste the link, description of the video, survey question for each video and thumbnail image of the video.

This feature was taken into consideration as team tried to develop it and realised feature is not too complex to implement

Purpose Driven Development

Client wanted to have a landing page where user can select unlocked to video to watch.

Client does not want a landing page. He wants an indication on the video gallery which was the last watched video. This would result in a change in data structure

This requirement change will be taken into consideration after mid-terms as this requirement is recent (9/2) and team has yet to finish up the minimum requirements

Group-based Tournament

Team could use client's existing data structure for Tournament.

Client wants team to create a new heat so that tournament game information is not attached to the rounds but to the heat instead.

Taken into consideration. Did not affect team's development progress.

Group-based Tournament

Team could use client's existing data structure for Tournament.

Client wants team to create a new heat so that tournament game information is not attached to the rounds but to the heat instead.

Taken into consideration. Did not affect team's development progress to a large extent.

Group-based Tournament

Tournament feature (existing) used to make calls to different APIs

Tournament feature now called to one API which the team created.

Taken into consideration. This did not affect team's development progress to a large extent and team thought it was wise to have this feature call to one API

Group-based Tournament - Create Tournament

Team discussed with client regarding the UI of this page using paper prototypes

Client wants team to follow the page layout of an older version of SingPath

Team first attempted Client's suggestion and realised it was possible to implement this change as it focused more on UI

Group-based Tournament - Live Ranking

'Country' field on the live ranking page

Remove 'country' field and add 'last solved time'

This requirement change will be taken into consideration after mid-terms as this requirement is recent (9/2) and team has yet to finish up the minimum requirements

Events Registration SingPath users would be able to request for an event by SingPath, Sponsorship Collaboration or Donate to SingPath. (Initially secondary feature)

Client wants Events to be where users would be able to sign up for a tournament.

This affected manpower allocation to a large extent.
Team reviewed requirement change and realised it is a vital feature if users need platform to sign up for tournament.
Allocated team member who was assisting with developing back-end APIs to develop this feature.

* This feature was added right before acceptance presentation - not included in the acceptance proposal
* Secondary feature previously - now primary feature so students can sign up for upcoming tournaments on 21st & 29th March 2014

Events Registration

Platform for participants to join and database will take note of who has signed up.

Include a table that shows the number of students registered, school they are from, who is coming for the event, rank them according to the problems solved,back button to return to Events Registration page, Top 50 with a cutoff line at 40, Facebook share button, highlight current player, always put the current player in the bottom row and if current player is not in top 50, don't show their rank. They should be able to see how many problems they are away from moving ahead of number 50.

This requirement change was taken into consideration as team was in the amidst of coding the feature.



  • Technical Challenges

Project Challenges:

Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.

Project Achievements:

Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.

Project Management

Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.

Project Schedule (Plan Vs Actual):

Actual Timeline:

Genshyft is480 Time line Summary7.1.PNG

Acceptance Timeline:

Genshyft Acceptance timline.jpg
Iterations Planned Actual Comments
3 Purpose Driven - First Half 7th Nov - 11th Nov Gathering New Requirements 5th Dec - 12th Dec
  • Team discussed with clients new project scope from acceptance.
Mastery Coaching - First Half 7th Nov - 11th Nov Creation of all paper prototypes 5th Dec - 12th Dec Client sign off prototypes
  • Team delay iteration 3 as the team was struggling to code during Near-Exam time.Therefore, Iteration 3 starts After Exams ended.
4 Purpose Driven - Second Half 22nd Dec Purpose Driven 31st Dec
  • Assigned to Project Mananager : Yousof
  • Both Member originally assigned were away.(Notification only after acceptance).
  • Function was client top 3 priority.
Mastery Coaching- Second Half 22nd Dec Mastery Based Coaching 31st Dec
  • Assigned to Business Analyst: Shanaaz
  • Both Member originally assigned were away.(Notification only after acceptance).
  • Function was client top 3 priority.
Group Based Tournament 31st Dec
  • Assigned to Co - Lead Developer: Glen
  • Both Member originally assigned were away.(Notification only after acceptance).
  • Function was client top 3 priority.
  • Fariq , Wahchun and Eng Sen were away for December.
  • Each member had to adapt do 1 function each in parallel in order to meet client's priority.
  • Project Manager and Business Analyst had to code otherwise, team is only left with 1 developer,
5 Co-Organized event
Hour of Code
23 Dec Purpose Driven 15 Jan
  • Yousof was coding both Purpose Driven and Mastery Based Coaching.
  • Client made changes to UI on the features different from paper prototype.
Recruit Participants for Singpath tournaments 23 Dec Mastery Based Coaching 15 Jan
  • Yousof was reassigned to this as Shanaaz was struggling with Angular.
  • She is to take assist more on her Secondary role as Co-PM.
  • Client made changes to UI
  • Client changed on the requirement of playing Mastery Base Coaching. User must complete a question before to master that question.
Group based tournament. 15 Jan
  • Eng Sen was assigned 3rd week of December to assist, - requires some time to learn.
  • Competition was was organized start of February is now pushed to 15 Feb - Giving the Team additional time.
  • Glen believed function is going well, hence only Eng sen was assigned to assist
  • Client wanted a new Json data structure for tournament instead of re-using client's existing data structure model.
Easy Web Prototyping. 15 Jan
  • Fariq and Wah Chun joined on the 29th of Decembers.
  • Both of them were to use this function to explore Angular as much as possible.
  • Client changed Collaborative Mode to Sharing of Codes Mode.
  • Team has several changes in scope by client during this time. Namely Purpose Driven and Mastery Based Coaching.
  • Tournament group needed to create a brand new Json data structure to support tournament. Development can continue after data structure is complete.Codes needed to be re-adapted to new data structure.
6 Predictive Analytics - ETL 10th Jan Group based tournament - Create Tournament 9th Feb
  • Client changed the UI and logic flow of Create Tournament.
  • Eng Sen required to make changes to the UI
  • As competition is coming, this became top priority.
  • Client later postponed tournament to March which requires team to re-prioritize.
Predictive Analytics - Statistical Application 10 Jan Group based tournament - Join Tournament 9th Feb
  • Glen encountered complication during creation of Join.
  • As competition is coming, this became top priority.
  • Client later postponed tournament to March which requires team to re-prioritize.
Predict User's School 10 Jan Group based tournament - Live Ranking 9th Feb
  • As Tournament was behind, Fariq was removed from Web Development Prototyping and relocated to assist Tournament.
  • As competition is coming, this became top priority.
  • Client later postponed tournament to March which requires team to re-prioritize.
Register for Event 9th Feb
  • As date is nearing, our client has a new requirement. To create an Events page.
  • Client deemed this as high priority as currently, there is no means for people to register.
  • Client requirements were simple, Wah Chun was relocated to this to quickly developed this.
  • Client added an Event-Ranking table requirement to display who will get in or get cut off from a particular event.
  • Client added Facebook Share requirement .
  • Client wanted current user's status to be shown requirement .
  • Client later postponed tournament to March which requires team to re-prioritize.
Mastery Based Coaching 9th Feb
  • Republic polytechnic was interested on this function hence now became Client top priority after change in Tournament Competition date.
  • Client recommended a different Json data structure.
  • Client change scope. Mastery will now load 1 game. Mastery will not load new game. Mastery will determine the type of improvement user can make.
Purpose Driven 9th Feb
  • Republic polytechnic was interested on this function hence now became Client top priority after change in Tournament Competition date.
  • Client recommended a different Json data structure.
  • Client change scope. Client wanted a Video-Gallery at the bottom of the page to allow user to see video progress.
Developer's Documentation 9th Feb
  • Client wanted a technical documentation stating the API calls and explanation of codes.
  • Client wanted this ASAP.
  • Shanaaz, who was BA/Co-PM was assigned to do this documentation.
  • Client made several scope changes such as UI, Data structures and New Features. Almost all feature had a change.
  • Tournament Competition had changed of dates which requires the team to re-prioritize while Client has different priorities along the way.
  • The team decided to put Web Development prototype on hold.
1

Project Metrics:

Click to View Metrics

Technical Complexity:

Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.

Quality of product

Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.

Project Deliverables:

List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.

Stage Specification Modules
Project Management Minutes Sponsor Minutes
Minutes Supervisor Minutes
Minutes Group Minutes
Metrics Bug metrics
Metrics Schedule metrics
Requirements Paper Prototypes [prototype]
Business Requirement Document The doc u did shanaaz
Analysis and Design Use case Use case
State Diagrams State diagrams
Component Diagram Component diagram
Market Survey Survey
Architecture Diagram Architecture diagram Not linked
Testing Test plan Test Plan
User Testing View Resources
Handover Manuals User tutorial, Developer manual, Setup manual
Developers Documentation The API document Cb ask you do.
Code client server
Deployment Diagram instructions Not Linked

Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.

Quality:

Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.

Deployment:

In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.

Testing:

A total of 1 User Acceptance Test has been completed along with a Heuristic Evaluation. For the UAT there was a total of 15 participants from SMU and the average age of the participants is 21.6 years old. The gender distribution of the participants is quite balanced as well. Participants were given either Tester Package A or Tester Package B. One contained detailed instructions while the other contained scenarios for the participants to follow. The participants were tasked to go through the 3 functionalities which we intended to test for UAT 1, namely - Purpose Driven Coding, Mastery Based Coaching and Events & Ranking. They wrote down the outcomes of the tasks assigned and filled in questionnaire form each which sought both qualitative and quantitative data from them such as programming languages currently known and ratings for Singpath in terms of utility and usability.

The survey results were generally positive, with the majority of the feedback focusing on the user interface more than the functions of the application, an indication that our functions developed are working perfectly and that we have to assign some resource to brush up on the usability aspect.

The bug points generated from the UAT was 7, which was quickly reduced to 1 as the developers were efficient in fixing the errors.

For more details - please refer to

Reflection

Compile common lessons and reflection for the team and for each team member. Be brief.

Team Reflection:

Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.

Individual Reflection:

Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.

Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.