CORA Methodology, playing with LegoIntroduction What is the impact of a business question on an IT landscape? The CORA model offers a layering model to help answering this question. But how does CORA determine this in practice? This is described in this blog by discussing the major steps to be taken in order to design an explainable and traceable solution in which we’re able to point out the risk areas, thus seeing the impact of the Business Question on the IT landscape. Within the many projects I used CORA as a starting point for creating IT solutions I discovered that a lot of these solutions are based on the same combination of CORA-elements. I call these combinations "CORA patterns", and because they are re-usable I'll introduce the "CORA pattern library", being a major part of the CORA Methodology. |
- 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


