## 5 Application to a Specific Case Study: ITER Divertor Remote Handling System
### ITER MAMIC Model Definition  
By integrating an iterative software development cycle within a MAMIC architecture, teams can effectively manage complexity, respond to change, and deliver high-quality software that meets the evolving needs of stakeholders and users. Focusing on the ITER environment, the MAMIC architecture presents an approach for building software systems with a centralized core that is separate from its interactions with external interfaces. This is realized through the utilization of ports and adapters, as depicted in Figure 5.  
The driving agents (primary) are those that initiate the interaction: the external input controller transfers data to the application through a port, the RH task operations in structure language process it in an automatic or semi-automatic way, and third-party frameworks send the data through the adapter to carry out some actions. The driven agents (secondary) are those that respond to the application's request: a database adapter is called upon by the application to retrieve the data, an RH controller device is commanded by the application layer and also publishes status information through the port, and mixed reality is presented to visualize the in-vessel critical environment. The domain layer is divided into several bounded contexts. These are a self-contained and delimited space where a specific set of business problems can be solved in isolation from the rest and without affecting anything beyond this context. Each context has its own set of concepts, terms, and specific domain models and may have its own technical implementation. The different bounded contexts depicted in the figure, which comprise the domain layer, are as follows:  
* Configuration domain: The MAMIC architecture provides a flexible configuration mechanism that allows customization of the design and the internal logic behavior of  
Figure 4: Software development, verification, and validation lifecycle. the RH-IHMI. This customization is achieved through configuration parameters that are stored in the configuration files and loaded during start-up time. * Error handling domain: The error management process defines the software behavior when an error occurs during its execution. The basic steps in an error management process are detection, identification, handling, mitigation, and resolution or recovery. Moreover, this domain is in charge of gathering controller event messages from RH devices and VR, AR, RHDB, and OMS actions. * Task prediction domain/application: This domain is based on predictive modeling, in which artificial intelligence can be included in the RH-IHMI to be more configurable, considering its usability by the operator. Therefore, it is necessary to incorporate the best operator inputs to train the artificial intelligence model, such as work hours, when the RH device is working, how much time has been spent on the development of the task, and so on. This domain allows the driving of processes in an automatic or semi-automatic way. This domain operates under continuous operator supervision, enabling manual intervention to return the system to a safe state at any time. * World interaction domain: An interactive experience in which the sensor readings are combined with HMI-generated content. The content can span multiple sensory modalities, including visual, auditory, haptic, somatosensory, and olfactory. Moreover, other techniques, such as augmented reality, are designed as a system that incorporates three basic features: a combination of real and virtual worlds, real-time interaction, and accurate 3D registration of virtual and real objects. * Assistant operation domain: In this domain, a cognitive architecture is applied, dividing the bounded context in different node behavior generation; world modeling, which interacts with the world interaction domain; sensory processing, adding user perception and operator fatigue state; and a value judgment process together with a knowledge database. In each node, there exists both a deliberative and a reactive component.