[show abstract][hide abstract] ABSTRACT: There are only few methods available that help refining software requirements to software architectures. An example is the CBSP (Component-Bus-System-Property) approach that uses general architectural concerns to classify and refine requirements and to capture architectural trade-off issues and options. This paper reports about experiences of applying CBSP in an industrial project in the area of mobile applications. We illustrate CBSP using project examples. We discuss how the approach was tailored and present extensions we developed. In particular, we show how CBSP can be used together with the Goal-Question-Metric approach to guide architectural decisions. We close our paper with a discussion of lessons learned during this project.
RE 2011, 19th IEEE International Requirements Engineering Conference, Trento, Italy, August 29 2011 - September 2, 2011; 01/2011
[show abstract][hide abstract] ABSTRACT: Deriving a product from a product line requires the involvement and cooperation of heterogeneous stakeholders such as customers, sales people, or engineers. Taking their different roles and needs into account is essential to exploit the possible benefits of product lines. In this paper we present the tool-supported product line engineering approach DOPLER. We demonstrate how the approach supports both non- technicians and engineers in product derivation and requirements engineering through a set of integrated tools.
Requirements Engineering Conference, 2007. RE '07. 15th IEEE International; 11/2007
[show abstract][hide abstract] ABSTRACT: As the world's leading supplier of metallurgical plants, Siemens VAI provides integrated and universally applicable continuous casting systems for the steel industry. The complexity of the process of casting liquid steel is supported by software products that enable high-quality steel casts and efficient plant performance. Over the last recent years Siemens VAI developed a flexible software product line. The system has been classified as highly reliable, which implies rigorous and systematic testing throughout all phases of the development lifecycle. In this paper we investigate how testing is embedded in the development life- cycle and how various testing methods are applied to ensure high software reliability. The lessons learned distilled from over five years of project experience discuss practices that contributed to the current testing approach.
[show abstract][hide abstract] ABSTRACT: The article presents essays from the configuration workshop held in August 2006 as part of ECAI in Riva del Garda, Italy. The essays address reasoning techniques, user interaction, business integration, and finally presents a practical case study. These essays aim to give the readers insight into current trends and challenges in configuration. If you order a computer system online, you likely have the opportunity to customize it to your individual needs: you can choose from different CPUs and main memory sizes, select the appropriate graphics card and hard drive, and so on. However, if the ordering system doesn't accept your configuration as is, you'll have to modify it. For example. a large LCD screen might require a special graphics card, or the CPU you've chosen might require a special main board, With more complex products, such as cars, the situation gets even more complicated - for example, you can choose from hundreds of equipment options when ordering a Mercedes, resulting in millions of possible combinations. Product configuration, the business process that supports these choices, offers both opportunities and challenges
[show abstract][hide abstract] ABSTRACT: Capturing and sharing architectural knowledge is already a complex endeavor when dealing with conventional software systems for single customers. In product line engineering, however, the situation is even more difficult due to architectural variability and complex relationships between features and technical solution components. In this paper, we present our experiences and approaches taken in eliciting and sharing architectural knowledge for the software product line infrastructure of a company in the plant building domain. An important lesson learned is the necessity of capturing architectural knowledge and making this knowledge available appropriately to various stakeholders in the product line environment