## EAM.1: The problem definition is coordinated with all parties involved and documented. It describes the objectives, the purpose of the software, the essential requirements, and the desired application class in a concise, understandable way.
Physicians and scientists must disclose valid information about the processes, effects, and risks associated with a particular treatment to patients or participants so that a self-determined, informed consent or refusal can be made. However, such informed consent forms (ICFs) are often complex and therefore difficult to understand. The project's goal is to develop a tool to support the understanding of ICFs by analyzing and visualizing their structure and content. Based on the combination of manual text analysis and automated natural language preprocessing the tool should identify structural similarities and application-specific differences within ICFs. These are then to be mapped to an icon language for easier comprehension. This way the software should create new possibilities of understanding to support an autonomous decision.
\ No newline at end of file
Physicians and scientists must disclose valid information about the processes, effects, and risks associated with a particular treatment to patients or participants so that a self-determined, informed consent or refusal can be made. However, such informed consent forms (ICFs) are often complex and difficult to understand. The project's goal is to develop a tool to support understanding ICFs by analyzing and visualizing their structure and content. Based on the combination of manual text analysis and automated natural language preprocessing the tool should identify structural similarities and application-specific differences within ICFs. These are then to be mapped to an icon language for easier comprehension. This way the software should create new possibilities of understanding to support an autonomous decision.
## EAM.2: Functional requirements are documented at least including a unique identifier, a description, the priority, the origin, and the contact person.
...
## EAM.3: The constraints are documented.
- It was decided to develop the front and back end in the same programming language (Python). Reason: Python offers many libraries that support machine learning and natural language processing.
- It was decided that no user data should be collected. Reason: Data reduction and data economy; are not needed for the software to work
## EAM.4: The quality requirements are documented and prioritised.
