2011 Model-Driven Requirements Engineering Workshop最新文献

Formalizing standards and regulations variability in longlife projects. A challenge for Model-driven engineering 使长寿命项目中的标准和法规可变性正规化。模型驱动工程的挑战

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045368

Nicolas Sannier, B. Baudry, Thuy Nguyen

引用次数: 11

Transforming an enterprise model into a use case model using existing heuristics 使用现有的启发式方法将企业模型转换为用例模型

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045363

F. Siqueira, P. S. M. Silva

引用次数: 10

Streamlining scenario modeling with Model-Driven Development: A case study 使用模型驱动的开发简化场景建模:一个案例研究

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MODRE.2011.6045367

M. Goulão, A. Moreira, João Araújo, João Pedro Santos

引用次数: 5

Interactive requirements validation for reactive systems through virtual requirements prototype 通过虚拟需求原型对反应性系统进行交互需求验证

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045361

Daniel Aceituna, Hyunsook Do, Seok-Won Lee

引用次数: 11

Validation of embedded system verification models 嵌入式系统验证模型的验证

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045366

Jelena Marincic, A. Mader, R. Wieringa

{"title":"Validation of embedded system verification models","authors":"Jelena Marincic, A. Mader, R. Wieringa","doi":"10.1109/MoDRE.2011.6045366","DOIUrl":"https://doi.org/10.1109/MoDRE.2011.6045366","url":null,"abstract":"The result of a model-based requirements verification shows that the model of a system satisfies (or not) formalised system requirements. The verification result is correct only if the model represents the system adequately. No matter what modelling technique we use, what precedes the model construction are non-formal activities. During these activities the modeller has to learn how the system works, what the requirements are, and to decide what is relevant to model and how to do it. Due to a partly non-formal nature of modelling steps, we do not have a formal proof that the model represents the system adequately. The most we can do is to increase the confidence in the model. In this paper we explore non-formal model validation steps while designing a formal model. On the example of a Uppaal performance model we designed in a company that produces printers, we will show what validation steps were necessary to increase the stakeholders' confidence in the model. Based on this case study, we propose more general, but non-formal model validation steps, that can structure model validation. The steps we propose deal with the same design elements and issues present in other model-based verification activities, therefore can accompany them as well.","PeriodicalId":391740,"journal":{"name":"2011 Model-Driven Requirements Engineering Workshop","volume":"101 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-10-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125897085","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

Requirements verification in the presence of variability 在存在可变性的情况下进行需求验证

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045369

J. Corriveau, Soheila Bashardoust-Tajali, Vojislav D. Radonjic

引用次数: 3

Transformation of aspect-oriented requirements specifications for reactive systems into aspect-oriented design specifications 将响应式系统的面向方面需求规范转换为面向方面的设计规范

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045365

G. Mussbacher, J. Kienzle, Daniel Amyot

{"title":"Transformation of aspect-oriented requirements specifications for reactive systems into aspect-oriented design specifications","authors":"G. Mussbacher, J. Kienzle, Daniel Amyot","doi":"10.1109/MoDRE.2011.6045365","DOIUrl":"https://doi.org/10.1109/MoDRE.2011.6045365","url":null,"abstract":"Model-driven engineering (MDE) promises faster and more reliable software development processes. A key factor of MDE is the transformation of models, allowing a software engineer to use the most appropriate modeling notation for a particular task. The earlier transformations can be applied during software development, the greater the potential cost savings. To that effect, we report on the transformation of aspect-oriented models for reactive systems development, i.e., from a scenario-based requirements model into a UML-based design model. We use Aspect-oriented Use Case Maps (AoUCM) as the requirements notation and Reusable Aspect Models (RAM) as the design notation. While AoUCM is ideally suited for the specification of the system workflow comprised of interactions between the environment and the system, RAM excels in providing a design view of system structure and defining the data dimension of the system including inputs and outputs. As the more abstract AoUCM models are transformed into more concrete RAM models, MDE ensures that the AoUCM workflow specifications do not have to be modeled again in RAM, thus avoiding a duplication of effort. We present transformation algorithms to show that an AoUCM-to-RAM mapping is indeed feasible and report on initial tool support for the transformation.","PeriodicalId":391740,"journal":{"name":"2011 Model-Driven Requirements Engineering Workshop","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-10-17","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121939106","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

An architecture-oriented model-driven requirements engineering approach 面向体系结构的模型驱动需求工程方法

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-10-17 DOI: 10.1109/MoDRE.2011.6045364

Grzegorz Loniewski, Ausias Armesto, E. Insfrán

引用次数: 9

Defining an annex language to the architecture analysis and design language for requirements engineering activities support 为需求工程活动支持定义架构分析和设计语言的附件语言

2011 Model-Driven Requirements Engineering Workshop Pub Date : 2011-08-29 DOI: 10.1109/MoDRE.2011.6045362

Dominique Blouin, E. Senn, S. Turki

{"title":"Defining an annex language to the architecture analysis and design language for requirements engineering activities support","authors":"Dominique Blouin, E. Senn, S. Turki","doi":"10.1109/MoDRE.2011.6045362","DOIUrl":"https://doi.org/10.1109/MoDRE.2011.6045362","url":null,"abstract":"Several requirements modeling languages such as the requirements package of SysML have been developed to improve the elicitation, analysis, validation and verification of requirements during project development life cycles. However, none of these languages is generic enough to embed explicit traces to components of arbitrary system architecture languages intending to provide a solution to the problem formalized by requirements specifications. For example, systems engineers using the Architecture Analysis and Design Language (AADL) cannot broidge SysML requirements to their architecture models in the same way it is done for UML models. The only way would be to define an external trace model linking the requirements to AADL model elements. In this paper, the new Requirements Definition and Analysis Language (RDAL) is presented. Inspired from SysML and the IEEE 15288 system life cycle processes standards, RDAL requirements can be traced to elements from any language of the solution domain, according to a settings model defining the allowed element types. Moreover, RDAL requirements can be expressed formally in terms of any constraint language such as OCL or REAL (for AADL) to provide automated verification against the associated solution (architecture) models. RDAL also adds important requirements engineering concepts such as environmental assumptions and goals not covered in SysML. RDAL is currently being standardized by the SAE AS-2C committee to become an annex of AADL.","PeriodicalId":391740,"journal":{"name":"2011 Model-Driven Requirements Engineering Workshop","volume":"100 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114924728","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}

引用次数: 24