soft dev Identification Prelim drei

When components of a system are integrated, new characteristics appear that were not present in the individual parts. These are known as

A computer system that includes hardware and software, but crucially includes people, operational processes, and organizational politics, is classified as a

Problems that are complex, have no definitive problem statement, and where stakeholders have conflicting views on the solution are referred to as

In the "Sociotechnical Systems Stack," the layer immediately above the operating system, which handles data management and communications, is often technically referred to as

Unlike hardware systems which usually behave predictably, systems involving human operators may react differently to the same input at different times. This characteristic is called

This specific layer of the sociotechnical stack is governed by regulations, laws, and ethical rules that dictate how a system must be operated within a country or community

This term describes the process of buying or acquiring a system, which involves deciding on the system scope and selecting suppliers

When a system failure occurs not because of a bug, but because the user interface was confusing and caused the operator to make a mistake, this is categorized as a error within the wider system context

This property refers to the ability of the system to deliver services when requested; it is often confused with reliability but focuses specifically on uptime

In the context of legacy systems, this term describes the activity where the system is modified to correct errors or adapt to environmental changes after it has been deployed

This specific emergent property is concerned with the system's ability to resist external attacks or accidental intrusion

This layer of the sociotechnical stack represents the specific set of tasks and workflows that the organization uses to achieve its goals using the software

A system that is deterministic and consists only of hardware and software without the human element is often strictly defined as a

The property that reflects the ease with which a system can be repaired or modified after a failure is discovered is called

The interdisciplinary field that encompasses the specification, design, implementation, validation, deployment, and operation of sociotechnical systems is called

This overarching concept reflects the degree of confidence a user has that the system will operate as expected and will not cause damage if it fails. It is a collective term containing properties like availability and safety

When measuring system performance, this metric does not track how often the system crashes, but rather the probability that the system is up, running, and able to deliver services at the exact moment a user requests them

This specific attribute is concerned with the continuity of service over a specified period. It measures the probability that the system will operate without a failure occurring during a defined time window

In critical systems, this property focuses entirely on ensuring that the system does not inflict injury on people or cause catastrophic damage to the environment, regardless of whether the system actually completes its intended task

This property measures the system's capacity to protect itself and its data from accidental or malicious intrusion

Instead of trying to implement every possible requirement, this approach identifies the most critical dangers to the system and limits the requirements to those necessary to mitigate those specific dangers

This term describes a system state or condition that has the potential to cause an accident or mishap, such as a sensor giving a false reading in a chemical plant

This term refers to the unplanned event or sequence of events which results in human death or injury, damage to property, or environmental harm

To improve dependability, engineers often include multiple components of the same type (e.g., three backup generators) to ensure the system functions even if one fails

This technique involves using different types of components or different implementations (e.g., software written by different teams in different languages) to perform the same function, reducing the chance of a common-mode failure

This dependability property reflects the ability of the system to operate correctly even when erroneous inputs are provided or when unexpected hardware faults occur

If a system failure occurs, this property measures how easily and quickly the system can be restored to an operational state

This type of failure occurs when the system performs the correct computation but delivers the result too late to be useful, which is critical in real-time embedded systems

This term describes the ability of a system to continue delivering a minimum level of service even when part of the system has been compromised or destroyed

The measure of the loss resulting from a mishap, which can be categorized by the severity of the consequences (e.g., catastrophic, marginal, negligible)

This acronym refers to a reliability metric used primarily for systems where services are demanded at irregular intervals, such as an emergency shutdown system

This principle suggests that risks should be reduced to a level where further reduction would cost a disproportionate amount of money compared to the safety benefit gained

This is a specific type of requirement that describes what the system must not do, or constraints on the system to prevent an accident

This term refers to the process of analyzing a system to determine what potential dangers exist before the system is even built

This reliability metric is appropriate for systems that run continuously, such as a web server or air traffic control radar, where the focus is on the frequency of crashes over time

This document or body of evidence provides a reasoned argument that a system is safe to operate in a specific context

In the context of safety specification, this term describes the potential for a system failure to cause damage or injury

This term describes a requirement that defines a checking or protection feature added to the system specifically to ensure safety (e.g., "The system shall check the sensor value every 5ms")

