2006
DOI: 10.1007/11824633_6
|View full text |Cite
|
Sign up to set email alerts
|

Towards a UML 2.0 Extension for the Modeling of Security Requirements in Business Processes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
33
0

Year Published

2007
2007
2017
2017

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 44 publications
(33 citation statements)
references
References 18 publications
0
33
0
Order By: Relevance
“…This approach will lead to security vulnerabilities. It justifies spending more effort in defining security objectives in pre-development phases, where finding and removing an error/bug is easy and cheaper [29]. Furthermore, mastering these security access control models, protocols, and security implementations is also a daunting task [12,28].…”
Section: Problems In Current Security Standards For Web Services Basementioning
confidence: 99%
“…This approach will lead to security vulnerabilities. It justifies spending more effort in defining security objectives in pre-development phases, where finding and removing an error/bug is easy and cheaper [29]. Furthermore, mastering these security access control models, protocols, and security implementations is also a daunting task [12,28].…”
Section: Problems In Current Security Standards For Web Services Basementioning
confidence: 99%
“…Fig. 2 The AURUM process Modeling security requirements in business processes is also the goal of an extension of UML 2.0 by Rodríguez et al [27]. According to the authors, this is essential since software developers derive necessary requirements for software design and implementation from business processes [27].…”
Section: Related Workmentioning
confidence: 99%
“…2 The AURUM process Modeling security requirements in business processes is also the goal of an extension of UML 2.0 by Rodríguez et al [27]. According to the authors, this is essential since software developers derive necessary requirements for software design and implementation from business processes [27]. This early design of security requirements shall (1) use the (at least high-level) security knowledge of business analysts concerning business process security while initially modeling the processes and (2) reduce potential costs avoiding the additional implementation of business processes' security after the business processes have been implemented.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…The POSeM approach [2] has the objective to facilitate the selection process of security measures by providing recommendations derived from process descriptions. The two main concepts to meet this objective are (1) its Security Enhanced Process Language (SEPL) which enables the representation of security requirements within business processes and (2) two rule bases in order to check the process security definitions for consistency and afterwards identify required safeguards.…”
Section: Process Oriented Security Model (Posem)mentioning
confidence: 99%