Application Architecture

On this page:

What is application architecture?

The definition of an architecture used in ANSI/IEEE Std 1471-2000is: "the fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution." — Source: MSDN

You can think of enterprise application architecture from four perspectives:

  • The business perspective
    How does your business work? What are your strategies for moving your business from the "as-is" to the "to-be"?
  • The application perspective
    What is your current application portfolio? What plans do you have for moving your portfolio from the "as-is" to the "to-be" in order to support your business perspective and stay aligned with evolving technology platforms?
  • The information perspective
    What does your organization need to know, and when? Do you have an enterprise data model? What are the patterns of information production and consumption?
  • The technology perspective
    What hardware and software do you need to support the application and information perspectives?

Produce software that works

Application architecture defines the structure and integration of your software components in a fashion that addresses each of the above four perspectives.

A good architecture is critical for producing software that works. It is necessary for you to address specific software requirements in a cost-effective and forward-thinking manner.

Let us help you

All custom application work we do includes an architecture phase. We can also complete your architecture or architectural review as a sub-project in conjunction with your broader project effort. Architectural work may focus on your enterprise, one or more applications, integration, or a combination of the three.

We work in both the Microsoft .Net and Java realms.