Software architecture is different from software design. The architecture is a view of the system as a whole rather than a collection of components assembled into a system.

We strongly believe in system architecture information conveyed in several books, white papers and case studies that application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.

Systems requirements are inherently ambiguous, intuitive, and informal. Defining requirements is a right-brain activity. Software is logically unintuitive and meant to be interpreted unambiguously by a machine. Software is a left-brain activity. Architecture bridges the semantic gaps between requirements and software.

Our technical architecture process involves the following steps:

1. Study the goals of the business in a clear and concise manner, using a notation that is readable by both humans and machine
2. Identify the Information Technology already in place that meets these goals.
3. Identify gaps in the levels of Information Technology that fail to meet these goals.
4. Identify the organizational structure needed to support the implementation of the strategy.
5. Define a layered framework for connecting the system components.