Second round of requirements review

Level 1 AI generated duplicate requirements:

[x] REQ-1 and REQ-108: Both involve regular intervals for data checks.
[x] REQ-2 and REQ-66: Both deal with making recommendations and warnings based on insufficient or abnormal data.
[x] REQ-3 and REQ-39: Both mention manual override/input of glucose data.
[x] REQ-5 and REQ-7: Both involve warnings when the insulin pump or other components are out of range.
[x] REQ-5 and REQ-23: Both involve the OpenAPS system alerting the human actor if it is no longer receiving information.
[x] REQ-6 and REQ-51: Both involve the insulin pump falling back to normal operation under certain conditions.
[x] REQ-8 and REQ-128: Both involve the insulin pump on low battery.
[x] REQ-9 and REQ-35: Both involve making dosing recommendations at specific intervals.
[x] REQ-10 and REQ-58: Both involve the accuracy and validation of the OpenAPS algorithm.
[x] REQ-11 and REQ-29: Both deal with communication problems and fallback to human-programmed basal rates.
[x] REQ-13 and REQ-87: Both involve detecting and acting upon communication issues.
[x] REQ-14 and REQ-63: Both involve plausibility checks on data.
[x] REQ-16 and REQ-49: Both involve warnings for improper connection of OpenAPS components.
[x] REQ-17 and REQ-19: Both involve checking connections and dependencies.
[x] REQ-17 and REQ-42: Both involve hardware integrity checks and connections.
[x] REQ-21 and REQ-111: Both involve integrity and validation checks for communication and data.
[x] REQ-22 and REQ-7: Both involve watchdog timers to detect insulin pump issues.
[x] REQ-24 and REQ-107: Both involve interpreting error signals and ensuring data integrity.
[x] REQ-25 and REQ-26: Both involve battery life and power warnings.
[x] REQ-31 and REQ-171: Both involve ensuring correct dependencies.
[x] REQ-32 and REQ-169: Both involve restoring software dependencies.
[x] REQ-33 and REQ-54: Both involve flagging compatibility and operational constraints.
[x] REQ-34 and REQ-138: Both involve heartbeat mechanisms for system monitoring.
[x] REQ-37 and REQ-46: Both involve ensuring correct time settings.
[x] REQ-38 and REQ-92: Both involve notifying time discrepancies between components.
[x] REQ-41 and REQ-47: Both involve handling time zone changes.
[x] REQ-43 and REQ-60: Both involve matching and validating glucose level data.
[x] REQ-48 and REQ-179: Both involve security of the OpenAPS rig.
[x] REQ-50 and REQ-81: Both involve human verification of entered data.
[x] REQ-52 and REQ-53: Both involve checking for compatible dependencies.
[x] REQ-55 and REQ-56: Both involve ensuring accurate configuration and time settings.
[ ] REQ-57 and REQ-90: Both involve awareness of Insulin On Board (IOB) and active dosing.
[x] REQ-61 and REQ-124: Both involve manual glucose readings for validation.
[x] REQ-62 and REQ-80: Both involve validating data from Nightscout and other sources.
[x] REQ-67 and REQ-68: Both involve incorporating human bolus dosing into IOB calculations.
[x] REQ-71 and REQ-219: Both involve advising on correct settings and timings.
[x] REQ-72 and REQ-89: Both involve verifying correct insulin pump settings.
[x] REQ-75 and REQ-208: Both involve prompting the human for data under certain conditions.
[x] REQ-77 and REQ-131: Both involve warnings about low insulin or hypoglycemia.
[x] REQ-82 and REQ-35: Both involve making dosing recommendations at regular intervals.
[x] REQ-84 and REQ-226: Both involve pulling configurations from the insulin pump.
[x] REQ-86 and REQ-195: Both involve fallback to normal pump operation if OpenAPS is disconnected.
[x] REQ-91 and REQ-57: Both involve ensuring awareness of IOB and active dosing.
[x] REQ-97 and REQ-100: Both involve specifying compatible versions.
[x] REQ-99 and REQ-157: Both involve verifying compatibility with insulin pump software and hardware.
[x] REQ-102 and REQ-125: Both involve warnings about incompatible versions.
[x] REQ-104 and REQ-106: Both involve checking timestamps for data validity.
[x] REQ-109 and REQ-112: Both involve using recent data for dosing recommendations.
[x] REQ-114 and REQ-115: Both involve considering timing changes when updating the algorithm.
[x] REQ-116 and REQ-117: Both involve specifying and monitoring scheduling and program flow.
[x] REQ-118 and REQ-126: Both involve synchronizing times accurately.
[x] REQ-120 and REQ-125: Both involve warnings when Nightscout or other components are not online.
[x] REQ-122 and REQ-157: Both involve compatibility checks with interfacing applications and hardware.
[x] REQ-123 and REQ-121: Both involve plausibility checks and time expectations for received data.
[x] REQ-128 and REQ-8: Both involve monitoring insulin pump battery.
[x] REQ-135 and REQ-132: Both involve verifying glucose level projections and accuracy.
[x] REQ-139 and REQ-38: Both involve notifying time discrepancies between components.
[x] REQ-140 and REQ-134: Both involve suspending insulin dosing during hypoglycemia.
[x] REQ-141 and REQ-216: Both involve clarity and completeness of rig setup instructions.
[x] REQ-146 and REQ-148: Both involve updating documentation with system changes.
[x] REQ-150 and REQ-128: Both involve warnings about wrong SD card size or format.
[x] REQ-156 and REQ-157: Both involve checking compatibility and allowing only tested configurations.
[x] REQ-160 and REQ-209: Both involve documenting errors found in instructions.
[x] REQ-166 and REQ-166: Both involve notifications and update prompts.
[x] REQ-168 and REQ-168: Both involve keeping track of and testing major updates to dependencies.
[x] REQ-170 and REQ-170: Both involve prompting updates when new versions are available.
[x] REQ-178 and REQ-178: Both involve involving new devices to improve functionality.
[x] REQ-184 and REQ-165: Both involve e-mail notifications for updates.
[x] REQ-188 and REQ-190: Both involve feedback to the human actor about dosing recommendations and doses administered.
[x] REQ-195 and REQ-86: Both involve fallback to normal operation if OpenAPS is disconnected.
[x] REQ-200 and REQ-191: Both involve ensuring that insulin dosing is working correctly.
[x] REQ-202 and REQ-204: Both involve clear labeling and warnings on the rig.
[x] REQ-205 and REQ-138: Both involve permanent warning symbols for problems.
[x] REQ-212 and REQ-75: Both involve prompts for meal data or other human inputs.
[x] REQ-214 and REQ-135: Both involve adjusting recommendations based on data accuracy.
[x] REQ-218 and REQ-217: Both involve advising on the timeframe for providing meal data.
[x] REQ-224 and REQ-85: Both involve warnings and prompts for non-recommended configurations.

