RisCal -- A Risk Estimation Tool for Software Engineering Purposes

Haisjackl, Christian; Felderer, Michael; Breu, Ruth

doi:10.1109/seaa.2013.10

Cited by 9 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The authors use a set of risks identified in software projects as a guide in this stage; these are listed in [117]. Haisjackl et al [70], for their part, state that this stage should make it possible to identify the different risk elements, as well as to then store them on a list of risk elements, since they will serve to establish the criteria and measurements that will enable us to determine the probability of risk, the factors of impact and of evolution of risk. This stage also provides a procedure that allows the risk exposure value to be calculated.…”

Section: Tablementioning

confidence: 99%

“…They also assert that in risk analysis it is possible to carry out an estimation of impact, exposure, and relationships between risks, as well as analysing the options for risk mitigation and the actual mitigation strategies used. Haisjackl et al [70] establish that in risk analysis exposure to risk can be calculated by applying some metrics. These measures can be applied manually; it is recommended that the stakeholders should take part in this process.…”

Section: Primary Studies Risk Management Activitiesmentioning

confidence: 99%

“…2 Odzaly et al [69] A prototype tool for agile risk management, within the context of agile projects; it makes use of software agents to support risk identification, evaluation, and monitoring [69]. 3 RisCal [70] This is a generic tool that supports all the risk estimation activities. The activities in this estimation are risk identification, risk analysis, and risk prioritisation.…”

Section: Limitations Of This Studymentioning

confidence: 99%

See 2 more Smart Citations

Risk management in the software life cycle: A systematic literature review

Masso

Pino

Pardo

et al. 2020

Computer Standards & Interfaces

View full text Add to dashboard Cite

Risk management (RM) plays a key role in project management, as it allows identification and prompt management of threats that may arise during project execution. Furthermore, project management within the software industry is evolving rapidly nowadays, a fact that implies new challenges, because the emergence and use of fresh approaches has brought a greater degree of complexity to the RM process. The objective of this paper is to carry out a systematic literature review (SLR) in the field of software risk, in an attempt to characterize and present the state of the art of this field, identifying gaps and opportunities for further research. From the analysis of the results of this SLR it could be observed that interest on the part of the scientific community has turned away from the definition of research work that addressed an integrated risk management process, to pay attention to work that concentrates on specific activities of this process. It was also possible to see that there is a clear lack of scientific rigour as regards the process of validation in the different studies, and a deficiency in the use of standards or of de facto models to define these.

show abstract

Section: Tablementioning

confidence: 99%

Section: Primary Studies Risk Management Activitiesmentioning

confidence: 99%

Section: Limitations Of This Studymentioning

confidence: 99%

See 1 more Smart Citation

Risk management in the software life cycle: A systematic literature review

Masso

Pino

Pardo

et al. 2020

Computer Standards & Interfaces

View full text Add to dashboard Cite

show abstract

“…In fact, most work on risk management in the context of requirements engineering focuses on identifying risks in a bottom-up approach and analysing risks during the requirements engineering process. For instance, Asnar et al [15] provide a goal-driven approach for risk assessment in requirements engineering, and Haisjackl et al [16] provide an estimation approach and respective tool support [16]. For risk management within requirements engineering itself, Lawrence et al [17] provide a list of top risks in requirements engineering, which includes overlooking a crucial requirement, inadequate customer representation, modelling only functional requirements, not inspecting requirements, attempting to perfect requirements before beginning construction as well as representing requirements in the form of designs.…”

Section: Background and Related Workmentioning

confidence: 99%

On Evidence-Based Risk Management in Requirements Engineering

Méndez

Tießler

Kalinowski

et al. 2017

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Background: The sensitivity of Requirements Engineering (RE) to the context makes it difficult to efficiently control problems therein, thus, hampering an effective risk management devoted to allow for early corrective or even preventive measures. Problem: There is still little empirical knowledge about context-specific RE phenomena which would be necessary for an effective contextsensitive risk management in RE. Goal: We propose and validate an evidence-based approach to assess risks in RE using cross-company data about problems, causes and effects. Research Method: We use survey data from 228 companies and build a probabilistic network that supports the forecast of context-specific RE phenomena. We implement this approach using spreadsheets to support a light-weight risk assessment. Results: Our results from an initial validation in 6 companies strengthen our confidence that the approach increases the awareness for individual risk factors in RE, and the feedback further allows for disseminating our approach into practice.

show abstract

“…The tooling may include printed forms as well as software tool support to perform the computations in an automatic way. Software tools supporting risk assessment for testing may be spreadsheets, specific risk assessment or management tools [28], or test or project management tools. The tooling is often fixed already before the risk model is defined, e.g., because a specific test management tool has to be used, and influences the definition of the risk model.…”

Section: Toolingmentioning

confidence: 99%

A Risk Assessment Framework for Software Testing

Felderer

Haisjackl

Pekar

et al. 2014

Leveraging Applications of Formal Methods, Verification and Validation. Specialized Techniques and Applications

Self Cite

View full text Add to dashboard Cite

Abstract. In industry, testing has to be performed under severe pressure due to limited resources. Risk-based testing which uses risks to guide the test process is applied to allocate resources and to reduce product risks. Risk assessment, i.e., risk identification, analysis and evaluation, determines the significance of the risk values assigned to tests and therefore the quality of the overall risk-based test process. In this paper we provide a risk assessment model and its integration into an established test process. This framework is derived on the basis of best practices extracted from published risk-based testing approaches and applied to an industrial test process.

show abstract

RisCal -- A Risk Estimation Tool for Software Engineering Purposes

Cited by 9 publications

References 11 publications

Risk management in the software life cycle: A systematic literature review

Risk management in the software life cycle: A systematic literature review

On Evidence-Based Risk Management in Requirements Engineering

A Risk Assessment Framework for Software Testing

Contact Info

Product

Resources

About