User Stories

  • A developer new to MIT visits developers.mit.edu and quickly find answers to preliminary, new-system startup questions from hosting to tools.
  • An end user can easily post developer-support questions and search questions that IPS has answered from prior users.
  • A developer can post an issue ticket with IPS for critical assistance, for instance with web services, and the site helps him understand the difference between a ticket and a forum or FAQ type question.
  • IPS and the MAP working group have UI based ways to contribute content or respond to end user questions.
  • An end user can easily find content that assures him that developers.mit.edu is a supported IS&T service offering.
  • A developer can see an example dashboard that demonstrates working reference examples of our web services and framework implementations, and get quick and easy access to the code
  • IPS and the MAP working group are notified by the system of postings to the site to reduce the need to actively monitor the site.
  • ISDA can track anonymous site access at a level that lets us know about lurker activity.

Constraints

  • No personal, single user blogging or publishing of content via portal technology.
  • Though we are using a portal, no personalized portal pages for now.
  • End users do not have access to portal-customization features.
  • Portal features will be constrained to allow all the required developer-support features but not come into competition with larger CMS and collaboration platform projects that are going on in IS&T.
  • No labels