An architecture is the set of significant decisions about the organization of a software system; the selection of structural elements and their interfaces by which the system is composed; together with their behavior as specified in the collaborations among those elements; the composition of these elements into progressively larger subsystems; and the architectural style that guides this organization - these elements and their interfaces, their collaborations, and their composition.
If you were to ask anyone to describe "architecture" to you, nine times out of ten, they'll make some reference to structure. While an architecture defines structure and behavior, it is not concerned with defining all of the structure and all of the behavior. It is only concerned with those elements that are deemed to be significant. Significant elements are those that have a long and lasting effect, such as the major structural elements, those elements associated with essential behavior, and those elements that address significant qualities such as reliability and scalability.
Many definitions of architecture also acknowledge not only the structural elements themselves, but also the composition of structural elements, their relationships (and any connectors needed to support these relationships), their interfaces, and their partitioning.
Below is a short list of some of our service capabilities: