Architecture needs to consider all stacks and layers of the company in defining and maintaining the Architecture Principles. We would need to consider the ground realities in conjunction with the people who are actually doing the work, as much as, if not more than, those sit in their ivory towers. If not, our architecture wouldn't be realistic.
Continuing further, I don't expect the Achitecture Principles to be cast in stone. More so, in these days, when the ground realities are changing faster than many businesses can adapt or even cope with. The principles need to be driven by both upstream and downstream.
For example, if SaaS is acceptable to your company, then there should be some architecture principle which accepts this solution. In fact, you should already have had this principle on your list, or accept that as a gap to be rectified. If not, SaaS should not be acceptable to your company, as it would potentialy conflict with one of your principles.
Hope this makes sense...
Kind regards,
Joseph
On Feb 11, 10:28 pm, Mark Cowan
> Is it possible or even desirable to gap fill EA principles by choosing
> a solution that aligns it. For example - in looking at a particular
> Saas solution that was based on the principle of "loose
> coupling" (insert the principle of your choice here) could its
> adoption force the desired design pattern?
> The solution doesn't have to be Saas or technology - it could be
> process based as well.
> All the best,
> Mark
> First Spike
> Information Management Simplified
>http://www.firstspike.com
No comments:
Post a Comment