Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Like any other such term, these terms are used differently in different places, and are sometimes interchangeable. Here's what the differences typically are:</p> <ul> <li>The <strong>Application Architect</strong> is is what many of us just call the Architect. The person responsible for the highest levels of design and scope for a particular solution/project. You'd bother using <em>Application</em> in the title if there were other types of architects around, and you wanted it clear that this person worries mainly about a particular application. </li> <li>The <strong>Enterprise Architect</strong> is worried about <em>all</em> of a companies solutions. How they rely on each other, how they use each other, how efficient can their common upkeep and improvement be made. He thinks about how all the solutions together support the company's mission. Only a larger company could warrant this grandiose title. The Enterprise Architect is a big shot who meets with the CIO, CTO, and other such big shots.</li> <li>The <strong>Systems Architect</strong> might be considered to have a wider scope than the Application Architect, and less than an Enterprise Architect. This title is sometimes the exact same thing as Application Architect - big shot on a <em>particular</em> project. Sometimes the <em>System</em> part of the title cannotes a wider scope: person who duties include software but also <em>hardware</em> and <em>IT</em>, or someone worried about multiple projects.</li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload