1=Never
5=Consistently or well-established
|
5.1 Architectural reviews? |
5.2 SOA included in reviews? |
5.3 Processes for publishing contracts? |
5.4 Change management process for contracts? |
5.5 A central repository for service contracts? |
5.6 Additional information on the management of service contracts |
5.7 Has SOA changed your IT governance? |
---|---|---|---|---|---|---|---|
UBC |
2 |
2 |
1 |
1 |
N |
|
|
Michigan |
2 |
2 |
1 |
1 |
N |
|
|
Cornell |
2 |
1 |
2 |
1 |
N |
|
|
Georgetown |
2 |
1 |
1 |
1 |
N |
|
|
Ohio State |
2 |
|
2 |
2 |
N |
|
|
Additional information on the management of service contracts
Michigan: We are currently working on a Directory of API project that will create a repository of web services and their meta data, which will include service level expectations.
Cornell: There is a Confluence wiki listing some of the service contracts. As we start up Oracle SOA Suite, Oracle Enterprise Repository and Oracle Service Registry, we will attempt to leverage the more-or-less automated features of these tools to improve the situation.
Ohio State
Currently maintaining spreadsheet/DB table. Also researching/evaluating Service Registry/Repository software
Cardiff
Characteristics of the interface to the Service. There may be more than one of these for any given Service.