HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 181: Line 181:
 
| Currently, our team has looked into the viability of implementing learning analytics, and we felt that it  would be too challenging to properly implement a fully functional learning analytics modulate within the short duration of 2 months
 
| Currently, our team has looked into the viability of implementing learning analytics, and we felt that it  would be too challenging to properly implement a fully functional learning analytics modulate within the short duration of 2 months
 
| As such, our team would like to replace this Good to have functionality, and improve on the existing secondary functionalities (Audit Trail, View Statistics, and Manipulate Statistics) for the rest of the iterations.
 
| As such, our team would like to replace this Good to have functionality, and improve on the existing secondary functionalities (Audit Trail, View Statistics, and Manipulate Statistics) for the rest of the iterations.
| rowspan='2' | <b> Audit Trail, View Statistics </b>(Previously scheduled in iteration 8) and <b>Manipulate Statistics</b> (Scheduled in Iteration 7) would be spread across the remaining iterations with learning analytics removed from the scope. Also, the extra 5 days of buffer would be used, if there's a need.  
+
| rowspan='2' | <b> Audit Trail, View Statistics </b>(Previously scheduled in iteration 8) and <b>Manipulate Statistics</b> (Scheduled in Iteration 7) would be spread across the remaining iterations. Also, the extra 5 days of buffer would be used, if there's a need.  
 
|-
 
|-
 
| After the last sponsor meeting which was held on 16th Jan 2015, 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.  <br>
 
| After the last sponsor meeting which was held on 16th Jan 2015, 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.  <br>

Revision as of 21:05, 31 January 2015

6Sigma Logo.png

Home

About Us

IS480 Management System

Project Management

Project Documentation

Home Midterm Finals


In a nutshell

Project Management


Functions achieved


Iteration Module Function Description
1 Student Module CRUD Student Profile Allows students to CRUD their profiles.
Team Module CRUD Team Profile Allows a student to CRUD a team profile.
CRUD Team member Allows a student to CRUD team members.
General Module SSO Allows all users with SMU domain credentials to login to the system.
2 Faculty Module CRUD Faculty Allows faculty to CRUD their profiles.
Sponsor Module CRUD Accounts Allows new sponsors to request an account and propose a project.
Login Allows external sponsors to login as they do not have SSO accounts.
3 Project Module CRUD Projects Allows sponsors to CRUD projects for students to take
4 Project Module CRUD Project Teams Allows sponsor to approve or reject teams for their projects.
Team Module CRUD Project Status Allows the course coordinator/supervisor to update the status of the team’s project. (i.e. accepted or rejected)
Coordinator Module CRUD Term Allows the Course Coordinator to CRUD terms in the system.
5 Faculty Module Assign Supervisor/Reviewer to Team Allows Course Coordinator to a specific supervisor and assign him to a specific team manually.
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.
Coordinator Module Assign Sponsor Role Course coordinator can assign sponsor roles to faculty.
6 Project Module Request Project Approval Allows students to request the sponsor to accept the team for the project.
Team Module CRUD Proposal/Mid- Term/Final Review Allows course coordinators, supervisors, reviewers and sponsors to add their proposal/mid-term/final reviews
Project Module CRUD Project Details/Documents Allows team to use the website as a replacement for wiki for their project.
7 General Module Download statistics User must be able to download IS480 statistics.
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

Planned Schedule

6Sigma OldPlan.png

Actual Schedule

6Sigma Timeline.png

Changes


Iteration 5 : 8 December 2014 to 23 December 2014
Issues Solution Mitigation towards schedule
Previously, we had resource files (File containing end points) which groups all business functions together, regardless of the role of the executor.

This resulted in each resource file extending up to 500 lines, and it was difficult to trace code and fix bugs, resulting in delay. This has also frustrated a lot of teammates.
Our team foresaw that maintainability was going to be a problem in the long run.

It was decided for individual resource / endpoint files to be developed for each function for each particular role. Eg: Functionalities involving teams for the Faculty role would be classified under facultyteam resources. This resulted in a delay of 2 days. As we previously had an increase in buffer day from iteration 3, this resulted in a deduction of 2 days from our buffer.
Our team was still new to the technology of JPA, and we developed our business logics in the resource files.
This resulted in repeated codes.
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.



Iteration 7 : 9 Jan 2015 to 24 Jan 2015
Issues Solution Mitigation towards schedule
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. 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 HERE 6Sigma has decided to remove CRUD Comments, iterations and the blue front page implantations from our project scope.
Currently, our team has looked into the viability of implementing learning analytics, and we felt that it would be too challenging to properly implement a fully functional learning analytics modulate within the short duration of 2 months As such, our team would like to replace this Good to have functionality, and improve on the existing secondary functionalities (Audit Trail, View Statistics, and Manipulate Statistics) for the rest of the iterations. Audit Trail, View Statistics (Previously scheduled in iteration 8) and Manipulate Statistics (Scheduled in Iteration 7) would be spread across the remaining iterations. Also, the extra 5 days of buffer would be used, if there's a need.
After the last sponsor meeting which was held on 16th Jan 2015, 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.

Our team felt that it would be wiser to prioritize on fixing the basic core functionalities of our application before moving on to tackle secondary functionalities.

Therefore, our team felt that more effort should be dedicated to the core functionalities to ensure the application is stable enough for user testing on 30th Jan. As a result, our team has decided to postpone manipulate statistics to further iterations.

Change in Scope

Surveys

Supervisor Meetings

Project Metrics

Bug Metrics

Schedule Metrics

Issues Faced

Risks

Technical Complexity