IS480 Team wiki: 2013T1 Kungfu Panda Technologies
Revision as of 20:46, 24 November 2013 by Yh.koon.2010 (talk | contribs) (→References: Technologies Used)
References: Technologies Used
No | Frontend/Backend | Technology | Link |
1 | Frontend | http://www.oracle.com/technetwork/java/javase/downloads/index.html | |
2 | Frontend | http://jquery.com/ | |
3 | Frontend | http://getbootstrap.com/ | |
4 | Frontend | http://backbonejs.org/ | |
5 | Frontend | ||
6 | Backend | ||
7 | Backend | ||
8 | Backend | ||
9 | Backend |
Front-End: Design & Technology Considerations
Single Page Application
- Reusable Codes
- More responsive application
- Reduce load on Server
- HTML loading etc.
Reasons for Client-Side Technologies Used
- MVC for client side code
- Making javascript codes modular
- Backbone’s Router
- Detects change in URL, which is needed in a SPA
- Big community for open source support
- Templating made easy with Underscore JS
- Stubs are easy to create with backbone’s Model
Reasons for Server-Side Technologies Used
- Simple interface with Service Mediation that uses TIBCO JMS
- Low learning curve
- Open-Source libraries that provide easy conversion from JSON to XML (vice-versa)
Back-End: Technical Complexity
Communication Model
This model depicts how messages are sent to and fro from our Bank Teller Application (Frontend) through the Enterprise Service bus to retrieve / store information in the database.
Integration with Front-End
This diagram shows the translation in message formats within our Teller Application which is used to interpret a SOAP Response or create a SOAP Request message.
Sample Backend Tibco Service
Service: Transaction_PartialLoanRepayment_Create
Entity-Relationship Diagram for SMU Core Services Database