HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 CLEBS Mid-Term"

From IS480
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 37: Line 37:
 
=Project Progress Summary=
 
=Project Progress Summary=
  
Midterm Slides:
+
Midterm Slides: [[Media:CLEBSIS480MIDTERMS.pptx|Midterm Presentation]]
<LINK>
 
  
 
Deployed Site Link:
 
Deployed Site Link:
http://ybcosg.herokuapp.com/
+
[[File:Ybco-web.png|frameless|center|800px|]]
  
 
<!--For proposal, please see Requirements at the Project Deliverables. This will help us understand your scope. Note wiki policy [[Help:Contents|here]].
 
<!--For proposal, please see Requirements at the Project Deliverables. This will help us understand your scope. Note wiki policy [[Help:Contents|here]].
Line 212: Line 211:
 
|}
 
|}
  
==Technical Complexity==
+
=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.-->
+
<!-- Add images or scenarios -->
  
<!-- Add images or scenarios -->
+
[[File:Clebscomplexity11.png|frameless|center|600px|]]
 +
[[File:Clebscomplexity12.png|frameless|center|600px|]] <br/>
 +
[[File:Clebscomplexity21.png|frameless|center|600px|]]
 +
<div style="text-align: center;"><b>ON WEB:</b></div><br/>
 +
[[File:Clebscomplexity221.png|frameless|center|600px|]]
 +
[[File:Clebscomplexity222.png|frameless|center|600px|]]
 +
[[File:Clebscomplexity223.png|frameless|center|600px|]]
 +
<br/>
 +
<div style="text-align: center;"><b>ON MOBILE:</b></div><br/>
 +
[[File:Clebscomplexity22.png|frameless|center|600px|]] <br/>
 +
[[File:Clebscomplexity3.png|frameless|center|600px|]]
  
=System Architecture Diagram=
+
==System Architecture Diagram==
  
 
<!-- 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.-->
 
<!-- 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.-->
Line 285: Line 294:
 
|}
 
|}
  
 
+
<!--
 
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
 
Not all parts of the deliverables are necessary but the evidence should be convincing of the progress. Try to include design deliverables that shows the quality of your project.
 +
-->
  
 
==Deployment Link==
 
==Deployment Link==
Line 295: Line 305:
 
==Testing==
 
==Testing==
  
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
+
As of 27th September 2016, we have completed 2 User Tests with a group of users (including some from our sponsors). These tests were to get a good indication that we are progressing in the right direction with regards to our web application and get users' feedback on the User Interface, the overall User Experience as well as the time taken to complete different functions to know where we may fall short.
 +
 
 +
<div style="background:#00beff; padding: 10px; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Century Gothic" color="#F7F7FF">
 +
User Test 1 Test Plan</font></div>
 +
<div style="background:#ffffff; padding: 10px">
 +
<b>Date:</b> 27 July 2016, Wednesday<br/>
 +
<b>Venue:</b> At participants' convenience<br/>
 +
<b>Duration:</b> 10 – 20 minutes per participant<br/>
 +
<b>Number of Participants:</b> 12<br/>
 +
<b>Age range:</b> 19 – 26<br/>
 +
<br/>
 +
<hr>
 +
<br/>
 +
 
 +
<b>Objectives:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Identify functionalities and usability issues</li>
 +
<li>&nbsp;&nbsp;Determine is the user interface is intuitive</li>
 +
<li>&nbsp;&nbsp;Discover ways to improve features and functions of the website based on the results of User Testing #1</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Scope:</b><br/>
 +
The scope for User Testing 1 are the modules from sprints 1 - 3<br/>
 +
<ol>
 +
<li>&nbsp;&nbsp;Registration Module</li>
 +
<ul>
 +
  ''<li>Log In</li>''
 +
  ''<li>Log Out</li>''
 +
  ''<li>Registration</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Profile Management Module</li>
 +
<ul>
 +
  ''<li>Update Profile (including upload profile picture)</li>''
 +
  ''<li><strike>Reset Password</strike> (Shifted to sprint 5)</li>''
 +
  ''<li>Change password</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Proposal Module</li>
 +
<ul>
 +
  ''<li>Submit Project Proposal</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;User Management Module</li>
 +
<ul>
 +
  ''<li>View All Users</li>''
 +
  ''<li>Ban Users</li>''
 +
  ''<li>Un-ban Users</li>''
 +
