Twenty Software Requirement Patterns to Specify Recommender Systems that Users Will Trust

Hoffmann, Axel; Söllner, Matthias; Hoffmann, Holger

doi:10.2139/ssrn.2484462

Cited by 12 publications

(4 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To strengthen this stream of research and enlarge the set of available techniques, further research into understanding and designing mutual and shared understanding is thus necessary. In requirements engineering, natural language software requirement patterns [30][31][32] could help to foster a mutual understanding by using standardised, well defined and discipline independent terms and formulations. Further, the Mutually Exclusive Individual Goals…”

Section: Discussionmentioning

confidence: 99%

The Emergence of Mutual and Shared Understanding in the System Development Process

Hoffmann

Bittner

Leimeister

2013

Requirements Engineering: Foundation for Software Quality

Self Cite

View full text Add to dashboard Cite

Context and motivation]In interdisciplinary requirements engineering, stakeholders need to understand how other disciplines think and work (mutual understanding) and agree on the system they develop (shared understanding) in order to collaborate effectively. [Question/problem] In this paper we analyse extent and forms of (lacking) mutual understanding according to the periods in the process of conceptual change. [Principal ideas/results] We analyse the communication of a multidisciplinary team while developing a mobile application. Although the team tried to resolve differences in meaning early on by applying approaches for clarification, questions for consolidation, exploration and elaboration occurred at different points in time throughout the process. Even when artefacts were already agreed upon, the development team explored lack of mutual understanding to underlying concepts or relationships. A revised shared understanding led to adjustments of the artefacts and thus hampered the process.[Contribution] We therefore call for research that explores ways of systematically building mutual and shared understanding in the development process.

show abstract

Section: Discussionmentioning

confidence: 99%

The Emergence of Mutual and Shared Understanding in the System Development Process

Hoffmann

Bittner

Leimeister

2013

Requirements Engineering: Foundation for Software Quality

Self Cite

View full text Add to dashboard Cite

show abstract

“…Forschungsarbeiten liefern bereits eine Auswahl an vertrauensbezogenen Anforderungen für verschiedenste IT-Systeme (Hoffmann et al 2012;Hoffmann/Söllner 2014;Hoffmann et al 2013). Cloud-Computing-Anbieter, welche den Prozess zur systematischen Vertrauensunterstützung durchlaufen, können die nachfolgenden vertrauensbezogenen Anforderungen als Grundlage verwenden, sollten aber kritisch prüfen, ob diese für den konkreten An-wendungsfall relevant sind.…”

Section: Schritt 4: Ableitung Vertrauensbezogener Anforderungenunclassified

Vertrauensunterstützende Mehrwertdienste – Ein systematisches Vorgehen zur Förderung von Vertrauen im Cloud-Computing-Umfeld

Gebauer¹,

Söllner²,

Leimeister³

2016

Cloud-Services Aus Der Geschäftsperspektive

View full text Add to dashboard Cite

In diesem Kapitel wird ein Prozess zur Entwicklung vertrauensunterstützender Mehrwertdienste erarbeitet, um mit den daraus abgeleiteten Lösungen den Vertrauensproblematiken im Cloud-Computing-Umfeld (siehe Kapitel 6) zu begegnen. Dazu wurde die Methode zur Entwicklung vertrauensunterstützender Komponenten für sozio-technische ubiquitäre Systeme nach Söllner et al. (2012a) auf den Cloud-Computing-Kontext übertragen und weiterentwickelt. Der Prozess zur systematischen Vertrauensunterstützung umfasst fünf aufeinander folgende Schritte (Abbildung 1) und soll Cloud-Computing-Anbieter befähigen ihre Cloud-Computing-Dienste vertrauenswürdiger zu gestalten. Jeder einzelne Schritt wird durch eine Leitfrage angeleitet, um so die Erarbeitung der einzelnen Entwicklungsaktivitäten zu unterstützen. Der Prozess zielt darauf ab, Lösungen in Form von vertrauensunterstützenden Mehrwertdiensten für den ausgewählten Cloud-Computing-Dienst abzuleiten. In den nachfolgenden Abschnitten wird der Prozess zur systematischen Vertrauensunterstützung erklärt und allgemein für Cloud-Computing durchlaufen, jedoch ohne Bezugnahme auf einen konkreten Dienst. Die exemplarischen Ergebnisse können von den Cloud-Computing-Anbietern als Grundlage verwendet werden, um eigene, individuelle Lösungen zu entwickeln. Dennoch empfiehlt es sich, eine kritische Überprüfung hinsichtlich der Übertragbarkeit auf den ausgewählten Cloud-Computing-Dienst durchzuführen. Es kann nicht ausgeschlossen werden, dass bestimmte Aspekte für den ausgewählten Cloud-Computing-Dienst keine Relevanz haben oder wiederum wichtige Aspekte noch nicht berücksichtigt wurden.

