Risk aware design: using CORA to investigate an IT solution Written by Léon Smiers |  | 
Introduction There are different reasons for using the CORA model to define the current and future state of an IT landscape, the most important one being able to identify risk areas which help to:
No matter what the objective, using the CORA model helps in clarifying the solution related to the Software Architecture and spot the risk areas. In order to get a quick understanding of the area under investigation, workshops facilitated with the CORA model are very usefull.
|
'Why' Driven Solution craftingWritten by Léon Smiers | |
Introduction Doing audits as a Solution Architect is very instructive for the daily routine of solution crafting. It boils down to the same question over and over again: why did you make this choice? What is the reasoning behind the solution? Too often we realize that there is a gap between Architecture and the Software solution. Grasping the rationale behind a proposed solution is essential because it ensures traceability all the way from achitecture down to the implementation details. It also helps to identify the risk areas which can help improve the predictability of the implementation project and/or program we are working in. Finally it helps to check whether the proposed solution is complete, if we made the right choices regarding possible reuse and if the functionality is available 'out-of-the-box' or do we have to build it from scratch.
|
- CORA Methodology, playing with Lego
- The roadmap for Fusion Applications, CORA is there to help
- Technovisions "Sector-as-a-Service" mapped
- Business Logic and the CORA Model, Part II
- CORA and Cloud Computing: Static versus Dynamic View
- Technovisions "Thriving on Data" mapped
- CORA Foundation
- Business Logic and the CORA Model, Part I
- CORA and IBM
- CORA and Microsoft
- CORA and Cloud Computing: Overview
- Technovisions "Process-on-the-Fly" mapped onto CORA
- Risk aware design: using CORA to investigate an IT solution
- A ROA based iPhone App for SAP: Part II
- A ROA based iPhone App for SAP: Part I
- Technovisions "We Collaborate" mapped onto CORA
- SAP platform decomposition with CORA: SOA/ROA style
- 'Why' Driven Solution crafting
- CORA and TOGAF
- SAP platform decomposition with CORA: N-tier style
- Requirements for CORA
- CORA and Oracle
- Technovisions "You Experience" mapped onto CORA
- CORA and SAP
- CORA in action: design guidelines to implement repositories
- The basis of all, your data
- CORA and IAF
- Technovision and CORA - Overview
- The importance of an Integration layer
