System/Application Architecture

System architecture is that subset of Enterprise Architecture that deals with how specific applications are designed and how they interact with each other.

A properly thought out system architecture can reduce the overall total cost of ownership in the long term by providing many benefits such as alleviating compatibility and interoperability problems between applications, allowing faster system upgrades, and making it easier to enhance applications to keep up with evolving business needs.


Typical questions related to system architecture include:
How do I select a distributed technology that meets my current and future needs?
What is "N-tier" architecture?
What is a "Service-Oriented" architecture and how can it improve my IT agility?
What are "Web Services" and why should I be concerned?
Which platform is best for me - Java or Microsoft .NET?
How do I prevent myself from being "married" to a vendor?
    Where does Open Source software fit in my strategy?
How do I make sure I am leveraging all the capabilities of the web?
Is my software scalable? Will it perform under load?
    Where are the potential bottlenecks in the system and how can they be addressed?
How do I architect my systems so that I do not end up with "islands of automation" but rather a completely integrated suite of enterprise applications?
    How do I integrate my existing "islands of automation

<<Back to Skills and Benefits Continuum™