Level 2 AI generated duplicate requirements:

[x] REQ-1 & REQ-5 & REQ-7 & REQ-8 REQ-1: OpenAPS shall be able to detect if dependencies are completely installed to match the current OpenAPS algorithm. REQ-5: OpenAPS shall have a script which can be run to detect if all dependencies are completely installed. REQ-7: There shall be a script to test that all the required dependencies have been installed which is separate from the installation script. REQ-8: OpenAPS install script shall have pre-install and post-install scripts, pre-install makes sure that OpenAPS has dependencies before the installation of OpenAPS, post-install makes sure that everything which is required has been installed.
[x] REQ-3 & REQ-4 REQ-3: Human shall make sure that the script has been run successfully. REQ-4: Human shall make sure OpenAPS installation has been successful.
[x] REQ-2 & REQ-24 & REQ-88 REQ-2: Raspberry OS is up to date. REQ-24: RasPi OS must not have broken dependencies and packages. REQ-88: OpenAPS must not have broken dependencies and packages.
[x] REQ-9 & REQ-10 REQ-9: OpenAPS shall check whether the software update is effective and conforming to OpenAPS recommendations in the context of the versions of the other components in the user's system. REQ-10: OpenAPS shall require specific versions of dependencies which have been tested to be compatible with all of the components.
[x] REQ-21 & REQ-27 REQ-21: For each RasPi OS dependency, the version(s) that are compatible with each supported version of OpenAPS must be documented. REQ-27: OpenAPS developers shall specify the versions of RaspiOS which are supported on each version of OpenAPS.
[x] REQ-29 & REQ-43 REQ-29: On boot, RaspiOS shall automatically start OpenAPS. REQ-43: RasPi OS must believe that it is looping when it is looping.
[x] REQ-11 & REQ-14 REQ-11: Human shall be warned in documentation not to install too many packages. REQ-14: Human user shall be warned of any possible security threats.
[x] REQ-31 & REQ-74 REQ-31: OpenAPS itself shall check to see if there is a newer version of OpenAPS installed. REQ-74: OpenAPS shall be able to detect whether the other component is able to receive and action command.
[x] REQ-41 & REQ-123 REQ-41: Alarm is needed if a handshake is expected but missing for too long. REQ-123: When communication is failing, insulin pump must fall back to regular operation.
[x] REQ-32 & REQ-51 REQ-32: OpenAPS shall check for multiple instances of it running. REQ-51: OpenAPS must recognize when its communication with RasPi OS is flawed.
[x] REQ-66 & REQ-67 REQ-66: Include unique identifiers (address, application name etc.) to more clearly indicate if a signal is from the OpenAPS app. REQ-67: Implement unique identifier or two-step verification prompt when there's a new input device that prevents accidental sending of commands from an unexpected source.
[x] REQ-56 & REQ-61 REQ-56: RasPi OS shall be able to recognize all devices that OpenAPS is expecting. REQ-61: RasPi OS shall recognize all commands that it has been issued by the OpenAPS app.
[x] REQ-77 & REQ-76 REQ-77: When RasPi hardware fails, insulin pump must fall back to regular operation. REQ-76: When RasPi processor is hung, insulin pump must fall back to regular operation.
[x] REQ-104 & REQ-105 REQ-104: If data that has an unexpected data format/data content is received, OpenAPS must be able to detect it. REQ-105: There must be a defined reaction of OpenAPS to unexpected data (to alarm the user or the other device/s).
[x] REQ-71 & REQ-73 REQ-71: OpenAPS shall send commands to be queued, wait for acknowledgement from NightScout; otherwise keep in queue and attempt to resend again. REQ-73: Wait for acknowledgement from NightScout; otherwise keep in queue and attempt to resend again.
[x] REQ-62 & REQ-59 REQ-62: If the algorithm determines that a command is unsafe, the system shall fallback to regular insulin pump operation and the user shall be notified. REQ-59: If a command from OpenAPS is not received by an external device (e.g., for network reasons), if safety-critical, warn the user and fallback to regular operation.
[x] REQ-33 & REQ-68 REQ-33: User shall have fresh install of Raspi OS on machine that meets minimum requirements with no other applications running except for OpenAPS. REQ-68: If Raspi OS is malfunctioning and not sending the correct commands, the user shall be notified to reinstall the Raspi OS and the piu.
[x] REQ-98 & REQ-99 REQ-98: OpenAPS shall provide a service to test the safety of algorithms. REQ-99: OpenAPS shall have a facility to allow the human to test an algorithm, while running a different algorithm, and compare dosing recommendations.
[x] REQ-102 & REQ-101 REQ-102: OpenAPS shall have a fixed spot to check for and implement updates in every (~5 minute) OpenAPS loop. REQ-101: OpenAPS shall have a fixed spot to check for and implement updates, either new settings or software updates, in every (~5 minute) OpenAPS loop.

elisa-tech / wg-medical-devices

Second round of requirements review #25