HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 The C-Suite Midterm Wiki"

From IS480
Jump to navigation Jump to search
 
(15 intermediate revisions by the same user not shown)
Line 39: Line 39:
  
 
<!--------------------------- Content Starts here ------------------>
 
<!--------------------------- Content Starts here ------------------>
==Midterm Slides==
+
==Midterm documents==
  
*[[Media: | '''Midterm Presentation Slides''']]
+
*[[Media: FYP_Midterm_(The_C-Suite).pdf| '''Midterm Presentation Slides''']]
 +
*[[Media: Schedule_logbook.pdf | '''Schedule Logbook''']]
  
==In A Nutshell==
+
==Demo==
[[File: one.png | 1000px ]]
 
[[File: two.png | 1000px ]]
 
 
 
 
 
<!--
 
==Project Management==
 
 
 
===Planned Schedule===
 
  
[[File: Project_timeline7.png| center | 1100px ]]
+
Demo link @ http://fyp-ccgoh.rhcloud.com/carecorner
 
+
{| class="wikitable" style="background-color:#FFFFFF; width: 500px;" align="center"
<br/>
 
 
 
===Actual Schedule===
 
[[File: Project_timeline8.png| center | 1100px ]]
 
 
 
 
 
===Issues Faced And Reasons for Change in Schedule===
 
<br>
 
<div style="text-align: center;"><font size="4" color=green> ''' Iteration 5 : 8 December 2014 to 23 December 2014'''</font></div>
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width 400px" | Issues
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 400px" | Solution
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 300px" | Mitigation towards schedule
 
 
|-
 
|-
| Previously, we had resource files (File containing end points) which separated the different roles from their business functions (Eg: Faculty's business functions on teams were classified into FacultyTeamResource). <b>this did not conform the the REST API standards</b>, and resulted in repeated codes.
+
! style="color:white; background-color:#8A0808;" width="100pt" | Username
This resulted in many different resource files, and it was difficult to trace code and fix bugs, resulting in delay. This has also frustrated a lot of teammates. <br>
+
! style="color:white; background-color:#8A0808;" width="100pt" | Password
<b>Our team foresaw that maintainability was going to be a problem in the long run. </b>
 
|  It was decided for all business functions to be grouped together under a same resource file, with different roles executing different tasks through the use of If-Else blocks. Eg: Functionalities involving teams would be classifed under TeamResource.
 
| rowspan="2" | <b> This resulted in a delay of 2 days.</b> As we previously had an increase in buffer day from iteration 3, <b>this resulted in a deduction of 2 days from our buffer.</b>
 
 
|-
 
|-
| Our team was still new to the technology of JPA, and we developed our business logics in the resource files. <br> This resulted in repeated codes.
+
|style="text-align: center;"| Admin1
| After researching on the best practices online, we discovered that business logics were best to be encapsulated in the service files, in order to achieve a Service Oriented Architecture. This resulted in refactoring of business logics into the service files.
+
|style="text-align: center;"| Admin1
|}
 
 
 
<br>
 
<br>
 
<div style="text-align: center;"><font size="4" color=green> ''' Iteration 7 : 9 Jan 2015 to 24 Jan 2015'''</font></div>
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width 400px" | Issues
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 400px" | Solution
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 300px" | Mitigation towards schedule
 
 
|-
 
|-
| Although we have finished the main functionalities required according to our sponsor’s requirements, our sponsors suggested many usability improvements which we tried to cater to. As a result, we found ourselves working harder and harder. This is a significant signal of a creep of scope. Moreover, our supervisor Prof. Chris Boesch reminded us that the ultimate aim of the system should be to benefit all stakeholders. <br><br> After much discussion with sponsors during the sponsor test on 16th Jan 2015, Fiona has suggested to the team that it would be advisable for the team to remove functions which are of less priority and without much value add such that more can be achieved by focusing on the core functionalities / functionalities with the most value add.
+
|style="text-align: center;"| Admin2
|  In order to find out whether this would be much of a value add to our main target users (Students), our team has actually conducted a survey and we’ve summarized the results in the surveys page [[IS480 Team wiki: 2015T2 6Sigma User Surveys | HERE]]
+
|style="text-align: center;"| Admin2
| 6Sigma has decided to remove CRUD Comments, iterations from our project scope,
 
|}
 
 
 
 
 
