|
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 |
1,3 |
|
|
none |
SOAP/REST/POX/RMI |
||
Michigan |
1 |
|
|
n/a |
2,3 |
none |
SOAP/REST/POX |
||||
Cornell |
1 |
|
|
n/a |
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. |
|
2 |
yes |
|
intended use |
SOAP/REST |
||
Ohio State |
2 |
We have an Application/Integration Architect who can "drop in" to a design activity. There are a limited number of technologists who are beginning to use SOA principles and web services as a part of their design methodology. It is not yet a formal part of the SDLC. |
|
no |
|
2 |
|
|
|
|
|
Overview
Content Tools