SOA Impact Analysis
In June, EasySOA Registry has been enriched with a new examplary SOA information browsing UI.
Actually, its point is to allow CIOs to choose and show exactly the information they want about their SOA how and where they want it, by providing an UI that is the easiest to customize into their own (by merely editing HTML templates). But to be able to choose the pieces of information they want to highlight, CIOs need to know for starters what information there is. That’s why we’ve written an SOA information browsing UI that shows every possible bit of knowledge and all available tools for each service definition, implementation and deployment.
But did you know it also provides impact analysis tools ?
Indeed, it builds on knowledge that the Registry has about an information system’s service-oriented architecture to deduce, for a Service :
- at business level, which Business Actor consumes it
- at runtime in staging environment, which deployed service (Endpoint) consumes it
- at technical level, which Application source code (for now Java) consumes it
This allows the CIO to know who uses a given service at all three conceptual levels, and enables him to make the right decision when there is an problem to be solved – such as a legacy piece of its Information System whose commercial support has just been terminated and which therefore needs to be replaced as soon as possible.