Versions Compared

Old Version 2

changes.mady.by.user Leo Fernig

Saved on

compared with

New Version 3

changes.mady.by.user Rich Stevenson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed the last set of questions around SOA project metrics, as I am not sure they are germain to products/vendors, and made some minor clarifications substituting product for project in some questions.

...

2.2 If your service contracts are published, can you supply the URL's?
2.3 If there has been a significant change in the adoption of SOA technologies for your product, can you identify the main drivers for the change

...

3.1 Which of the following standards does your product interoperate withuse as an interoperability standard

  • PESC: Admissions Application
  • PESC: High School Transcript
  • PESC: College Transcript
  • PESC: Educational Test Scores
  • IMS: e-Portfolio
  • IMS: LTI (Learning Tools Interoperability)
  • IMS: LIS (Learning Infrastructure Services)
  • KIM: Kuali Identity Management
  • Kuali Student
  • Other:

...

  • Do you have processes for documenting and publishing service contracts ?externally to your product
  • Is there a change management process for service contracts?Is there a central (enterprise wide) repository of service contracts?
  • Can your product export service contracts to an external, enterprise service repository? 

4.2 Please add any additional information on the management of service contracts (that is not captured above)

4.3 Data
Successful SOA is dependent on a clearly articulated ontology. Service endpoints must be able to understand tha data contained in messages.

  • Have you developed and/or published a conceptual data model for the domains that your product covers?
  • Have you developed entity relationship diagrams?
  • Do you publish documented database models?

...

5.2 Please explain in greater detail how you product handles Identity and Access Management in the context of interacting with services exposed from your product:

6. SOA design principles

6.1 Have Has your SOA projects product development been informed by high-level architectural artifacts?

  • Have you developed domain specific capability maps?
  • Have you developed a domain ontology?
  • Have you developed a domain conceptual data architecture?
  • Other: 

6.2 Do you version your service contracts during the design process?

...

6.4 Do you publish meta-data about each service (assumptions, intended use, glossaries)?
6.5 Which message types do you usedoes your product support?

  • SOAP
  • REST
  • POX (Plain Old XML) RPC
  • Java interfaces
  • Other:

7. Technologies

7.1 Does your product use integrate with a commercial turnkey SOA solution

  • Yes
  • No
    7.2 If the answer to 7.1 is "Yes", please indicate which one.
  • Oracle SOA suite
  • IBM websphere
  • Other:

7.3 Are you using Does your product integration with one or more of te the following service-bus applications.  Please describe a typical integration scenario.

  • Mulesoft
  • WSO2 ESB
  • Fuse (built on Apache ServiceMix)
  • Apache ServiceMix
  • JBoss ESB
  • KSB (Kuali Service Bus)
  • Other:

...

  • SAML
  • WS-Security
  • WS-Trust
  • WS-Policy
  • Kuali Identity Management (KIM)

7. Cost benefit analysis

7.1 Indicate whether you think there has been an increase in strategic value in any of the following areas

  • Process improvement
  • The deployment of new capabilities
  • Rationalization and simplification of access to enterprise data

7.2 Metrics

  • In theory, could you calculate the cost of developing a service?
  • Have there been savings in terms of service re-use: