Difference between revisions of "IS480 Team wiki: 2011T1 Ascension/Ascension Finals Wiki"
Wk.peh.2009 (talk | contribs) |
Wk.peh.2009 (talk | contribs) |
||
Line 524: | Line 524: | ||
− | + | [[Image:Ascension ClientEmail.png| 800px]] | |
|} | |} |
Revision as of 15:23, 20 November 2011
Contents
Ascension Finals Wiki
This is Ascension's Finals Wiki page. Click to return to our team's Main Wiki Page.
Project Progress Summary
Project Highlights
Milestone E - Iteration 8
Why do we have a milestone directly after only 1 iteration? This is because iteration 8 which happens in recess week means that we would have the most time to work on our project. The speed of our development and the amount completed by end of this iteration would have high impact and effect on our planning of functionalities and the amount of stuff we can do, leading towards final presentation.
As the hosting manager of Sanctuary house does not allow installation of tomcat apache, we have to use alternative methods. We got a server from Sanctuary House and deployed our reporting server on it, integrate it with our current deployment at the hosting manager. We spent much time on it, to and fro Sanctuary House and was glad that by end of iteration, we already resolved this issue.
1. Changes from UAT C a) Progress report UI b) Android Contingency Plan (master resend and connection switch off)
3. Development Report
*Highlighted in red are functions that are fully completed. |
From mid term to final, the highlights of the project progress is as follows:
1. One Other info |
Project Challenges
We have faced strong challenges as we embark on this project.
Challenges can be summarized in the following.
Handling Android programming was definitely not easy as I have thought. On the contrary, it has gotten me stuck on many occasions because I simply have no idea how to code that particular function. What seems easy to do on the web becomes painstaking difficult when coding on the mobile platform. In addition to JAVA programming, the user interactions such as swiping left or right have to be handled. Moreover, coming up with an intuitive user interface on a mobile platform is very challenging. I am faced with not only space constraint but also the difficulty of presenting information or buttons in such a way that makes it easy to understand instantly. Integrating both user-friendliness with required functions was no mean feat. I am glad that in the process of learning, I have found and adopted a new form of learning methodology.
Team management was a difficult thing i face in this project. Different people have different expectations and their words mean different things. Hence, to ensure that things get on hand, i have to communicate differently with different people to get things done in the expected manner. Thus it was very important to keep open communication and bring about differences as soon as i realized it on table for everyone to discuss and resolve them.
|
Project Achievements
Content here |
Project Management
Project Schedule (Plan vs Actual)
Iterations | Planned | Actual | Schedule Metric | Comments | |
---|---|---|---|---|---|
1 | 1. Requirements gathering
2. Mock up on web-front |
12th May | 12th May | 1.0 | On Time |
2 | 1. Requirements gathering
2. Mock up on Android and Management Portal |
28th May | 28th May | 1.0 | On Time |
3 | 1. Revision of mock up
2. Finalized and developed web front 3. Proposal Submission |
21st June | 21st June | 1.0 | On Time |
4 | 1. Refinements of tracking module requirements
2. Developed node dollars, comment and MCQ 3. Report algorithm refinements 4. UAT A |
22nd July | 22nd July | 1.0 | On Time |
5 | 1. Developed Supermarket
2. Developed Traffic Management 3. Progress Report – Half completed 4. UAT B – Acceptance Presentation |
12th Aug | 12th Aug | 1.6 | The other half of progress report could be developed in time due to the learning curve in BIRT. We rescope after acceptance as the project idea was not focussed. |
6 | 1. Developed scenario and prioritization module
2. Developed progress report configurations 3. Improvements on Traffic |
2nd Sep | 2nd Sep | 1.0 | On Time |
7 | 1. Developed maze configurations
2. Completed Progress Report 3. Completed UAT C – Mid term presentation 4. Implemented Swype function |
29th Sep | 29th Sep | 1.0 | On Time. Replaced speech to text with swype function. |
8 | 1. Changes from UAT Feedback
- Traffic Management refreshing page issue - Report UI - Android contingency plans 2. Integration of instant messenger 3. Development Report |
15th Oct | 15th Oct | 1.0 | On Time. |
9 | 1. Android UI
2. Operations Report 3. Customization of Instant Messenger with traffic management |
25th Oct | 25th Oct | 1.0 | On Time. Shift the designing of poster from iteration 11 to this iteration. |
10 | 1. Testing
2. Day in a life workshop 3. Completion of project 4. Android Interface Enhancement |
11th Nov | 11th Nov | 1.0 | On time. All UAT except Noel has been completed. UAT with Noel scheduled on 14th Nov. |
11 | 1. Poster
2. Preparation for Presentation |
21st Nov | 21st Nov | 1.0 | On time. Presentation slides done. presentation date scheduled on 24th Nov, 4pm. |
Project Metrics
Schedule Metrics Description here
|
Bug Metrics Description here
Click to access our Bug Log |
Technical Complexity
The following are ranked accordingly to the level of difficulty. 1. Pushing of automated messages from the backend portal to Android Application. This includes the difficulty in trying to understand the push architecture of the technology, manipulating the data received and troubleshooting integration issues. 2. The need to integrate Instant Messenger with Traffic Management and Android Application. 3. Difficulty in retrieving the alarm set in database, configuring the alarm countdown timer and elapsed time in different pages and getting them to sync with each other. 4. Flexible adjustment of scores and weightages if student did not attempt the module. 5. Using BIRT technology to produce intuitive and flexible charts. 6. Algorithm behind the overall maze lapse timing to push suggestions to Traffic Manager. |
Quality of Product
Project Deliverables
Content here |
Quality
Content here |
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
UAT D We have conducted 4 sessions of UAT D with our clients, past facilitators and potential facilitators of the project.
Total Number of testers: 20 Total Number of potential facilitators: 10 Total Number of facilitators: 5 Total Number of executives: 5
Interview style UAT is employed to get more precise user feedback and understand business gaps.
1. Potential Facilitators: 1 hour. Scope on Android tablet and Traffic Management 2. Facilitators: 2.5 hours. Scope on Android tablet and Traffic Management 3. Executive: 2.5 hours. Scope on Management Portal (Configuration, TM, Report)
Facilitators: Went through the maze in July as facilitators. Executives: YDC main committee. Responsible for planning and execution of the maze.
|
Reflection
Team Reflection
We have come a long way since April this year.
We started off understanding and mapping the requirements from their business process and scenario. It was really difficult. Just as how it was difficult for both our supervisor and reviewer to understand, we met the same problem then. Eventually, we have to come out with technical solutions to resolve the business issues, which are hindsight, i do not know how did we achieve it.
During the requirements stage of our presentation, we needed more sessions to understand and map requirements. However, the extra amount of time was difficult as our clients were all working. We resolved this with the clients through a set of procedures to talk to different owners on different portions of the project and took on our initiative to propose and suggest options.
Throughout the project, we faced many difficulties ranging from Android, BIRT, Instant Messenger, deployment and many integration issues. One of those were our wrong deployment to realizing that the actual deployment with hosting manager does not support Tomcat Apache. We eventually resolve it through much communication with the hosting manager and our clients. We decided to re-use one of Sanctuary House server to publish and deploy our report server. Subsequently, as we are implementing our Instant Messenger, we needed to test the broker and port which took place on many nights (as late as till 4am).
We have our differences, disagreements over the course of 7 months, be it the technical aspect, project management, scope, datelines and many other different things we probably find it difficult to remember. But, we always make it a point to talk things out, understand each other and recover from it. Learning how to work together is an important lesson that we all have mastered. A good testament of our relationship is that after going through so much together, we are sticking together as we bid our modules together for next semester to continue working with one another. What really kept us together throughout the 7 months was one important thing that we have done at the start.
We lay out our common objectives, learning points and targets for the project, and when tough times occurs, we always remind ourselves of our goal to be one of the top project and continue to push on! All the way! |
Individual Reflection
Ng Choon Teck
I am so proud that we have completed the project at this stage. At one point it seems to me that it was an uphill struggle.
Honestly, I never thought and could imagined our product being the way it is. Absolutely amazing stuff.
|
Au Cheong Hing
This entire journey has been incredibly enriching for myself. There have been tough times and enjoyable ones of which many of these events has values and lessons to be drawn out of it. I remember the time when most of the members in the team were unhappy with the size of the scope. We felt that it was too big to handle given the amount of resources we had. I personally felt that we did not give ourselves enough time to perfect our solution. But then we learnt together as a team and worked the scope together. We also reduced risk very well by attempting all the unknown early and give ourselves time for progressive learning. For example, I started on BIRT technology early for simple text reporting. Thereafter, I moved on to chart creation using BIRT technology as well. Because BIRT is open source and is an unfinished product, there are many areas which I have to find an alternative solution to my problems. Furthermore, my business scenario is more complex than a simplistic sales figure reporting. All in all, I think I gained a lot in learning to learn, to be sensitive to the larger picture when I am confronted by a scenario and decision making. |
Chen Jun Fan
It has been a long journey since we started from April this year. This FYP project has pushed us to our limits, and made us realize that nothing is technologically impossible. Many a times, when a new suggestion is raised up by our PM to improve our system, we are always bounded by our individual technical capabilities, and would deem the suggestion impossible to be accomplished. However, in the end, most of these ‘impossible’ suggestions became the most value-adding functions of our system.
|
Chee Jing Hui
Tough times don’t last but tough teams do. I guess this sums up what I have thought of this team. We have certainly gone a long way. Like any other teams, we have had disagreements over the scope, functions, user interfaces etc. However, one thing that stands out is that at the end of the day, we will always come together and resolve these issues. And though each one of us has different responsibilities, we will always help one another in troubleshooting problems even if it falls outside of our own scope.
|
Peh Wei Kiat
Reflection here |
Prof Comments
Reflection here |
Client Commments
Didn't have the chance to say it yesterday, (it' so not "me" to say these out in words actually), but I just thought that I should have let the team know about this.. Sincerely a big thank you for a great job on this initaitive. Many thoughts and details have been put in, it's quite obvious - especially when there are initiatives that it's really "we don't know what we don't know" cataology kind of suggestions. (Example, the suggestion when >=50% of the maze is in the red alert, suggestions are prompt, little details like the keyboards of the android apps, drill down graphs etc) I guess it's the last milestone and last few weeks of this FYP project. Thanks guys, and sincerely; it's finishing so, hang it there. (: |