1. Presenters: Hampton Sublett & Curtis Bray Date: November 15 th, 2011 Time: 2:30 ORGANIZING THE INTEGRATION OF MULTIPLE APPLICATIONS WITH A STAND-ALONE RICE SERVICE

2. AGENDA 1.About Us 2.Rice @ UC Davis – Background 3.Distributed Apps integrating w/ Rice 4.Committee Organization & Key Docs 5.Technology & Architecture 6.Staying in Sync 7.Campus Communications 8.Key “Take-Aways” 9.Q&A

3. ABOUT US: UC DAVIS Founded 1905 4 Colleges & 6 Schools $600+ in Research ‘09 Only Trauma 1 center in Sacramento Teaching Vet Hospital 1.5hr drive SF or Lake Tahoe

4. ABOUT US: APPLICATION DEVELOPMENT Management Hampton Sublett – Program Manager Curtis Bray – Technical Manager Purview Middleware Infrastructure (IAM, Rice) Enterprise Services (Campus Portal, Online Directory, Sakai) Web Development (campus recharge development services)

5. RICE @ UC DAVIS - BACKGROUND KFS - initial driver for Rice @ UC Davis MyInfoVault Kuali Coeus (next year) Time & Reporting System (next year) Rice rounds out UCD’s Middleware offerings Fills gap for enterprise workflow / service bus eDocLite offering

6. DISTRIBUTED APPS INTEGRATING W/ CENTRAL RICE KC – Office of Research & Safety Services MIV – Academic Personnel KFS – Account & Finance Local App - Vet Med RICE – Information Tech

7. COMMITTEE ORGANIZATION & KEY DOCS Committees: Rice Oversight Committee Project Coordination workgroup Technical Coordination workgroup Key Documents Charters (Committees & Workgroups) Terms and Conditions Service Level Agreements Roadmap

8. UC DAVIS RICE ROADMAP

9. TECHNOLOGY & ARCHITECTURE

10. TECHNOLOGY & ARCHITECTURE (CON’T) Rice environments are all virtualized Environments Development sandboxes Development integration QA Stage Production Simultaneous support of multiple releases

11. TECHNOLOGY & ARCHITECTURE (CON’T)

12. STAYING IN SYNC Project Tools Confluence - Service documentation, agendas/notes, plans Jira - Dev & Ops issues, including Deployments Technical Docs to Integrating App teams Configuration samples/guidelines Release notes with impacting issues

13. STAYING IN SYNC (CON’T) Integrated QA testing Coordinated load and functional testing Release Management SVN, Bamboo/Maven, Standard version # scheme 1.0.3.1 UCD-SR2 – UC Davis’s service release Day of Release Integrated Release Plan Communications (Instant Message) Application Signoffs

14. STAYING IN SYNC (CON’T) Contributions Tendered developer / Jira patch submission Integrates local fixes back to foundation Our Jiras track Local vs Foundation fixes

15. CAMPUS COMMUNICATIONS Who & When? = Balancing Act Audience: Technology or Business How soon? Expectations? How frequent? By what means?

16. KEY “TAKE-AWAYS” 1.Identify all key groups/apps and sponsors 2.Forge a partnership & create key docs for future 3.Frequent, recurring meetings w/ partners 4.Leverage agile technologies 5.Est. detailed integrated release plans/processes 6.Use shared collaboration tools 7.Communicate

17. QUESTIONS?

18. CONTACT US Curtis Bray – App Dev Technical Manager clbray@ucdavis.edu Hampton Sublett – App Dev Program Manager hbsublett@ucdavis.edu