Systematic Analysis
Software quality is dynamic and the result of active management.
To systematically increase performance, stability, and quality,
targeted, results-oriented management tools are used to continuously evaluate and improve both
software systems and development processes.
While organizational control of software quality operates at the strategic level,
the study of resilient software systems focuses on functional mechanisms based on three fundamental properties:
prevention, response (adaptation and maintenance), and recovery (restoration and evolution).
From a functional perspective, this results in the activities
(1) avoiding failure states,
(2) responding to failure states and maintaining essential system functions, and
(3) restoring the target state, including necessary lessons learned activities.
This approach goes beyond simply improving reliability (ISO/IEC 25010)
through failure prevention and correction (see ).
Improving performance through qualitative measures
Evaluation of Software Systems and Processes:
The evaluation (audit process) offers the opportunity to support even smaller,
resource-poor organizations in better protecting information by systematically assessing architectural and development practices.
The audit process encompasses software systems and processes and is based on objective standards (e.g., NIST SP 800-160). The results provide an objective basis for investments, addressing both economic benefits and risks.
Analysis of Organizational Elements:
Software doesn't emerge in a vacuum; it requires organizational structures and human interaction. Increased complexity, frequent errors and runtime failures, and slower development are symptoms of declining organizational performance. Team, work culture, management, individual expectations, and the situational environment are the key challenges facing modern organizations. This dynamic and multidimensional construct of the situation thus comes into focus.
The results of the analysis of socio-technical factors allow for the identification, prioritization, and
implementation of measures to strengthen organizational performance and increase quality, as well as to reduce risks.
It is not only in common parlance that it seems plausible to describe quality as relevant to ;
in detail, this phenomenon can be applied to software engineering and further specified through resilience engineering.
How does resilience engineering differ from other quality concepts?
How resilience engineering differs from other quality concepts becomes clear when compared with a quality characteristic
such as reliability.
Reliability, according to the ISO/IEC 25010:2023 standard, is understood as a quality characteristic that describes
how long and under what conditions a specified performance is or can be delivered.
This characteristic is related to one or more system functions and specified requirements.
Resilience engineering can be understood as an interdisciplinary paradigm that focuses on the design of resilient systems.
Resilient systems are designed to react adaptively. This means they can anticipate and absorb disturbances and
restore impaired functions.