show abstract

“…Hoffmann et al (2012) developed twenty software requirement patterns and the pre-defined requirement templates that can be used to specify trust requirements in recommender system development. In general, pattern-based approaches have already established well within the field of information systems to facilitate complex designing processes.…”

Section: Limitations In Dq Requirements Analysis and Modellingmentioning

confidence: 99%

“…As mentioned in section 2.3.4, in literature the pattern are used in various other disciplines to create models, due to the muddling power that the patterns provide in modelling complex scenarios (Franch 2013;Hoffmann et al 2012;Rolland et al 1998). Therefore, in defining the meta-model for DQ requirements, we want to define each construct in the meta-model as a DQ pattern so that an extra potential can be gained in modelling complex DQ requirements.…”

Section: Developing a Meta-model For A Dq Requirementmentioning

confidence: 99%

A pattern based approach for data quality requirements modelling

Jayawardene¹

View full text Add to dashboard Cite

Data quality (DQ) is a critical issue in today's information systems. Both academic researchers and industry practitioners have contributed to addressing the problem of data quality through management strategies and technological advancements over the last three decades, yet data quality management remains a challenge in the organizational management portfolio. Requirement models have been used successfully to develop solutions in areas like software and database development. The current state of the art in DQ management methodologies developed by both academic researchers and industry practitioners have largely overlooked the area of DQ requirements modelling and analysis. However DQ requirements are fundamental to DQ management since the ultimate purpose of DQ management is to develop solutions to satisfy the DQ requirements. Thus, a clearly defined DQ requirement model is a necessary prelude to systematically develop solutions to organizational DQ problems. In this research, we have developed a repository of thirty-three DQ patterns to model DQ requirements. The patterns are rich in representing the real world DQ requirements while free from notational complexities, thereby allowing them to be used practically to support DQ management. We used design science as the guiding methodology for developing DQ patterns while maintaining a rationale for the rigor and the relevance of our artefacts through appropriate validations and verifications throughout the design process. One of the challenges faced in the conceptualization of DQ patterns was the lack of shared understanding among researchers about DQ dimensions, which is a key concept in representing a DQ requirement. Owing to the importance of shared understanding we systematically refactor the concept of DQ dimensions by consolidating different viewpoints from both academic and practitioner community. As a secondary aim of this study, we adapted a credible requirements engineering methodology from literature to analyse and elicit DQ requirements. We demonstrate through empirical studies that by using this methodology DQ patterns can be effectively used to elicit and model DQ requirements in organizations.iii Declaration by authorThis thesis is composed of my original work and contains no material previously published or written by another person except where due reference has been made in the text. I have clearly stated the contribution by others to jointly-authored works that I have included in my thesis.

show abstract

Twenty Software Requirement Patterns to Specify Recommender Systems that Users Will Trust

Cited by 12 publications

References 29 publications

The Emergence of Mutual and Shared Understanding in the System Development Process

The Emergence of Mutual and Shared Understanding in the System Development Process

Vertrauensunterstützende Mehrwertdienste – Ein systematisches Vorgehen zur Förderung von Vertrauen im Cloud-Computing-Umfeld

A pattern based approach for data quality requirements modelling

Contact Info

Product

Resources

About