2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)最新文献

Towards Software Assets Origin Selection Supported by a Knowledge Repository 面向知识库支持的软件资产来源选择

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH) Pub Date : 2016-04-05 DOI: 10.1109/MARCH.2016.11

A. Cicchetti, Markus Borg, Séverine Sentilles, K. Wnuk, Jan Carlson, Efi Papatheocharous

{"title":"Towards Software Assets Origin Selection Supported by a Knowledge Repository","authors":"A. Cicchetti, Markus Borg, Séverine Sentilles, K. Wnuk, Jan Carlson, Efi Papatheocharous","doi":"10.1109/MARCH.2016.11","DOIUrl":"https://doi.org/10.1109/MARCH.2016.11","url":null,"abstract":"Software architecture is no more a mere system specification as resulting from the design phase, but it includes the process by which its specification was carried out. In this respect, design decisions in component-based software engineering play an important role: they are used to enhance the quality of the system, keep the current market level, keep partnership relationships, reduce costs, and so forth. For non trivial systems, a recurring situation is the selection of an asset origin, that is if going for in-house, outsourcing, open-source, or COTS, when in the need of a certain missing functionality. Usually, the decision making process follows a case-by-case approach, in which historical information is largely neglected: hence, it is avoided the overhead of keeping detailed documentation about past decisions, but it is hampered consistency among multiple, possibly related, decisions.The ORION project aims at developing a decision support framework in which historical decision information plays a pivotal role: it is used to analyse current decision scenarios, take well-founded decisions, and store the collected data for future exploitation. In this paper, we outline the potentials of such a knowledge repository, including the information it is intended to be stored in it, and when and how to retrieve it within a decision case.","PeriodicalId":131381,"journal":{"name":"2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-04-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121622567","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}

引用次数: 17

A Context Model for Architectural Decision Support 架构决策支持的上下文模型

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH) Pub Date : 2016-04-05 DOI: 10.1109/MARCH.2016.6

Jan Carlson, Efi Papatheocharous, K. Petersen

{"title":"A Context Model for Architectural Decision Support","authors":"Jan Carlson, Efi Papatheocharous, K. Petersen","doi":"10.1109/MARCH.2016.6","DOIUrl":"https://doi.org/10.1109/MARCH.2016.6","url":null,"abstract":"Developing efficient and effective decision making support includes identifying means to reduce repeated manual work and providing possibilities to take advantage of the experience gained in previous decision situations. For this to be possible, there is a need to explicitly model the context of a decision case, for example to determine how much the evidence from one decision case can be trusted in another, similar context. In earlier work, context has been recognized as important when transferring and understanding outcomes between cases. The contribution of this paper is threefold. First, we describe different ways of utilizing context in an envisioned decision support system. Thereby, we distinguish between internal and external context usage, possibilities of context representation, and context inheritance. Second, we present a systematically developed context model comprised of five types of context information, namely organization, product, stakeholder, development method & technology, and market & business. Third, we exemplary illustrate the relation of the context information to architectural decision making using existing literature.","PeriodicalId":131381,"journal":{"name":"2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)","volume":"24 7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-04-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128926314","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}

引用次数: 12

SECO Patterns: Architectural Decision Support in Software Ecosystems SECO模式:软件生态系统中的架构决策支持

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH) Pub Date : 2016-04-05 DOI: 10.1109/MARCH.2016.10

Kilian Telschig, Nikolai Schoffel, K. Schultis, Christoph Elsner, Alexander Knapp

引用次数: 3

DecDoc: A Tool for Documenting Design Decisions Collaboratively and Incrementally DecDoc:一个以协作和增量方式记录设计决策的工具

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH) Pub Date : 2016-04-05 DOI: 10.1109/MARCH.2016.9

Tom-Michael Hesse, Arthur Kühlwein, T. Roehm

{"title":"DecDoc: A Tool for Documenting Design Decisions Collaboratively and Incrementally","authors":"Tom-Michael Hesse, Arthur Kühlwein, T. Roehm","doi":"10.1109/MARCH.2016.9","DOIUrl":"https://doi.org/10.1109/MARCH.2016.9","url":null,"abstract":"The outcome and quality of design decisions highly depend on the knowledge reflected during decision-making. Typically, making design decisions is not one singular action.Instead, developers discuss and cooperate during requirements engineering, design and implementation of a system to make and adapt design decisions. This decision-making process is influenced by different decision-making strategies, personal experiences, and biases. In consequence, decision-related knowledge emerges incrementally over time in an incomplete and heterogeneous way. This hinders the documentation of such knowledge in practice. First, most documentation tools capture decision-related knowledge within one particular development activity.However, they do not focus on the collaborative and shared documentation during multiple activities. Second, static documentation templates and formal rules are not suitable for capturing incomplete knowledge, as additional documentation effort is imposed for developers. Thus, text templates are not used or filled with generic contents. As a result, decision-related knowledge remains implicit and is not available to guide future decision-making. To address these issues, we have created the tool DecDoc based on our incremental documentation model. The tool enables developers to capture decision-related knowledge and collaborate on a comprehensive documentation of design decisions with relations to artifacts, such as requirement specifications, design diagrams, and code. This helps to improve the decision-making process for design decisions, as it helps to make explicit and reflect related knowledge during the process. In this paper, we present DecDoc with regard to requirements from the decision-making process.Then, we describe its application on design decisions in example projects. Finally, we discuss our insights from using the tool and highlight open challenges.","PeriodicalId":131381,"journal":{"name":"2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)","volume":"20 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-04-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127847566","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}

引用次数: 16

Inclusion of Ethical Aspects in Multi-criteria Decision Analysis 在多准则决策分析中包含伦理方面

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH) Pub Date : 2016-04-05 DOI: 10.1109/MARCH.2016.8

Gaetana Sapienza, G. Dodig-Crnkovic, I. Crnkovic

{"title":"Inclusion of Ethical Aspects in Multi-criteria Decision Analysis","authors":"Gaetana Sapienza, G. Dodig-Crnkovic, I. Crnkovic","doi":"10.1109/MARCH.2016.8","DOIUrl":"https://doi.org/10.1109/MARCH.2016.8","url":null,"abstract":"Decision process is often based on multi-faceted and mutually opposing criteria. In order to provide rigorous techniques for problem structuring and criteria aggregation used for classification and ranking of alternatives, Multiple Criteria Decision Analysis (MCDA) has been used as a method to achieve architectural decisions. Even though it has already been argued in literature that MCDA essentially depends on value systems of decision-makers, it is a question how the decision result reflects a particular criterion, requirement or a particular decision. This is especially true if a criterion is not precisely specified. In this paper we analyse the ethical aspects of MCDA. In our analysis we argue that it is in the long run necessary to make value basis of decision-making and ethical considerations explicit and subject for scrutiny. As a support to encourage introduction of transparent value-based deliberation we propose an extended MCDA scheme that would explicitly take into account ethical analysis. As an illustration, we present an industrial case study for the Software (SW)/Hardware (HW) partitioning of a wind turbine application in which different decisions can be taken, depending on the ethical aspects.","PeriodicalId":131381,"journal":{"name":"2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)","volume":"170 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2016-04-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123286144","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}

引用次数: 8

Architectural Decision-Making in Open-Source Systems -- Preliminary Observations 开源系统中的架构决策——初步观察

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH) Pub Date : 2016-04-05 DOI: 10.1109/MARCH.2016.7

Neil B. Harrison, E. Gubler, Danielle Skinner

引用次数: 5