The document discusses various frameworks related to enterprise architecture including business frameworks, architecture frameworks, programming frameworks, project management frameworks, and industry operations frameworks. It also discusses what constitutes an enterprise, the differences between architects and developers, ways to categorize frameworks, and provides examples of specific frameworks like TOGAF and Zachman Framework.
Swan(sea) Song – personal research during my six years at Swansea ... and bey...
Enterprise Architecture Frameworks and Best Practices
1. Enterprise Architecture As
practice
Business Frameworks (e.g. BMM, Six Markets, Porters 5 Forces,
McKinsey 7S, etc)
Architecture Frameworks (e.g. PEAF, MODAF, TOGAF, TEAF, IAF, etc)
- Programming Frameworks (e.g. .NET, J2EE, etc)
- Project Management Frameworks (e.g. PRINCE2, MSP, etc)
- Service Management Frameworks (e.g. ITIL, etc)
Industry Operations Frameworks (e.g. eTOM, Pragmatic Marketing, etc)
2. What is Enterprise?7M
Man, Material, Machine, Money,
Method, Management, Moral Values
(Governance)
• ENTERPRISE - The word Enterprise should be
interpreted as a general noun – the name of something
- to refer to any and all of these types of thing; public
and private companies, government agencies,
charities, universities etc. This is not an exhaustive list
but illustrates the point. In addition the word
Enterprise should also be interpreted to mean any
name give to any of these types of Enterprises, e.g. a
private company may be referred to as a Company,
Business, Corporation, Conglomerate, Organisation,
SME, Firm, Establishment, Group, Multinational,
Venture. The word Enterprise to refers to them all.
3. Architecture Vs Developer
Developer Architect
More into coding and concerned about
best way to solve a particular problem.
Sees big picture of the system before it is
built.
Usually no need to sell his way of working
(which is often down to coding).
Need to convince (or sell) stakeholders
about vision, ideas and recommendation.
No involvement in strategic decisions. Often recommends and selects tools for
strategic implementation.
Tend to recommend a tool/language he is
most familiar with.
Evaluates and compares all available
options and selects one which is best for
business.
Goes for best technical solution. Goes for best fit solution for the
organization.
Less scope for delegation. More scope for delegation.
Responsible for implementation Defines general layout of the system.
Heavily involved in coding. Usually not involved in coding.
Finds a solution to a problem according to
design.
Finds the definition of actual problem and
suggests design to solve it.
Soft skill is less important. Soft skill is more important.
Often works in single project. Often works in multiple projects across
the organization.
4. Make distinction more clear
• Architect in software world is one who designs
systems almost similar to Building Architect.
• Difference between developer and architect is
same as between civil engineer and Architect.
• Both make building but architect designs it to
specs after taking lots of factors into
consideration and civil engineer see whether
strength of cement mixture or width of steel rod
enough to support building same way architect
sees whether exposing it as webservices is
advantageous to SAP or integrate with BAPI.
5. Categorization
• Strategy – Value Creation e.g. CMMI, PCMMI
• Valuation and Decision making: Break Even
Point, six sigma.
• Organization change culture: e.g. RACI
(Responsible, Accountable, Supportive,
Consulted, Informed)
• Leadership And management: e.g. Activity
Based accounting, Root cause Analysis