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

Compare with Current View Page History

Version 1 Next »

  1. We need to keep the IS&T software grid data model defined firmly as a subset of the service portfolio model.
  2. To do that, we need to establish a feedback loop between the design teams (do Pat and Alison establish this?)
  3. The service-to-product mapping we’ve done might solve design problems in the software grid if it’s a many-to-many relationship. (A “product” can be a component of more than one “service.”)
  4. Functions in the umbrella “portfolio” design might be currently performed by IS&T web pages that are in the IS&T look and feel but not integrated into Drupal or into the Web Services team for support. Propose this? To who? Consider: 3Down, request forms maintained by network.
  5. Noted by Chris that Higher Ed has not solved the “software grid” problem but the software and IT-services industry has lots of download-and-support web sites to analyze. This analysis would be useful to either project.
  • No labels