Skip to main content

Principles

Our principles are cross-functional, high level, and easy to remember concepts that should be considered and applied when designing and building enterprise solutions. These principles should be technology and platform agnostic.

Tab heading icon
Tab heading icon
Strategic
Tab heading icon
Tab heading icon
Secure
Tab heading icon
Tab heading icon
Simple
Tab heading icon
Tab heading icon
Solid
Tab heading icon
Tab heading icon
Scalable
Tab heading icon
Tab heading icon
Sustainable

Align IT solutions and decisions to the strategic imperatives, architecture principles, and BYU's Strategic Plan objectives.

Hidden image
Core Concepts
Actively promote strategic and sustainable partnerships with CES Institutions.
✅ Promote and sustain relationships with strategic commercial vendors.
✅ Services must have well-defined and documented roadmaps which articulate long-term strategic value.
✅ Services must be well-documented and connected to the institutions' IT Services catalog
✅ Purchased and vendor supported solutions are strongly preferred to custom developed, in-house solutions.
✅ Solutions implementing best practice cloud patterns are strongly preferred.
✅ Eliminate unneeded technology and platforms.
✅ Services and solutions that do not meet architectural principles or strategic imperatives must be tracked and should be removed, replaced, or refactored.
✅ Leverage or reuse existing strategic CES and/or campus technology investments.
✅ Design solutions that are broadly applicable and scalable across institutions. Consider the needs and applicability of all CES partners.

Imperatives

Retire & Remove

Unneeded and duplicate technology is eliminated.

Live Golden Rule

Treat each other as the Savior would

Keep Commitments

Build trust by doing what we say
Architect, build, and deliver solutions that are secure, resilient, and incorporate multi-layer, defense-in-depth patterns. Protect user privacy.

Hidden image
Core Concepts
Protect user privacy by adhering to the institution's privacy policy and CES data classification standard.
Build security into the entire application lifecycle.
Assess security risk and build in security controls across all architectural layers (defense-in-depth) that conform to the institution's minimum-security controls.
✅ Data must be classified by sensitivity and business criticality / value using the CES Data Classification standard.
Avoid unnecessary complexity in system designs to reduce failure conditions that expose vulnerabilities.
Insecure, outdated, and end-of-life (EOL) systems should be tracked and removed, refactored, or replaced.
Solutions must leverage industry security standards and design patterns.

Imperatives

Security & Privacy

Protect data, IT systems, people, and good name of the university

Always Available

Technology is reliable and resilient

Retire & Remove

Unneeded and duplicate technology is eliminated.
Solutions should follow well-defined design patterns, templates, models, and approaches to reduce complexity and increase sustainability. Solutions should strive to simplify our IT portfolios and infrastructure.

Hidden image
Core Concepts
Prune and pare down designs, reducing them to essential components. Select the simplest solution that will work.
Solutions should be built using independently deployable components, modules, and services.
Unnecessarily complex systems should be tracked and removed, refactored, or replaced.
Solutions must be loosely coupled and highly reusable.

Imperatives

Retire & Remove

Unneeded and duplicate technology is eliminated.

Always Available

Technology is reliable and resilient

Keep Commitments

Build trust by doing what we say

Security & Privacy

Protect data, IT systems, people, and good name of the university
Solutions should be designed to be resilient and responsive in the face of failure.

Hidden image
Core Concepts
Solutions must be resilient and stay responsive in the face of failure.
Solutions should leverage asynchronous and message-driven design patterns.
Unreliable solutions should be tracked and removed, refactored, or replaced.
Solutions must provide automated testing, monitoring, and alerting.

Imperatives

Keep Commitments

Build trust by doing what we say

Always Available

Technology is reliable and resilient
Systems and services should be designed to accommodate growth and rapidly respond to fluctuations in demand in a cost-effective manner.
Hidden image
Core Concepts
Use cloud services/platforms as business and technology enablers.
Design solutions that are elastic, stay responsive, and automatically respond to varying workloads.
Services that are not scalable should be tracked and removed, replaced, or refactored.
Design scalability into solutions from the start
Design solutions to scale out, not scale up.

Imperatives

Always Available

Technology is reliable and resilient

Keep Commitments

Build trust by doing what we say
Balance long term business capability needs with cost effective technology solutions that are sustainable, manageable, and measurable.
Hidden image
Core Concepts
✅Designs must be well documented, with specific attention on architectural diagrams and artifacts that visualize, conceptualize, and communicate intent.
Documentation must be well organized, and easily discoverable.
Solutions must implement active monitoring, logging, and auditing.
Solutions must implement measurement of system and workflow performance.
Solutions must support continuous testing, integration, and delivery.
Solutions that are not sustainable should be tracked and removed, refactored, or replaced.

Imperatives

Always Available

Technology is reliable and resilient

Security & Privacy

Protect data, IT systems, people, and good name of the university

Keep Commitments

Build trust by doing what we say