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

Compare with Current View Page History

« Previous Version 36 Next »

SOA maturity of your organization

  1. Can you describe the SOA level of maturity of your organization using the terminology of the HP capability model (see notes)?

    Area

    Ad-hoc

    Basic

    Standardized

    Managed

    Adaptive

    Comments on the rank

    Business

     

     

     

     

     

     

    Program management

     

     

     

     

     

     

    Governance

     

     

     

     

     

     

    Architecture

     

     

     

     

     

     

    Operations

     

     

     

     

     

     

    People

     

     

     

     

     

     

    Enabling technologies

     

     

     

     

     

     

Individual SOA projects:

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. 

  1. Where they fall on the project lifecycle:
    1. Investigation
    2. Planning
    3. Execution
    4. Review
  2. What business domains are addressed by this project:
    1. Student (recruitment, admissions, academic records, registration, awards and financial aid, degree audit, advising)
    2. HR (recruitment, benefits, payroll, pension, leaves)
    3. Research (grant applications, ethics, funding, publications)
    4. Finance
  3. Enterprise infrastructure
    1. Identity (Authentication, authorization, managing user attributes)
    2. Workflow

Are industry (vertical) standards being used either directly or, to provide guidance.

  1. PESC (be specific about which ones)
  2. IMS Global (be specific about which ones)
    1. LIS
    2. LTI
    3. Etc
  3. Other
  4. Kuali
    1. Kuali Student
    2. Kuali Identity Management

Identity and access management

  1. Are standards contracts being used?
  2. Trust in a distributed environment

Governance

Describe governance structures that support SOA

  1. Inventory Management
  2. Data Governance
  3. Configuration, Change and Release Management
  4. Other
  5. Has SOA changed your governance? If so how?
  6. Has SOA introduced new roles and/or responsibilities?

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?

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

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?
  • No labels