This statistical value represents the average time a component is expected to function before it encounters a failure

This term describes a system state where the system has failed, but it has done so in a way that does not threaten human life or the environment (e.g., a train stopping when the signal is lost)

This process involves assessing the likelihood of a hazard occurring and the severity of its consequences

This type of reliability requirement specifies the required probability of success or failure rate using numerical values (e.g., "The system shall be available 99.99% of the time")

This strategy involves designing the system so that the occurrence of a hazard is made less likely, often through the use of monitoring or interlocks

This term refers to the unplanned event that results in death, injury, or damage, which occurs when a hazard is not controlled

This metric measures the percentage of time that a system is up and running compared to the total time it is required to be operational

This general architectural concept involves including extra components in a system that are not strictly necessary for normal operation but serve to handle failure scenarios

This term describes the specific ability of a system to continue delivering its intended services, perhaps at a reduced level, even when hardware or software faults occur

To prevent common-mode failures where a single design error causes all backup systems to fail simultaneously, engineers use different teams or algorithms to implement the same specification

In this specific software fault tolerance architecture, three or more versions of the software are executed in parallel, and a voting mechanism determines the correct output by majority rule

This is a technique used in error detection where a specific piece of hardware or software monitors the execution time of a process; if the process does not reset the timer within a specific window, it is assumed to have crashed

This fault tolerance strategy involves periodically saving the state of the system to stable storage so that, in the event of a failure, the system can restart from the last known good state rather than from the beginning

This type of error recovery allows the system to correct the damaged state and continue processing without rolling back; it typically requires accurate knowledge of the error type (e.g., error-correcting codes)

This dynamic software fault tolerance technique executes a primary algorithm and then checks the result against an acceptance test; if the test fails, the system restores the state and tries an alternative algorithm

This term refers to a specific type of failure where multiple redundant components fail at the exact same time due to a shared cause, such as a power supply surge or a specification error in the software

This simplistic hardware redundancy architecture uses three identical hardware modules processing the same input, with a voting circuit selecting the majority output to mask a single component failure

This recovery mechanism relies on restoring the system to a previous consistent state after a failure is detected; it is the most common mechanism used in database transaction systems

In the context of diverse programming, this specific component is responsible for comparing the outputs of the different software versions to decide on the result

This term describes a system behavior where, upon the detection of a failure, the system does not stop entirely but continues to provide a subset of the most critical functionalities

This is a check placed inside a Recovery Block to verify that the output of the code execution is valid before passing it to the rest of the system

This specific type of diversity involves running the exact same software on hardware components from different vendors (e.g., Intel vs. AMD) to protect against chip-level design faults

This term refers to a specific piece of information, a software component, or a piece of hardware within the system that has value to the organization and therefore requires protection

This is a weakness or flaw in the system design, implementation, or code that could be utilized by an external party to cause harm to the system

This term describes a circumstance or event with the potential to adversely impact the system, such as a hacker attempting to guess passwords or a fire in the server room

This specific security property ensures that information is not disclosed or made accessible to unauthorized individuals or entities

This refers to the protective measure or mechanism put in place to reduce the system's vulnerability or the likelihood of a threat materializing

This security attribute guarantees that the system's data and resources have not been altered or corrupted by unauthorized activity

This process involves identifying potential dangers to the system, estimating the likelihood of those dangers occurring, and assessing the potential consequences

This formal document or set of rules defines what is allowed and what is prohibited within the system, such as password strength requirements or data access rules

This is the exploitation of a system vulnerability, where a threat actor successfully bypasses security controls to damage or steal assets

This term describes the calculated probability that a specific threat will exploit a vulnerability and cause a specific amount of damage

This architectural strategy involves organizing the system into multiple levels of protection, so that if one level is breached, others remain to protect the assets

This specific process verifies the identity of a user or system entity, ensuring they are who they claim to be (e.g., checking a password)

After identity is confirmed, this process determines what actions the authenticated user is permitted to perform or which data they are allowed to access

This type of security strategy focuses on recovering the system and its data after a successful attack has occurred, rather than preventing the attack

This specific type of threat involves an authorized user misusing their privileges to harm the system, which is often difficult to detect because the user has legitimate access