An Early Multi-Criteria Risk Assessment Model

2022 ◽  
pp. 612-626
Author(s):  
Priyanka Chandani ◽  
Chetna Gupta
Keyword(s):  
Risk Assessment ◽  
Software Development ◽  
Cumulative Risk ◽  
Requirement Engineering ◽  
Assessment Model ◽  
Risk Assessment Model ◽  
Software Projects ◽  
Development Life Cycle ◽  
Weighted Score ◽  
Software Development Life Cycle

Accurate time and budget is an essential estimate for planning software projects correctly. Quite often, the software projects fall into unrealistic estimates and the core reason generally owes to problems with the requirement analysis. For investigating such problems, risk has to identified and assessed at the requirement engineering phase only so that defects do not seep down to other software development phases. This article proposes a multi-criteria risk assessment model to compute risk at a requirement level by computing cumulative risk score based on a weighted score assigned to each criterion. The result of comparison with other approaches and experimentation shows that using this model it is possible to predict the risk at the early phase of software development life cycle with high accuracy.

An Early Multi-Criteria Risk Assessment Model

2019 ◽  
Vol 21 (2) ◽  
pp. 51-64
Author(s):  
Priyanka Chandani ◽  
Chetna Gupta
Keyword(s):  
Risk Assessment ◽  
Software Development ◽  
Cumulative Risk ◽  
Requirement Engineering ◽  
Assessment Model ◽  
Risk Assessment Model ◽  
Software Projects ◽  
Development Life Cycle ◽  
Weighted Score ◽  
Development Phases

Accurate time and budget is an essential estimate for planning software projects correctly. Quite often, the software projects fall into unrealistic estimates and the core reason generally owes to problems with the requirement analysis. For investigating such problems, risk has to identified and assessed at the requirement engineering phase only so that defects do not seep down to other software development phases. This article proposes a multi-criteria risk assessment model to compute risk at a requirement level by computing cumulative risk score based on a weighted score assigned to each criterion. The result of comparison with other approaches and experimentation shows that using this model it is possible to predict the risk at the early phase of software development life cycle with high accuracy.

A Quantitative Risk Assessment Model for the Management of Software Projects

2003 ◽  
pp. 97-115
Author(s):  
Dan Shoemaker
Keyword(s):  
Risk Assessment ◽  
Information Technology ◽  
Organizational Change ◽  
Assessment Model ◽  
Quantitative Risk Assessment ◽  
Management Model ◽  
Risk Assessment Model ◽  
Software Projects ◽  
Quantitative Management

This chapter presents a comprehensive quantitative management model for information technology (IT). It is assessment based and can be easily implemented without imposing an unacceptable organizational-change solution. It supplies detailed information about the functioning of processes, which will allow managers to both effectively oversee operations, as well as assess their prospective and ongoing risks of execution.

Risk assessment model for venous thromboembolism in hospitalized surgical and non-surgical patients in the 4th Hungarian Antithrombotic Guidelines entitled “Diminution and Treatment of Venous Thromboembolism”

2010 ◽  
Vol 151 (34) ◽  
pp. 1365-1374 ◽  
Author(s):  
Marianna Dávid ◽  
Hajna Losonczy ◽  
Miklós Udvardy ◽  
Zoltán Boda ◽  
György Blaskó ◽  
...  
Keyword(s):  
Risk Assessment ◽  
Venous Thromboembolism ◽  
Assessment Model ◽  
Surgical Patients ◽  
Risk Assessment Model

A kórházban kezelt sebészeti és belgyógyászati betegekben jelentős a vénásthromboembolia-rizikó. Profilaxis nélkül, a műtét típusától függően, a sebészeti beavatkozások kapcsán a betegek 15–60%-ában alakul ki mélyvénás trombózis vagy tüdőembólia, és az utóbbi ma is vezető kórházi halálok. Bár a vénás thromboemboliát leggyakrabban a közelmúltban végzett műtéttel vagy traumával hozzák kapcsolatba, a szimptómás thromboemboliás események 50–70%-a és a fatális tüdőembóliák 70–80%-a nem a sebészeti betegekben alakul ki. Nemzetközi és hazai felmérések alapján a nagy kockázattal rendelkező sebészeti betegek többsége megkapja a szükséges trombózisprofilaxist. Azonban profilaxis nélkül marad a rizikóval rendelkező belgyógyászati betegek jelentős része, a konszenzuson alapuló nemzetközi és hazai irányelvi ajánlások ellenére. A belgyógyászati betegek körében növelni kell a profilaxisban részesülők arányát és el kell érni, hogy trombózisrizikó esetén a betegek megkapják a hatásos megelőzést. A beteg trombóziskockázatának felmérése fontos eszköze a vénás thromboembolia által veszélyeztetett betegek felderítésének, megkönnyíti a döntést a profilaxis elrendeléséről és javítja az irányelvi ajánlások betartását. A trombózisveszély megállapításakor, ha nem ellenjavallt, profilaxist kell alkalmazni. „A thromboemboliák kockázatának csökkentése és kezelése” című, 4. magyar antithromboticus irányelv felhívja a figyelmet a vénástrombózis-rizikó felmérésének szükségességére, és elsőként tartalmazza a kórházban fekvő belgyógyászati és sebészeti betegek kockázati kérdőívét. Ismertetjük a kockázatbecslő kérdőíveket és áttekintjük a kérdőívekben szereplő rizikófaktorokra vonatkozó bizonyítékokon alapuló adatokat.

