Integrating functional and security requirements with use case decomposition

Misuse case modeling is a viable option to depict the security requirements together with functional requirements. To investigate the interplay between functional and security requirements, this paper presents an approach to decomposing use cases, misuse cases, and mitigation use cases. We identify relationships among decomposed cases for each case type (use, misuse, mitigation use) and ensure consistency among the cases as decomposition occurs by properly modeling shared and optional cases. We also assign applicable actors to the decomposed cases. Decomposition is conducted for each case type independently and then integrated with the "threatens" and "mitigates" relationships. We provide processes for the proper use of the "threatens" relationship between misuse cases and use cases and the "mitigates" relationship between mitigation use cases and misuse cases at different levels of abstraction. Thus, a complete set of security-centric requirements can be specified from the project outset to guide subsequent software development phases

[1]  D. Rosenberg,et al.  Use Case Driven Object Modeling With UML , 1999 .

[2]  Axel van Lamsweerde,et al.  Elaborating security requirements by construction of intentional anti-models , 2004, Proceedings. 26th International Conference on Software Engineering.

[3]  Ian F. Alexander,et al.  Initial industrial experience of misuse cases in trade-off analysis , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[4]  I. Alexander,et al.  Misuse cases help to elicit non-functional requirements , 2003 .

[5]  Tim Kelly,et al.  Deriving safety requirements using scenarios , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[6]  John Mylopoulos,et al.  Security and privacy requirements analysis within a social setting , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[7]  Peter G. Neumann.  Achieving principled assuredly trustworthy composable systems and networks , 2003, Proceedings DARPA Information Survivability Conference and Exposition.

[8]  Premkumar T. Devanbu,et al.  Software engineering for security: a roadmap , 2000, ICSE '00.

[9]  Edward D. Lazowska,et al.  Cyber Security: A Crisis of Prioritization , 2005 .

[10]  Khaled M. Khan,et al.  Composing Security-Aware Software , 2002, IEEE Softw..

[11]  Donald Firesmith,et al.  Security Use Cases , 2003, J. Object Technol..

[12]  Axel van Lamsweerde,et al.  From system goals to intruder anti-goals: attack generation and resolution for security requirements engineering , 2003 .

[13]  Andreas L. Opdahl,et al.  Eliciting security requirements with misuse cases , 2000, Proceedings 37th International Conference on Technology of Object-Oriented Languages and Systems. TOOLS-Pacific 2000.

[14]  Bashar Nuseibeh,et al.  Security requirements engineering: when anti-requirements hit the fan , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[15]  Ian F. Alexander,et al.  Misuse Cases: Use Cases with Hostile Intent , 2003, IEEE Softw..

[16]  A. Opdahl,et al.  A Reuse-Based Approach to Determining Secur ity Requirements , 2003 .

[17]  Bill Doult,et al.  On with the new. , 1996, Nursing standard (Royal College of Nursing (Great Britain) : 1987).

[18]  Leonard J. Bass,et al.  Scenario-Based Analysis of Software Architecture , 1996, IEEE Softw..

[19]  John Smith,et al.  The Estimation of Effort Based on Use Cases , 1999 .

[20]  Frank Swiderski,et al.  Threat Modeling , 2018, Hacking Connected Cars.

[21]  Larry Constantine,et al.  Structure and style in use cases for user interface design , 2001 .

[22]  Andreas L. Opdahl,et al.  Templates for Misuse Case Description , 2001 .

[23]  Dianxiang Xu,et al.  Threat-Driven Architectural Design of Secure Information Systems , 2018, ICEIS.

[24]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[25]  Ian F. Alexander,et al.  Modelling the Interplay of Conflicting Goals with Use and Misuse Cases , 2002, GBPM.

[26]  Lin Liu,et al.  Modelling Trust for System Design Using the i* Strategic Actors Framework , 2000, Trust in Cyber-societies.

[27]  Kurt Bittner,et al.  Use Case Modeling , 2002 .

[28]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[29]  George W. Wetherill,et al.  Where do the Apollo objects come from , 1988 .

[30]  Jifeng He,et al.  A Relational Model for Formal Object-Oriented Requirement Analysis in UML , 2003, ICFEM.

[31]  Peter G. Neumann,et al.  Principled assuredly trustworthy composable architectures , 2003 .