<br>
 
<br>
 
<div style="text-align: center;"><font size="4" color=green> ''' Iteration 8 : 24 Jan 2015 to 7 Feb 2015'''</font></div>
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width 400px" | Issues
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 400px" | Solution
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 300px" | Mitigation towards schedule
 
|-
 
| After a series of user tests (Student and Faculty) conducted on 28 - 30th Jan, our team realized that usability was a huge issue to all of our stakeholders. Most of our users found that our fonts and colors were difficult to read, functionalities were difficult to find as they were not intuitively displayed.
 
|  While our team understand that it would not be feasible to develop a UI which suits the needs of all members in the IS480 Community, we decided to research more about the best practices of UI Designing. Hence, we discovered Angular Material, a library built for AngularJS, which implements Google's material design principles. Angular Material provides a set of reusable, well-tested, and accessible UI components based on the Material Design system. We decided to adopt this because the elements in Material Design is based on Google's empirical research on the best design principles.  <br><br> <b>Google Material Design</b> is a comprehensive guide for visual, motion, and interaction design across platforms and devices.To find out more about Material Design, click [http://www.google.com/design/spec/material-design/introduction.html here]
 
| 6Sigma has decided to replace the previously scheduled Integrated Grid View for faculty. Also, our team has finished the "send email notifications to sponsors upon creation" function. However, the rest of the notifications functions and view notifications would be pushed to iteration 11. If need be, our team would use our Iteration 12 buffer to handle this functionality.
 
|}
 
 
 
===User Tests===
 
<div style="text-align: center;"><font size="4" color=green> ''' User Tests'''</font></div>
 
{| class="wikitable" style="margin: auto;width:50%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width 100px" | Event
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 100px" | Previous Date
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 100px" | Re-scheduled to
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 100px" | Re-scheduled date
 
 
|-
 
|-
| Sponsor Test 1
+
|style="text-align: center;"| Admin3
| 2 Jan 2015
+
|style="text-align: center;"| Admin3
| Faculty Test
 
| 30 Jan 2015
 
 
|-
 
|-
| Student Test 1
+
|style="text-align: center;"| Admin4
| 12 Jan 2015
+
|style="text-align: center;"| Admin4
| Student Test
 
| 30 Jan 2015
 
|-
 
| Student Test 2
 
| 2 Feb 2015
 
| rowspan="2" | User Test 2
 
| rowspan="2" | 12 Feb 2015
 
|-
 
| Faculty Test 2
 
| 9th Feb 2015
 
 
|}
 
|}
  
==Changes in Scope==
+
==In A Nutshell==
 
