Requirement Accuracy (Gereksinim Doğruluğu)

1. On most avionics projects, most requirements pertain to Safety. (False)

In aviation projects, most requirements are not related to safety. Requirements

can be categorized into different categories such as functional, performance,
quality, reliability, availability, maintenance, testing, training, etc. Safety is a
subset of requirements and is referred to as safety-critical requirements. Safety-
critical requirements are those directly affecting or endangering flight safety.
The number of safety-critical requirements varies depending on the project's
complexity, risk level, and standards. However, generally, the ratio of safety-
critical requirements to the total number of requirements is less than 10%.

2. Avionics requirement development must follow a Waterfall. (False)

Developing aviation requirements doesn't necessarily have to adhere to the

Waterfall model. The Waterfall model envisions a sequential and linear
progression of the requirement development process. This model comes with
certain disadvantages, such as predetermined requirements, lack of adaptability
to changes, and validation only up until the testing phase. Therefore, in aviation
requirement development, various lifecycle models can be utilized. Models like
the spiral model, iterative model, incremental model, agile model, etc., can
render the requirement development process more flexible, efficient, and high-
quality. These models facilitate early validation of requirements, adaptability to
changes, and enhancement of customer satisfaction. However, employing these
models requires additional tools and techniques to ensure criteria such as
traceability, consistency, and completeness of the requirements.

3. The best way to assess safety-critical requirements is via test execution. (False)

Security-critical requirements evaluation doesn't solely rely on test execution.

Test execution ensures the validation of requirements, meaning it checks
whether the requirements correctly define what the software should do.
However, test execution doesn't ensure validation, i.e., whether the requirements
fulfill the customer's needs. Both validation and verification are crucial in
evaluating security-critical requirements. Therefore, the most effective approach
to evaluating security-critical requirements involves not just test execution but
also the utilization of other techniques. For instance, techniques such as
requirement reviews, requirement analysis, requirement traceability,
requirement validation and verification matrix, requirement risk analysis, etc.,
can be employed in assessing security-critical requirements.
4. DO-XXX and ARP475A provide clear guidance for developing and assessing
requirements. (True)

DO-XXX and ARP475A provide explicit guidance for requirement

development and assessment. DO-XXX serves as a standard for aviation
software development and validation. DO-XXX categorizes software into five
levels based on its safety-criticality, defining the required activities, methods,
tools, and documents for each level. It contributes to ensuring the quality,
reliability, and security of the software by contributing to the requirement
development and assessment process.On the other hand, ARP475A is a standard
for aviation system development and validation. It outlines the system safety
assessment process and integrates it into the requirement development and
assessment process. ARP475A offers methods and techniques for identifying,
allocating, monitoring, and validating system safety requirements.

5. Most avionics defects are due to bugs and manufacturing defects. (False)

Most aviation errors don't stem from software bugs or manufacturing defects.
Instead, they largely originate from requirement errors. Requirement errors
occur when the requirements are incomplete, incorrect, ambiguous, inconsistent,
immeasurable, unverifiable, or untraceable. These errors typically surface in
later stages of software development, making rectification more challenging and
costly. Requirement errors adversely impact software quality, performance,
security, and customer satisfaction. Hence, preventing and detecting
requirement errors early on is crucial in reducing aviation mishaps.

6. When using model-based development, both system and software requirements

must be textual and external to the model. (False)

When using model-based development, both system and software

requirements are not obliged to be textual and external to the model. Model-
based development is a method where the model plays a central role in the
software development process. It enables requirements, design, coding,
testing, and validation to be conducted through the model. Model-based
development enhances the quality, efficiency, and consistency of the
software development process.
 EXAMPLE
 The software shall be designed using the model-based development method.
 The software shall be compatible with the aircraft’s hardware platform.
 The software shall continuously sense and control the aircraft’s flight
parameters (speed, altitude, direction, acceleration, etc.).
 The software shall select and apply the appropriate control algorithms
according to the aircraft’s flight mode (normal, emergency, maneuver, etc.)
 The software shall determine the aircraft’s flight status (in the air, on the
ground, takeoff, landing, etc.) and give the appropriate control commands.
 The software shall monitor the aircraft’s flight limits (maximum speed,
altitude, angle, etc.) and warn if they are exceeded.
 The software shall provide navigation according to the aircraft’s flight plan
(route, target, timing, etc.) and update it if necessary.
 The software shall record and store the aircraft’s flight data (parameters,
modes, statuses, etc.).
 The software shall select and apply the appropriate mission scenarios
according to the aircraft’s mission type (reconnaissance, attack, defense,
etc.)
 The software shall control and monitor the aircraft’s mission equipment
(radar, camera, weapon, etc.)
 The software shall receive, process and display the aircraft’s mission data
(target, threat, image, etc.)
 The software shall perform a self-diagnosis and report any anomalies or
malfunctions to the pilot and the ground station.
 The software shall update itself automatically when a new version is
available.
 The software shall allow the pilot to adjust the brightness, contrast and
volume of the user interface.
 The software shall calculate the optimal fuel consumption rate according to
the flight mode and plan.
 The software shall detect and avoid any collision with other aircrafts or
objects.
 The software shall encrypt and decrypt the data using the AES-256
algorithm.
 The software shall backup the data to a secure cloud server every 24 hours.
 The software shall log all the events and actions to a text file.
 The software shall display the user interface in English or Turkish according
to the pilot’s preference.