No blogs for some time - I much prefer "micro blogs" and therefore use Twitter (http://twitter.com/petereeles) more often than Blogger. Anyhow, whenever something significant comes up I'll post here.
I've spent a considerable amount of time over the last few years focusing on a particular domain - development environments. I first described my thoughts in this paper. That work is undergoing a serious "refresh" and I'll be reporting back as collateral is created. The first item to be refined (based on lessons learned since that paper was written) is the definition of a development environment. The major elements have stayed the same (context, method, tools, enablement, organization, infrastructure and adoption), but my team and I have been teasing apart the different considerations when either defining, deploying or managing a development environment.
It's really interesting work and will underpin (for example) an architecture description standard for development environments (with relevant viewpoints defined) and a maturity model for development environments that extends CMMI. Watch this space!
Glad to see that the WICSA 2011 call for papers is now open.
Wednesday 14 July 2010
Saturday 30 January 2010
What does Enterprise Architecture mean to you?
I delivered some enablement yesterday for my colleagues and one item that resonated is Alan Brown's list of possible interpretations of what EA might mean to any given organisation:
1. An IT-driven initiative to define the IT application landscape
2. One source of the truth via an integrated view of the enterprise, across all lines of business
3. Assessing current and future states of the enterprise, along with the programs and controls to achieve desired capabilities
4. Architecture framework governance and reporting (e.g. Zachman, TOGAF, EA3, FEAF, MoDAF, DoDAF)
5. Portfolio planning for resources, projects and initiatives
6. “Uber-architecture” for development teams
7. Architectural conformance
8. Model-Driven Architecture (MDA)
9. Alignment of strategy, business, information, applications and technical infrastructure in support of a strategic intent
I prefer the last definition :)
- Pete
1. An IT-driven initiative to define the IT application landscape
2. One source of the truth via an integrated view of the enterprise, across all lines of business
3. Assessing current and future states of the enterprise, along with the programs and controls to achieve desired capabilities
4. Architecture framework governance and reporting (e.g. Zachman, TOGAF, EA3, FEAF, MoDAF, DoDAF)
5. Portfolio planning for resources, projects and initiatives
6. “Uber-architecture” for development teams
7. Architectural conformance
8. Model-Driven Architecture (MDA)
9. Alignment of strategy, business, information, applications and technical infrastructure in support of a strategic intent
I prefer the last definition :)
- Pete
Subscribe to:
Posts (Atom)
