Monday, November 21, 2005

3 x 3 Architecture Tools

3 sets of architectural tasks:
  • Modeling
  • Documentation
  • Communication
3 classes of architectural products:
  • Enterprise Architecture
  • Domain-specific Architecture
  • Software Architecture



Enterprise
Architecture


(global)
Domain-specific
Architecture


(cross-functional)
Software
Architecture


(project-centric)
Modeling   
Documentation   
Communication   


2 Comments:

Blogger Paul said...

I like the grid. I'm assuming that what comes next is to define what goes into the cells.

11:27 AM  
Anonymous e2eiod said...

I have been trying to reconcile your diagram with my concept reply to the question below.


Q) If I don't need to change the service description, can I change the service implementation? If so, do I still have to go to the service domain owner?


A) Does your service implementation change affect the Service Level Management/Service Level Agreement (SLM/SLA) agreement for that Service Domain or any sub-domain in it?

Sub-domains are currently defined alphabetically as Business Continuance, Compute, Disaster Recovery, Information High Availability, Information Integrity, Network, and Storage. I am working on others. Key Processes are Event Management, Findability and User Experience. SFO (Search, Find, Obtain) is the key process in Findability.

For technical performance:
The Event Management system cues from the implemented SLM/SLA system for that Service Domain and all related sub-domains.

For ROI (Return on Investment) and TCO (Total Cost of Ownership):
The Unit of Information resides on some Unit of Technology and is acted on by other Units of Technology. Taking the simple one to one case, By Definition, a Managed Unit of Information must reside on a Managed Unit of Technology. All Managed Units of Information and Technology are managed by the SLM/SLA system. In this scenario, when you change anything in a Domain, the core XML definitions must be changed.
If these core definitions are not changed, authorized and validated the Event Management system will report the "service implementation" change and it will have to reconciled.
In the fully automated system the core definitions will be changed automatically by the "Infotone" process which detects the changes and checks for authorization. Once authenticated these changes ripple out through the entire SOA automatically.

My answer to the question then is:
Both changes require Service Domain Owner approval which should be obtained in advance for ROI/TCO reasons.
Changing the Service Implementation has more consequences than changing the Service Description.

1:02 PM  

Post a Comment

<< Home