An IT architecture project is typically started to define a complete architecture for the "system". In this case, the objectives of the project are to produce a complete perspective, or set of perspectives. The set of perspectives required need to be specified at the very least. Other options are possible, depending upon the needs of the enterprise. These possible objectives are summarize, and by no means limited to:

• Perspectives - complete IT architecture perspectives are defined: Business, Logical and Technical, with the require set specified;
• Simple - a Simple IT architecture, largely based upon existing documentation, is to be define at the Logical and/or Technical level;
• Entity Models - this effort is focused on the Entity models, typically based upon an existing IT architecture with the goal of defining this Technical level model to the point where data modelers take over and define the implementation level models;
• Storage & Servers - this effort is focused on the Locations models, typically based upon an existing IT architecture with the goal of defining the enterprise strategy for servers (e.g. consolidation) and / or storage (rationalization or centralization);
• Network & Telecommunications - this effort is focused on the Locations models, typically based upon an existing IT architecture with the goal of defining the enterprise model and strategy for the IP network and perhaps the telecommunications (WAN) network as well. The purpose and objectives for this effort defines the required focus;
• User Processes - this effort is focused on the Process and Roles models, typically based upon an existing IT architecture with the goal of re-engineering processes and / or rationalizing or improving the user experience. Introducing new technologies (presentation or workflow) may be part of the focus of this effort.

There are likely many other areas, or combinations of aspects, where IT architecture project could be focused, depending upon the needs of the enterprise.