Develop an overview of how the software is deployed. 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 locations), defined in user profiles and use cases
-
organization of business data
-
service level requirements
-
constraints (such as requirements to interface with legacy systems)
Provisionally assign components and data to nodes, and indicate how users access components that access data. Detailed
specification of nodes and connections is deferred, except where they are important for estimating or assessing
viability. Existing assets can be used if appropriate assets are available.
Although this is the first operational model produced in the project, and it is produced quickly and at a high level,
it might identify actual hardware and software products if they are known, or if it is important to make these
selection decisions at this time.
If a non-trivial distributed system is required, then deployment units can be specified by grouping components (and
their different operational facets). This significantly reduces the number of things that need to be placed and the
level of complexity in developing the operational architecture aspect of a complex, distributed IT system.
|