The accuracy manager component

This component controls a view with two main parts: in the Prevention column we have all statistics regarding the current (active) prevention solution. It will contain a description about the prevention mechanism, where it is placed, and how many times it was hit during the last run.

In the cure column we have the option to add feedback about the incident that happened after application execution. In other words, the main difference between prevention and cure is that prevention is a read-only in-memory object that is created during the application run cycle, while cure is a CRUD-able Firebase object (CRUD: Create, Read, Update, and Delete) that we have full control over how it is going to be managed within the component's view. The following screenshot summarizes the business logic for this component:

Like a real life problem, in our application cure cannot control the prevention, but prevention may have a chance to delete a specific cure if a condition is met...