Model-driven standardization of public authority data interchange

Büttner, Fabian; Bartels, Ullrich; Hamann, Lars; Hofrichter, Oliver; Kuhlmann, Mirco; Gogolla, Martin; Rabe, Lutz; Steimke, Frank; Rabenstein, Yorck; Stosiek, Alina

doi:10.1016/j.scico.2013.03.009

Cited by 16 publications

(5 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As discussed in Finding 4, those NFRs are better supported by MDD approaches. For example, Büttner et al [65] showed a reduced number of bugs thanks to the quality control performed at model level and the adequate transformations performed from the specifications. Moreover, they pointed out a productivity improvement due to the separation of higher-level concerns from implementation details.…”

Section: How Do Mdd Approaches Adopted By Companies Support Nfrs? (Rq2)mentioning

confidence: 99%

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

Ameller

Franch

Gómez

et al. 2021

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Managing Non-Functional Requirements (NFRs) in software projects is challenging, and projects that adopt Model-Driven Development (MDD) are no exception. Although several methods and techniques have been proposed to face this challenge, there is still little evidence on how NFRs are handled in MDD by practitioners. Knowing more about the state of the practice may help researchers to steer their research and practitioners to improve their daily work. Objective: In this paper, we present our findings from an interview-based survey conducted with practitioners working in 18 different companies from 6 European countries. From a practitioner's point of view, the paper shows what barriers and benefits the management of NFRs as part of the MDD process can bring to companies, how NFRs are supported by MDD approaches, and which strategies are followed when (some) types of NFRs are not supported by MDD approaches. Results: Our study shows that practitioners perceive MDD adoption as a complex process with little to no tool support for NFRs, reporting productivity and maintainability as the types of NFRs expected to be supported when MDD is adopted. But in general, companies adapt MDD to deal with NFRs. When NFRs are not supported, the generated code is sometimes changed manually, thus compromising the maintainability of the software developed. However, the interviewed practitioners claim that the benefits of using MDD outweight the extra effort required by these manual adaptations. Conclusion: Overall, the results indicate that it is important for practitioners to handle NFRs in MDD, but further research is necessary in order to lower the barrier for supporting a broad spectrum of NFRs with MDD. Still, much conceptual and tool implementation work seems to be necessary to lower the barrier of integrating the broad spectrum of NFRs in practice.

show abstract

Section: How Do Mdd Approaches Adopted By Companies Support Nfrs? (Rq2)mentioning

confidence: 99%

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

Ameller

Franch

Gómez

et al. 2021

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…In particular, standardization is challenged by the complexity of government procedures [14], [2] and is often ineffective in practice [36], [37]. Various approaches to information management that are tailored to the context of government bodies through standardization have been developed in response [38], [39]. For example, frameworks like SAGA in Germany [40], with its focus on software specifications and development methods in the context of government bodies, and the European Interoperability Framework [41] have been proposed to management practice.…”

Section: Standardizationmentioning

confidence: 99%

Managing Standardization in eGovernment: A Coordination Theory based Analysis Framework

Balta

Krcmar

2018

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Standardization plays an important role for a smooth organizational, semantic, technical and legal interoperation of eGovernment services. Still, standardization struggles with the complexity of administrative procedures that have to be supported and provided online. Managing this complexity poses a crucial challenge for an efficient and effective eGovernment. Different management frameworks have been developed, but the progress of standardization in practice is still perceived as insufficient. To address the challenge of standardization management in eGovernment, we propose a coordination theory based framework for analysis. It consists of three coordination modes distinguished based on their mechanisms and relevant context dimensions. In our research approach, we interpret a single case study of a standardization project in Germany where artefacts were developed from a pragmatism perspective. We discuss our findings and conclude on implications for research and practice.

show abstract

“…Since interoperability allows IT systems to exchange information, it describes an alternative interface to forms between governments and citizens and companies. Therefore, frameworks such as XÖV [7] are standards for interfaces between governments and customers and can serve as basis for the standardization of forms.…”

Section: Forms In Actionmentioning

confidence: 99%