+
[[File: one.png | 1000px ]]
===Addition===
+
[[File: two.png | 1000px ]]
{| class="wikitable" style="margin: auto;width:80%; text-align:center"
+
[[File: three.png | 1000px ]]
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width 400px" | Function
+
[[File: sm.png | center | 800px ]]
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 100px" | Scheduled into:
+
[[File: four.png | 1000px ]]
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 300px" | Mitigation towards schedule
+
[[File: bug midterm.png | center| 800px ]]
|-
+
[[File: five.png | 1000px ]]
| <strike><b>Integrated Grid View for grading </b>. <br><br>After gathering feedback from Prof. Jason Woodard, he suggested that an integrated grid view for grading would be useful for the faculty members. </strike> <br><br> <b> UPDATE: </b> The grading view is pushed back after mid term and was replaced by Google (Angular) Material Design due to usability concerns which was one of the reason why the previous project failed. Angular Material Design provides a set of reusable, well-tested, and accessible UI components based on the Material Design system, which is a researched and well tested visual language for users that synthesizes the classic principles of good design. This is done so as to benefit all stakeholders through a more usable application based on best UI design practices.
+
[[File: six.png | 1000px ]]
 
+
[[File: Deployment pictures.png | center| 800px ]]
 
+
<br/>
| Iteration 8
+
Demo link @ http://fyp-ccgoh.rhcloud.com/carecorner
| Send notifications to users and View Notifications would be scheduled to iteration 11. If need be, we would use the 2 weeks buffer (Iteration 12), which was previously allocated for bug fixing before full time rollout
+
{| class="wikitable" style="background-color:#FFFFFF; width: 500px;" align="center"
|}
 
 
 
===Removal===
 
{| class="wikitable" style="margin: auto;width:80%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width 400px" | Function
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width: 300px" | Mitigation towards schedule
 
 
|-
 
|-
| <b>Sponsor Comments</b> <br><br> We conducted a [[IS480 Team wiki: 2015T2 6Sigma User Surveys | survey]] to find out whether sponsor comments would be beneficial to the student community. The results of the survey suggests that majority of the students preferred communicating with the sponsors on a face to face basis, and they were also worried about the privacy of their comments. Hence, we decided not to proceed with the development of this function. <br><br> [[IS480 Team wiki: 2015T2 6Sigma User Surveys | More information about the survey]]
+
! style="color:white; background-color:#8A0808;" width="100pt" | Username
| The time allocated for developing this function would be allocated into Integrated Grid View and Analytics module
+
! style="color:white; background-color:#8A0808;" width="100pt" | Password
|-
 
| <b>Iterations</b> <br><br> We conducted a [[IS480 Team wiki: 2015T2 6Sigma User Surveys | survey]] to find out whether students would prefer to upload their iteration information onto the system such that analysis results could be provided to them for better project management. The results of the survey suggests that majority of the students did not welcome this as they felt that the increase in workload outweighs the added advantage it brings.<br><br> [[IS480 Team wiki: 2015T2 6Sigma User Surveys | More information about the survey]]
 
| The time allocated for developing this function would be allocated into Integrated Grid View and Analytics module.
 
|}
 
 
 
==Project Metrics==
 
 
 
===Schedule Metrics===
 
<div style="text-align: center;"><font size="4"> We've adopted the following schedule metrics guidelines to help us track the progress of our project.</font></div>
 
 
 
[[File:6Sigma Schedule Metrics.png|center| 800px]]
 
<br>
 
[[File:6 Sigma Schedule Metrics timeline.png | center | 900px ]]
 
 
 
{| class="wikitable" style="margin: auto;width:70%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:50px" | Iteration
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:70px" | Planned Days
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:70px" | Actual Days
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:50px" | Score
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:300px" | Actions Taken
 
 
|-
 
|-
| 1
+
|style="text-align: center;"| Admin1
| 14
+
|style="text-align: center;"| Admin1
| 14
 
| 100%
 
| None. We are on schedule
 
 
|-
 
|-
| 2
+
|style="text-align: center;"| Admin2
| 14
+
|style="text-align: center;"| Admin2
| 14
 
| 100%
 
| None. We are on schedule
 
 
|-
 
|-
| 3
+
|style="text-align: center;"| Admin3
| 14
+
|style="text-align: center;"| Admin3
| 13
 
| 107%
 
| Add one day to buffer
 
 
|-
 
|-
| 4
+
|style="text-align: center;"| Admin4
| 14
+
|style="text-align: center;"| Admin4
| 14
 
| 100%
 
| None. We are on schedule
 
|-
 
| 5
 
| 14
 
| 16
 
| 87.5%
 
| As we previously had an increase in buffer day from iteration 3, this resulted in a deduction of 1 day from our buffer. For more information on the problems and solutions for this iteration, refer to the [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| "Issues Faced"]] tab.
 
|-
 
| 6
 
| 14
 
| 14
 
| 100%
 
| None. We are on schedule
 
|-
 
| 7
 
| 14
 
| 14
 
| 100%
 
|Decided to push Manipulate Statistics to further iterations. For more information on the problems and solutions for this iteration, refer to the [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| "Issues Faced"]] tab.
 
|-
 
| 8
 
| 14
 
| 14
 
| 100%
 
