Difference between revisions of "2010T2 B.I. JOE : Final Presentation"

From IS480
Jump to navigation Jump to search
Line 4: Line 4:
[[Image:Bijoe - jessica-highlight.jpg|900px|center]]
[[Image:Bijoe - jessica-highlight.jpg|900px|center]]
* List of requirement changes
* Additional requirements in Iteration 7
** Control Chart
** Apply config file to deployment architecture
===<div style="background: #b8ffef; padding: 12px; font-weight: bold"><font color="black" size="4" face="hobo std">Project Challenges</font></div>===
===<div style="background: #b8ffef; padding: 12px; font-weight: bold"><font color="black" size="4" face="hobo std">Project Challenges</font></div>===

Revision as of 04:20, 12 April 2011

Project Progress Summary

After Mid Term Presentation, reviews from various stakeholders were collated and reviewed within the team. Improvements and changes were made to different segments of the system. Towards the end of the development, a series of User Acceptance Tests were conducted. The purpose is to ensure the system is fully functional ready for deployment and handing over to the client. At the same time, we would make use of this opportunity to further enhance the user interface design of the application. The project is well managed and completed on time. The stakeholders are satisfied and pleased with the deliverables.

Project Highlights

Bijoe - jessica-highlight.jpg
  • Additional requirements in Iteration 7
    • Control Chart
    • Apply config file to deployment architecture

Project Challenges


Project Management

Project Scheduled (Actual vs Planned)


Project Metrics

Schedule Metric v2.png

Project/Technical Complexity

Quality of Project

Project Deliverables

Stage Specification Modules
Project Management Minutes Weekly Sponsor meetings | Weekly Supervisor meetings
Metrics Bug metrics | Schedule metrics
Requirements Story cards Storyboard scene
Technical specifications Technical specifications
Analysis Use case Overview
Sequence Diagram (Core) Linked View (View Data), Image Coverflow
Business Workflow Diagram 1,2,3,4,5
Screen Shots CRUD Customer, Trend Analysis
Design Logical Diagram Overview
Class Diagram Overview | Detail
System Architecture Structure
Testing Test plan Test scripts for Iteration 2, 3, 4, 5, 6 and 7
UAT UAT Script | Result
Heuristic Evaluation Script | Result
Handover Manuals User tutorial, Developer manual, Setup manual
Code client server
Deployment Diagram Diagram | Instructions


Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.


To access the application online, please visit this deployment link

BIJoe current deployment.PNG

The diagram above shows the current deployment methods. Basically everything is being host on one server which contains Apache 2.2 commanded from XAMPP and Postgis 9.0 extended from Postgres. However, as we have a configuration text file, it makes this deployment design highly scalable. Not only is this application scalable in hardware wise, it is also scalable in software. Even though we are uding Postgis as our database, client can also choose to use MySQL database to replace Postgis. The reason for choosing Postgis over MySQL in current case is because Postgis allows extension of calculating distance in geographical manner which allows functional scalability if the client would wish to extend this application. The diagram below illustrates the recommended deployment design to be used in the client's environment. The application server is being distributed even workload from the several load balance to prevent single point of failure. From there, the application server will be connected to a cluster of database to prevent any over utilization on the database as well.

BIJoe scalability design.PNG


Describe the testing done on your system. For example, the number of UAT, tester profile, test cases, survey results, issue tracker, bug reports, etc.


Team Reflection

Individual Reflection

Sim Sing Hong

Isaac Lim

After going through this FYP, which in my opinion is the most challenging and difficult module ever, there are a few points I would like to share. Initially, when I started off with Flex Builder, I thought this is a very difficult programming language which is very unusual thing that happens to me as I am quite competent in adapting new languages. In addition, Flex gave a weird logic way of coding as everything is able to go concurrently instead of the usual coding style where step A has to be done before step B. That really makes me feel uncomfortable. However, in the end, I would say that I have mastered it perfectly and finds it very user-friendly instead.

Secondly, as I progress my FYP, I advanced myself to a Dad as well. Up till the point before becoming a father, I always believe in balancing work-life. However, I feel that balancing work-life is impossible. Work-life integration seems to be the more feasible way. For example, I would do some calls home to my wife to settle some housing matters which in other words I am "controlling" my life from school or from work.

Last but not least, I would like to say that family is important! I can perfectly understand the meaning behind the movie 'Click' featuring Adam Sandler acting as a workaholic and neglecting family which in the end he regretted. Therefore, I have appreciate my family more than ever.

Ng Wei Quan

Tan Ying Da

Marcus Yap

Client's Comment