Page tree
Skip to end of metadata
Go to start of metadata

<< Prev Next >>

 

8.1 Is SOA part of SDLC?

8.2 If so, explain how

8.3 SOA architectural artifacts?

8.4 Version contracts during design?

8.5 How do you publish contracts?
1=web
2=docs
3=XML schema

8.6 What kinds of meta-data

8.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.

An enterprise ontology

yes

2

intended use

SOAP/REST

UMUC

2

We have a stated design intent to build and identify re-usable services in our projects. We intend to implement an architectural review in our project design phase to catalog these services going forward.

We aspire to do service and functional decompositions in line with TOGAF architectural layers.

yes

1, 2

intended use

SOAP/REST/POX

UofT

2

The developers are being initiated into Service Oriented Modelling and Architecture (SOMA).  This is proving to be more difficult than we expected but progress is being made.

We don't have these as yet but we are developing architectural components that will address these concerns.

yes

Published in WSRR

Intended use, Glossaries

SOAP/POX

MIT

1

n/a

n/a

n/a

n/a

n/a

SOAP/REST

Washington

3

Some projects like myPlan are very contract based 

Business capability maps are used in several domains
Never got around to doing full service decomposition (often ended at the POC level)

yes

1,3

Intended use, Glossaries

SOAP/REST

UW-Madison

2

It is beginning to change our application architecture.  We are beginning to partition responsibilities more cleanly with well defined interfaces.

The beginnings of enterprise ontologies -- especially as regards curricular data.

Yes

1

Assumptions, glossaries

SOAP

UC-Irvine

2

Applied if it hits the ARB.  Some projects don't get to the ARB.

Primarily for UCPATH.  
There is a catalog of web services generated by javadoc

n/a

Nothing formal

 

 

Colorado

2

SOA components utilize the same issue/bug tracking and change management processes as other software components

Not yet

yes

XML Schema

Intended use

SOAP/REST

Indiana

4

Many of our systems take advantage of services that are provided by the enterprise. So part of the SDLC is to integrate and test with services which are needed by the applications.

Not really

yes

XML Schema,
javadoc api's

 

SOAP/REST/POX



<< Prev Next >>

  • No labels