Technology Architecture, a big term that really means a defined framework by which applications can interact with one another and with the people who are using them.

A technology architecture within an organization defines a common set of tools and resources used for developing and supporting applications. If properly implemented, these become building blocks for supporting a technology, at many levels: application, database, operating system and server infrastructure. In the long run, this ”building block” approach helps to keep software manageable and cost-effective. In a web-connected world, a defined technology architecure helps to make sure we connect data and business processes across applications to “get stuff done” more efficiently.

2011: Renewal of architecture to happen in Summer 2011.

2010: Collaboration with UBC-IT on broader technology architecture issues and opportunities.

2009: Sauder LTS took the first step to define a technology architecture that would become the foundation for implementing new application and server environments.

Why is technology architecture important?

Over the past few years LTS has been migrating several of Sauder’s “legacy” applications, which ran in old technologies (i.e. FoxPro, Novell Netware). These technologies   are no longer supported by the vendor and/or rely on outdated operating systems that cannot be integrated with contemporary “web services” environments. Business processes, data and related software applications all need to work together, but outdated software environments inhibit Sauder’s ability to share business processes and data effectively.

Click on the links to the right to view our Goal Architecture, a list of the applications that we use and an overview of the infrastructure that supports us.