SOA Using Business Entities and Explicit State Knowledge
In a previous post, I mentioned the use of directed graphs as the payload. I discussed this in relation to alternative entry points beyond SOAP (HTTP or JMS) for services. Let's take the direct graph...
View ArticleRobust and Rapid Architectural Methodologies - Part I
I will start sharing the analytic and design methods I use to develop an architectural approach. These general techniques are applicable regardless of the type of effort, e.g. project, enterprise...
View ArticleRobust and Rapid Architectural Methodologies - Part II
During the first phases of architectural development I think about the business domain model. I am constantly surprised how few people leverage this concept/technique. I find two different sets of...
View ArticleAgile Development and Architecture - Yeah Right!
Agile development has garnered a fair share of attention. Having watched it in action on various projects I am left with the following observations and subtle disquiet. In the examples I have seen,...
View ArticleRobust and Rapid Architectural Methodologies - Part III
What comes next? At this point there is a logical process model (usually represented as a sequence, state-chart, and/or process diagrams) and a business domain entity model. Before going on it is...
View ArticleArchitectural Methodologies Part IV: Application Layering and Services/SOA -...
A standard idea with Object Oriented Analysis and Design (OOAD) and web applications is layering an application by responsibility. The OOAD concept was around first (and there was probably others...
View ArticleArchitectural Methodologies Part V - Technology Stack
There are two aspects to the technology stack of relevance. The first is the categories of product or product types. Each product type has strengths and weaknesses regardless of the specific product....
View ArticleAdditional Notes/Thoughts on the Technology Stack
Then let's consider examples to determine a basic architectural principle, namely, how do I decide if I should assign and deploy multiple products to a solution or limit them for simplification.
View ArticleRELATIONSHIP BETWEEN TECHNOLOGY AND ARCHITECTURAL PRINCIPLE OF COUPLING
I find there are several key considerations beyond my discussions so far to determine the architectural design. One issue is to define a process/methodology for steering key design decision based on,...
View ArticleTech Conferences, Speaker, Games Shows, Taxonomic Confusions and Semantic...
  I am at a technical conference. I am sure many of you have attended one of these. Lots of sessions, discussions, tech talk, marketing, and of course industry hype. At these conferences you...
View ArticleKeynotes, Tech Sales Pitches, and Glitches
  Imagine you represent a large technology company. You hold the rank of Chief of this or that or possibly Product Manager. There is an audience of 1,000 technologists waiting with bated breath...
View ArticleDO YOU WANT AN ENTERPRISE SERVICE OR A HAMBURGER? - Architectural Methodologies
At some point all the pieces have to be put together. I think it is valuable if there is a mechanism for decisions (a process/method) providing a common framework for discussion and/or decision within...
View ArticleEnterprise Development Environment Thoughts
There is at times a great debate regarding development environments particularly Java and .NET. I have been thinking about this a bit lately. Let's look at this from two perspectives architectural and...
View ArticleSpeeding up delivery
Most organizations are searching for ways to speed delivery. Reduced time to market is a good thing. In the search for saving time, many different things are being tried with varying degrees of...
View ArticleDon't Kid Yourself
The responsibility for providing the right direction, design, and most importantly thought processes and patterns comes from architecture. The constraints, limitations, and excuses that are often...
View Article
More Pages to Explore .....