Alignment of software product management and software architecture with discussion models

Lucassen, Garm; Werf, Jan Martijn E. M. van der; Brinkkemper, Sjaak

doi:10.1109/iwspm.2014.6891064

Cited by 6 publications

(7 citation statements)

References 37 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To overcome this limitation, in earlier work, we introduced the Reciprocal Contributions Model (RCM) [12]. It describes the relationship between the responsibilities of product managers and software architects as defined by literature in both fields [28], [30], and highlights the mutual contributions that enable these stakeholders to fulfill their own responsibilities.…”

Section: The Reciprocal Twin Peaks Modelmentioning

confidence: 99%

“…(3) artifacts, denoted as rectangles, produced trying to reach the responsibilities as we identified in [12]; and (4) artifact flows. We explain each element from top to bottom by means of a running example: BankProd, a fictitious software product of a company from the Netherlands that, among On a daily basis Alice, BankProd's product manager, receives new market requirements.…”

Section: The Reciprocal Twin Peaks Modelmentioning

confidence: 99%

“…problem for software products. They focus on generating software architecture from requirements [12] or apply Twin Peaks in the context of Software Product Lines [13], which fails to consider product software without a line architecture.…”

Section: Introductionmentioning

confidence: 99%

“…To mitigate this problem, we extend our previous work [12] by means of comparative case study research, and propose the Reciprocal Twin Peaks model. This is a conceptual framework that defines how product managers and software architects can effectively collaborate in product software development through the exchange of concrete information artifacts.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Bridging the Twin Peaks -- The Case of the Software Industry

Lucassen

Dalpiaz

Werf

et al. 2015

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture

Self Cite

View full text Add to dashboard Cite

We review the relationship between software architecture and requirements in the context of software products. Based on empirical evidence from a comparative case study, we promote four positions: (1) the requirements/architecture alignment problem for software products is inherently different than the same problem for tailor-made software; (2) bridging the Twin Peaks corresponds to defining and enacting a stepwise evolution of the product architecture; (3) communication tasks are ascribed to the product manager rather than the architect; and (4) integrated and cross-disciplinary tools are key to maintain requirements/architecture alignment. We argue that these positions motivate and characterize future research in the field.

show abstract

Section: The Reciprocal Twin Peaks Modelmentioning

confidence: 99%

Section: The Reciprocal Twin Peaks Modelmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Bridging the Twin Peaks -- The Case of the Software Industry

Lucassen

Dalpiaz

Werf

et al. 2015

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture

Self Cite

View full text Add to dashboard Cite

show abstract

“…However, due to many external constraints, such as time-to-market, proper architectural documentation comes at the bottom of the list. Consequently, many of these organisations have outdated documentation [12]. Thus the risk of technical debt is high for such organisations [25].…”

Section: Introductionmentioning

confidence: 99%

A genetic approach to architectural pattern discovery

Peters

Werf

2016

Proccedings of the 10th European Conference on Software Architecture Workshops

Self Cite

View full text Add to dashboard Cite

Architectural patterns represent reusable design of software architecture at a high level of abstraction. They can be used to structure new applications and to recover the modular structure of existing systems. Techniques like Architecture Compliance Checking (ACC) focus on testing whether realised artefacts adhere to the architecture. Typically, these techniques require a complete architecture as input.In this paper, we present a genetic approach to express and discover architectural patterns based on the allowed and disallowed dependencies between the pattern elements. Through static ACC, we validate the genuineness of the found instances. Initial validation shows the potential of the approach.

show abstract