Architecting and designing : NATO Architecture Framework (NAF) : NAF v3 : Creating Technical Architecture View products for NAF 3 : Technical Architecture View (NAF 3)
  
Technical Architecture View (NAF 3)
The technical component of an architecture is the set of rules that governs the implementation and operation of the system.
The following standards apply to the technical architecture view:
Architecture view defines a set of standards and rules that govern system implementation and system operation.
Technical views are based on associations between operational requirements.
Standards and criteria should reflect multiple paradigms for implementing information systems.
Architecture view accommodate new technology, evolving standards and the phasing out of old technology.
Technical architecture should be driven by commercial standards and direction.
Technical architecture profiles account for the requirements of multiplatform and network interconnections among all systems that produce, use, or exchange information electronically for a specifically bounded architecture configuration.
TV-1 Technical Architecture Profile
In most cases, especially in describing architectures with less than a service-wide scope, “building” a technical architecture view consists of identifying the applicable portions of existing technical guidance documentation, tailoring those portions as needed in accordance in the latitude allowed, and filling in any gaps.
This product references the technical standards that apply to the architecture and how they need to be, or have been, implemented. The profile is time-phased to facilitate a structured, disciplined process of system development and evolution. Time-phasing also promotes the consideration of emerging technologies and the likelihood of current technologies and standards becoming obsolete. A Technical Architecture Profile constructed as part of a given architecture is structured appropriately and in accordance with the purposes for which the architecture is being built. Typically, this process involves starting with one or more overarching reference models to which the system is subject and selecting from them the service areas relevant to the system. For example, because real-time operating system variants are outside the scope of a non-real-time system, real-time services would be dropped from further consideration. The identification of relevant services in service areas subsequently points to agreed-upon standards, to which appropriate options and parameters are applied to create a relevant subset for the system.
TV-2 Standards Technology Forecast
A standards technology forecast is a detailed description of emerging technology standards relevant to the systems and business processes covered by the architecture. It contains predictions about the availability of emerging standards and the likely obsolescence of existing standards in specific time frames (such as 6-month, 12-month, 18-month intervals), and confidence factors for the predictions. The forecast also contains matching predictions for market acceptance of each standard and an overall risk assessment associated with using the standard. The forecast includes potential standards impacts on current architectures, and thus influences the development of transition and objective architectures. The forecast should be tailored to focus on technology areas that are related to the purpose for which a given architecture description is being built, and should identify issues that affect the architecture.
See also
Creating Technical Architecture View products for NAF 3