scholarly journals A Knowledge Engineering Process for the Development of Argumentation Schemes for Risk Management in Software Projects

2017 ◽  
Author(s):  
Denise Da Luz Siqueira ◽  
Lisandra M. Fontoura ◽  
Rafael H. Bordini ◽  
Luis A. L. Silva
Keyword(s):  
Risk Management ◽  
Knowledge Engineering ◽  
Argumentation Schemes ◽  
Engineering Process ◽  
Software Projects

Argumentation Schemes for Collaborative Debate of Requirement Risks in Software Projects

2017 ◽  
Vol 27 (09n10) ◽  
pp. 1613-1635 ◽  
Author(s):  
Denise da Luz Siqueira ◽  
Lisandra M. Fontoura ◽  
Rafael H. Bordini ◽  
Luis A. L. Silva
Keyword(s):  
Artificial Intelligence ◽  
Risk Management ◽  
Argumentation Schemes ◽  
Software Projects ◽  
Quality Requirements ◽  
Poor Understanding ◽  
Software Engineers ◽  
Client Needs ◽  
Significant Class

Managing risks in real-world software projects is of paramount importance. A significant class of such risks is related to the engineering of requirements, commonly involving the presentation and analysis of risk management arguments from both software engineers and clients involved in collaborative debates. In this work, drawing inspiration from argumentation theory in Artificial Intelligence, we introduce a number of “argumentation schemes” and associated “critical questions” to support such discussions. In doing so, we propose schemes related to risks due to excessive numbers of requirements; inadequate client representatives and poor understanding of client needs; incorrect, incomplete and conflicting requirements; complex and non-traceable requirements; non-stable requirements; and low quality requirements. We also discuss a case study and two experiments where the developed schemes supported the discussion of requirement risks in software projects. The overall results of these experiments indicate that our schemes are useful in the identification, proposition and analysis of requirement risks, adequately supporting debates on requirement risks.

Case study on risk management practice in large offshore‐outsourced Agile software projects

IET Software ◽  
2014 ◽  
Vol 8 (6) ◽  
pp. 245-257 ◽  
Author(s):  
Srikrishnan Sundararajan ◽  
Marath Bhasi ◽  
Pramod K. Vijayaraghavan
Keyword(s):  
Risk Management ◽  
Management Practice ◽  
Software Projects ◽  
Agile Software

Practical Experience in Customization for a Software Development Process for Small Companies Based on RUP Process and MSF

2011 ◽  
pp. 71-93 ◽  
Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Practical Experience ◽  
Software Development Process ◽  
Small Companies ◽  
Engineering Process ◽  
Software Projects ◽  
Software Engineering Process ◽  
Unified Process

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).

Adapting a Requirements Engineering Process by Key Factors Estimation

2022 ◽  
pp. 709-725
Author(s):  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn ◽  
Viviana Alejandra Ledesma
Keyword(s):  
Requirements Engineering ◽  
Situational Factors ◽  
Engineering Process ◽  
Key Factors ◽  
Software Projects ◽  
Requirements Engineering Process ◽  
Requirements Process ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Specific Control

Literature mainly focuses the adaptation of any requirements engineering process on the possible variations of elicitation techniques, mainly due to information sources characteristics. However, these particularities, usually called situational factors, are seldom considered in other activities of the requirements process. Most situational factors, when considered in software projects, have a high influence on the requirements process. Therefore, the different situations that may attempt against or may favor a successful requirements process should be identified at the beginning of the project. Additionally, some of such factors may evolve along software development life cycle; this should motivate a reengineering of the requirements process at some strategic milestones. In this chapter, a process for constructing and dynamically adapting a requirements process is proposed, focusing on the evolving factors. The process follows rules based on different combinations of situational factors at specific control points and manages a repository of process blocks to perform the tailoring.

Dealing with Risk: A Practical Approach

1996 ◽  
Vol 11 (4) ◽  
pp. 333-346 ◽  
Author(s):  
Fred J. Heemstra ◽  
Rob J. Kusters
Keyword(s):  
Risk Management ◽  
Practical Approach ◽  
Successful Outcome ◽  
Software Projects ◽  
Counter Measures ◽  
Neutral Process ◽  
Related Approach ◽  
Process Risk ◽  
Management Method

Most software projects take place in a volatile environment in which many dangers exist that may affect the successful outcome of the project. After completion of the project an evaluation may show that many of the problems encountered during the project could have been foreseen before they actually occurred. Risk management is an approach that is aimed at predicting the occurrence of this type of problem and at taking counter measures to either prevent them from affecting the project or to soften their impact. In this paper the basic activities related to risk management are described. Furthermore a concrete method aimed at supporting risk management is presented. This method has been used successfully in practice. Some of the results obtained by using it are presented on the basis of five cases. Some conclusions are that: (1) the use of a short and structured checklist will ease identification of and discussions about risks, (2) a risk management method in which explicit use is made of a group related approach, involving all parties, will increase reliability and acceptance of the results, and (3) involvement of a neutral process risk advisor will further both the successful use of the method and the acceptance of the results.

scholarly journals Integrating a Usability Engineering Process into a Consisting Risk Management

2018 ◽  
Vol 4 (1) ◽  
pp. 645-647
Author(s):  
Michael Scholtes ◽  
Stephanie Buedenbender ◽  
Annemarie Behrend ◽  
Keywan Sohrabi ◽  
Volker Gross
Keyword(s):  
Risk Management ◽  
Medical Device ◽  
Engineering Process ◽  
Usability Engineering ◽  
User Interactions ◽  
Management Processes ◽  
Medical Device Manufacturers ◽  
Incident Reports ◽  
Development Step ◽  
Medical Device Regulation

AbstractThe complexity of medical devices and its user interactions increases. A growing number of incident reports are assumed to be associated primarily with user errors. This development is tackled through current modifications in standards, such as ISO 13485:2016 and legislations, such as the Medical Device Regulation. Both intensify the focus on use errors significantly. The aim of this paper was the development of a process orientated approach integrating usability engineering into a consisting risk management based on a classic V-model. An appropriate procedure was worked out. For each development step, risk and usability activities were cumulated. Thus, the present paper might help medical device manufacturers to reflect their risk management and usability management processes to find synergies. Prospectively, a step-by-step guide for the integration of risk management and usability engineering based on this approach should be developed.

Sign in / Sign up

Export Citation Format

Share Document