Using TOGAF- Part6- Information System Architecture-Application
In the context of Application Architecture (after previously covering DATA Architecture )using standard TOGAF was very helpful specific to certain steps such as
- Select Reference Models, Viewpoints, and Tools
- Review and Validate set of application principles.
- Select relevant applications architecture resources like reference models,
- patterns from the Architecture Continuum based on the Business drivers, and the stakeholders and concerns.
- Identify appropriate tools and techniques to be used for capture, modeling and analysis.
- Identify System/Functionality matrix.
- Target application interaction diagram and target application blocks.
we Revalidated Application Principles in the context of order and Buy such as
- Exploitation of Reusable Components
- Logical Separation of Components
- Loose Coupling of Applications and Components
- Virtualisation of Data Stores.
- Leverage a Common Skill base & Deploying Core Technologies.
- Use of Standards.
- Ease of Use.
- Designing for Change.
Develop Baseline Applications Architecture Description
Highlights of Current System (s):
- Current Existing System (s) is separate applications, with almost similar application architecture.
- Workflow is hard coded into the application code.
- Assessment Business Rules are also hard coded into the application code.
- Policy Administration system (s) as part of End of Day process generates a delta file containing changed policy details, which will be retrieved from predetermined file folder by the current Order and buy systems and policy details are entered into the system.
|
Abbreviation |
Name of Component |
Description |
|
CN |
Claim Notification |
Claim Notification is responsible for Entry of Claim Details in system, uploading of claim related documents and initiating workflow for claims |
|
CA |
Claim Assessment |
Claims Assessment includes services to validate claim details, in built business rules for assessing claims and compute the claim payments |
|
CP |
Claim Payment |
Claims Payment includes services functionality to sent the claim payment details to external payment systems for further processing |
|
CC |
Claim Closure |
Claim Closure includes services functionality to mark the claim as processed and closed |
|
CE |
Claim Exception |
Claim Exception includes services functionality for processing claims which can not be assessed. |
|
URM |
User Management |
User to define user profiles required for access permissions. |
|
CRD |
Claim Report and Dash Board |
Claim Reports and Dash board to generate reports about claims processing |
|
PA |
Policy Administration Systems |
Existing Policy Administration independent Applications |
|
PSF |
Payment Systems |
File Folder (s) of the Payment Systems which are external to the current system. |
|
DB |
Database |
Database to store the claims data |
|
File Folder |
File Folder |
System File Folder acting as claims document repository and to share the policy details file generated by policy management system (PA) with claims processing system. |
|
PD |
Policy Data |
Component responsible for loading the policy details from file generated by Policy Administration System. |
Business-Application Service Matrix is depicted below.
Develop Target Applications Architecture Description
Highlights of Target System:
- Target System is a single Application deployment for both Home and Motor insurance
- Claims (Insurance) Workflow in managed using a Business Process Management System.
- Claims (Insurance) Assessment Business Rules are configured, processed using Rule Engine.
- As part of End of Day process, Changed policy details will be pushed into the Claim System using ETL process.
- Document Repository will be used to handle the entire claim related document.
|
Abbreviation |
Name of Component |
Description |
|
CN |
Claim Notification |
Claim Notification is responsible for Entry of Claim Details in system, uploading of claim related documents and initiating workflow for claims |
|
CA |
Claim Assessment |
Claims Assessment includes services/web functionality to validate claim details (Using Rule Engine) and compute the claim payments |
|
CP |
Claim Payment |
Claims Payment includes services/web functionality to sent the claim payment details to external payment systems for further processing |
|
CC |
Claim Closure |
Claim Closure includes services/web functionality to mark the claim as processed and closed |
|
CE |
Claim Exception |
Claim Exception includes services/web functionality for processing claims which can not be assessed. |
|
URM |
User and Role Management |
User and Role Management to define user profiles required to identify the data visibility and access permissions. Like Core User,End User, All Data Access |
|
CRD |
Claim Report and Dash Board |
Claim Reports and Dash board to generate reports about claims processing and SLA dash board |
|
RE |
Rule Engine |
Rule Engine to process the claim business rules. Like JBoss Rules, Jess Rule Engine |
|
DR |
Document Repository |
Document Repository to store the documents related to claims |
|
BPM |
Business Process Management |
Business Process Management used to manage the claims business processing. Like JBPM |
|
PA |
Policy Administration Systems |
Existing Policy Administration independent Applications in all domains. |
|
PSF |
Payment Systems |
File Folder (s) of the Payment Systems which are external to the current system. |
|
DB |
Database |
Database to store the claims data |
Target Application Architecture is depicted beloe where all those components mentioned above will be exposed as Services through Enterprise Service Bus.
The dynamic interactions between the components in this conceptual model are shown in the following Component Interaction Diagram . This particular diagram reflects a generic view that shows information retrieval across the complete system. .
Moving On to Next Blog