HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2011T1 Ascension/Ascension Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 152: Line 152:
 
<<Graphs here>>
 
<<Graphs here>>
  
Refer to our [[IS480_Team_wiki:_2011T1_Ascension#Project_Metrics | Main Metrics]] to see how we calculate the scores and their respective action plans.
+
To see how we calculate the scores and their respective action plans, click to view our [[IS480_Team_wiki:_2011T1_Ascension#Project_Metrics | Main Metrics]].
 
 
  
 
====Project Risks====
 
====Project Risks====

Revision as of 16:26, 28 September 2011

Ascension Midterm Wiki

Project Progress Summary

Project Highlights

Project Management

Project Status

Completed

System Function Status Confidence Level
Management Portal TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT
Operations Tracking Application (OTA) TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT


Work-In-Progress

System Function Status Confidence Level
Management Portal TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT
Operations Tracking Application (OTA) TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT
TEXT TEXT TEXT

Project Schedule (Plan Vs Actual)

Iterations Planned Actual Comments
TEXT TEXT TEXT TEXT TEXT TEXT
TEXT TEXT TEXT TEXT TEXT TEXT

Project Metrics

Schedule Metrics

<<Graphs here>>


Bug Metrics

<<Graphs here>>

To see how we calculate the scores and their respective action plans, click to view our Main Metrics.

Project Risks

Business Risk

Midterm Business Risk

Technical Risk

Midterm Technical Risk

External Risk

Midterm External Risk


Technical Complexity

The following are ranked accordingly to the level of difficulty.

1. TEXT

2. TEXT

3. TEXT

4. TEXT


Quality of Product

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes Ascension_Meeting_Minutes
Metrics Metrics
Presentation Slides Acceptance Presentation Part I

Acceptance Presentation Part II

LOMS Team LOMS

Individual LOMS

Requirements Functional Requirements Storyboard v1.0

Storyboard v2.0

Analysis Use Case Use Case v1.0

Use Case v2.0

Process Flow Diagram Process Flow Diagram
Solution Architecture Diagram Solution Architecture
Design ER Diagram Implementation Schema
Testing Test Plan Milestone A

Deployment

Our entire project (except the reporting module) has been deployed to Sanctuary house server.

To better understand our entire deployment, click to view our Deployment Diagram.


User Acceptance Testing

Our team has completed a total of 3 UAT.

UAT A


UAT B


UAT C


Refer to our Main Wiki to view the complete test plans and test results.

Reflection

Ng Choon Teck

It has been an incredible 4 months since we first embarked on our major project. I have never expected this entire thing to be so physically and mentally draining but yet so meaningful, vibrant and full of learning points. Working with Project Node as part of my CSP program for 2 years have made me realize how small a program can be grown into such a huge scale implementation. It has already been extremely touching just be seeing how our fruits of labour took off, and even having a trial on how our system would fit in the maze to better scope requirements back in July.


Working with clients that have no IT background, do not know exactly what they want, we ended up working on items repeatedly to meet the client demands. In the process of communicating with both clients, supervisor and team mates, I have learnt much on looking at things from different perspectives and bring communication in a concise manner to my team mates.


The end is near. We will continue to work towards meeting our goals in final presentation.


Au Cheong Hing

For myself, this project had been especially meaningful because of the history I share with the maze project. The NoDE project was a community involvement project(CSP) I was volunteering for during my first academic year. When the time came for sponsor selection for our IS480, this project was really suitable. Having been through the maze implementation, I am aware of the shortcomings and strength of the maze implementation. This understanding I have of the maze is precisely the reason why I am assigned the role of business analyst where I am to align the business needs of the maze with the technical delivery of our FYP team.


Chen Jun Fan

Through this particular project, I’ve learnt to work with different types of people. However, it was fun understanding each and every one of them, and tuning my working style to each individual. It is a different perspective of working as compared to other smaller scale school projects, as a large amount of accommodation has to be made for the team to progress.


I’ve also learnt the importance of communication and team work in this project. Without the constant encouragement from one another, we would not have gone thus far. I hope the remaining months will allow us to show greater team work and communication in completing this entire project.


Chee Jing Hui

Peh Wei Kiat

As the Design Analyst, I was tasked to handle all the aesthetics and usability of our product such as the web portal and management portal. I was given the chance to apply my design interest as well as learn to put myself in the users’ shoes to design an engaging and interactive user interface that they will enjoy using.


In the past few months of doing this final year project, not all has been smooth sailing. There were several challenges that occurred such as changes in user’s requirements and having to manage with the tight timeline. However, I managed to learn to adapt and cope with them.


One of the reasons that fuelled me on despite the challenges was the wonderful social cause behind what we are doing. I sincerely hope that our system will be able to help our client in facilitating the activities such as the maze so that out of it, the youths will be impacted and benefit out of the activity and our project.