Page History
| 7.1 Is SOA part of SDLC? | 7.2 If so, explain how | 7.3 SOA architectural artifacts? | 7.4 Version contracts during design? | 7.5 How do you publish contracts? | 7.6 What kinds of meta-data | 7.7 What message structures? | ||
|---|---|---|---|---|---|---|---|---|---|
UBC | 1 |
|
| no | Textual descriptions on the web, XML schema 1,3 |
|
| none | SOAP/REST/POX/RMI |
Michigan | 1 |
|
| n/a | Textual descriptions in documents (not available on the web), XML schema 2,3 | none | SOAP/REST/POX | ||
Cornell | 1 |
|
| n/a | Textual descriptions on the web 1 | intended use | SOAP/REST | ||
Georgetown | 3 |
| Developers/implementers are aware of SOA technologies and encouraged to think in terms of re-usable services. There is no formal training or management of this however. |
| Textual descriptions in documents (not available on the web) 2 | yes |
| intended use | SOAP/REST |
Overview
Content Tools