2017
DOI: 10.5120/ijais2017451731
|View full text |Cite
|
Sign up to set email alerts
|

Modeling Security Requirements: Extending SysML with Security Requirements Engineering Concepts

Abstract: In Security Requirements Engineering, many approaches offer different ways to model security requirements. This paper presents a model that can be used in conjunction with any of the former approaches. The model is an extension of SysML requirements diagrams that adds concepts from Security Requirements Engineering: Stakeholder, Goal, Asset and Risk. The proposed model is illustrated by applying it to a telemedicine system.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2018
2018
2018
2018

Publication Types

Select...
1
1

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 15 publications
0
1
0
Order By: Relevance
“…Once requirements are elicited (through phase 2 or 3), they must be modeled. The model created to be used with CompASRE or other SRE approaches is an extension of SysML requirements diagrams [6] and was presented in detail in previous paper [7]. In phase 4, elicited requirements are categorized and prioritized, then inspected for validation to resolve conflicts and eliminate redundancies.…”
Section: B Compasrementioning
confidence: 99%
“…Once requirements are elicited (through phase 2 or 3), they must be modeled. The model created to be used with CompASRE or other SRE approaches is an extension of SysML requirements diagrams [6] and was presented in detail in previous paper [7]. In phase 4, elicited requirements are categorized and prioritized, then inspected for validation to resolve conflicts and eliminate redundancies.…”
Section: B Compasrementioning
confidence: 99%