HeaderSIS.jpg

IS480 Team wiki: 2012T1 Pro-cept Mid Term Wiki

From IS480
Jump to navigation Jump to search
Pro-Cept logo v4.png





Home
Star.jpgMid-Term Wiki Page

Project Progress Summary


Overview

As of 7 Oct 2012, Pro-cept has completed 7 of the assigned functionalities, after 10 iterations of the project.

Left


During these 5 months, our team has achieved several key accomplishments since the project progress on 21 May 2012:

  • Exposure to 3rd party sources in the process of developing our project
  • Use of Google Doc List API in the process of developing the Google Doc Integration
  • Hosting of 2 Usability Tests and and using the feedback to improve our website to better suits users


Pro-cept is currently on track according to our schedule and hence we are confident of completing the project within the Schedule.


Project Highlights

Event Highlights/Issue Description
1

Delay in completing Google Doc Integration in Iteration 7

Initially, our team planned to complete the Google Doc Integration from Iteration 6 to 7. However, due to limited knowledge on how to collaborate and implement Google Doc Integration with the Google Doc List API 2.0, we faced a setback that required an additional iteration to complete this function.

2

Lack of Project Requirements

As Pro-cept is an self-initiated team, we do not have a fixed set of requirements that we can gather from the clients. The most realistic option that we can adopt to resolve this issue is through the gathering of feedback during the User Tests. Thereafter, we can make use of the devised Criteria List to determine which functions can be implemented in the project.



Project Management

Project Status

Feature Status Confident Level (0 - 1) Person In-Charge
Task List Calendar 100% developed and deployed
1 Wee Long & Kelvin Tan
Newsfeed 100% developed and deployed
1 Christie
Project Group 100% developed and deployed
1 Kelvin Tan
Google Doc Integration 80% developed and deployed
1 Christie
Chronoline (Timeline) 100% developed and deployed
1 Wee Long
Document View 100% developed and deployed
1 Wee Long
Minute Taker 80% developed and deployed
1 Christie
Chat Not Started
1 Kelvin Tan
Filtering Not Started
1 Wen Xiong



Project Schedule (Planned VS. Actual)

Functions Task Planned Schedule Actual Schedule Comment
Start Date End Date Start Date End Date
Task List Calendar Create Task Function 19 Jun 2012 20 Jun 2012 19 Jun 2012 20 Jun 2012
Retrieve Task Function 21 Jun 2012 22 Jun 2012 21 Jun 2012 22 Jun 2012
Update Task Function 23 Jun 2012 23 Jun 2012 23 Jun 2012 23 Jun 2012
Delete Task Function 24 Jun 2012 24 Jun 2012 24 Jun 2012 24 Jun 2012
Create Calendar Function 25 Jun 2012 25 Jun 2012 25 Jun 2012 25 Jun 2012
Retrieve Calendar Function 26 Jun 2012 26 Jun 2012 26 Jun 2012 26 Jun 2012
Update Calendar Function 27 Jun 2012 27 Jun 2012 27 Jun 2012 27 Jun 2012
Delete Calendar Function 28 Jun 2012 28 Jun 2012 28 Jun 2012 28 Jun 2012
Newsfeed Create Newsfeed Function (All, Personal, Group) 3 Jul 2012 4 Jul 2012 3 Jul 2012 4 Jul 2012
Retrieve Newsfeed Function 5 Jul 2012 6 Jul 2012 5 Jul 2012 6 Jul 2012
Update Newsfeed Function 7 Jul 2012 8 Jul 2012 7 Jul 2012 8 Jul 2012
Delete Newsfeed Function 9 Jul 2012 9 Jul 2012 9 Jul 2012 9 Jul 2012
Project Group Create Form 17 Jul 2012 19 Jul 2012 17 Jul 2012 19 Jul 2012
Check User Function 20 Jul 2012 21 Jul 2012 20 Jul 2012 21 Jul 2012
Insert data to Database 22 Jul 2012 23 Jul 2012 22 Jul 2012 23 Jul 2012
Google Doc Integration Code Oauth 31 Jul 2012 3 Aug 2012 31 Jul 2012 3 Aug 2012
Code Logging In 4 Aug 2012 6 Aug 2012 4 Aug 2012 6 Aug 2012
Code Refresh of Access 7 Aug 2012 9 Aug 2012 7 Aug 2012 9 Aug 2012
Retrieve Files (Real-Time) 13 Aug 2012 14 Aug 2012 13 Aug 2012 14 Aug 2012
Update Files 15 Aug 2012 16 Aug 2012 15 Aug 2012 16 Aug 2012
Create Files 17 Aug 2012 18 Aug 2012 17 Aug2012 25 Aug 2012 As we were unable to complete these tasks on time, we had to spill over to iteration 8 where we will complete these tasks while working on the Chronoline (Timeline) function concurrently.
Delete Files 19 Aug 2012 20 Aug 2012 26 Aug 2012 3 Sep 2012
Chronoline (Timeline) Create Milestones/Deadline 28 Aug 2012 29 Aug 2012 28 Aug 2012 29 Aug 2012
Retrieve Milestones/Deadline 30 Aug 2012 31 Aug 2012 30 Aug 2012 31 Aug 2012
Update Milestones/Deadline 1 Sep 2012 2 Sep 2012 1 Sep 2012 2 Sep 2012
Delete Milestones/Deadline 3 Sep 2012 3 Sep 2012 3 Sep 2012 3 Sep 2012
Document View Code Opening GDOC link in I-Frame 11 Sep 2012 14 Sep 2012 11 Sep 2012 14 Sep 2012
Code Opening subsequent GDOC link in I-Frame 15 Sep 2012 17 Sep 2012 15 Sep 2012 17 Oct 2012
Minute Taker Create Form List (Adding of Minute) 25 Sep 2012 26 Sep 2012 25 Sep 2012 26 Sep 2012
Retrieve User List 27 Sep 2012 28 Sep 2012 27 Sep 2012 28 Sep 2012
Delete Minute 29 Sep 2012 29 Sep 2012 29 Sep 2012 29 Sep 2012
Upload Minutes to Google Drive (PDF Format) 30 Sep 2012 1 Oct 2012 30 Sep 2012 ongoing We were unable to complete this function on-time due to technical complexity. This task will be spilled over to Iteration 11.



