| Prev | Next |
UAF Services Views
The UAF Services Views encompass a set of viewpoints that describe services and their interconnections in support of DoD functions, covering both warfighting and business domains. These viewpoints link service resources to operational and capability requirements, ensuring alignment with operational activities and enabling effective information exchange. Within the broader architecture, they explore how services are contextualized by mapping resource flows, analyzing service functionality and behavior, modeling task workflows and functional decompositions, and creating matrices that define relationships between systems and services. They also capture the specifications of service connections that implement operational resource flow exchanges. Taken together, the Services Views provide a comprehensive perspective on service-oriented architecture, bridging operational needs with the technical realization of services that underpin organizational functions and enterprise-wide information sharing.
UAF Services Views
|
ServicesTaxonomy Sv-Tx |
Stakeholders: Enterprise Architects, Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: Service types and required and provided service levels of these types. Definition: Shows the taxonomy of types of services and the level of service that they are expected to provide or are required to meet through the display of actual measurements associated with the Provided and Required Service Level. |
|
Services Structure Sv-Sr |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: Combination of services required to exhibit a capability. Definition: Shows the composition of services and how services are combined into a higher level service required to exhibit a capability or support an operational activity. |
|
Services Connectivity Sv-Cn |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: Interoperability among services Definition: Specifies service interfaces, e.g., provided and required service methods, signal receptions, and/or flow properties, to ensure compatibility and reusability of services. |
|
Services Processes Sv-Pr |
Stakeholders: Security Architects, Security Engineers. Concerns: The specification of the Security Control families, security controls, and measures required to address a specific security baseline. Definition: Provides a set of Security Controls and any possible enhancements as applicable to assets. The activity diagram describes operational or resource level processes that apply (operational level) or implement (resource level) security controls/enhancements to assets located in enclaves and across enclaves. This Security Process view can be instantiated either as a variant of an activity/flow diagram or as a hierarchical work breakdown structure. |
|
Services States Sv-St |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: The behavior of a service in terms of states and events causing transitions between states. Definition: Specifies the possible states a service may have, and the possible transitions between those states. |
|
Services Sequences St-Sq |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: The behavior of a service in terms of expected time-ordered examination of the interactions between service roles. Definition: Specifies how service roles interact with each other, service providers and consumers, and the sequence and dependencies of those interactions. |
|
Services Constraints Sv-Ct |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: Service policies that apply to implementations of services. Definition: Specifies traditional textual service policies that are constraints on the way that services are implemented within resources. The addition of SysML parametrics provide a computational means of defining service policies across the enterprise or within a specific service configuration. |
|
Services Roadmap Sv-Rm |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: Service changes over time. Definition: Provides an overview of how a service changes over time. It shows the combination of several services mapped against a timeline. |
|
Services Traceability Sv-Tr |
Stakeholders: Solution Providers, Systems Engineers, Software Architects, Business Architects. Concerns: Traceability between operational activities and services that support them. Definition: Depicts the mapping of services to operational activities and how services contribute to the achievement of a capability. |