Signature Analysis: Statistical Models and Their Application to FA

1996 ◽  
Author(s):  
C.K. Lakshminarayan ◽  
S. Pabbisetty ◽  
O. Adams ◽  
F. Pires ◽  
M. Thomas ◽  
...  
Keyword(s):  
Risk Assessment ◽  
Failure Analysis ◽  
Statistical Models ◽  
Essential Elements ◽  
Assessment Model ◽  
Signature Analysis ◽  
Risk Assessment Model ◽  
Sample Sizes ◽  
Reliability Engineering ◽  
Semiconductor Chips

Abstract This paper deals with the basic concepts of Signature Analysis and the application of statistical models for its implementation. It develops a scheme for computing sample sizes when the failures are random. It also introduces statistical models that comprehend correlations among failures that fail due to the same failure mechanism. The idea of correlation is important because semiconductor chips are processed in batches. Also any risk assessment model should comprehend correlations over time. The statistical models developed will provide the required sample sizes for the Failure Analysis lab to state "We are A% confident that B% of future parts will fail due to the same signature." The paper provides tables and graphs for the evaluation of such a risk assessment. The implementation of Signature Analysis will achieve the dual objective of improved customer satisfaction and reduced cycle time. This paper will also highlight it's applicability as well as the essential elements that need to be in place for it to be effective. Different examples have been illustrated of how the concept is being used by Failure Analysis Operations (FA) and Customer Quality and Reliability Engineering groups.

Computable metrics of personal performance in software development teams

2019 ◽  
Author(s):  
Andriy Lishchytovych ◽  
Volodymyr Pavlenko
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Product Quality ◽  
Performance Indicators ◽  
Key Performance Indicators ◽  
Project Manager ◽  
Development Life Cycle ◽  
Software Product ◽  
Software Development Life Cycle

The present article describes setup, configuration and usage of the key performance indicators (KPIs) of members of project teams involved into the software development life cycle. Key performance indicators are described for the full software development life cycle and imply the deep integration with both task tracking systems and project code management systems, as well as a software product quality testing system. To illustrate, we used the extremely popular products - Atlassian Jira (tracking development tasks and bugs tracking system) and git (code management system). The calculation of key performance indicators is given for a team of three developers, two testing engineers responsible for product quality, one designer, one system administrator, one product manager (responsible for setting business requirements) and one project manager. For the key members of the team, it is suggested to use one integral key performance indicator per the role / team member, which reflects the quality of the fulfillment of the corresponding role of the tasks. The model of performance indicators is inverse positive - the initial value of each of the indicators is zero and increases in the case of certain deviations from the standard performance of official duties inherent in a particular role. The calculation of the proposed key performance indicators can be fully automated (in particular, using Atlassian Jira and Atlassian Bitbucket (git) or any other systems, like Redmine, GitLab or TestLink), which eliminates the human factor and, after the automation, does not require any additional effort to calculate. Using such a tool as the key performance indicators allows project managers to completely eliminate bias, reduce the emotional component and provide objective data for the project manager. The described key performance indicators can be used to reduce the time required to resolve conflicts in the team, increase productivity and improve the quality of the software product.

A semi-quantitative risk assessment model for the outbreak of grass carp hemorrhage

2013 ◽  
Vol 19 (3) ◽  
pp. 521-527 ◽  
Author(s):  
Song YANG ◽  
Shuqin WU ◽  
Ningqiu LI ◽  
Cunbin SHI ◽  
Guocheng DENG ◽  
...  
Keyword(s):  
Risk Assessment ◽  
Grass Carp ◽  
Assessment Model ◽  
Quantitative Risk Assessment ◽  
Risk Assessment Model
Sign in / Sign up

Export Citation Format

Share Document