Difference between revisions of "IS480 Team wiki: 2013T1 Kungfu Panda Technologies"
Jump to navigation
Jump to search
Yh.koon.2010 (talk | contribs) |
Yh.koon.2010 (talk | contribs) |
||
| Line 39: | Line 39: | ||
| style="background: #000000; color: #FFFFFF;text-align: center;" | <b>Link</b> | | style="background: #000000; color: #FFFFFF;text-align: center;" | <b>Link</b> | ||
|- | |- | ||
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | 1 |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | Frontend |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | [[Image:]] |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | |
|- | |- | ||
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | 2 |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | Frontend |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | [[Image:]] |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | |
|- | |- | ||
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | 3 |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | Frontend |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | [[Image:]] |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | |
|- | |- | ||
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | 4 |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | Frontend |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | [[Image:]] |
| − | | style="background: # | + | | style="background: #FFFFFF;text-align: center;" | |
|} | |} | ||
| + | |||
== Front-End: Design & Technology Considerations== | == Front-End: Design & Technology Considerations== | ||
<strong>Single Page Application</strong> | <strong>Single Page Application</strong> | ||
Revision as of 19:27, 24 November 2013
.PNG)
References: Technologies Used
| No | Frontend/Backend | Technology | Link |
| 1 | Frontend | [[Image:]] | |
| 2 | Frontend | [[Image:]] | |
| 3 | Frontend | [[Image:]] | |
| 4 | Frontend | [[Image:]] |
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