</ul>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<div style="background:#00beff; padding: 10px; line-height: 1em; text-indent: 10px; border-left: #0273b5 solid 32px; font-size: 18px"><font face="Century Gothic" color="#F7F7FF">
 +
User Test 2 Test Plan</font></div>
 +
<div style="background:#ffffff; padding: 10px">
 +
<b>Date:</b> 21 September 2016, Wednesday, 7 PM Onwards<br/>
 +
<b>Venue:</b> SIS GSR 2-3 <br/>
 +
<b>Duration:</b> 10 – 20 minutes per participant<br/>
 +
<b>Number of Participants:</b> 20<br/>
 +
<b>Age range:</b> 19 – 24<br/>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Objectives:</b>
 +
<ol>
 +
<li>&nbsp;&nbsp;Identify functionalities and usability issues</li>
 +
<li>&nbsp;&nbsp;Determine is the user interface is intuitive</li>
 +
<li>&nbsp;&nbsp;Discover ways to improve features and functions of the website based on the results of User Test 2</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
 +
<b>Scope:</b><br/>
 +
The scope for User Testing 2 are the modules from sprints 3 - 6<br/>
 +
<ol>
 +
<li>&nbsp;&nbsp;Module</li>
 +
<ul>
 +
  ''<li>Log In</li>''
 +
  ''<li>Log Out</li>''
 +
  ''<li>Registration</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Proposal Module</li>
 +
<ul>
 +
  ''<li>Submit Project Proposal</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Review Module</li>
 +
<ul>
 +
  ''<li>Accept/Reject project proposals</li>''
 +
</ul>
 +
<li>&nbsp;&nbsp;Project Creation Module (Edit)</li>
 +
<li>&nbsp;&nbsp;Reset Password</li>
 +
</ol>
 +
<br/>
 +
<hr>
 +
<br/>
  
 
=Reflection=
 
=Reflection=

Latest revision as of 23:06, 27 September 2016

ClebsLogo.png
ClebsHome.png HOME

ClebsAboutUS.png THE TEAM

ClebsProjectOverview.png PROJECT OVERVIEW

ClebsProjectManagement.png PROJECT MANAGEMENT

ClebsDocumentation.png DOCUMENTATION

M A I N

M I D - T E R M

F I N A L


Project Progress Summary

Midterm Slides: Midterm Presentation

Deployed Site Link:

Ybco-web.png


Project Highlights

What was achieved from Acceptance?

  • Completion of our most major iteration
    • Project Creation Module (Iteration 5) was completed and users, after having their project proposal accepted, are able to create their projects
  • En-route to achieving X-Factor:
    • 20 Users Sign Up
    • 20 Project Proposal Created


What unexpected events occurred?

  • Changes to Project Scope and Timeline
    • Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back
    • Replaced Payment Gateway Module with Admin Dashboard Module
  • Delay in Iteration 5
    • Team had multiple other commitments to juggle
    • Team were unfamiliar with the implementation of JQuery and JavaScript, and as a result, constantly
    • Sponsor added changes they would like to see in the Project Creation page

Project Management

Project Status

This was our initial planned Project Scope, before the changes:
Clebs-scope.png


And this is our actual Project Scope (With Changes):
CLEBS-scope-2-updated.png


This chart below shows the changes to our Project Scope
Date Scope Type Module Name Original Details Changes Final Details
14 Aug 2016 Primary Scope Project Creation Module Create, View, Edit Project Greater Definition of the Project Creation Module i.e. added more description for the scope
14 Aug 2016 Good-To-Have Scope UI/UX Improvement Module Was not present before UI/UX Improvement Module was added to the Good-To-Have Feature "Good to have user interface and user experience improvements that can be made"
19 Aug 2016 Primary Scope Admin Dashboard Module Was not present before Admin Dashboard Module was added to the Secondary Feature Show the tasks required for admin dashboard module, mainly scaffolding and create layouts

Project Schedule (Plan Vs Actual)

This was our initial Planned Schedule:
CLEBSTimeline-oldversion.png


This is our Actual Schedule:
CLEBSTimeline-2-changes.png


Listed below is our Schedule Progress Chart to show the tasks that are completed or incomplete:
CLEBSProgress1.png
CLEBSProgress2.png

Project Metrics

Listed below are our collated and updated Schedule Metrics and Bug Metrics.
CLEBSSchMetricsGraph.png


CLEBSBugMetricsGraph.png


Change Management

