HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 6Sigma final wiki"

From IS480
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 45: Line 45:
  
 
<!--------------------------- Content Starts here ------------------>
 
<!--------------------------- Content Starts here ------------------>
 +
==Documents==
 +
[https://www.dropbox.com/s/u3qc8xlriblp5mo/6SIGMA%20-%20IS480%20Final%20Presentation.pdf?dl=0 Final Presentation Slides] <br>
 +
[https://www.dropbox.com/s/he4xf97hjvm7wc1/6Sigma%20-%20List%20of%20APIs%20for%20IS480%20System%202.pdf?dl=0 IS480 Management System II List of APIs]
 +
 
==Project Management==
 
==Project Management==
 
===Functions achieved===
 
===Functions achieved===
Line 526: Line 530:
 
| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_6Sigma_User_Surveys#Gathering_of_Faculty.27s_Vision Click HERE for detailed survey results]
 
| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2015T2_6Sigma_User_Surveys#Gathering_of_Faculty.27s_Vision Click HERE for detailed survey results]
 
| [https://www.dropbox.com/s/h1for7nxeo26208/Faculty%20Visioning.xlsx?dl=0 Click HERE for Raw Data]
 
| [https://www.dropbox.com/s/h1for7nxeo26208/Faculty%20Visioning.xlsx?dl=0 Click HERE for Raw Data]
 +
|-
 +
| <b> SUMMARY OF TOTAL Feedback implemented vs gathered from all feedback sessions </b>
 +
| -
 +
| -
 +
| -
 +
| [https://www.dropbox.com/s/ajbm1dnb3b9c0nx/Comments%20implemented%20vs%20not%20implemented.xlsx?dl=0 Click HERE for Raw Data]
 
|}
 
|}
  
Line 663: Line 673:
 
==Technical Complexity==
 
==Technical Complexity==
 
[[File:6Sigma Technical Complexity.png | 800px | center]]
 
[[File:6Sigma Technical Complexity.png | 800px | center]]
 
==Learning Outcomes==
 
  
 
== X Factor==
 
== X Factor==
 
[[File:X-factors-6sigma.png|centre|800px]]
 
[[File:X-factors-6sigma.png|centre|800px]]
 +
 +
==Learning Outcomes==
 
===Individual===
 
===Individual===
 
[[File:Learing Outcomes 2.png | center | 800px]]
 
[[File:Learing Outcomes 2.png | center | 800px]]

Latest revision as of 20:27, 21 April 2015

6Sigma Logo.png

Home

About Us

IS480 Management System

Project Management

Project Documentation

Home Midterm Finals

Documents

Final Presentation Slides
IS480 Management System II List of APIs

Project Management

Functions achieved

Functionalities highlighted in red are not achieved.
6Sigma Priority Circle.jpg


Iteration Module Function Description Confidence Comments
1 Student Module CRUD Student Profile Allows students to CRUD their profiles. 1 -
Team Module CRUD Team Profile Allows a student to CRUD a team profile. 1 -
CRUD Team member Allows a student to CRUD team members. 1 -
General Module SSO Allows all users with SMU domain credentials to login to the system. 1 Some faculty members were still unable to SSO into our application due to the different user groups assigned to each faculty. We quickly resolved this by liaising with IITS to obtain all SIS faculty user groups
2 Faculty Module CRUD Faculty Allows faculty to CRUD their profiles. 1 -
Sponsor Module CRUD Accounts Allows new sponsors to request an account and propose a project. 1 -
Login Allows external sponsors to login as they do not have SSO accounts. 1 -
3 Project Module CRUD Projects Allows sponsors to CRUD projects for students to take 1 -
4 Project Module CRUD Project Teams Allows sponsor to approve or reject teams for their projects. 1 -
Team Module CRUD Project Status Allows the course coordinator/supervisor to update the status of the team’s project. (i.e. accepted or rejected) 1 -
Coordinator Module CRUD Term Allows the Course Coordinator to CRUD terms in the system. 1 -
5 Faculty Module Assign Supervisor/Reviewer to Team Allows Course Coordinator to a specific supervisor and assign him to a specific team manually. 1 -
Coordinator Module Suspend Team Suspend the team users so that they will not be a nuisance to the other users. Team will be unsuspended once the Course Coordinator deemed its ok. There is a user status attached to all the users (active/ suspended) which is only viewable by the admin. 1 -
Coordinator Module Assign Sponsor Role Course coordinator can assign sponsor roles to faculty. 1 -
6 Project Module Request Project Approval Allows students to request the sponsor to accept the team for the project. 1 -
Team Module CRUD Acceptance/Mid- Term/Final Review Allows course coordinators, supervisors, reviewers and sponsors to add their proposal/mid-term/final reviews 1 -
Project Module CRUD Project Details/Documents Allows team to use the website as a replacement for wiki for their project. 1 -
7 General Module Download statistics User must be able to download IS480 statistics. 1 -
Search Module Search Student / Faculty / Project / Sponsor / Team Search for Student / Faculty / Project / Sponsor / Team based on what user entered into the search bar so that he can retrieve the information 1 -
8 General Module Generation of Email to Sponsors Generate an email to sponsor upon signing up for the system 1 -
9 Analytics Module Cosine Similarity Index Use of algorithm to find out the similar teams in IS480 based on Technologies Used, Industries and Project Type. 1 -
10 General Module View Statistics Displaying of statistics through the use of NVD3 Charts 1 -
Logging Logging of important information for accountability purposes 1 -
11 Scheduling Module Generating of CSV File format to suit scheduling system. Generating of CSV File format to suit scheduling system for integration purposes. 1 -
General Module Send notifications to users Generates a list of email via the system when there are important announcements to make. 1 -



6Sigma Functions Achieved.png



Planned Schedule during Mid Terms

6Sigma Midterm Schedule.png

Actual Schedule

6Sigma Timeline.png

Reasons for Change in Schedule & Functionalities

Function Mitigation towards schedule
Manipulate Statistics
After our mid term presentation, our sponsors suggested that more emphasis should be placed on the grading function as the faculty members would be using the grading functionality for grading in the final presentations.

Due to our tight schedule, we felt that more time should be allocated to the enhancement and fixing of the grading module such that it is well tested and usable enough for faculty members to adopt the IS480 Management System II for grading.
During our 11, 12 and 13th iteration, extensive user tests would be conducted on the faculty members and the grading module would be improved as well.
Notifications (Changed to mailing list)
After our mid term presentation, our sponsors suggested that more emphasis should be placed on the grading function as the faculty members would be using the grading functionality for grading in the final presentations.

Due to our tight schedule, we felt that more time should be allocated to the enhancement and fixing of the grading module such that it is well tested and usable enough for faculty members to adopt the IS480 Management System II for grading.
Audit (Changed to logging)

It was technically unfeasible due to the requiring of multiple databases. Moreover, our database structure was already decided before this function was requested by the sponsor. Hence, we've scaled down the Audit functionality to logging. On the other hand, we scaled this functionality down to cater more time for extensive testing and enhancement of the grading functionality. The logging function would only log important tasks performed by users for accountability purposes.

Schedule Metrics

After our mid term presentation, our reviewer, Prof Alan, advised us that we should be tracking planned vs actual no. of hours if we were using time boxing.
6Sigma Total hours.png


Iteration Planned Days Actual Days Score Actions Taken
1 14 14 100% None. We are on schedule
2 14 14 100% None. We are on schedule
3 14 13 107% Add one day to buffer
4 14 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 "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 "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 "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
10 14 14 100% None. We are on schedule.
11 14 14 100% None. We are on schedule.
12 14 14 100% None. We are on schedule.
13 14 14 100% None. We are on schedule.
14 9 9 100% None. We are on schedule.

Bug Metrics

6Sigma Bugmetric.png


6Sigma Bug Metrics.png
Iteration Low High Critical Total Score Actions Taken
1 1 5 0 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 1 1 0 6 Use scheduled debugging time for debugging
3 2 4 0 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 0 7 0 35 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 0 17 0 95 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 0 6 0 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 2 8 0 42 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 HERE to find out more
8 0 9 3 75 Stop current development and resolve the bug immediately. Click HERE to find out more about the change management plan to Angular Material
9 0 16 0 80 Stop current development and resolve the bug immediately. Click HERE to find out more about the change management plan to Angular Material
10 4 1 1 39 The critical bug observed here was due to the SSO Service. We realized that not all smu user groups were captured in our system and hence, one faculty member could not log in. We seek technical help from IITS to retrieve all smu user groups in order to prevent this from happening again.
11 12 3 0 27 Use the scheduled debugging time for debugging.
12 9 1 0 14 Use the scheduled debugging time for debugging.
13 4 1 0 9 Use the scheduled debugging time for debugging.
14 0 1 0 5 Use the scheduled debugging time for debugging

User Tests & Feedback

User Tests
Event Date No of Particpants Results Raw Data
Student Test 28th Jan 2015 32 Students Click HERE for detailed results Click HERE for raw data
Faculty Test 1
(Session 1 and Session 2)
Session 1
(30th Jan 2015)
Prof Jason
Prof Benjamin Gan
Instructor Fiona Lee
Click HERE for detailed results Click Here for raw Data
Session 2
(12th-13th Feb 2015)
Prof Benjamin Gan
Instructor Fiona Lee
Click HERE for detailed results Click Here for raw Data
Student Test 2 14th Feb 2015 20 Students Click HERE for detailed results Click HERE for raw Data
Faculty Test 2 18th - 25th March 2015 Prof Jason
Prof Benjamin Gan
Prof Debin Gao
Prof Chris Boesch
Prof Li Yingjiu
Prof Cheok Lai Tee
Prof Patrick Thng
Prof David Lo
Prof Alan Megargel
Click HERE for detailed results Click HERE for Raw Data


User Feedback
Event Date No of Particpants Results Raw Data
Student Survey 23rd Jan 2015 61 Students Click HERE for detailed survey results Click HERE for Raw Data
6Sigma IS480 User Feedback Session With GongCha Giveaway 23rd March - 25th March 2015 150 unique students Click HERE for detailed survey results Click HERE for Raw Data
Gathering of Faculty's Visioning 23rd - 31st March 2015 Prof Chris Boesch
Prof Cheok Lai Tee
Prof Patrick Thng
Prof Debin Gao
Click HERE for detailed survey results Click HERE for Raw Data
SUMMARY OF TOTAL Feedback implemented vs gathered from all feedback sessions - - - Click HERE for Raw Data

Load Testing

Test Configuration

Max User Load Duration (Minutes) Threads Rampup
50 20 50 300

Faculty & Admin Functions

Results

[Hazelcast Report] [Reference Report]

Result Type Graph
User Load Usersf.png
Response Time Responsef.png
Latency Latencyf.png
Bandwidth in KB/s Bandwidthf.png
Hits/s Hitsf.png
Errors Errorsf.png

Student Functions

Results

[Hazelcast Report] [Reference Report]

Result Type Graph
User Load Users.png
Response Time Response.png
Latency Latency.png
Bandwidth in KB/s Bandwidth.png
Hits/s Hits.png
Errors Errors.png

Conclusion

For faculty and admin test cases, average throughput increased from 1 hit/s to 12 hits/s. The average page response time decreased from 76495ms to 2739ms, a 28 fold improvement. At the 90th percentile, page response time dropped from 110285ms to 6569ms, a 16 fold improvement.


For student test cases, average throughput increased from 1 hit/s to 8 hits/s. The average page response time decreased from 68700ms to 4133ms, a 16 fold improvement. At the 90th percentile, page response time dropped from 103455ms to 9355ms, a 11 fold improvement.


As the results were stable (0 errors), the testing environment controlled and the test run on the similar deployment environment, the overall improvements provided by Hazelcast significantly improved the performance of the application.

Risks

6Sigma Risk Table.png


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.


Top 3 risks identified
Risk Type Risk Event Occurrence Impact Category Preventive measures Reactive Measures
Adoption Risk We might run into the risk of not understanding how good it had to be for the client to adopt it. We might run into the cycle of constantly trying to be good enough, hoping its good enough, without actually knowing what is good enough. High High A Our team would conduct early user test and aim an early deployment for faculty members to explore the system. Our team gathered feedback from the faculty members personally to meet their requirements of the system. Also, we also addressed the concerns which faculty members might have regarding our application before the final presentation starts. Moreover, we got a sensing of how comfortable the faculty were with using our application.
Live deployment risk Our applications might face issues in the production environment when it is used for actual grading. High High A Our testing environment would be replicated as closely as possible to the deployment environment. During the final presentation period, we would schedule ourselves to be on standby for assistance in case of technical difficulties faced by faculty members.
Integration Risk During the integration of our application with the SSO service provided by IITS, there might be data compatibility issues. High High A Use available data on LDAP (Lightweight Directory Access Protocol) in hopes of a full compatibility. When there were login issues, we communicated with IITS and conducted an investigation with regards to the smu_groups fields that the SSO application returns to resolve it

Technical Complexity

6Sigma Technical Complexity.png

X Factor

X-factors-6sigma.png

Learning Outcomes

Individual

Learing Outcomes 2.png

What we have learnt and what we would have done better

6Sigma Learning outcome2.png