Summary of the principles Comment

General/Business principlesIT and business alignment (These Principles apply to both IT and Business) 1 1

Maximum benefits at the lowest cost and risk to the enterprise as a whole 2 23

Business continuity 3 4

Common Use Applications (Re-use before Buy before Build) 5

Service Orientation (enabler for business agility) 6

Compliance with standards and policies (incl law, regulations) 4 7

IT Responsibility for owning / implementing IT processes and Infrastructure 8

Protection of Enterprise Intellectual Property (Security Policies etc) 95

Information principles6 10

7 11

Accessible information (by users to perform their function) 8 1213

Common terminology and data definitions across enterprise. 9 1410 15

Application principles11 16

12 17

Component reusability and simplicity (modular/plug and play) 1314

15

16

IBM Principle NUM for Financial Services

TOGAF v9.1

Principle NUM

Current Principle

Y/N

Desired Principle

Y/N

Principle functionally in

place Y/N

Information Management is everyone's business (Information users are the key stakeholders in decisions)

Adoption of the best practices for the market (IT Governance, Processing, Management)

Information treated as an asset (has value to the enterprise and should be managed accordingly)

Shared information (Timely access to accurate information increases the efficiency and quality of decision making)

Data Trustee accountable for data quality. Each data element has an accountable data trustee to ensure accuracy and currency.

Information security (information is protected from unauthorised use and disclosure)

Technological independence (applications are independent and can run on a variety technology platforms)

Easy-to-use applications (technology is not an inhibitor to users who can focus on the task at hand)

Adaptability and flexibility (Adaptability and flexibility reduce the complexity and promote integration)

Convergence with the enterprise architecture (legacy decommissioning, management of technical debt)

Enterprise architecture also applies to external applications (investment vision for the business must include IT requirements)

Low-coupling interfaces (are self--described, and offer low impact during changes)17

18

Technology principlesChanges based on requirements 19 18

Responsive Change Management 1920 20

21 21

Referenceshttp://pubs.opengroup.org/architecture/togaf9-doc/arch/chap23.htmlhttp://www.ibm.com/developerworks/rational/library/enterprise-architecture-financial-sector/

Adherence to functional domains (business rules and functionality of a system are consistent with the mission of that system)

Control of technical diversity and suppliers (minimize the non-trivial cost of maintaining expertise in and connectivity)

Interoperability (Software and hardware conform to defined standards that promote interoperability for data, applications, and technology)