Presenters: Hampton Sublett & Curtis Bray

Date: November 15th, 2011

Time: 2:30

ORGANIZING THE INTEGRATION OF MULTIPLEAPPLICATIONS WITH A STAND-ALONE RICE SERVICE

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

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

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)

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

DISTRIBUTED APPS INTEGRATING W/ CENTRAL RICEKC – Office of Research& Safety Services

MIV – Academic Personnel

KFS – Account & Finance

Local App - Vet Med

RICE – Information Tech

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

UC DAVIS RICE ROADMAP

TECHNOLOGY & ARCHITECTURE

TECHNOLOGY & ARCHITECTURE (CON’T)

• Rice environments are all virtualized

• Environments

• Development sandboxes

• Development integration

• QA

• Stage

• Production

• Simultaneous support of multiple releases

TECHNOLOGY & ARCHITECTURE (CON’T)

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

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

STAYING IN SYNC (CON’T)

• Contributions

• Tendered developer / Jira patch submission

• Integrates local fixes back to foundation

• Our Jiras track Local vs Foundation fixes

CAMPUS COMMUNICATIONS

• Who & When? = Balancing Act

• Audience: Technology or Business

• How soon?

• Expectations?

• How frequent?

• By what means?

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

QUESTIONS?

CONTACT US

• Curtis Bray – App Dev Technical Manager

• clbray@ucdavis.edu

• Hampton Sublett – App Dev Program Manager

• hbsublett@ucdavis.edu