| We completed the sending of email notification to sponsors. However, other notifications would be pushed to further iterations such that we can focus on Angular Material. For more information on the problems and solutions for this iteration, refer to the [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| "Issues Faced"]] tab.
 
|-
 
| 9
 
| 14
 
| 14
 
| 100%
 
| None. We are on schedule. However, it is important to note that there were still many bugs in this iteration, which is due to the Angular Material UI change
 
 
|}
 
|}
 +
<br/>
 +
[[File: seven.png | 1000px ]]
 +
[[File: ut1.png | center | 600px ]]
 +
[[File: nine.png | 1000px ]]
 +
[[File: ut2.png | center | 600px ]]
 +
[[File: Ut2pics.png | center | 600px ]]
  
===Bug Metrics===
+
{| class="wikitable" style="background-color:#FFFFFF; width: 500px;" align="center"
 
 
[[File:6Sigma Bug Metrics.png | center | 900px]]
 
 
 
{| class="wikitable" style="margin: auto;width:80%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:50px" | Iteration
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:50px" | Score
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:300px" | Notable reasons
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:300px" | Actions Taken
 
|-
 
| 1
 
| 26
 
| -
 
|Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled
 
|-
 
| 2
 
| 6
 
| -
 
| Use scheduled debugging time for debugging
 
|-
 
| 3
 
| 30
 
| -
 
| Stop current development and resolve the bug immediately. However, as we completed the functionalities early, we managed to solve the bugs before the end of iteration. Hence, project was not rescheduled
 
 
|-
 
|-
| 4
+
! style="color:white; background-color:#8A0808;" width="150pt" | User Test no.
| 35
+
! style="color:white; background-color:#8A0808;" width="300pt" | Link
| -
 
| Stop current development and resolve the bug immediately.We managed to solve the bugs before the end of iteration. Hence, project was not rescheduled
 
|-
 
| 5
 
| 95
 
| Previously, we had resource files (File containing end points) which groups all business functions together, regardless of the role of the executor. Our team foresaw that maintainability was going to be a problem in the long run with the adoption of this structure. <br><br>A major overhaul of codes was done in this iteration, and hence, the high bug count.
 
| Stop current development and resolve the bug immediately. We are unable to complete bug fixing on time, and hence, we decided to use up 2 days of our buffer. Currently, we are left with 5 days of buffer after this iteration.
 
|-
 
| 6
 
| 30
 
| -
 
| Stop current development and resolve the bug immediately. We managed to solve the bugs before the end of iteration. Hence, project was not rescheduled.
 
|-
 
| 7
 
| 42
 
| It was evident that the basic core functionalities of our application was still not up to standard, and the basic functionalities require more work to be added on. Apart from that, the user test was to be conducted 2 weeks’ time, on Jan 30th.
 
| Stop current development and resolve the bug immediately. As too many funactionalties was breaking at this point in time, we decided to reschedule "Manipulate Statistics" to later iterations.  Click [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| HERE]] to find out more
 
|-
 
| 8
 
| 75
 
| We decided to revamp our UI to adopt the best practices and principles of design through the use of Angular Material. As such, there were many UI bugs which were discovered with the re-designing of our UI.
 
| Stop current development and resolve the bug immediately. Click [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| HERE]] to find out more about the change management plan for Angular Material
 
|-
 
| 9
 
| 80
 
| We decided to revamp our UI to adopt the best practices and principles of design through the use of Angular Material. As such, there were many UI bugs which were discovered with the re-designing of our UI.
 
| Stop current development and resolve the bug immediately. Click [[IS480 Team wiki: 2015T2 6Sigma Issues Faced| HERE]] to find out more about the change management plan for Angular Material
 
|}
 
 
 
== Team's Metrics ==
 
 
 
===Coding Workload===
 
[[File:6Sigma Coding workload.png | center | 1000px]]
 
 
 
===Coding Hours===
 
[[File:6Sigma Coding Hours.png | center | 1000px]]
 
 
 
===Non Coding Hours===
 
[[File:6Sigma Non Coding Hours.png | center | 1000px]]
 
 
 
===Total Hours===
 
[[File:6Sigma Total Hours.png | center | 1000px]]
 
 
 
