- data model updates
- prototype status
- Rich has expressed interest in developing our prototype in drupal
- questions we need to answer first:
- what is Rich's resource commitment?
- could we get bumped by DCAD in terms of priority?
- what is Rich's timeline?
- what is the Service Catalog's timeline in terms of needing the data?
- is Rich open to this being malleable?
- data model may change
- business requirements may change
- how flexible is Rich? How long would resources be available for us as we learn things and as things change?
- Pat, Dave and Steve meeting with Rich to discuss on 9/23
- provide Rich requirements, data model and business rules about what data is to be held in the system
- Rich will come back with functional specs and what additional info he needs from us
- architect as resource - Kevin Lyons to consult?
- no, we are using an existing platform
- inform Kevin once technology decision is made
- need to formalize business rules in October (what data is tracked where)
- need to revisit Product Release Checklist in October
- need to start looking at what is next for the Library of Procedures
- distributed sw life cycle
- retirement process
- "how to run a release project"
- distributed sw life cycle
- download server option to move to Server Ops
- need monitoring
- needs SLA
- evolution to a download service?
- can we talk to Paul about the current level of service and improve from there? Garry will facilitate
- next steps
- Pat set up mtg with Rich - done
- Dave working on update to data model and business rules about what data is to be held in the system
- Dave will reach out to Alison as to status of Catalog categorization breakdowns to update diff doc
Overview
Content Tools
Activity