1. Prototype review and feedback
    1. how do we store data?
      1. WYSIWYG editor, html, wiki mark up?
      2. does the tool normalize the data?
      3. we need to store the data in the same format
    2. attachments
      1. risk of having same document attached in two or more places, so updates are not captured universally
      2. have certain information stored in one specific place (e.g. all terms and conditions are attached to the "license bundle")
    3. configuration dependencies
      1. we will keep the list flat and add content type for differentiation
    4. version field will be open text (need to capture for certain products)
    5. "assets" (license, finance, support) linked to service offering and configuration item. Linking of assets to "service" level removed.
    6. parent to child links in service, offering, and configuration item are done using different widgets (checkbox, multiselect, autofill) on purpose, for evaluation
  1. Prototype Next Steps
    1. proper configuration of "assets."
    2. adding "vendor" and linking relationships
    3. team adding "configuration item" data in order to test Views of SWRT and VSLS product grids
      1. build out Distributed Software as a service (Steve)
      2. use information//data for Office 2010 (Dave)
  1. Retirement of Mac OS X 10.5 as case study for draft retirement process
    1. checklist
    2. "at-a-glance" document

Next team meeting is December 1, 2011: will work on draft retirement checklist and milestones for portfolio prototype (Dec through March)

  • No labels