Telos: representing knowledge about information systems
ACM Transactions on Information Systems (TOIS)
Software safety in embedded computer systems
Communications of the ACM
Software product lines: practices and patterns
Software product lines: practices and patterns
A comprehensive product line scoping approach and its validation
Proceedings of the 24th International Conference on Software Engineering
FORM: A feature-oriented reuse method with domain-specific reference architectures
Annals of Software Engineering
Validated Designs For Object-oriented Systems
Validated Designs For Object-oriented Systems
Software Product Line Engineering: Foundations, Principles and Techniques
Software Product Line Engineering: Foundations, Principles and Techniques
A Practical Guide to Product Line Scoping
SPLC '06 Proceedings of the 10th International on Software Product Line Conference
SPLC '08 Proceedings of the 2008 12th International Software Product Line Conference
Proceedings of the 13th International Software Product Line Conference
Relating requirements and feature configurations: a systematic approach
Proceedings of the 13th International Software Product Line Conference
Requirements Engineering: Fundamentals, Principles, and Techniques
Requirements Engineering: Fundamentals, Principles, and Techniques
Context-dependent product line practice for constructing reliable embedded systems
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
Usage context as key driver for feature selection
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
RE '11 Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference
Context-dependent product line engineering with lightweight formal approaches
Science of Computer Programming
Hi-index | 0.00 |
During the development of embedded software, the system context (mechanical, electronical, business, etc.) has to be considered. Typically, this context is diverse and highly complex. Moreover, the context in which the system is embedded can vary. For example, the system can be used in different technical environments or in different countries. This variability in the context influences the software to be developed and typically leads to system variability. This paper systematically analyses the impact of context variability on the system development, more precisely, on the variability of the system. Related work is discussed and an example from the automotive domain is presented to identify open issues that need to be addressed.