HeaderSIS.jpg

IS480 Team wiki: 2010T2 B.I. JOE

From IS480
Jump to navigation Jump to search
FYP Logo.png
FYP Title.jpg




Final Wiki Page

Go straight to our [Wiki Page]

Team B.I.JOE

in collaboration with Integrated Distribution Services

Bi-joe-intro.png

Members


Bi-joe-members.png

Role Responsibilities


Bi-joe-role-responsibilities.png

Role Allocation


Prior coming together as a team, everyone has little or some working relation with one another. However, the team knows what is installed for them during this FYP. As such, we have decided to adopt the best fit model approach for role allocation in the team.

Using the best fit model, the team evaluated every individual on their strengths and limitations. With an open-minded environment and culture, everyone in the team shared their experiences and challenges. At the end of the sharing, the team sat together and evaluate how everyone can leverage on each other's strengths and compliment each other's shortcomings.


Project Overview

Project Title: Geospatial Dashboard for Integrated Distribution Services Analytics

Stakeholders


Bi-joe-stakeholders.png

IDS Background


Bi-joe-ids-bg.png


Current AS-IS Model


AS-IS-MODEL-UPDATE.png



TO-BE Model


TO-BE-MODEL-UPDATE.png



Objectives

Bi-joe-objective.001.png

Project Technical Specifications

Bi-joe-technical-specs.png

Project Management

Use Case

Bi-joe-use-case-visualization.png


Bi-joe-use-case-geodata-connection.png


Bi-joe-use-case-geospatial.png


Logical Diagram

Bi-joe-logical-diagram.png


Deployment Diagram


Bi-joe-deployment-diagram.jpg


Scalability Design


Bi-joe-scalability-design.jpg


Class Diagram

Bi-joe-class-diagram.jpg


System Architecture

Bi-joe-logical-diagram.png


Project Metrics


Bug Tracking


Schedule Tracking


Current Project Status

  • Completed



Project Schedule


Bi-joe-iteration 1.jpg


Bi-joe-iteration 2 and 3(add-on).jpg


Bi-joe-iteration 2 and 3.jpg


Bi-joe-iteration 4 and 5.jpg


Bi-joe-iteration 6 and 7.jpg


Bi-joe-iteration 8.jpg


Team Calendar

Click here to find out


Project Documentation

Project Proposal

Click here to download

Project Resources


FYP Resources.png
  • Development Environment: Flash Builder 4, Notepad++
  • Test Environment: Firefox, Chrome with Flash Player
  • SDK & Language: FLEX 3.5 (AS3), PHP
  • Libraries & APIs: Modest Map, Flare, Juicekit for Visual Analytics
  • Deployment: XAMPP
  • Database: PostgreSQL, PostGis
  • Project Management: MS Office, Google Cal, Google Docs, Dropbox, Subclipse
  • Graphics: Photoshop


Useful Resources

  • How to understand and read a treemap. [1]



Challenges Faced


Bi-joe-challenge.png


Team Reflections and Learning Outcomes


Bi-joe-learning-outcome.png


Project Supervisor Meeting Minutes


DECEMBER

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 22 December 2010 Supervisor Meeting 01 * Re-arrange project acceptance presentation
* Improve on the technical specifications


JANUARY

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 13 January 2011 Supervisor Meeting 02 * Upload all documentations on Wiki page
* Firm up project specifications with the client
* Do a video recording of the video conference with IDS Hong Kong
2. 21 January 2011 Supervisor Meeting 03 * Follow up with the suggestions made by Supervisor


FEBRUARY

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 11 February 2011 Supervisor Meeting 04 * Send a copy of Mid Term Presentation slides to Supervisor by 14 Feb


MARCH

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 9 March 2011 Supervisor Meeting 05 * Reflect improvements suggested and discussed
2. 11 March 2011 Supervisor Meeting 06 * Reflect improvements suggested and discussed
3. 18 March 2011 Supervisor Meeting 07 * Reflect improvements suggested and discussed
4. 25 March 2011 Supervisor Meeting 08 * Finish up on the poster design
* Begin conducting of UAT


APRIL

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 8 April 2011 Supervisor Meeting 09 * Update the slides accordingly

Project Sponsor Meeting Minutes


DECEMBER

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 23 December 2010 Client Meeting 01 * Amend project requirement and schedule


JANUARY

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 5 January 2011 Client Meeting 02 * Client will send the necessary data and data structure to the team
* Schedule a video conference with IDS stakeholders
2. 12 January 2011 Client Meeting 03 * Client will be following up with the requests from the team
3. 19 January 2011 Client Meeting 04 * Include improvements and suggestions provided by Client
4. 26 January 2011 Client Meeting 05 * Schedule an internal meeting to re-discuss on the feedbacks provided by the Client and how the team can work on the inputs


FEBRUARY

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 2 February 2011 Client Meeting 06 * Prepare video conference presentation schedule and deliverables
* Request for additional data to bring up database
2. 7 February 2011 Client Meeting 07 * Hold an internal meeting within the team to follow up with the requests from IDS Hong Kong
3. 9 February 2011 Client Meeting 08 * Decide to decline the request of changing the development application to be iPhone and iPad ready
4. 14 February 2011 Client Meeting 09 * Improvements must be reflected before mid term presentations
5. 23 February 2011 Client Meeting 10 * Improvements must be reflected before mid term presentations


MARCH

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 2 March 2011 Client Meeting 11 * Bugs are found in the system by project sponsor.
* Rectify the problems
2. 9 March 2011 Client Meeting 12 * Work on the inputs provided by the project sponsor
3. 23 March 2011 Client Meeting 13 * Note the next video conference with IDS
* Reflect the changes shared wand discussed with the project sponsor


APRIL

S/N Date Detailed Minutes Download Follow Up Actions from Meeting
1. 6 April 2011 Client Meeting 14 * Reflect changes and fixes bugs found in the application

Design Considerations

Design Consideration