Experiences with a Requirements Object Model

Beatty, Joy; Hulgan, James

doi:10.1007/978-3-642-02050-6_9

Search citation statements

Order By: Relevance

Paper Sections

Select...

Literature Review1

Related Work1

Citation Types

Supporting

Mentioning

Contrasting

Year Published

2012

2024

Publication Types

Select...

Book1

Other1

Relationship

Self Cite0

Independent2

Authors

Journals

Cited by 2 publications

(2 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In conclusion, the publication contains recommendations for achieving the target state of the enterprise architecture, based on the ADM TOGAF method. This allows you to design the target vision of the system [5].…”

Section: Literature Reviewmentioning

confidence: 99%

Implementation of a Customer Routing System in a Commercial Organization

Ksenofontova

2024

Implementation of a Customer Routing System in a Commercial Organization

View full text Add to dashboard Cite

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Implementation of a Customer Routing System in a Commercial Organization

Ksenofontova

2024

Implementation of a Customer Routing System in a Commercial Organization

View full text Add to dashboard Cite

show abstract

“…The gap between these two types of requirements has been a major problem in the domain of requirement engineering [11][12][13] and although a lot of work has been done on understanding, eliciting, analyzing user requirements [14] and translating them into system requirements for different application domains [15,16], it remains one of the prominent topics in software engineering research [10,17].…”

Section: Related Workmentioning

confidence: 99%

Deriving implementation-level policies for usage control enforcement

Kumari

Pretschner

2012

Proceedings of the Second ACM Conference on Data and Application Security and Privacy

View full text Add to dashboard Cite

Usage control is concerned with how data is used after access to it has been granted. As such, it is particularly relevant to end users who own the data. System implementations of access and usage control enforcement mechanisms, however, do not always adequately reflect end user requirements. This is due to several reasons, one of which is the problem of mapping concepts in the end user's domain to technical events and artifacts. For instance, semantics of basic operators such as "copy" or "delete", which are fundamental for specifying privacy policies, tend to vary according to context. For this reason they can be mapped to different sets of system events. The behaviour users expect from the system, therefore, may differ from the actual behaviour. In this paper we present a translation of specification-level usage control policies into implementation-level policies which takes into account the precise semantics of domain-specific abstractions. A tool for automating the translation has also been implemented.

show abstract

Experiences with a Requirements Object Model

Cited by 2 publications

References 2 publications

Implementation of a Customer Routing System in a Commercial Organization

Implementation of a Customer Routing System in a Commercial Organization

Deriving implementation-level policies for usage control enforcement

Contact Info

Product

Resources

About