Functional and Non-Functional Properties in a Family of Embedded Operating Systems

Lohmann, Daniel; Schröder-Preikschat, Wolfgang; Spinczyk, Olaf

doi:10.1109/words.2005.37

Cited by 12 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Feature modeling was originally proposed as part of the Feature-Oriented Domain Analysis (FODA) method , and, since then, it has been applied in a range of domains, including telecom systems (Griss et al, 1998, Lee et al, 2002, template libraries (Czarnecki and Eisenecker 2000), network protocols (Barbeau and Bordeleau 2002), and embedded systems (Czarnecki et al, 2002, Lohmann et al, 2005. On the basis of this growing experience, a number of extensions and variants of the original FODA notation have been put forward (Griss et al, 1998, Czarnecki 1998, Hein et al, 2000, van Gurp et al, 2001, Lee et al, 2002, Riebisch et al, 2002, Czarnecki et al, 2002, Beuche 2003, Cechticky et al, 2004.…”

Section: Introductionmentioning

confidence: 99%

Staged configuration through specialization and multilevel configuration of feature models

Czarnecki

Helsen

Eisenecker

2005

Softw Process Imprv Pract

341

216

View full text Add to dashboard Cite

Feature modeling is a key technique for capturing commonalities and variabilities in system families and product lines. In this article, we propose a cardinality-based notation for feature modeling, which integrates a number of existing extensions of previous approaches. We then introduce and motivate the novel concept of staged configuration. Staged configuration can be achieved by the stepwise specialization of feature models or by multilevel configuration, where the configuration choices available in each stage are defined by separate feature models. Staged configuration is important because, in a realistic development process, different groups and different people make product configuration choices in different stages. Finally, we also discuss how multilevel configuration avoids a breakdown between the different abstraction levels of individual features. This problem, sometimes referred to as 'analysis paralysis', easily occurs in feature modeling because features can denote entities at arbitrary levels of abstraction within a system family.

show abstract

Section: Introductionmentioning

confidence: 99%

Staged configuration through specialization and multilevel configuration of feature models

Czarnecki

Helsen

Eisenecker

2005

Softw Process Imprv Pract

341

216

View full text Add to dashboard Cite

show abstract

“…Examples are: code size, memory footprint, performance, security, reliability, scalability, etc. Our experience developing families of operating systems show that these properties emerge from the complex interactions among the different modules that comprise the entire system [26], [25].…”

Section: B Non-functional Propertiesmentioning

confidence: 99%

Towards Tool Support for the Configuration of Non-Functional Properties in SPLs

Sincero

Schröder-Preikschat

Spinczyk

2009

2009 42nd Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

Abstract-The configuration of NFPs (non-functional properties) is a crucial problem in the development of software-intensive systems. Most of the approaches currently available tackle this problem during software design. However, at this stage, NFPs cannot be properly predicted. As a solution for this problem we present the new extensions of the Feedback approach which aims at improving the configuration of NFPs in SPLs. We introduce our set of tools that are used to support the approach and show how to use them by applying it to the well-known SPL (The Graph Product Line) that was suggested as a platform for evaluating SPL technologies. I. INTRODUCTION A. Software Product LinesThe development of software product lines (SPLs) are considered [31] to be a new paradigm, as the result of its implementation, different members of a family of systems (product portfolio) can be generated. A SPL is, normally, comprised of a set of assets (software components, documentation, etc.) that can be assembled together to deliver products that satisfy the needs of a particular domain.Several methodologies have been proposed in order to support the development of SPLs. Domain engineering [11] is the act of studying and documenting a specific domain in order to support the subsequent development phases (e.g. application engineering). Feature modeling is the approach used to capture the common, the variable and the interdependency's present in a specific domain, the results are captured in a model (normally a represented in the form of a feature diagram) that determines which sets of features are valid product specifications. Hence, feature modeling is specially important during domain engineering and also during product configuration. [29] are also addressed. The use of these, and, of course, other methodologies, in the context of SPL development, aim at reduced time to market, reduced costs, higher productivity, better product quality [31], etc.

show abstract

“…Being able to model non-functional interdependencies, however, is only one issue, another issue is to implement them in a modular way to generally improve software maintenance [23,25]. PURE proved that it must not be a contradiction to come up with a highly modular operating system design and implementation and at the same time keeping the many building blocks manageable.…”

Section: Aspect Orientation Of Operating Systemsmentioning

confidence: 99%

The Design of Application-Tailorable Operating System Product Lines

Lohmann

Schröder-Preikschat

Spinczyk

2006

Construction and Analysis of Safe, Secure, and Interoperable Smart Devices

View full text Add to dashboard Cite

Abstract. System software for deeply embedded devices has to cope with a broad variety of requirements and platforms, but especially with strict resource constraints. To compete against proprietary systems (and thereby to facilitate reuse), an operating system product line for deeply embedded systems has to be highly configurable and tailorable. It is therefore crucial that all selectable and configurable features can be encapsulated into fine-grained, exchangeable and reusable implementation components. However, the encapsulation of non-functional properties is often limited, due to their cross-cutting character. Fundamental system policies, like synchronization or activation points for the scheduler, have typically to be reflected in many points of the operating system component code. The presented approach is based on feature modeling, C++ class composition and overcomes the above mentioned problems by means of aspect-oriented programming (AOP). It facilitates a finegrained encapsulation and configuration of even non-functional properties in system software.

show abstract

Functional and Non-Functional Properties in a Family of Embedded Operating Systems

Abstract: The increasing complexity of embedded systems calls for software design

Cited by 12 publications

References 11 publications

Staged configuration through specialization and multilevel configuration of feature models

Staged configuration through specialization and multilevel configuration of feature models

Towards Tool Support for the Configuration of Non-Functional Properties in SPLs

The Design of Application-Tailorable Operating System Product Lines

Contact Info

Product

Resources

About