• Solve one or more mission need
  • Look beyond the functional requirements of a project
    • Consider needs like security, support, training, information assurance, business continuity, expected lifecycle, and financial model to make sure that it will be successful
  • Stress a service & component oriented philosophy - as opposed to a technology-centered view.
    • How does a project, position, service make UNL competitive?


  • Lifeblood of the university
  • All information should be managed consistently, with one source and one owner.
  • Applications and data should be accessible by authorized parties from anywhere & designed for multiple consumers.
    • Information assurance standards, such as those related to authentication & protection of sensitive data at rest and in transit.
  • Applications should support standard methods of access.


  • Use or reinforce what already exists
  • Whenever possible use, reinforce or extend an existing service or building block.
  • When no existing university service exists, explore the option of whether to acquire an existing technology vs. building new.
    • Include community source in the exploration
  • EA will help projects identify reusable assets within the university and, when no asset is available, assist in evaluating options according to principles.


  • Use agreed-upon standards whenever possible
  • Standards include specific technologies as well as processes to consider when using complete solutions.
  • The process of maintaining useful standards requires input and collaboration from many parties.
  • Standards should be updated and published as technologies change, by the individuals or groups most directly involved in their application - with input from the broader organization.
  • Should improve the ability of services to scale to serve broader needs.