===Punch Card (GIT)===
 
[[File:6Sigma Punch card.png | center | 1000px]]
 
 
 
==Risks==
 
 
 
===Risks===
 
[[File:6Sigma Risk Table.png |center| 800px]]
 
 
 
 
 
<div style="text-align: center;"><font size="4"> We've classified the risks we've identified into 3 categories: A, B and C.
 
 
 
'A' risks need the most attention and most well developed mitigation or recovery strategies,
 
 
 
'C' risks can occur but deserve the least amount of planning.
 
</font></div>
 
<br>
 
<div style="text-align: center;"><font size="4" color="red"> '''Top 3 risks identified''' </font></div>
 
 
 
{| class="wikitable" style="margin: auto;width:90%; text-align:center"
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:150px" | Risk Type
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:200px" | Risk Event
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:70px" | Occurrence
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:70px" | Impact
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:100px" | Category
 
! style="font-weight: bold;background: #16a085;color:#ecf0f1; width:400px" | Mitigation
 
 
|-
 
|-
|Adoption Risk
+
|style="text-align: center;"| UT 1
|Our system might not be well received by the IS480 Community for usage and efforts to capture user's data for analytics might fail
+
|style="text-align: center;"| [[IS480 Team wiki: 2015T2 The C-Suite User Test 1| View our User Test 1]]
|High
 
|High
 
|style="color:red;" | '''A'''
 
|We intend to roll the system out in week 7, such that the next IS480 Batch can start using our system. Also, our team would be conducting numerous user tests and survey to improve usability.
 
 
|-
 
|-
|Regulatory Risk
+
|style="text-align: center;"| UT 2
|Analytics and statistics used in this project may require the use of personal data and may violate the Personal Data Protection Act (PDPA).
+
|style="text-align: center;"| [[IS480 Team wiki: 2015T2 The C-Suite User Test 2| View our User Test 2]]
|High
 
|High
 
|style="color:red;" | '''A'''
 
|The use of any personal data will be declared to the sponsor and all data will be protected from unauthorized access/use.
 
 
|-
 
|-
|Technology Risk
+
|style="text-align: center;"| UT 3
|As mediawiki is highly unfavorable to crawling, crawling efforts might fail
+
|style="text-align: center;"| [[IS480 Team wiki: 2015T2 The C-Suite User Test 3| View our User Test 3]]
|High
 
|High
 
|style="color:red;" | '''A'''
 
|The development for learning analytics is kept to the end so as to cater time to manually extract data in the event the wiki is uncrawlable.
 
 
|}
 
|}
 
+
[[File: eight.png | 1000px ]]
 
 
===Mitigation===
 
 
 
[[File:6Sigma Risk mitigation.png | center | 900px]]
 
 
 
==Technical Complexity==
 
 
 
[[File:6Sigma Technical Complexity.png | center | 800px]]
 
 
 
==Learning Outcomes==
 
 
 
Link to our Knowledge Based Contribution :[https://wiki.smu.edu.sg/is480/Knowledge_base#Angular_JS here]
 
[[File:6Sigma Learning outcomes.png | center | 700px]]
 
-->
 

Latest revision as of 17:59, 26 February 2015

Frameless
Home About us Project Overview Project Management Documentation
Home Midterm Wiki Final Wiki


Midterm documents

Demo

Demo link @ http://fyp-ccgoh.rhcloud.com/carecorner

Username Password
Admin1 Admin1
Admin2 Admin2
Admin3 Admin3
Admin4 Admin4

In A Nutshell

One.png Two.png Three.png

Sm.png

Four.png

Bug midterm.png

Five.png Six.png

Deployment pictures.png


Demo link @ http://fyp-ccgoh.rhcloud.com/carecorner

Username Password
Admin1 Admin1
Admin2 Admin2
Admin3 Admin3
Admin4 Admin4


Seven.png

Ut1.png

Nine.png

Ut2.png
Ut2pics.png
User Test no. Link
UT 1 View our User Test 1
UT 2 View our User Test 2
UT 3 View our User Test 3

Eight.png