HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 Dynamic Crew Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 137: Line 137:
 
| align="center"| ER Diagram
 
| align="center"| ER Diagram
 
| align="center"| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Dynamic_Crew_Project_Documentation ER Diagram]
 
| align="center"| [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2012T2_Dynamic_Crew_Project_Documentation ER Diagram]
|-
 
 
| align="center"| Design
 
| align="center"| Use Case Diagram
 
| align="center"| [[IS480_Team_wiki:_2012T2_Dynamic_Crew_Project_Documentation|Use Case Diagram]]
 
 
|-
 
|-
  

Revision as of 03:55, 22 February 2013


Project Progress Summary


Project Progress

Dynamic Crew has progressed considerably slowly since our acceptance phase. We have been facing with several issues. Firstly, one of the members left the team during the most critical phase (Post Function and Home Page Design). In addition, the difficulty to meet up with our client appears to be another reason that contributes to our project slow progress since we could not clarify doubts and discuss about the project with the client. Besides, all of the team members are not familiar with Drupal, resulting in a steep learning curve. We have faced several technical challenges along the way as well.

We are approaching the 4th Milestone - Midterm Presentation. Before this, we managed to achieve the following tasks: Develop Post Function, Design the Home Page, Deploy to the client's production environment, Carry out User Testing 1.

Currently we are in the progress of developing the second core Function which is the Interactive Map. In the next iteration we will be developing the Search Function

Screen Shot 2013-02-21 at 9.46.57 PM.png


Project Highlights


ProjectHighlight.png


Technical Complexity


Tech1.png

Tech2.png


Project Management


Project Status


PS1.png

PS2.png


Project Schedule (Planned vs Actual)


Planned.png
DCChange1.png
DCChange12.png

Reason: One of the members left the team
'Schedule Changed: The estimated duration of Iteration 5 is extended for 10 days

DCChange2.png
Reason: One of the members left the team. Iteration 5 is extended for 10 days hence we will have to plan to drop 1 function so as to finish the project on time. Since the previous meeting with the client, we realized that the Analytic Function does not add values to the client.
Schedule Changed: Drop the Analytic Function.

DCChange3.png
Reason: Since the previous meeting with the client, we found out that the Interactive Map is quite a big task because it involves segregation based on countries, not based on continents as we expected.
Schedule Changed:Hence we decided to add another Iteration to develop the Interactive Map.

DCChange4.png
Reason: We want to test whether all the configurations and homepage design are compatible with the client's production environment.
Schedule Changed: Instead of waiting until the last iteration to deploy the system, we have moved the deployment forwards to Iteration 5. After developing the Homepage, we deployed our system to the client's production environment.

DCChange5.png
Reason: We would need the client's database in order to develop and test the next few interations
Schedule Changed: Instead of waiting until the last iteration to integrate with the client's database, we have moved the integration forwards to Iteration 6. After developing the Interactive Map, we will integrate our system with the client's database.

DCActual.png

SNF.png


Project Metrics


Schedule Metric: Dynamic Crew Schedule Metric
Bug Metric : Dynamic Crew Bug Metric


2.4. Project Risks


Visit our Risk Management Page: Risk Management Page


Quality of Product



Intermediate Deliverables

Stage Specification Modules
Project Management Meeting Minutes (Team, Supervisor, Client) Minutes Page
Project Management Metrics Metrics Page
Project Management Risk Management Risk Management Page
Analysis Use Case Use Case Diagram
Analysis UI Mock Up UI Mock Up
Design ER Diagram ER Diagram
Design System Architecture Diagram System Architecture Diagram

Deployment

Link to our website: WhitebandTest.org
After you access to the link please enter the following credentials:
Username: whitebandtest
Password: cfhf9abfuomc

Testing

We conducted two types of testing. One testing is using a fully guided test case fully guided test case for our client, another testing is using a less guided test case done by SMU students. The reason why we conducted the test with less guided test case to SMU students is to gather feedback on how easily used the website from the daily user's point of view.

We had 20 SMU students (10 SIS students and 10 non-SIS students) tested our system and filled up a questionnaire regarding our system
Test Plan : UAT 1 Test Plan
Questionnaire : UAT 1 Questionaire
Survey Results : UAT Result
UAT Comments : Client Comments, SMU Students Comments
Bug Reports : UAT Bug Report

Links to Usability Page


Reflection

Team Reflection