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

On the Role of Early Architectural Assumptions in Quality Attribute Scenarios: A Qualitative and Quantitative Study 早期架构假设在质量属性场景中的作用:定性与定量研究

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture Pub Date : 2015-05-16 DOI: 10.1109/TWINPEAKS.2015.10

D. Landuyt, W. Joosen

{"title":"On the Role of Early Architectural Assumptions in Quality Attribute Scenarios: A Qualitative and Quantitative Study","authors":"D. Landuyt, W. Joosen","doi":"10.1109/TWINPEAKS.2015.10","DOIUrl":"https://doi.org/10.1109/TWINPEAKS.2015.10","url":null,"abstract":"Architectural assumptions are fundamentally different from architectural decisions because they can not be traced directly to requirements, nor to domain, technical or environmental constraints, they represent conditions under which the designed solution is expected to be valid. Early architectural assumptions are similar in nature, with the key difference that they are not made during architectural design but during requirement elicitation, not by the software architect (a solution-oriented stakeholder), but by the requirements engineer (a problem-oriented stakeholder). They represent initial assumptions about the system's architecture, and allow the requirements engineer to be more precise in documenting the requirements of the system. The role of early architectural assumptions in the current practice of quality attribute scenario elicitation and related development activities in the transition to architecture is unknown and under-investigated. In this paper, we present the results of an exploratory study that focuses on the role and nature of these assumptions in the early development stages. We studied a reasonably large set of quality attribute scenarios for a realistic industrial case, a smart metering system. Our study (i) confirms that quality attribute scenario elicitation in practice does rely heavily on early architectural assumptions, and (ii) shows that they do influence the perceived quality of the requirements body as a whole, in some cases positively, in other cases negatively. These findings provide empirical arguments in favor of making such assumptions explicit already during the requirements elicitation activities. Especially in the context of iterative software development methodologies such as the Twin Peaks model, a well-defined and -documented set of assumptions could smoothen the transition between successive development iterations.","PeriodicalId":112329,"journal":{"name":"2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114707545","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 5

Is Requirements Engineering Inherently Counterproductive? 需求工程本质上是适得其反的吗?

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture Pub Date : 2015-05-16 DOI: 10.1109/TWINPEAKS.2015.12

P. Ralph, Rahul Mohanani

引用次数: 18

Identifying Architecturally Significant Functional Requirements 识别架构上重要的功能需求

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture Pub Date : 2015-05-16 DOI: 10.1109/TWINPEAKS.2015.9

Preethu Rose Anish, Balaji Balasubramaniam, J. Cleland-Huang, R. Wieringa, M. Daneva, S. Ghaisas

{"title":"Identifying Architecturally Significant Functional Requirements","authors":"Preethu Rose Anish, Balaji Balasubramaniam, J. Cleland-Huang, R. Wieringa, M. Daneva, S. Ghaisas","doi":"10.1109/TWINPEAKS.2015.9","DOIUrl":"https://doi.org/10.1109/TWINPEAKS.2015.9","url":null,"abstract":"Failure to identify and analyze architecturally significant functional and non-functional requirements (NFRs) early on in the life cycle of a project can result in costly rework in later stages of software development. While NFRs indicate an explicit architectural impact, the impact that functional requirements may have on architecture is often implicit. The skills needed for capturing functional requirements are different than those needed for making architectural decisions. As a result, these two activities are often conducted by different teams in a project. Therefore it becomes necessary to integrate the knowledge gathered by people with different expertise to make informed architectural decisions. We present a study to bring out that functional requirements often have implicit architectural impact and do not always contain comprehensive information to aid architectural decisions. Further, we present our initial work on automating the identification of architecturally significant functional requirements from requirements documents and their classification into categories based on the different kinds of architectural impact they can have. We believe this to be a crucial precursor for recommending specific design decisions. We envisage ArcheR, a tool that (a) automates the identification of architecturally significant functional requirements from requirement specification documents, (b) classify them into categories based on the different kinds of architectural impact they can have, (c) recommend probing questions the business analyst should ask in order to produce a more complete requirements specification, and (d) recommend possible architectural solutions in response to the architectural impact.","PeriodicalId":112329,"journal":{"name":"2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132355683","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 15

Bridging the Twin Peaks -- The Case of the Software Industry 跨越双峰——软件行业的案例

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture Pub Date : 2015-05-16 DOI: 10.1109/TWINPEAKS.2015.13

G. Lucassen, F. Dalpiaz, J. V. D. Werf, S. Brinkkemper

引用次数: 9

Scenario-Based Architecting with Architecture Trace Diagrams 使用架构跟踪图的基于场景的架构

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture Pub Date : 2015-05-16 DOI: 10.1109/TWINPEAKS.2015.11

E. Hebisch, Matthias Book, V. Gruhn

引用次数: 6

Architecting to Ensure Requirement Relevance: Keynote TwinPeaks Workshop 架构确保需求相关性:TwinPeaks研讨会主题演讲

2015 IEEE/ACM 5th International Workshop on the Twin Peaks of Requirements and Architecture Pub Date : 2015-05-16 DOI: 10.1109/TWINPEAKS.2015.8

J. Bosch

引用次数: 1