{"product_id":"risk-management-in-software-quality-assurance-risk-based-testing-von-jan-sickinger","title":"Risk management in software quality assurance","description":"\u003cp\u003eStudienarbeit aus dem Jahr 2010 im Fachbereich BWL - Unternehmensführung, Management, Organisation, Note: 2,0, FOM Essen, Hochschule für Oekonomie  \u0026amp; Management gemeinnützige GmbH, Hochschulleitung Essen früher Fachhochschule, Veranstaltung: Risk \u0026amp; Contract Management, Sprache: Deutsch, Abstract: In general, risk can be expressed as product of amount of damage and probability of\u003c\/p\u003e\u003cp\u003edamage. Due to the fact that software controls more and more aspects of life in modern\u003c\/p\u003e\u003cp\u003eindustrialised societies, software failures inherit risks for businesses, human health or\u003c\/p\u003e\u003cp\u003eeven human life. Software testing is a structured approach to minimise product risks of\u003c\/p\u003e\u003cp\u003esoftware systems. When the problem arises that, due to a given budget and timeframe, it\u003c\/p\u003e\u003cp\u003eis not possible to cover all parts of the software through testing, Risk-Based Testing is a\u003c\/p\u003e\u003cp\u003epossibility to test the most critical parts of the software first or more intensive. When\u003c\/p\u003e\u003cp\u003eusing this method, both amount of damage and probability of damage must be\u003c\/p\u003e\u003cp\u003equantified. Quantifying the amount of damage must happen by considering the different\u003c\/p\u003e\u003cp\u003eviewpoints of the software system¿s stakeholders, while quantifying the probability of\u003c\/p\u003e\u003cp\u003edamage can only happen indirectly, for example through quality indicators like the\u003c\/p\u003e\u003cp\u003ecomplexity of the software itself, the quality of the documentation etc. When having\u003c\/p\u003e\u003cp\u003ederived quantitative values both for the amount of damage and the probability of\u003c\/p\u003e\u003cp\u003edamage, the priority of the test cases can be determined by using a risk matrix.\u003c\/p\u003e\u003cp\u003eFurthermore, these values can also be used for metrics.\u003c\/p\u003e\u003cp\u003eAn extension of Risk-Based Testing is Risk and Requirement-Based Testing, where\u003c\/p\u003e\u003cp\u003eproduct risks are linked to the requirements against which the software is tested in order\u003c\/p\u003e\u003cp\u003eto gain an overview if the lists of requirements and risks defined for the software are\u003c\/p\u003e\u003cp\u003ecomplete.\u003c\/p\u003e\u003cdiv class=\"aw-variant-hidden-subtitle-div\" id=\"aw-variant-subtitle-9783640999941\"\u003e\u003ch3\u003eRisk-Based Testing\u003c\/h3\u003e\u003c\/div\u003e","brand":"Libri","offers":[{"title":"Softcover - 9783640999941","offer_id":39428968808541,"sku":"9783640999941","price":18.95,"currency_code":"EUR","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0940\/0622\/files\/3c20ff46-dd29-4021-b7e9-20f3a3dd0af3.jpg?v=1777868076","url":"https:\/\/shop.autorenwelt.de\/en\/products\/risk-management-in-software-quality-assurance-risk-based-testing-von-jan-sickinger","provider":"Autorenwelt Shop","version":"1.0","type":"link"}