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 Physical View within the 4+1 model. The physical view depicts the system from a system engineer’s point of view. It is concerned with the topology of software components on the physical layer as well as the physical connections between these components. This view is also known as the deployment view. UML diagrams used to represent the physical view include the deployment diagram.
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 physical aspects of 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.
- Desktop deployment.
- Mobile computer (notebook, laptop, etc.) deployment.
- Tablet deployment.
- Smartphone deployment.
- Use as a utility via web (browser) based delivery.
- Front-end web server deployment, potentially embedded on a user device.
- Cascaded web server deployment, a resource to other web servers which may be responsible for the direct interaction with the user.
- Multi-machine deployment 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.
- Integrated knowledge-base deployment
- External database system deployment
- Remote database deployment
- Cascaded, federated database deployment
- EATS framework version roll-forward, inter-version inter-operations
- v4.6 deployment
- v5.2020 deployment
- Operating Software version roll-forward, inter-system inter-operations
- Windows deployment
- Linux deployment
- Apple-based deployment
- Android deployment
- Physical hardware architectural family roll-forward, inter-architecture inter-operations
- i86 deployment
- RasPi deployment
- Android deployment
- Logical View
- Process View
- Development View
- Development Plan
- Component Packaging
- Eclipse IDE Configuration
- Maven Build System
- Physical View