Source: Click Here
The article is about how EA is applicable only in IT though it is spread across stakeholders,business information,technology and solution architecture.There are wide gaps seen in the approach of developing EA.
Some of the gaps are:
The article is about how EA is applicable only in IT though it is spread across stakeholders,business information,technology and solution architecture.There are wide gaps seen in the approach of developing EA.
Some of the gaps are:
- Developing a business context:
- The IT-Investment Decision Making process
- Creating a governance and assurance mechanism
Also a common trend seen is when EA conflates the business architecture viewpoint of EA.The business context of EA is said to be formed of A vision of the future state,an anchor model and a set of guiding principles.However it is a common mis interpretation of neglecting the business context,treating the business architecture as a separate entity and narrowing down EA to only IT.
Mature practitioners understand the business context and work towards relating it with EA.They focus on the interdependencies,the relationships and how it can drive the actual process.Also experienced personnel in this field look at the view that only when business architecture is engaged does assurance and governance come in place.It is indeed necessary to understand and go into details to see how every business action has a role to play with EA frame.It is sad to see people over look these at most instances but by setting practices it can be brought into picture.Thereby it will be a very good methodology to incorporate the business architecture well inside the enterprise architecture framework or rules to be played.
No comments:
Post a Comment