Identifying architectural goals is all about deciding what architecturally-significant things you plan to focus on.  Look at the requirements and work with the team to describe the goals for the architecture. These goals should be regularly reviewed to make sure that they are still valid and that the system is on track to deliver them.

For more information, see Concept: Architectural Goals.

Identify the key concepts and abstractions that the system needs to handle. The requirements are good sources for key abstractions.  Don't spend too much time describing abstractions in detail at this initial stage, because there is a risk that spending too much time will result in identifying classes and relationships that the solution does not actually need.

When identifying key abstractions, it can be useful to also define any obvious relationships that exist between them. These can be captured in a table or in diagrams (in a tool or whiteboard. In general, it is not worth agonizing over defining a highly detailed set of relationships at this early stage in design. The relationships will become more concrete and detailed later and will probably modify these early assumptions. 

For more information, see Concept: Key Abstractions.

Identify which of the current requirements are architecturally significant. Explore and refine those that must be implemented in order to realize the Architectural Goals. See Concept: Architecturally Significant Requirements for more information.

Architecturally significant requirements that are poorly understood or likely to change should be prioritized for clarification and stabilization. In some cases, this means further requirements analysis should be done before implementing the requirement. In other cases, some form of prototyping may be best.

In addition to identifying which of the requirements are architecturally significant, it is also important to propose an approach for meeting those requirements.

Gather information about the existing environment and identify any constraints in the solution. List any constraints on the architecture and any trade-offs between competing requirements and resources. Decide how the architecture will meet these issues. Justify each of the decisions made and capture this information. Regularly review the list of constraints to make sure that they are still valid and that no new ones have appeared.

For more information, see Concept: Architectural Constraints.

Survey, assess, and select available assets.  Identify assets from other areas that may be reused in the current architecture. For more information, see Guideline: Software Reuse.

Decide how to partition the software, both in logical and physical terms. Partitioning your system helps you manage its complexity by using the well-known "divide and conquer" strategy. By breaking the process into smaller and more manageable pieces, you make development easier.

As a minimum, decide on:

• How to partition the software when managing development (the use of layering as a partitioning strategy, for example).  For more information, see Guideline: Layering.
• How the software will be composed at run time.

For each software partition, briefly describe

• Its name and purpose.
• Its relationships to other partitions.

At this point, you do not need to identify the elements that should be placed in each of these partitions.  Instead, you define how many partitions you will need and how they should be related. Later, during design activities, you decide which elements will populate these partitions.

Describe the overall approach for how the software will be deployed over the nodes on the network. For example, determine if the system needs to be accessed remotely, or has requirements that suggest distribution across multiple nodes.

Some sources of information to consider are:

• users at geographical locations
• organization of business data
• service level requirements
• constraints (such as requirements to interface with legacy systems)

Work with stakeholders such as network support and deployment teams to ensure that the proposed approach is a good fit for the wider technical environment.

Validate that the proposed deployment approach supports users (especially those users at remote locations if this is required) performing typical usage scenarios while satisfying nonfunctional requirements and constraints.

Make a list of the technical services that the system needs to provide and capture some basic information about each item on the list. It's generally a good idea to make an initial list of all the mechanisms required for the project and then prioritize the development of those that need to be delivered to achieve the architectural goals.

At this point, usually only the analysis mechanisms are defined.  However, specific Architectural Constraints may mean that some of those mechanisms can be described as design mechanisms (even at this early stage).

For more information on architectural mechanisms, see Concept: Architectural Mechanism. 

At this point, identify the external systems with which this system must interact.  An external system may be anything from software to hardware units that the current system will use, such as printers, terminals, alarm devices, and sensors.

Describe thpose interfaces at a high level, concentrating on the information that must pass between the systems.