Can metamodels link development to design intent?

Gamble, M.T.

doi:10.1145/2896935.2896937

Cited by 6 publications

(5 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are several works in the literature that use creativity techniques to support the software development process [11], [57], [56], [36], [26], [42], [19], [30]. In addition, several authors use creative techniques to elicit requirements during the agile software development process [21], [46], [40], [27], [44], [59]. It is possible to find relevant works that address requirements elicitation and Empathy in general [60], [9], [20], [29], [62], [54], [4], [61].…”

Section: Slr Resultsmentioning

confidence: 99%

Empathy and Criativity in Privacy Requirements Elicitation: Systematic Literature Review

Calazans,

Cerqueira,

Canedo

2020

Anais Do Workshop Em Engenharia De Requisitos

View full text Add to dashboard Cite

This paper presents a Systematic Literature Review (SLR) in order to find in the literature papers that use creativity and empathy techniques in privacy requirements elicitation. These techniques have been used in requirements elicitation in order to facilitate the understanding of the requirements and provide a collaborative interaction between the teams and the end user. Thus, we investigated whether the literature already has reports on the use of these techniques as facilitators in the process of privacy requirements elicitation. As a result of the SLR, we found few papers related to the use of Empathy in privacy requirements elicitation and no papers that relate Creativity to the elicitation of privacy requirements.

show abstract

Section: Slr Resultsmentioning

confidence: 99%

Empathy and Criativity in Privacy Requirements Elicitation: Systematic Literature Review

Calazans,

Cerqueira,

Canedo

2020

Anais Do Workshop Em Engenharia De Requisitos

View full text Add to dashboard Cite

show abstract

“…However, it remains to be seen if and how enterprise architects can adapt to a new way of working [7]. While the agile development methods are commonplace in many large organizations, insight into the relations and interactions with architecture methods at the enterprise level remains elusive [14]. Prior research has attempted to link traditional EA with the Agile Manifesto [60] or integrate TOGAF and Scrum [66].…”

Section: Literaturementioning

confidence: 99%

“…However, governing such approaches in combination with EA methods causes new challenges. Researchers disagree on which aspects of EA are important in an agile context [60], how enterprise architects can adapt to an agile way of working [7], the relationships between agile and EA methods [14], and how these can strengthen each other [60], [62]. In addition, issues remain regarding balancing emergent and intentional architecture, ensuring vertical coordination between top-down governance of architecture efforts, and bottom-up autonomy of agile teams and aligning horizontal coordination between multiple agile teams [73], [75].…”

Section: Literaturementioning

confidence: 99%

“…Traditionally, this is the field of enterprise architecture (EA) that aims to develop IT-enabled systems in a coherent way, while standards allow for interoperability between these systems [10]- [12]. Agile methods have been criticized for lack of attention to architecture [13], [14]. Ross et al [10] related EA to business processes and IT infrastructures that deal with organizations' integration and standardization requirements.…”

mentioning

confidence: 99%

See 1 more Smart Citation

Scaling Agile Company-Wide: The Organizational Challenge of Combining Agile-Scaling Frameworks and Enterprise Architecture in Service Companies

Wessel

Kroon²,

Vries

2022

IEEE Trans. Eng. Manage.

View full text Add to dashboard Cite

Many organizations have embraced agile methods. Studies show a trend of large-scale application of agile frameworks company-wide. Emergent architecture design as part of an agile approach is effective at the project level but causes issues when services need to interact seamlessly at the enterprise level. Enterprise architecture (EA) can provide such coherence. Combining the scaling agile methods with EA is challenging. However, such a combination could benefit from the flexibility that agile approaches offer and provide the consistency and long-term focus that EA pursues. This article uses the longitudinal case study research to explore how organizations can effectively govern Agile and EA in large-scale agile transformations. Our case analysis shows that methods for scaling Agile do not provide sufficient guidance to properly handle the transformation from existing EA practices to an Agile EA combination company-wide. We propose how EA can be applied effectively in large-scale agile transformations despite the two seemingly conflicting approaches of Agile and EA. Based on our findings, we propose a conceptual model for future research that incorporates factors that take EA into account in the governance of agile-scaling frameworks. Our findings extend current literature on coordination mechanisms between architects and agile teams in large-scale agile transformations, thereby balancing emergent and intentional architectures.

show abstract

“…This study was attempted to align IT with business metamodel. The EA metamodel based on TOGAF [1] was combined with the agile enterprise development metamodel based on the Scaled Agile Framework (SAFe) [13] published in [14]. The results from using both the TOGAF and SAFe were further simplified to minimize the level of complexity.…”

Section: Related Workmentioning

confidence: 99%

Selecting General Entities for TOGAF’s Core Content Metamodel using Best Worst Method

Zuliansyah,

Desa,

Ahmad

2019

IJITEE

View full text Add to dashboard Cite

Enterprise Architecture (EA) Developments are often faced with metamodel complexity problem. The data for metamodel exploration significantly affects the depth of an EA analysis. In practice, however, it is limited by the scope, cost, time and quality. The entities in the EA initiation metamodel is crucial in forming an optimal metamodel based on data completeness, time, cost, quality, and scope. In this study, entities in the EA metamodel were selected from general entities in the TOGAF's core content metamodel, combined with various standards related to the upstream petroleum industry. The entity selection methodology consists of two stages, namely Preparation and Screening, as well as Analysis and Selection. Entity data are extracted from the needs of the upstream petroleum industry. The analysis was done using the best worst method (BWM). The criteria are based on the EA development goals of the Federation of Enterprise Architecture Professional Organizations. BWM analysis produces a relatively meaningful ranking of the entities that forms as general entities in the core content metamodel. This study proposes the methodology, ranking order of entities, and entities composition that form general entities for the core content metamodel.

show abstract

Can metamodels link development to design intent?

Cited by 6 publications

References 2 publications

Empathy and Criativity in Privacy Requirements Elicitation: Systematic Literature Review

Empathy and Criativity in Privacy Requirements Elicitation: Systematic Literature Review

Scaling Agile Company-Wide: The Organizational Challenge of Combining Agile-Scaling Frameworks and Enterprise Architecture in Service Companies

Selecting General Entities for TOGAF’s Core Content Metamodel using Best Worst Method

Contact Info

Product

Resources

About