Aggregated enterprise architecture wisdom
James Parnitzke This post explores the step where we discover the optimum sequence of actions recognizing predecessor – successor relationships. This is undertaken now that we have the initiatives and the prioritization is done. What things do we have to get accomplished first, before others? Are there dependencies we have identified that need to be satisfied before moving forward? What about the capacity for the organization to absorb change?
This post continues an earlier discussion about how to use the results from steps 1 – 3 to prioritize the actions we have identified to close the gap or difference (delta) from where we are to what we aspire to be. This is usually driven by evaluating the relative business value AND the technical complexity, plotting the results in a quadrant graph using an Action Priority Matrix. Other complimentary methods are discussed to help IDENTIFY what is feasible and what has the highest business value balancing business need with the capability to execute.
This post discusses how to use the results from steps 1 – 3 to prioritize the actions we have identified to close the gap or difference (delta) from where we are to what we aspire to be. This is usually driven by evaluating the relative business value AND the technical complexity, plotting the results in a quadrant graph using an Action Priority Matrix. What we are doing here is IDENTIFYING what is feasible and what has the highest business value balancing business need with the capability to execute.
Before proceeding with the Building better systems series I thought I should write a quick post over the weekend about the underlying Natural Language Processing (NLP) and text engineering technologies proposed in the solution. I have received a lot of questions about this when I posted How to build better systems – the specification.
We probably can all agree that defining functional and non-functional requirements are the most critical elements of a project’s success or failure. Reducing specification requirements errors is the single most effective action we can take to improve project outcomes. The approach I propose is inexpensive and mitigates much of the risk associated with defects and errors early in the development life cycle.
This post will discuss how to develop a robust gap analysis to identify any significant shortcomings between the current and desired end state. We use these findings to begin develop strategy alternatives (and related initiatives) to address what has been uncovered. The intent is to identify the difference (delta) from where we are to what we aspire to become. This exercise is critical to identify what needs to be accomplished. 
This post will provide a little more exposition and insight into one method I have found useful in practice for quickly defining desired end states. Done well, it can provide an honest and objective look to successfully understand where we truly want to be as an organization and face the uncomfortable truth in some cases where we need to improve. 
This post will provide a little more exposition and insight into one method I have found useful in practice for quickly defining current state. Done well, it can provide an honest and objective look in the mirror to successfully understand where we truly are as an organization and face the uncomfortable truth in some cases where we need to improve. 
Introduction of a basic pattern for developing a robust road map for any organization using an example of the adoption of a Master Data Management initiative.
An enterprise architecture value proposition is presented with accompanying tables of suggested values that can be explored and used within any organization.
It is always a good idea to express our stated design goals right up front – and use these to guide the inevitable trade-offs and decisions that will need to be made along this journey. So let’s get started with a few design goals in our space based architecture model that combines and integrates distributed caching, content-based distributed messaging, and parallel processing into a powerful architecture within a grid computing framework. 
Introduction to the Tuple Space (Space based Architecture) pattern model that combines and integrates distributed caching (Data Grid), content-based distributed messaging (Messaging Grid), and parallel processing (Processing Grid) into a powerful service oriented architecture built on shared spaces within a grid computing framework. 