{"title":"Interdisciplinary Requirements Analysis Using the Model-based RM Tool AUTORAID","authors":"Eva Geisberger, J. Grunbauer, B. Schatz","doi":"10.1109/AURE.2006.2","DOIUrl":"https://doi.org/10.1109/AURE.2006.2","url":null,"abstract":"A major task in designing embedded systems is the systematic elaboration of functional system requirements and their integration into the environment of the overall technical system. The main challenge is to handle the versatile tasks of coordinating the communication and consolidation of the various stakeholder requirements of the different involved diciplines and derive a common definition of the system behavior, which is appropriate to the problem. The problem- and customer-related product definition must be consolidated with and integrated into the manifold requirements of the functional and technical system design. Accordingly, the model-based requirements analysis and system-definition presented here defines a well-structured modeling approach, which provides a basic model of RE work products (RE Product Model) and systematically guides the goal-oriented formulation and adjustment of the different stakeholder-requirements by using functional system views and descriptive specification techniques. Thus it allows a clear specification of a consistent and complete system design. The central steps of this approach are implemented in a requirements management (RM) tool prototype called AUTORAID.","PeriodicalId":162850,"journal":{"name":"International Automotive Requirements Engineering Workshop (AURE'06 - RE'06 Workshop)","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122713650","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}
{"title":"Applying Aspect-Orientation Techniques in Automotive Software Product-Line Engineering","authors":"K. Mehner, Mark-Oliver Reiser, Matthias Weber","doi":"10.1109/AURE.2006.1","DOIUrl":"https://doi.org/10.1109/AURE.2006.1","url":null,"abstract":"The application of product-line engineering concepts to automotive software development has received increasing attention during the last few years. A core facet of software product-line approaches is the definition and management of variability within various development artifacts. Aspect-orientation techniques provide an interesting alternative to the traditional way of defining variability with variation points and variants. In this paper we (1) show where and how aspectorientation can be embedded in an automotive product-line approach, (2) compare the traditional technique for variability definition with the aspectoriented one and finally (3) discuss the benefits as well as possible shortcomings of applying aspectorientation for automotive software product-lines.","PeriodicalId":162850,"journal":{"name":"International Automotive Requirements Engineering Workshop (AURE'06 - RE'06 Workshop)","volume":"78 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125348535","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}
{"title":"Tailoring the Process for Automotive Software Requirements Engineering","authors":"B. Hwong, Xiping Song","doi":"10.1109/AURE.2006.5","DOIUrl":"https://doi.org/10.1109/AURE.2006.5","url":null,"abstract":"When an automotive organization goes from being part of the OEM organization to being a supplier organization, several Requirements Engineering issues must be faced. The first is how the organization adapts to a new parent organization and its software development processes. Another is recognizing the need for more formal artifacts to better define the responsibility boundary between customer and supplier. One other change is adapting to working in a distributed fashion when software development is split among multiple locations, while manufacturing entails yet another location. We recently piloted an automotive software development group through this change and this paper will report on the lessons we learned.","PeriodicalId":162850,"journal":{"name":"International Automotive Requirements Engineering Workshop (AURE'06 - RE'06 Workshop)","volume":"159 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115563382","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}