You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Organizational SOA maturity

Maturation (http://h71028.www7.hp.com/ERC/downloads/4AA0-4824ENW.pdf) 

Message styles.

SOAP, REST and POX messages have different structures and syntax. However, the differences goes much deeper than that and affect the whole design of a system. REST builds on the fundamental concepts of HTTP and there are essentially two methods (GET and PUT). SOAP, by contrast, grew out earlier remote object technologies (such as CORBA and DCOM) and so it attempts to model remote object interactions. You can specify the equivalent of method names and input and output parameters.

1. SOA maturity of your organization

4. Governance

Describe governance structures that support SOA.  Is this governance enterprise-wide or distributed.

  1. Inventory Management (service inventory).  Publication of contracts.  Is there an enterprise wide process for managing this?
    1. Do you have processes for documenting and publishing the services
    2. Do you have processes for managing changes to the services (change management)
    3. Is there any gate keeping over the publication of services (assuming you have an overall SOA for your enterprise)
  2. Data Governance.  Successful SOA and successful data management go together?
    1. Have you developed a conceptual enterprise data model (or parts of one) ?
    2. Do you have data stewards.  Do data stewards contribute to the definition of services?
    3. Is there an MDM (master data management) strategy?
    4. How does this connect to service message structures?
  3. Has SOA changed your IT governance? If so how?
  4. Has SOA introduced new roles and/or responsibilities?

5. Cost benefit analysis

  1. Metrics
    1. Cost to build each service
    2. Integration costs related to service re-use
    3. service reuse opportunities
  2. Strategic Value -- ROI
    1. Have processes been improved?
    2. Have new capabilities been provided?
    3. What other benefits have resulted from SOA, e.g., reusabile services  reduced development time  better access to enterprise data  rationalization of business process?

6. SOA styles

  1. Message styles (notes). Different message styles are appropriate for different contexts. Which ones do you use?
    1. SOAP
    2. REST
    3. Plain old XML (POX)
    4. Other
  2. Design approach.  How do you design your contracts?
    1. Contract first
    2. Bottom up (java annotations)
  3. Documentation. How do you document your service contracts?
    1. Interfaces published in javadoc
    2. XML schema
    3. Textual descriptions on wikis
  4. How do you mange trust between the various components
  5. If some components are in the cloud, how will that affect your security architecture
  6. Messaging: synch/asynch

7. Technologies

  1. Is a commercial "turnkey" SOA solution being used:
    1. Oracle fusion
    2. IBM websphere
  2. Are any open source or open source plus support solutions being used:
    1. MuleSoft
    2. WSO2
    3. Fuse
    4. Apache ServiceMix
  3. Has SOA led you to re-engineer your infrastructure? For example, if your data warehouse is the current hub of data exchange, does SOA change this?

8. Individual SOA projects and initiatives:

List up to three projects.  Distinguish between SOA projects and projects that involve SOA.  Where do these fall in the SOA maturation.  Top-down or bottom-up.  What business processes are being supported.  How does this project move you forward in the maturity model.  Does not have to be a technology project?   SizrWhat are the goals of the project?  Quantification.  Can we make generalizations about where there is the most activity?

  1. Where they fall on the project lifecycle:
    1. Investigation
    2. Planning
    3. Execution
    4. Review
  2. What were the goals (business and technology)
  3. What business domains are addressed by this project:
    1. Learning tools ecosystem
      1. Learningt objects
      2. e-Portfolio
    2. Administrative systems
      1. Student (recruitment, admissions, academic records, registration, awards and financial aid, degree audit, advising)
      2. HR (recruitment, benefits, payroll, pension, leaves)
      3. Finance
    3. Research (grant applications, ethics, funding, publications)
      1. Publications
  4. Enterprise infrastructure
    1. Workflow
    2. Other (please describe)
  • No labels