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 Process View within the 4+1 model. The process view deals with the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the run time behavior of the system. The process view addresses concurrency, distribution, integrator, performance, and scalability, etc. UML diagrams to represent process view include the sequence diagram, communication diagram, activity diagram.
Use Case Dynamics
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.
- Desktop interactions.
- Mobile computer (notebook, laptop, etc.) interactions.
- Tablet interactions.
- Smartphone interactions.
- Use as a utility via web (browser) based delivery.
- Front-end web server interactions.
- Cascaded web server interactions.
- Server utility federated interactions.
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 Repository interactions.
- EATS framework interactions.
- Operating environment interactions.
- Physical hardware interactions.
- Logical View
- Process View
- Development View
- Development Plan
- Component Packaging
- Eclipse IDE Configuration
- Maven Build System
- Physical View