ISBN-13: 9783659669668 / Angielski / Miękka / 2014 / 100 str.
In the present age, software is exploited and the understanding of increasing extent of risk exposure as a result is rarely developed. Security should be incorporate right from the requirements phase so that the security is inbuilt and properly incorporated into the software in development. To establish the fact that a process is improving or not is a matter that seems impossible without obtaining the measurements. Security requirements are qualitative hence they needs to be converted into quantitative measure using some metrics. Certain Object Oriented modeling techniques like Misuse case, Abuse case are very helpful in incorporating security requirements in the early stages of software development phases.ie requirement phase. In this book, we propose MACOQR (Misuse & Abuse Case Oriented Quality Requirements) metrics whose aim is to measure the predicated and observed ratio of flaw and flawlessness in modeling of misuse cases during requirements engineering phase. The measures and ratios obtained may help the requirements engineering team to plan eliminate defects of misuse case modeling during the requirements engineering phase.
In the present age, software is exploited and the understanding of increasing extent of risk exposure as a result is rarely developed. Security should be incorporate right from the requirements phase so that the security is inbuilt and properly incorporated into the software in development. To establish the fact that a process is improving or not is a matter that seems impossible without obtaining the measurements. Security requirements are qualitative hence they needs to be converted into quantitative measure using some metrics. Certain Object Oriented modeling techniques like Misuse case, Abuse case are very helpful in incorporating security requirements in the early stages of software development phases.ie requirement phase. In this book, we propose MACOQR (Misuse & Abuse Case Oriented Quality Requirements) metrics whose aim is to measure the predicated and observed ratio of flaw and flawlessness in modeling of misuse cases during requirements engineering phase. The measures and ratios obtained may help the requirements engineering team to plan eliminate defects of misuse case modeling during the requirements engineering phase.