Kruchten 4+1 Model
The principal viewpoint set for the EATS Technical Architecture is Philippe Kruchten’s 4+1 View model. The Technical Architecture defines choices made in the design of the system, and constraints that limit how the Application Architecture can, or must, accomplish intention. When constrained to the cyber components within the architecture the Kruchten 4+1 View model becomes comprehensive.
The focus of this component is the Scenarios View within the 4+1 model. The scenarios describe sequences of interactions between objects and between processes. They are used to identify architectural elements and to illustrate and validate the architecture design. They also serve as a starting point for tests of an architecture prototype. This view is also known as the use case view.
Use Case Scenarios
Scenarios are used to define requirements, design objectives, and test requirements. They define the general functionality to be placed on the technology which implements the system architecture.
From a technical architecture perspective the key use case scenarios associated with validation of the architecture have to do with the usability of the technology from it’s three distinctive presentation frameworks:
- Use as a primary application as an independent utility delivered via direct instantiation of an automation instance of EATS on a user device.
- Mobile computer (notebook, laptop, etc.).
- Use as a utility via web (browser) based delivery.
- Front-end web server, potentially embedded on a user device.
- Cascaded web server, a resource to other web servers which may be responsible for the direct interaction with the user.
- Use as a server-based, networked utility as part of a federation of two or more EATS instances acting in cooperation as a unified, federated set of information services.
In addition addition to the ability of an instance of the system to provide functional interactive services related to application purpose (e.g., documentation, modeling, etc.) the system must demonstrate it’s ability to perform routine cyber evolutionary tasks.
- Knowledge-base back-up/restore, import/export.
- EATS framework version roll-forward, inter-version inter-operations
- Operating Software version roll-forward, inter-system inter-operations
- Physical hardware architectural family roll-forward, inter-architecture inter-operations
- Logical View
- Process View
- Development View
- Development Plan
- Component Packaging
- Eclipse IDE Configuration
- Maven Build System
- Physical View