Requirements

As part of the requirement acquisition process, various functional, non-functional, and environmental requirements were developed through discussions with General Dynamics Mission Systems. The following contains a brief overview of these requirements. For a full list of requirements, see the documents page.

Functional Requirements

The following high-level functional requirements are as follows:

• The solution should be developed as a mobile application.
• The application allows the user to select a radio waveform.
• The application allows the user to provision a selected radio waveform.
• The application allows the user to activate a radio waveform.
• The application supports transfering files over the connected radio simulator.
• The application supports receiving files over the connected radio simulator.

In addition, the following deliverables are to be provided to General Dynamics:

• A demonstration report of the solution
• All necessary source code
• Design documentation
• Design review material

Performance (Non-Functional) Requirements

The following high-level non-functional requirements are as follows:

• The application should not take longer than 30 seconds to load.
• The application should display a progress bar if the loading time takes longer than 3 seconds.
• The icon bar at the top of the screen should be updated every 0.5 to 2 seconds.
• The application should use safe colors to account for any color blindness such as Deuteranopia, Protanopia, and Tritanopia.

Environmental Requirements

The following high-level environmental requirements are as follows:

• The application should be compatible with android versions 12, 13, and 14, with primary focus on android 13.
• The application should be able to send and receive emails up to 20 MB each.
• The application should support up to 10 emails queued for transmission.