Principle Name
Common Use Applications (potential rewording – Adopt “standard” solutions that can be shared across business units and functions, avoiding redundancy or duplication)
Statement
Development of applications used across the University is preferred over the development of similar or duplicative applications which are only provided to a particular organization.
Rationale
Duplicative capability is expensive, difficult to support, and proliferates conflicting data. We should create reusable, scalable, and flexible solutions.
Implications
- Organizations will be discouraged from develop capabilities for their own use which are similar/duplicative of University-wide capabilities. In this way, expenditures of scarce resources to develop essentially the same capability in marginally different ways will be reduced.
- We should proactively manage the entire application lifecycle, and look for opportunities to create, combine, and sunset solutions as things evolve.
Architecture Domains
- Application