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

Compare with Current View Page History

« Previous Version 4 Next »

MAP stands for "MIT Application Platform." It is a set of services provided by IS&T for the MIT software-development community. This charter lays the foundation for:

The primary team members are currently selected from development teams across IS&T, with plans to expand. Facilitation and management of MAP is provided by ISDA (Infrastructure Software Development and Architecture). MAP is part of IS&T's goal of better supporting of, and engaging with, the larger MIT developer community.

We will leverage all necessary technologies to make software development and system implementation by the MIT Community faster and easier, and to make access to enterprise data both easier and more secure.
The road map for our services is set by the MAP Working Group. All aspects of MAP are supported by DSPS. Formalization and prioritization of MAP services are reviewed by the MAP Steering Committee.

This road map will be public information at all times and subject to comment and review by the MIT community.

Roles by Team

The MAP Working Group

  • The Working Group is composed of Programmer/Analysts with hands-on programming projects at MIT.
  • They develop reference implementations and developer documentation useful to one another.
  • They plan with ISDA their developer support and infrastructure needs.
  • They have access to ISDA web-services and client-integration platforms which they can extend on their own.
  • They are the liasons between ISDA and their own respective development teams.

The MAP Steering Committee

  • The committee is composed of Senior Consulting Architects in IS&T.
  • They review the Working Group's contributions and determine which contributions should migrate from "contrib" status to the official MAP Handbook and Repository.
  • They help IPS prioritize infrastructure services specified by the Working Group

The Infrastructure Platform Support team in ISDA supports the MIT Application Platform.

  • Based on the Steering Committee's input, IPS polishes contrib material for inclusion in the Handbook.
  • They support working group members with their use of MAP systems.
  • They are the liason to vendors whose products become part of MAP, representing the needs of the Working Group and the Steering Committee.
  • They support and update the fundamental MAP infrastructure.

Service Level Agreements

These are some notes about SLAs we will need around MAP.

Managers' SLA

  • Steve arranged with other Managers that the members of the Working Group are assigned to the effort, so this is not a user group or club.
  • A Manager is someone who reports to a Director. This represents a "wing" of a given organization.
  • That manager commits to a 2-3 day-per-month availability of the developer for MAP work.
  • In return, that manager knows the developer has access to web-services and client-integration platforms to do work directly related to their immediate integration needs.
  • Right now, each "wing" gets one representative only. That person is a liason to the rest of his/her team.

SLA between IPS and the Working Group

  • The Working Group helps set the direction for IPS for the continuous improvement of all aspects of MAP
  • However, the Working Group is constrained by limitations set by IPS. These limitations will be based formal support avenues.
    • Example: The Java framework must be designed around tools from which we can get consistent support from a vendor (right now, SourceLabs). Adding new tools to the supported framework have to come by taking the time to work with the vendor.
    • Example: The client-integration platform's features, and therefore the architecture for UI clients to MAP services, will be constrained by the platform we choose.
  • IPS and the Steering Committee set the acceptance criteria to platform enhancements developed by the working group.
  • No labels