Project Metrics

Schedule Metric


The graph below shows the schedule metric values of the 10 iterations which we have completed.

Left

Schedule Metric Value


From the graph, you can see that:

  • Firstly, there is a 8 days delay in the schedule for Iteration 7, in which the team was supposed to complete the Google Doc Integration.

  • Secondly, there is a 2 days (and still counting) delay in the schedule for Iteration 10, in which the team is supposed to complete the Minute Taker. The reason for the delay in this iteration is due to the technical complexity of the integration of Google Docs together with our Minute Taker. This is accounted for in one of our technical complexities, which explains the reason for the delay in the schedule.


Links:

Bug Metric


The graph below shows the number of bugs recorded in the past 10 iterations which we have completed.

Left

Number of Bugs Found


From the graph, you can see that:

  • There was a steep increase in the number of bugs found in Iteration 9 our team conducted our first User Testing in iteration 9. The bugs were discovered by the 13 users who tested our platform and reported in our User Test results.


  • Also, as there was insufficient time for us to solve all the bugs, 4 bugs were carried forward from Iteration 9 to 10.


The Bug Metric Severity Chart below shows the severity scores of the bugs recorded in the past 10 iterations which we have completed.

Left

Bug Metric Severity Chart


This graph shows the corresponding severity score with the number of bugs found.

Again, the impact was the highest in Iteration 9 because of the results from User Testing 1.


Links:


Project Risks

Risk Risk Description Impact Impact Level (Low/Med/High) Likelihood Level (Low/Med/High) Mitigation Strategy Status
Project Management Risk
1 Self-initiated project does not provide us with the required set of requirement for our project scope Scope of Project Scope High High To conduct Usability Testing to gather user's feedbacks and suggestion on what they want for the project. Mitigation strategy in force
Acceptance Risk
2 End user's unwillingness to switch to our platform for managing of their projects Project will be useless High High The need to create a user-intuitive platform for ease of use to attract end users Mitigation strategy in force



Technical Complexity

Technical complexity are listed in the order of highest complexity:

S/No Description
1. Customization of Task List Calendar with 3rd Party (Full Calendar)

What is this feature about?

  • A calendar where users can keep track of their current tasks and events, members of a group can also schedule tasks for other members.


How is it complex?

  • The 3rd party application, Full Calendar provided libraries that did not really suit our needs.
  • Customization of the libraries:
    • Created pop-ups when users click on the task/event on the calendar
    • Implemented date and time picker when user creates a task
    • Created context menu – when user right clicks the task they have the option to delete the task
2. Uploading of Google Docs

What is this feature about?

  • Integration of Google Docs/Drive with our platform so that users can Create, Read, Update and Delete (CRUD) Google Docs and files in their Google Drive folder directly from the platform.


How is it complex?

  • The latest version of Google API is Google Docs List API 3.0 – which is for Chrome apps. Since we’re not doing a Chrome app, we had to implement Google Docs List API 2.0. There were few instructions or help available on the implementation of this API.
3. Integration of Google Docs and Minute Taker

What is this feature about?

  • As we aim to provide a one-stop platform, our platform needs to provide a way for users to upload their minutes into the Google Drive (which can then be viewed on our platform). To do this, we need to integrate Google Docs/Drive with Minute Taker so that minutes that the users create will automatically by converted to a PDF document and will be saved in the user's Google Drive folder.


How is it complex?

  • Google introduced resumable protocol to replace uploading of files, this protocol consists of posting a request to Google in order to retrieve a unique upload URL. Using this URL, you will then need to implement a Put request to upload the file. As compared to the original API, which simply uses the "insert" method. Due to our lack of experience in dealing with HTTP requests and responses, we require more time to research and implement this integration.



Quality of Product

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes
Metrics
Proposal/Powerpoint Document
Requirements User Interface - Storyboard
Website (Live)
Analysis Use Case Diagram
Sequence Diagram
Design ER Diagram
Logical Diagram
Class Diagram
Deployment Diagram
Architecture Diagram
Testing Pro-cept Test Case
User Testing Documents
User Testing - Criteria List



Deployment

  • Staging & Development Environment: Deployed on VMWare at IS480 Server
  • Database: MySQL
  • Web Services: Google RESTFUL webservices
  • Web Links: View our Deployment Diagram Here!



Testing



Reflection