API Strategy, Design and Governance

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Email *

Name of the Institute *

How long has your organization been using APIs for its products or services?
*

Less than a year

1-2 years

2-5 years

More than 5 years

1. How many APIs has your organization developed and released for public consumption?

1-10

11-50

51-100

More than 100

What is the primary driver for your institute's adoption of APIs?

Business strategy: APIs can help an organization to expand its business model

Digital transformation: APIs can help digitize legacy systems and modernizing IT infrastructure

Customer engagement: APIs can be used to create new customer experiences

Data monetization: APIs can be used to market data and services to partners

Partner integration: APIs enable collaboration and integration with external partners

Data delivery and possibly some process object exposure (e.g. “create a new NetID”)

Other:

Required

How are API opportunities identified in your organization?

Ad hoc: API opportunities are identified on a case-by-case basis with no formalized process

Reactive: API opportunities are identified in response to specific business needs or challenges

Proactive: API opportunities are identified through ongoing analysis of business processes and customer needs.

Strategic: API opportunities are identified through a comprehensive analysis of the organization's strategic goals and priorities.

How are APIs prioritized in your organization?

Ad hoc: APIs are prioritized on a case-by-case basis with no formalized process

Based on project needs: APIs are prioritized based on the needs of specific projects or initiatives

Based on business value: APIs are prioritized based on the potential business value they can deliver

Based on strategic alignment: APIs are prioritized based on their alignment with the organization's strategic goals and priorities

Who is involved in architecting APIs *

Enterprise Architect

Technical Architect

IAM Architects

API Developers

Data Architects

Required

How are APIs managed within your organization? (Select all that apply)

APIs are managed by individual teams, without centralized oversight

APIs are managed by a centralized API team or group

APIs are managed through a governance board or committee

APIs are managed using a shared API gateway or management platform

Other:

How are these APIs being used in your institute?
*

Integrating data between different systems

Building custom applications

Enabling mobile access to institutional services

Automating administrative tasks

Facilitating collaboration with external organizations

Other:

Required

Which API architectural patterns is being used at your institutes?

RESTful APIs

SOAP API

GraphQL API

RPC API

Microservices API

Other:

Required

What is the current state of your organization's API governance? (Select the one that best represents your organization)

Ad hoc, no formalized governance processes in place

Initial, some governance processes are in place, but they are not well-defined or consistently followed

Defined, formalized API governance processes and policies are in place, but they are not fully implemented

Managed, API governance processes are well-defined, consistently followed, and monitored for compliance

Optimized, API governance processes are continuously improved and optimized based on feedback and metrics

What are the biggest challenges in implementing APIs in your institute? (Please select all that apply)

Lack of technical expertise

Resistance to change from stakeholders

Legacy system compatibility

Data security and privacy concerns

Budget constraints

Lack of institutional support

Other:

Required

Submit

Clear form

Never submit passwords through Google Forms.

This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy

Forms