When software systems are verified against security requirements, formal and informal arguments provide a structure for organizing the software artifacts. Our recent work on the evolution of security-critical software systems demonstrates that our argumentation technique is useful in limiting the scope of change and in identifying changes to security properties. In support of this work, we have developed OpenArgue, a tool for syntax checking, visualizing, formalizing, and reasoning about incremental arguments. OpenArgue has been integrated with requirements engineering tools for Problem Frames and i*, and applied to an Air Traffic Management (ATM) case study
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
When showing that a software system meets certain security requirements, it is often necessary to wo...
non-peer-reviewedWhen software systems are verified against security requirements, formal and inform...
Software systems are made to evolve in response to changes in their contexts and requirements. As t...
Computer-based systems are increasingly being exposed to evolving security threats, which often reve...
Computer-based systems are increasingly being exposed to evolving security threats, which often reve...
Identifying threats and risks to complex systems often requires some form of brainstorming. In addit...
Abstract. The satisfaction of software security requirements can be argued using supporting facts an...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
This chapter presents a process for security requirements elicitation and analysis, based around th...
non-peer-reviewedWhen showing that a software system meets certain security requirements, it is ofte...
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
Part 1: Full PapersInternational audienceThe development and evolution of secure open architecture s...
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
When showing that a software system meets certain security requirements, it is often necessary to wo...
non-peer-reviewedWhen software systems are verified against security requirements, formal and inform...
Software systems are made to evolve in response to changes in their contexts and requirements. As t...
Computer-based systems are increasingly being exposed to evolving security threats, which often reve...
Computer-based systems are increasingly being exposed to evolving security threats, which often reve...
Identifying threats and risks to complex systems often requires some form of brainstorming. In addit...
Abstract. The satisfaction of software security requirements can be argued using supporting facts an...
When considering the security of a system, the analyst must simultaneously work with two types of pr...
This chapter presents a process for security requirements elicitation and analysis, based around th...
non-peer-reviewedWhen showing that a software system meets certain security requirements, it is ofte...
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
Part 1: Full PapersInternational audienceThe development and evolution of secure open architecture s...
When showing that a software system meets certain security requirements, it is often necessary to wo...
This paper proposes using both formal and structured informal arguments to show that an eventual rea...
When showing that a software system meets certain security requirements, it is often necessary to wo...