Aggregated enterprise architecture wisdom
If we provide a service that is a monopoly or natural-monopoly, how should we relate with those who use our services? What’s the most appropriate metaphor to use, to guide our decision-making? I’ve been thinking hard about this for quite…
When configuration management is well addressed in software engineering, baseline monikers are absolutely great. If you consistently adhere to the ROCK SOLID principle that once created a baseline MUST be immutable, there cannot ever exist any ambiguity about what, for example, represents 1.0. Unfortunately the conventional scheme of … Continue reading →
A complete Enterprise Architecture that effectively supports the business cannot be purchased as a fully realisable off-the-shelf commodity. This statement should of course be qualified by at least considering the possibility of acquiring a hypothetical ‘business-in-a-box’ with everything already defined … Continue reading →
Gartner just released a report entitled, "EA Practitioners Have Significant Influence on $1.1 Trillion in Enterprise IT Spend” that strongly links to their Business Outcome Driven Enterprise Architecture. This is interesting article because it’s shows the latest thinking from real…
Cloud, SOA, Enterprise Mobility, Social Media/Enterprise/Business, The Internet of Things, Big Data (you name it) – each in its own way is part of an overall tendency. The general trend is for enterprises to become increasingly involved in increasingly broad ecosystems. … Continue reading →
In case you haven’t heard Microsoft is ending support for Windows XP and Office 2003 in April of 2014. What this means is that Microsoft will no longer patch security vulnerabilities discovered in XP or Office 2003, and therefore there will be security holes discovered that can be exploited by hackers which will never be […]
If you sell a problem too successfully, you will not enjoy what comes next.
Enterprise Architecture doesn’t usually decide specific action.
So be very careful about how you characterise the need for action.
A problem-focus generates conflict and disorder.
A benefit-focus generates unity and collaboration.
If you sell a problem too successfully, you will not enjoy what comes next.
Enterprise Architecture doesn’t usually decide specific action.
So be very careful about how you characterise the need for action.
A problem-focus generates conflict and disor…
It would be naive to expect that when running a business that decisions would not need to be made. Situations are constantly arising that will require a response. To be able to reliably respond, appropriately and with some degree of … Continue reading →
How should we respond to inherent-uncertainty in qualitative-requirements, for enterprise-architecture and the like? Yes, we can reduce every qualitative-requirement to some sort of metric, but is that always a wise thing to do? And if not, how can we tell whether…
All businesses capture and store information, in some form, about: What they are doing How they are doing it and Why This information may be structured but often is not. Information abounds that relates specifically to individual projects or activities … Continue reading →
Good architects also need to be good “marketects”: they must be able to sell and promote their cause as well as publicize their achievements, outcomes, and results. But how do they do this? What tips and guidelines from the world of marketing can architects adopt to their advantage? First of all, what do we mean Read more