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

Compare with Current View Page History

« Previous Version 26 Next »

1. Respondent background

1.1 Institution name
1.2 Department name
1.3a Respondent#1: Name and title
1.3b Respondent #2: Name and title
1.4 May we publish your name and institution on the survey results website?

  1. Yes
  2. No

2. SOA maturity of your organization

2.1 Can you describe the SOA matrurity of your organization using the terminology developed in the HP SOA capability model?

 

Ad-hoc

Basic

Standardized

Managed

Adaptive

Business 2007

 

 

 

 

 

2012

 

 

 

 

 

Program management 2007

 

 

 

 

 

2012

 

 

 

 

 

Governance 2007

 

 

 

 

 

2012

 

 

 

 

 

Architecture 2007

 

 

 

 

 

2012

 

 

 

 

 

Operations 2007

 

 

 

 

 

2012

 

 

 

 

 

People 2007

 

 

 

 

 

2012

 

 

 

 

 

Enabling technologies 2007

 

 

 

 

 

2012

 

 

 

 

 

2.2 If you have indicated a significant change in your maturity level, can you describe the projects that have done most to advance that maturity?

2.3 If there has been a significant change, can you identify the main drivers for that change?

  • The need for enterprise integration of of back-end administrative systems (HR, Finance, Student)
  • The need for better Master Data Management
  • The need for greater agility
  • The need to integrate learning technologies
  • The de facto result of acquiring middleware bundled with other products
  • Executive leadership (CIO or Enterprise Architecture)
  • Other:

3. Industry (vertical) standards

3.1 PESC: Admissions application

  • Used to receive applications
  • Used for internal application integration
  • There is an enterprise-wide commitment to the standard
  • The standard is used as a guideline for design

3.2 PESC: Edcucational Test Scores

  • Used to receive test scores from agencies
  • Used for internal application integration
  • There is an enterprise-wide commitment to the standard
  • The standard is used as a guideline for design

3.3 If you have checked one or more items in 3.2, please list the tests (eg SAT, TOEFL, GRE etc)

3.4 PESC: High School Transcript

  • Used to receive transcripts
  • Used for internal application integration
  • There is an enterprise-wide commitment to the standard
  • The standard is used as a guideline for design

3.5 PESC: College transcript

  • Used to receive transcripts
  • Used to send transcripts
  • Used for internal application integration
  • There is an enterprise wide commitment to the standard
  • The standard is used as a guideline for design

3.6 Kuali Student

  • Is being used in a Kuali implementation
  • Used in enterprise application integration
  • There is an enterprise wide commitment to the standard
  • The standard is used as a guideline for design

3.7 Kuali Identity Management

  • Is being used in one or more Kuali implementations
  • Is being used for application integration
  • These is an enterprise wide commitment to the standard
  • The standard is being used as a guideline for design

3.8 Do you use any of the following IMS standards (in any capacity)

  • IMS: e-Portfolio
  • IMS: LIS (Learning Infrastructure Services)
  • IMS: LTI (Learning Tools Interoperability)

3.9 Please list any other industry (vertical) standards that do not appear in the lists above

4. SOA Governance

4.1 Does your organization include architectural reviews in its project methodology
1=None at all
5=Well established

4.2 Are the principles of SOA applied during architectural reviews?
1=None at all
5=Well established

4.3 Do you have processes for documenting and publishing service contracts?
1=None at all
5=Well established

4.4 Do you have a change management process for service contracts?
1=None at all
5=Well established
4.5 Is there a central (enterprise wide) repository for service contracts?

  • Yes
  • No
    4.6 Please add any additional information on the management of service contracts

4.7 Has SOA changed your IT governance? If so, how?

5 Data governance

Successful SOA depends on a clearly articulated ontology. Service endpoints need to understand the data contained in messages. Maturity around data architecture is a precondition for SOA maturity.

5.1 Do you have a conceptual enterprise data model?
1=None at all
5=A highly developed model

5.2 Do you have well documented logical data models?
1=None at all
5=A highly developed model

5.3 Do you have well documented physical data models?
1=None at all
5=A highly developed model

5.4 Have you developed governance structures around data?
1=None at all
5=Mature governance

6. Identity and access management

Services need to be built on mature identity and access management practices. Successful IAM is another precondition for successful SOA.

6.1 Do you have an enterprise Identity and Access Management roadmap?

  • Yes
  • No
  • We are in the process of creating one

6.2 Which of the following statements describe your Identity and Access Management environment?

  • You have implemented federated authentication
  • You have a single sign-on solution
  • You can delegate the management of groups and user attributes
  • Services are available to manage and communicate user attributes across the enterprise

