Portal architectural decisions
Regardless of the adopted development methodology from an architectural perspective, it is must to document architectural decisions for the infrastructure and application domains. This document provides a rationale and justification as to decisions being made on architectural items and helps the team to have a clear vision of each item discussed. There is also the benefit of traceability to how and when the decision was made, and the respective reviewers and approvers. In the following table, we will point out the high-level architecture decisions' topics documented for A2Z Bullion Bank portal:
High level |
Low level | |
---|---|---|
1 |
IBM WebSphere Portal and Mobile Capabilities |
Utilize portlet-to-portlet and event-driven communication |
2 |
IBM DataPower for service-oriented architecture (SOA) realization |
Utilize Session Initiation Protocol (SIP) for telephony integration. |
3 |
Utilize the cloud for agile infrastructure |
Global and portlet session size decisions |
4 |
Utilize... |