• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (3)

1 localhost commented Permalink

Ali,similarly there is the question on who owns the data persistance element of the service. The service provider may not like to own it, as he believes it is a pure IT function, leading to further breakdown in the architecture. In answer to your question, if you are responsible for the service implementation and have managed to maintain the clear delineation between service implementation and description and the change to implementation will not impact the service definition / function, there would be no need to go back to the service domain owner, unless he is funding the change.

2 localhost commented Permalink

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 related all 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 Technology 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. In the fully automated system they will be changed auotmatically 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.

3 localhost commented Permalink

Error Correction---The line "By Definition, a Managed Unit of Technology must reside on a Managed Unit of Technology"Should read "By Definition, a Managed Unit of Information must reside on a Managed Unit of Technology"

Add a Comment Add a Comment