Change Request Reason For Change Team's Decision
Mobile-friendly (Responsive) UI Most users now surf the web using their smart phones or tablets, and thus, the sponsors feel that we should make the YBCO platform responsive and mobile-friendly to cater to these group of people Approved (to be completed in the last iteration)
Move Payment Gateway Module Back Sponsor experienced difficulty in setting up a BrainTree account and asked to push the Payment Gateway Module back to give them time to settle the administrative issues Approved
Make Project Creation Module Editable In-page Sponsor asked for us to implement user-friendly and in-page editing for project creators (so that they won't be constantly redirected to other pages) when creating a project. This enhances the overall user experience for them Approved
Create intuitive "TypeForm-like" Forms in Project Proposal Sponsor requested for us to consider enhancing the Project Proposal form, similar to that of TypeForm. Rejected (Too complex)

Project Risks

Number Risk & Description Impact Mitigation Plan
1 Taking on Ruby on Rails Development without prior knowledge High Team has to constantly work together and ask questions if there are any issues. In the event that a member(s) is/are unsure of how to code out a function, he or she should source for help, not just among the team, but other alternative options as well
2 Choice of servers (GoDaddy, AWS and Heroku) that are unfamiliar and complex High Team has to read online documentations as much as possible and look out for related online forums for help. Team should also look into asking YBCO CTO Uttam for help as he is familiar with such technologies
3 Additional project scope from the sponsors Medium As of now, most of the plans have been finalised. In the event that there are changes to the scope, Project Manager should evaluate and decide as a team whether to take up the change request and inform the sponsors of the team's decision. Team has to manage the expectations of the sponsors and ensure that we can deliver what we aim to

Technical Complexity

Clebscomplexity11.png
Clebscomplexity12.png


Clebscomplexity21.png
ON WEB:


Clebscomplexity221.png
Clebscomplexity222.png
Clebscomplexity223.png


ON MOBILE:


Clebscomplexity22.png


Clebscomplexity3.png

System Architecture Diagram

Clebsarchitecture.png

Intermediate Deliverables

Stage Specification Module
Project Management Minutes Meeting Minutes
Project Schedule Project Schedule
Project Scope Project Scope
Metrics Schedule & Bug Metric
Risk Management
Change Management Change Management
X-Factor X-Factor
Documentation & Design Use Case Use Case Diagram
Designs ER Diagram
LD Diagram
User Story
Tools & Architecture Tools Used
Technologies Used
Architecture Diagram Architecture Diagram
Testing Iteration Tests Iteration Test Results
User Tests User Test 1
User Test 2


Deployment Link

Ybco-web.png

Testing

As of 27th September 2016, we have completed 2 User Tests with a group of users (including some from our sponsors). These tests were to get a good indication that we are progressing in the right direction with regards to our web application and get users' feedback on the User Interface, the overall User Experience as well as the time taken to complete different functions to know where we may fall short.

User Test 1 Test Plan

Date: 27 July 2016, Wednesday
Venue: At participants' convenience
Duration: 10 – 20 minutes per participant
Number of Participants: 12
Age range: 19 – 26



Objectives:

  1.   Identify functionalities and usability issues
  2.   Determine is the user interface is intuitive
  3.   Discover ways to improve features and functions of the website based on the results of User Testing #1




Scope:
The scope for User Testing 1 are the modules from sprints 1 - 3

  1.   Registration Module
    • Log In
    • Log Out
    • Registration
  2.   Profile Management Module
    • Update Profile (including upload profile picture)
    • Reset Password (Shifted to sprint 5)
    • Change password
  3.   Project Proposal Module
    • Submit Project Proposal
  4.   User Management Module
    • View All Users
    • Ban Users
    • Un-ban Users




User Test 2 Test Plan

Date: 21 September 2016, Wednesday, 7 PM Onwards
Venue: SIS GSR 2-3
Duration: 10 – 20 minutes per participant
Number of Participants: 20
Age range: 19 – 24



Objectives:

  1.   Identify functionalities and usability issues
  2.   Determine is the user interface is intuitive
  3.   Discover ways to improve features and functions of the website based on the results of User Test 2




Scope:
The scope for User Testing 2 are the modules from sprints 3 - 6

  1.   Module
    • Log In
    • Log Out
    • Registration
  2.   Project Proposal Module
    • Submit Project Proposal
  3.   Project Review Module
    • Accept/Reject project proposals
  4.   Project Creation Module (Edit)
  5.   Reset Password




Reflection

Team Reflection:

Clebsreflection1.png
Clebsreflection2.png
Clebsreflection3.png