Architecting and designing : Unified Architecture Framework (UAF) : Resource viewpoints
  
Resource viewpoints
The UAF Resource domain supersedes the Systems domain of DoDAF, NAF, MODAF, and DNDAF. Resource viewpoints enable you to capture the physical Systems that are used to get work done in the organization – and also Resources in general – or Resource Artifacts. UAF adds concepts to the metamodel such as Software and Technology, and also classifies Organizations, Posts (job titles), and Persons as physical Resources (previously they were mostly thought of as operational performers).
The core concept that you capture in the Resources view is what Systems (or Resources) are used to get work done, and the Functions they perform – these Functions are at the Resource or System level (in DoDAF they were called System Functions). These are quite different than Operational Activities which are functions of the enterprise. So, for example, an Operational Activity for a Search and Rescue organization would be “Search”. You use physical resources or systems to perform a Search, such as a Drone. The Drone is a system that has Functions.
The full set of Resource viewpoints is:
Rs-Cn Resource Connectivity
Rs-Cn Resource Connectivity (Resource Interfaces)
Rs-If Resource Information: Physical Model
Rs-Is Resource Interaction Scenarios: Resource Roles
Rs-Is Resource Interaction Scenarios: Resources
Rs-Pr Resource Processes: Decomposition
Rs-Pr Resource Processes: Flow
Rs-Rm Resource Roadmap: Evolution
Rs-Sr Resource Structure
Rs-St Resource States
Rs-Tr Resources Traceability (Activity To Function)
Rs-Ct Resource Constraints
Parent topic
Unified Architecture Framework (UAF)