Versions Compared

Version Old Version 11 New Version 12
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Objectives

  • To define the framework and direction for the architecture and design efforts of all projects on the integration roadmap

  • Provide ‘tools’ for traceability from business and IT objectives through architecture to implementation.

  • Provide a common vocabulary to communicate overarching Integration Architecture principles and direction across multiple communities within Columbia University including integration teams, web services, academic applications, PeopleSoft and SIS development teams, IT management and business groups.

  • Provide the means against which to measure architectural compliance of the work product from the various Columbia University IT teams chartered to produce integration solutions.

  • Provide guidance for building the Columbia University Integration Platform consisting of COTS solution (will be selected via RFP).

  • Define the Columbia University Integration Reference Architecture

Integration Strategy

  1. API Strategy (published Nov. 2016) 

    1. Draft next version (unpublished google doc)

Integration Processes

  1. API - InTake Process

  2. API - Process Flow

Architectural Standards

Enterprise Integration Methodology

Patterns

  1. /wiki/spaces/CUITEA/pages/60130251

  2. /wiki/spaces/CUITEA/pages/60130204

 APIs

  1. Restful API - Best Practices

  2. API Specification ({json:api} and RAML 1.0)

  3. Schema Standards (json-schema.org)

  4. API/Integration Domain Names

Security

Integration Templates

  1. Interface Specification Template

  2. Data Mapping Template

Resources