softdev2 eds

New characteristics that appear when system components are integrated and were not present in the individual parts

A computer system that includes hardware, software, people, operational processes, and organizational politics

Complex problems with no definitive problem statement and conflicting stakeholder views

The layer above the operating system that handles data management and communications

The characteristic where systems involving humans may react differently to the same input at different times

The layer governed by regulations, laws, and ethical rules that dictate how a system must be operated

The process of buying or acquiring a system, including deciding scope and selecting suppliers

A failure caused by a confusing user interface that leads an operator to make a mistake

The ability of a system to deliver services when requested, focusing on uptime

The modification of a deployed system to correct errors or adapt to environmental changes

The ability of a system to resist external attacks or accidental intrusion

The set of tasks and workflows an organization uses to achieve its goals using software

A deterministic system consisting only of hardware and software without human involvement

The ease with which a system can be repaired or modified after a failure

The interdisciplinary field covering specification, design, implementation, validation, deployment, and operation of systems

A collective term describing confidence that a system will operate correctly and not cause harm

The probability that a system is operational and able to deliver services when requested

The probability that a system operates without failure over a specified time period

Ensuring the system does not cause injury or catastrophic damage regardless of task completion

Accidental or malicious intrusion into the system and its data

An approach that limits requirements to those needed to mitigate the most critical risks

A system state or condition with the potential to cause an accident

An unplanned event resulting in injury, death, property damage, or environmental harm

Including multiple components to ensure system operation if one fails

Using different implementations to reduce common-mode failures

The ability of a system to operate correctly despite faults or erroneous inputs

How easily and quickly a system can be restored after failure

A failure where correct results are delivered too late to be useful

The ability to continue delivering minimum service after partial system damage

The measure of loss resulting from a mishap based on consequence severity

Probability of Failure on Demand

As Low as Reasonably Practicable

A requirement defining what the system must not do to prevent accidents

The process of identifying potential dangers before a system is built

Rate of Occurrence of Failures

A documented argument supported by evidence that a system is safe in a given context

A requirement defining a checking or protection feature to ensure safety

The average time a component is expected to operate before failing

A failed system state that does not threaten life or the environment

Evaluating the likelihood and severity of hazards

A reliability requirement expressed using numerical values

Designing a system to make hazards less likely to occur

The percentage of time a system is operational

Including extra components to handle failure scenarios

The ability to continue delivering services despite faults

Common-mode failures

Executing multiple software versions in parallel with majority voting

A mechanism that detects system crashes by monitoring execution time

Saving system state periodically to enable recovery after failure

Correcting errors and continuing execution without rollback

A technique that retries alternative algorithms after acceptance test failure

Multiple redundant components failing simultaneously due to a shared cause

Using three identical modules with majority voting to mask failures

Restoring a system to a previous consistent state after failure

A component that compares outputs of diverse software versions

Continuing limited critical functionality after a failure

A check that verifies correctness of output in recovery blocks

Running the same software on hardware from different vendors

A system component or information with value that requires protection

A weakness that can be exploited to harm the system

A circumstance or event with the potential to cause harm

Ensuring information is not disclosed to unauthorized entities

A mechanism used to reduce vulnerability or threat likelihood

Ensuring data and resources are not altered without authorization

Identifying threats, estimating likelihood, and assessing consequences

A formal set of rules defining allowed and prohibited actions

The exploitation of a vulnerability to damage or steal assets

The probability that a threat exploits a vulnerability causing damage

Using multiple security layers to protect assets

Verifying the identity of a user or system

Determining what actions an authenticated user may perform

Restoring systems and data after a successful attack

A threat caused by an authorized user misusing their privileges