Difference between revisions of "IS480 Team wiki: 2013T1 Kungfu Panda Technologies"
Jump to navigation
Jump to search
Yg.tan.2010 (talk | contribs) |
|||
Line 28: | Line 28: | ||
<br> | <br> | ||
[[Image:KP-TechnologiesUsed.png|837x466px|center]] | [[Image:KP-TechnologiesUsed.png|837x466px|center]] | ||
− | == Front-End== | + | |
− | <strong> | + | == References: Technologies Used==<br/> |
+ | |||
+ | == Front-End: Design & Technology Considerations== | ||
+ | <strong>Single Page Application</strong> <br/> | ||
*Reusable Codes | *Reusable Codes | ||
Line 39: | Line 42: | ||
− | <strong> | + | <strong>Reasons for Client-Side Technologies Used </strong> <br/> |
*MVC for client side code | *MVC for client side code | ||
Line 53: | Line 56: | ||
*Stubs are easy to create with backbone’s Model | *Stubs are easy to create with backbone’s Model | ||
− | <strong> | + | <strong>Reasons for Client-Side Technologies Used </strong> <br/> |
− | *Simple interface with Service Mediation that uses | + | *Simple interface with Service Mediation that uses TIBCO JMS |
*Low learning curve | *Low learning curve | ||
Line 61: | Line 64: | ||
*Open-Source libraries that provide easy conversion from JSON to XML (vice-versa) | *Open-Source libraries that provide easy conversion from JSON to XML (vice-versa) | ||
− | == Back-End== | + | == Back-End: Technical Complexity== |
<strong>Communication Model </strong> <br/> | <strong>Communication Model </strong> <br/> | ||
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. <br/> | 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. <br/> | ||
Line 81: | Line 84: | ||
<br/> | <br/> | ||
<br/> | <br/> | ||
− | |||
<br/> | <br/> | ||
− | <strong> | + | <strong>Entity-Relationship Diagram for SMU Core Services Database</strong> |
<br/><br/> | <br/><br/> | ||
[[Image:KP-Core Services ER Diagram.png|769x1054px]] | [[Image:KP-Core Services ER Diagram.png|769x1054px]] |
Revision as of 15:17, 24 November 2013
== References: Technologies Used==
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 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: 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