This content has been marked as final. Show 6 replies
Regarding the granularity of governing - don't you have some more coarse-grained services that eventually invoke more fine-grained services ? That's what we have. Ideally you'd want to trace the dependencies between them all I'd think.
Start small, get your buy-in from your business people and get your roles and responsilibilties and amendments to current processes sorted out as well.. The repository can help with governance but also there is the People and Process side of it that unless is tackled and you get buy-in from your stakeholders your repository won't get used and you will end up going back to spreadsheets and word-of-mouth.
Thanks again for your response. I do indeed have the situation you describe ... coarse-grained services calling finer-grained services.
I have recorded both types of service in OER as Service assets (using different values of Asset Function to differentiate between the two types of Service), and I've created References/Is Referenced By relationships between the Services.
That works well for Services with a single operation, but if the target Service is a Data Service with a range of CRUD-type operations I can currently only record the relationship between the calling service and the target Data Service.
There is no indication of which operation(s) the calling Service uses.
This is what I was referring to as fine-grained impact analysis.
I could change the meta-model to add an Operation asset and model the relationships that way, but are there other options that you're aware of ?