HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2011T1 Aperture - Final-Term Wiki"

From IS480
Jump to navigation Jump to search
Line 169: Line 169:
 
===<span style="color: #797979; padding: 0px 30px 0px 29px;">Testing</span>===
 
===<span style="color: #797979; padding: 0px 30px 0px 29px;">Testing</span>===
 
<div style="border-left: #797979 solid 12px; padding: 0px 30px 0px 18px; font-family: Arial, Helvetica;">
 
<div style="border-left: #797979 solid 12px; padding: 0px 30px 0px 18px; font-family: Arial, Helvetica;">
TEXT TEXT
+
<b>Back end tests</b><br />
 +
<<Description and instructions by Raymond>>
 
<br /><br />
 
<br /><br />
TEXT TEXT
+
<b>Front end tests</b><br />
 +
<<Description and instructions by Kenneth>>
 
<br /><br />
 
<br /><br />
 
</div>
 
</div>

Revision as of 17:33, 19 November 2011

Pivotalexpert2-aperture-wiki-finalwikiupdate-header-v01-700px.jpg





Project Progress Summary

Project Highlights

  • The previous team's code had quite a few issues. So we had to start building the application from scratch.
  • Client suggested that we explore Angular JS for our front-end views. We divided the team into 2 separate teams. The front-end team would develop the views, while the back-end team developed the models and controllers.
  • PayPal required us to have a live application before allowing us to create a live PayPal account for Pivotal Expert.
  • We met Andy Croll, a talented designer, for his feedback on the design and usability of our website.
  • Project Management
    • The front-end team took 7 weeks to learn Angular JS, which was much longer than expected.
    • We did not account and plan for a number of functionalities when we decided to build the application from scratch. In addition, The difficulties of several tasks were underestimated. In other words, we allocated too few points to tasks. This resulted in an overly-optimistic schedule. Eg. Completing basic functionalities by week 4.


Project Challenges

Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.

  • TEXT TEXT
  • TEXT TEXT


Project Achievements

Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.

  • TEXT
  • TEXT


Project Management

Project Schedule (Planned vs Actual)

Planned Project Schedule

LINK Planned Project Schedule Page
3.. Project Management
3.1.. Planned Project Schedule
3.1.1.. Planned Project Timeline
3.1.2.. Planned Project Iteration Breakdown

Actual Project Schedule

LINK Project Management - Actual Schedule Page
3.. Project Management
3.2.. Actual Project Schedule
3.2.1.. Actual Project Iteration Breakdown

Project Metrics

Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.

Technical Complexity

  • TEXT TEXT
  • TEXT TEXT


Quality of Product

Project Deliverables

S/N Stage Specification Modules
1. Project Management Minutes

Project Summary - Minutes Repository Page

Metrics

Main Page - Velocity Metrics, Main Page - Bug Metrics

2. Client's Requirements List of functionalities Project Overview - Client Requirements Page
3. Analysis Use case

Main Page - Use Case, Project Overview - Use Case Description Page

4. Design Class Diagram <<Upload doc by Daniel/Raymond>>
5. Testing UET test results <<link to User Experience Testing (UET)>>
System tests <<link to "Testing" section below>>
6. Handover Deployment Instructions <<link to "Deployment" section below>>

Quality Achieved

<<link to midterm wiki "Quality Achieved">>

Testing

Back end tests
<<Description and instructions by Raymond>>

Front end tests
<<Description and instructions by Kenneth>>

Deployment

TEXT TEXT

TEXT TEXT

Reflection

[ TEAM ] Aperture

TEXT TEXT

TEXT TEXT



[ INDIVIDUAL ] Mark Chen

TEXT TEXT

TEXT TEXT

[ INDIVIDUAL ] Robert Chai

TEXT TEXT

TEXT TEXT

[ INDIVIDUAL ] Kenneth Kok

TEXT TEXT

TEXT TEXT

[ INDIVIDUAL ] Daniel Tsou

TEXT TEXT

TEXT TEXT

[ INDIVIDUAL ] Raymond Chua

TEXT TEXT

TEXT TEXT



[ SPONSOR ] Comments

TEXT TEXT

TEXT TEXT

Project Sitemap