Using FSM patterns to size security non-functional requirements with COSMIC

Ungan, Erdir; Trudel, Sylvie; Poulin, L.

doi:10.1145/3143434.3143461

Cited by 3 publications

(12 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…On the other hand, customers use software size to control their suppliers' price/performance, the delivered product quality, etc. In addition to its advantages compared to the first FSM generation methods, COSMIC has been successfully used for approximate sizing variants for use in early/rapid project estimation [11], guidance on how to deal with non-functional requirements (cf., [2], [12]), sizing functional change requests (cf., [9], [10]), and making decisions on software project development (cf., [21], [3]). Fig.…”

Section: B Cosmic Fsm Methods Overviewmentioning

confidence: 99%

“…As shown in Table I, several studies have recently proposed to measure the functional size of some system-NFR such as portability, security, performance, etc. Some of these studies used FSM methods such as COSMIC (cf., [2], [12]), while others proposed their own methods and tools (cf., [24], [25]). For instance, Kassab et al, [12] proposed to apply the COSMIC-FFP method in measuring the functional size of non-functional requirements in order to reduce the uncertainty in software estimation.…”

Section: Related Work a Measuring Non-functional Requirements Overviewmentioning

confidence: 99%

“…More specifically, this study focused on the "Authenticity" quality sub-characteristic in order to identify the risk of authenticity violation. Ungan et al, [2] proposed a method that makes the system-NFR more easily converted to functional requirements in order to reduce the gap between approximate and precise size measurements. This study used the FSM patterns to facilitate the measurement of non-functional requirements at later software life-cycle phases, in particular the security quality characteristic.…”

Section: Related Work a Measuring Non-functional Requirements Overviewmentioning

confidence: 99%

“…To capture the security concept, this study used soft-goal inter-dependency graphs and three main security types: system availability, confidentiality and integrity. As summarized in Table I, many researchers used COSMIC to quantify the functional size of security requirements (cf., [2], [26]). However, none of them focused on measuring changes in software security.…”

Section: Related Work a Measuring Non-functional Requirements Overviewmentioning

confidence: 99%

“…Based on the fact that the success of any management activity highly depends on the accuracy of software size measurement [2], software organizations frequently use software size measurement as a technique to estimate the development effort, make decisions, etc. (cf., [3], [4]).…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Evaluating Software Security Change Requests: A COSMIC-Based Quantification Approach

Haoues

Sellami

Ben-Abdallah

et al. 2019

2019 45th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)

View full text Add to dashboard Cite

Software project scope defines functional and nonfunctional requirements. These requirements may change to satisfy the customers' needs. However, the control of scope creep represents one of the success keys in software project management. Changes in non-functional requirements affect the ISO/IEC 25010 quality characteristics such as security, portability, etc. Furthermore, some of these quality characteristics may evolve throughout the software life cycle into functional requirements. In this paper, we explore the use of COSMIC method -ISO/IEC 19761 to quantify and evaluate security change requests. Measuring the functional size of security change requests allows stakeholders to make appropriate decisions about whether to accept, defer, or deny the change.

show abstract

Section: B Cosmic Fsm Methods Overviewmentioning

confidence: 99%

Section: Related Work a Measuring Non-functional Requirements Overviewmentioning

confidence: 99%

Section: Related Work a Measuring Non-functional Requirements Overviewmentioning

confidence: 99%

Section: Related Work a Measuring Non-functional Requirements Overviewmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Evaluating Software Security Change Requests: A COSMIC-Based Quantification Approach

Haoues

Sellami

Ben-Abdallah

et al. 2019

2019 45th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)

View full text Add to dashboard Cite

show abstract

Penetration Frameworks and Development Issues in Secure Mobile Application Development: A Systematic Literature Review

Haq

Khan

2021

IEEE Access

View full text Add to dashboard Cite

The invention of smartphones has opened a new market for mobile application development. Amateur android app developers often do not possess knowledge of the latest android vulnerabilities and thus create applications with attack surface that hackers exploit. In this literature review, many available frameworks and techniques have been analyzed using ISO/IEC 25010 software quality model and identified challenges that android developers face in designing a secure application for android. This paper also presents a comprehensive survey of different penetration tools, evaluated by using criteria such as code analysis, code review, vulnerability analysis, vulnerability exploit, payload and whether these can be used in vulnerability modeling during the design phase. Our study effectively identifies the issues and gaps which can further help develop a framework/tool for designing a penetration secure mobile application by embedding all the vulnerabilities during the design phase using an android vulnerability repository.

show abstract

Mejora del proceso de desarrollo de software en instituciones públicas del Perú incorporando el método COSMIC: caso de estudio en el OSINFOR

Marca Quispe,

Bautista Ubillús

2023

Rev peru comput sist

View full text Add to dashboard Cite

Uno de los principales retos cuando se administra proyectos de software es determinar el esfuerzo que se necesita para la entrega del producto, y en el Perú, las entidades públicas están enmarcadas en el cumplimiento normativo por lo que se ha incrementado el uso de enfoques ágiles debido a la incertidumbre en la medición del tamaño del software. En ese sentido, a través de la presente investigación se realizó la mejora al proceso de desarrollo para el OSINFOR incorporando el método COSMIC para medir el tamaño del software y determinar el esfuerzo para los desarrollos. El proceso mejorado ha sido analizado en dos casos de estudio para corroborar la medición estándar y el uso del enfoque de aproximación del método COSMIC. Finalmente, como resultado se ha demostrado que la incorporación de actividades de medición considerando el estándar COSMIC mejora el proceso para la construcción de software logrando un 75% en cumplimiento de las actividades, 75% en la eficiencia de la medición y 76% en la satisfacción del uso del proceso mejorado.

show abstract

Using FSM patterns to size security non-functional requirements with COSMIC

Cited by 3 publications

References 13 publications

Evaluating Software Security Change Requests: A COSMIC-Based Quantification Approach

Evaluating Software Security Change Requests: A COSMIC-Based Quantification Approach

Penetration Frameworks and Development Issues in Secure Mobile Application Development: A Systematic Literature Review

Mejora del proceso de desarrollo de software en instituciones públicas del Perú incorporando el método COSMIC: caso de estudio en el OSINFOR

Contact Info

Product

Resources

About