IS480 Team wiki: 2013T1 ThunderBolt Final wiki
Mid-Term Wiki | Final Wiki |
Contents
Project Progress Summary
Immediate Deliverable
Click here [1] download final presentation slides
Link to deployment server: http://bit.ly/is480-ss
Link to live server : http://202.161.45.168/is480-scheduling/login.jsp
Our Key Accomplishments
- 99% of the project completed |
Project timeline overview
Click [2] to view our full project schedule.
Project Highlights
Video Pitch
Click here to watch the video!
Project Poster
Project Management
Project Status
We have completed all core, secondary and additional functionality of the system and its fully functional now
Click here to see more detail of our project status.
However, there are still some improvements that we would like to make after our final presentations:
- UI improvements as per our sponsors request
- Allow admin to change type of presentation
- Customize SMS to supervisors
- URL pointing to live server in emails should be configurable
- Allow the user to download an ICS file from the website
Project Schedule (Plan Vs Actual)
Click here to see plan vs actual schedule
Project Metrics
Schedule Metrics
The chart below shows the overview of schedule metrics for our entire project
Click here to understand how we derive our metrics and what are the action plans to each metric.
Bug Metrics
Click here to find out how we calculate our bug score and what are the respective action plans for different category of score.
Click here for detailed bug log:
Figure 1 shows the distribution of bug severity
Figure 2 further elaborate figure 1 by breaking down bug severity distribution over iteration
Figure 3 shows an overall bug score for our system as of now
Bugs logged here were discovered during internal testing which carried out at end of each iteration based on the test cases we created.Regression testing methodology was used to conduct internal testing.
Technology
Technical Complexity
Time-based View Selection
The problem with the IS480 schedules on the IS480 Wiki is that it is difficult to find exactly which one you are involved in. If you are a user of Term 1, and scheduling of the Acceptance presentations, the default top most item you can find on the IS480 Main Page would be Term 2. Finding which term you belong to, and the most important milestone, requires some effort.
Therefore, we have implemented an algorithm that does this work for you. The algorithm is as follows:
If there is only one term, the most important milestone is shown you. The default milestone is determined by, in descending order of importance:
Default Milestone
- The current time is between the range of dates of the milestone
- The current time is before the start date of the upcoming milestone
- The current time has passed the end date of the last milestone
If there are multiple terms, before the default milestone selection logic, the default term selection logic is determined by, in descending order of importance:
Default Term
- If you are a user of multiple terms, and the current time is at a point where both terms overlap, the earlier term is the default term because it is not complete yet.
- If you are a user of multiple terms and there are more pending bookings in the later term, the later term is the default term because it is more active.
- If you are a user of a future term and not the current term, the default term is the future term.
- If you are a non-user of any term and the current time is at a point where both terms overlap, the default term is the earlier term.
- If there is no current term and there are multiple future terms, the default term is the earliest future term.
- If there is no current term and there were multiple terms in the past, the default term is the latest past term.
Usability
The Calendar Interface
We have adopted the ever-familiar calendar interface present in the most popular calendars out there: Microsoft Outlook Calendar, Google Calendar, and Apple iCal.
Our old calendar interface:
Our new calendar interface:
Multifunctional Calendar
There are 5 different roles in the IS480 course - Course Coordinator, Administrator, Faculty (Supervisor/Reviewer), Student, and TA. We have developed a calendar interface that caters to each role in terms of visuals and functionality.
The functions of each role are listed below. New functions implemented since Midterm are marked in green.
Course Coordinator
- View a dashboard showing which teams haven't booked
- Override the entire booking approval process
- Book on behalf of teams
- Update bookings by Drag-N-Drop
Administrator
- Track TA presentation sign ups
- Email TAs to sign up for a slot with a single click
- Do everything the Course Coordinator can do
Faculty
- View a dashboard showing which teams haven't booked
- Approve or Reject bookings
- Cancel bookings
- RSVP to presentations
- See only bookings that matter
- Indicate availability
Student
- RSVP to presentations
- Book with a single-click
- See only bookings that matter
- Invite SMU peers and faculty
- Have a visual trail of their booking history
TA
- Swap slots with other TAs
- See TA statistics
- RSVP to presentations
- See only bookings that matter
- Sign up for filming
Quality of product
Intermediate Deliverables
Stage | Specification | Links |
---|---|---|
Project Management | Metrics | |
Minutes | ||
Requirements | Change Requests Log | |
Prototype | ||
Analysis | Use Case | |
Design | System Architecture Diagram | |
Testing | Internal Testing Test Plan | |
Internal Testing Test cases and results | ||
User Testing 1 | ||
User Testing 2 | ||
User Testing 3 |
Deployment
System was first deployed on 26 Sept, followed by second deployment on 22 Oct and final deployment with full functionality on 21 Nov 2013
Testing
Internal Testing
Internal Testing was conducted at end of each iteration. Total of 12 internal testings were carried out.
Click here for internal testing test plan
Click here for internal testing test cases by iterations
User Testing
3 User Testings were conducted with key users of the system
- 1st User Testing: 2 Sep
- 2nd User Testing: 4 Oct
- 3rd User Testing: 18 Nov
Click here to find out more about our User Testing
Reflection
In this section, describe what have the team learn? Be brief. Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
Team Reflection
Any training and lesson learn? What are the take-away so far? It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.