6.3 Please indicate which products form part of your Identity and Access Management solution

  • LDAP or OpenLDAP
  • EAD (Enterprise Active Direcoty)
  • AD (Active Directory)
  • Novell
  • Shibboleth
  • CAS
  • Grouper
  • KIM
  • Oracle Identity Manager
  • Other:
    6.4 How do you handle service-to-service authentication and authorization?

6.5 Please indicate in greater detail how key components of your Identity and Access Management solution interpoerate with your services?

6.6 More generally, how do you manage trust between distributed components ?

7. SOA design principles

7.1 Is SOA part of your Software Development Life-cycle?
1=Not at all
5=Consistently

7.2 If SOA is part of your SDLC, please explain how

7.3 Have your projects been informed by any of the following high-level architectural artifacts?

  • Enterprise capability maps
  • An enterprise ontology
  • Enterprise business process maps
  • Other:

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

  • Yes
  • No
  • n/a

7.5 How do you publish (document) your service contracts?

  • Textual descriptions in documents (not available on the web)
  • Textual descriptions on the web
  • XML schema
  • api's in javadoc
  • Other:

7.6 What kinds of meta data do you maintain about your services

  • Assumptions
  • Intended use
  • Glossaries
  • Other:

7.7 What message structures do you use?

  • SOAP
  • REST
  • POX (Plain Old XML)
  • Other:

8. Technologies

8.1 Are you using an integrated commercial SOA suite, or any of the components in the suites listed below?

  • Oracle SOA suite
  • IBM Websphere
  • Microsoft Biztalk
  • Red Hat JBoss Enterprise SOA Platform
  • SAP NetWeaver 7.3
  • TIBCO ActiveMatrix 3.0
  • Other:

8.2 Are you using one or more of the following service bus applications?

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

8.3 Please indicate which enterprise services are connected via a bus

8.4 Which of the following technology standards do you use?

  • XML binding: JAXB, JAX-WS
  • WS-Transaction
  • BPEL
  • Other:

8.5 Which of the following security related standards do you use?

  • SAML
  • WS-Security
  • WS-Trust
  • WS-Policy
  • Other:

8.6 How would you describe the logical topology of your SOA

  • Bus (endpoints only connect via a bus)
  • Hub and spoke
  • Point-to-point
  • Federated
  • A mixture of the above
  • Other:

8.7 Has the introduction of SOA related technologies altered your enterprise technology road-map?

9. Cost benefit analysis

9.1 Indicate whether you think that SOA has led to an increase in strategic value in any of these areas

  • Process improvement
  • The deployment of new capabilities
  • Simplification of access to enterprise data
  • Lowering costs
  • Other:

9.2 Metrics

  • Yes: in theory the cost of developing and deploying a service could be calculated
  • Yes: there have been cost savings in terms of service re-use
  • Other:
    9.3 Are there any other comments you might like to add on the topic of SOA and cost-benefit

10. Individual projects and intitiatives that illustrate SOA principles

In this section we would like to collect some detailed information about individual SOA projects or initiatives that you have undertaken in the last 18 months. The section allows for up to 2 projects. However, if there are more you would like to share, there is a freeform text box at the end of the section.

Project #1

10.1a Name of the project

10.2a Project URL (if public)

10.3a Where is the project at on the project lifecycle?

  • Investigation
  • Planning
  • Execution
  • Review
  • In production

10.4a What are the goals of the project (technology goals and business goals)

10.5a Is there any additional information about the project you would like to supply

10.6a What business domains does this project address?

  • Learning tools ecosystem (LMS, e-Portfolio, learning objects)
  • Student (enrollment, planning, records, awards)
  • Research admin (grants, ethics, accounting, publications)
  • Back-end administration (HR, Payroll, Finance)
  • Enterprise infrastructure (workflow, identity, business rules management)
  • Other:
Project #2

10.1b Name of the project

10.2b Project URL (if public)

10.3b Where is the project at on the project lifecycle?

  • Investigation
  • Planning
  • Execution
  • Review
  • In production

10.4b What are the goals of the project (technology goals and business goals)

10.5b Is there any additional information about the project you would like to supply

10.6b What business domains does this project address?

  • Learning tools ecosystem (LMS, e-Portfolio, learning objects)
  • Student (enrollment, planning, records, awards)
  • Research admin (grants, ethics, accounting, publications)
  • Back-end administration (HR, Payroll, Finance)
  • Enterprise infrastructure (workflow, identity, business rules management)
  • Other:
  • No labels