Sketching Software Architecture

Read Complete Research Material

SKETCHING SOFTWARE ARCHITECTURE

Sketching Software Architecture



Abstract

The following paper describes the components of four systems. This is based on how these systems need to be defined based on the functionality that is needed to be achieved by them. The architecture has been developed based on the understanding developed during the course, lectures and the text book for the course that has been referred to.

Sketching Software Architecture

System of Automated Banking Machines

Provided in the following topics are the details of the Reference Architecture and the key asset types of the Banking Payments content pack.

The banking domain can be segmented into core business capabilities, namely, Core Banking, Front Office, Customer Insight, and Payments. The Banking Payments Content Pack supports business processes across the payments value chain in a financial institution.

The Banking Payments Content Pack focuses on business areas such as Payments Initiation, Payments Clearing and Settlement, and Payment Transactions (Vendor, Investment, Lending, Payroll, and Trust). The Banking Payments Content Pack is a core offering from IBM Payments Framework for Financial Services. The industry standards used by Banking Payments Content Pack are:

ISO 20022 standards

SEPA Standards

NACHA standards

IBM Information Framework (IFW) Models

The following figure explains the Reference Architecture for the Banking Payments Content Pack.

Figure 1. Banking Payments Content Pack Reference Architecture

Assets packaged in the Banking Payments Content Pack

Provided here are the details about each asset in the Banking Payments Content Pack.

Banking Payments Capability and Process Maps:

The Banking Payments process maps are based on best practices in the banking industry and the ISO 20022 data dictionary processes.

Banking Payments Business Service Templates:

The definition and granularity of the Banking Payments Business Service Templates is dependant on the following factors:

The Banking Payments Capability and Process Maps

The application ecosystem in banking industry

The application of SOA principles and methodologies for granularity of services

Banking Payments Service Interfaces:

The Banking Payments Service Interfaces are based on the IFW standard and the best practices in the banking industry.

Banking Payments Business Glossary:

Banking Payments Business Glossary is derived using ISO 20022 data dictionary, NACHA, IFW, and SEPA.

Roles: are based on IFW BOM and ISO 20022 data dictionary

Assertions: are derived from IFW, NACHA, SEPA, ISO 20022 data dictionary, and banking payments best practices

Channels: are based on IFW BOM

Banking Payments Common Services:

Banking Payments Common Services are based on ISO 20022 Payments Messages and banking payments best practices. Common services also contain reusable components that are commonly used across the banking industry.

Banking Payments Business Object Model:

Banking Payments business object model is derived using ISO 20022. This model provides an information or data reference model and a common information or data vocabulary from a business and systems perspective. This model uses Unified Modeling Language (UML) to formalize the expression of the needs of a particular view. It provides consistent data and concept that can be reused across multiple information structures including messages. It represents a rich set of concepts that can be shared throughout the banking systems.

Banking Payments Content Pack logical view

The following figure provides a logical view of the Reference Architecture for Banking Payments Content ...
Related Ads