Difference between revisions of "IS480 Team wiki: 2013T1 Kungfu Panda Technologies"
Jump to navigation
Jump to search
Yg.tan.2010 (talk | contribs) |
Yg.tan.2010 (talk | contribs) |
||
Line 61: | Line 61: | ||
<br/> | <br/> | ||
<strong> Integration with Front-End </strong> <br/> | <strong> Integration with Front-End </strong> <br/> | ||
+ | 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. | ||
<br/> | <br/> | ||
[[Image:communication-model-teller.png]] | [[Image:communication-model-teller.png]] |
Revision as of 13:22, 16 August 2013
Front-End
Front End: 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
Front End: Reasons for Client-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
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_Withdrawal_Create