Distributed Application Development (or DAD)
an initiative of the Office of Executive Vice Chancellor for Academic Affairs at UC San Diego

 

DAD Development Model

Each application developed for academic affairs use will be guided by a structure of groups that will insure project oversight and accountability and still allow for rapid and agile application development. These committees and groups will consist of:

Executive Committee – this is a small group of resource decision makers for an academic affairs application (for our strawman, we are proposing Steve Ross and Kathy Hay for this group). The purpose of this group is to make final decisions on key implementation components of an application and to resolve any issues passed up by the steering/governance group. These people are also responsible for properly resourcing the project as outlined in the MOU.

Governance/Steering Committee: This committee is made up of key members responsible for business process decisions, technical architectural decisions, and project responsibility. While the project is in active development this group acts as a steering committee prioritizing project requirements and design, project timelines, and project implementation.

Stakeholder Advisory group: This group is made up of key stakeholders that act as subject matter experts for the given needs of a project. This group provides specifications through user stories, helps give input as to priority of project requirements, and assists with testing of application. These members can also act as the subject matter experts for their department/division during the implementation phase of a project.

Developer group: This group is made up of the applications developers for a given project and interfaces with the stakeholder advisory group to understand project needs and outcomes. They also work closely with stakeholders under the oversight of the steering committee throughout the project development cycle.

DAD Goals

To produce tools that enhance the productive efficiency and quality of work that gets done in Academic Affairs. These tools are definable, measurable, collaborative and sustainable and delivered as planned. Reliability and transparency are goals of DAD; we want to build trust and confidence to meet stakeholders' stated goals with relevant, consistent product that is delivered in a timely manner.

It is a DAD goal to create tools that are meaningful and collaborative as appropriate. These tools should be founded in the strategic plan with all projects tying back to strategic plan/vision. It is a goal that all products have the ability to interface with existing and future projects. We will have periodic review of applications in portfolio and of the portfolio as a whole.

Guiding Principals

Applications created within the group of participating DAD members shall be considered for applicability to the academic community. Recommendations regarding architectural decisions for such applications shall be made in the context of use for all of academic affairs by the DAD Advisory Committee.

DAD projects must have agreed upon resource requirements and deliverables.

Distributed applications development shall follow MOU documents as drawn up and agreed upon by the EVC, Business, and Technical representatives.

Distributed App Development