...
We want to discuss how this effort can converge and support the Service Catalog project, and how to coordinate these efforts.
Discussion:
SE effort around the IS&T Website is two fold:
- rebrand the website
- redefine the Service Catalog
There is agreement that the Portfolio (as the robust data source) could easily drive the Catalog (web presentation of a subset of this data), thus alignment is key. We should all be using the same language, in the Portfolio, the Catalog, the Ticketing Tool and Hermes.
In more simple terms, the Portfolio is the backend, the website is one front end.
The website has significant time constraints, and needs to be completed by June 30th, 2011. This will be an issue in terms of synchronizing and development that takes place.
Agreed on next steps:
- cross pollinate at the conceptual model level and move in parallel
- develop a data dictionary (Portfolio and Catalog together)
- collect the data (Portfolio and Catalog together)
- define layers of website (Catalog)
- define model and repository for procurement thru release processes (Portfolio)
- integration and reconciliation (Portfolio and Catalog together)