Grant: Discovery Grants Program - Individual
University of Waterloo
$41,000.00
Feature-Oriented Software Engineering
FY 2023-24
Summary
A software system is often thought of in terms of its constituent features, where each feature is an optional or incremental unit of functionality (e.g., undo, word count, and track changes are features in word processing software). Software developers use features as a criterion for decomposing their work into tasks that can be performed incrementally, in parallel, or by third-party vendors. Feature-oriented software engineering enables incremental development and rapid evolution of software systems. The downside is that integrating seemingly orthogonal features can result in feature interactions where one feature unexpectedly affects the behaviour of another (e.g., conflicting actions, emergent behaviours, violated assumptions). Interactions are common problems in feature-rich software products. As a notable example: in both of the Boeing 737 MAX aircraft crashes, a faulty input sensor led to multiple feature interactions in which the infamous MCAS feature overpowered other features related to the aircraft's pitch (including pilot-controlled features) and forced the aircraft into a nose dive. To be safe, software engineers need to manage how features behave when integrated together. This proposal investigates two avenues of research that address different aspects of the Feature Interaction Problem. The first focuses on establishing a precise system-wide analysis to detect feature interactions in large feature-rich software systems. Novel advancements will be analyses that (1) examine actual software rather than models or test results (2) are comprehensive in the types of interactions they detect, (3) scale to large software products, and (4) are adequately precise. The second research avenue pursues a more holistic approach to manage feature interactions, by means of a software architecture that the features plug into. The architecture coordinates and constrains how features can execute and communicate, thereby avoiding or resolving certain classes of interactions. An architectural solution to managing interactions has the potential of ensuring safe integration of features, thereby reducing the number of residual interactions that the engineer must detect and resolve. The result will be technologies and HQP trained in feature-oriented designs and analyses that realize the improvements in developer productivity and product quality that feature-oriented software engineering has always promised.
Program
Discovery Grants Program - Individual
Recipient
Location
Ontario, Canada
Recipient Type
Academia
Type
Grant
Source
NSERC's Awards Data
As published
Application id
RGPIN-2020-04219
Name nom
Atlee, Joanne
Department département
David R. Cheriton School of Computer Science
Organization id
33
Institution établissement
University of Waterloo
Province en
Ontario
Province fr
Ontario
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2023
Competition year année de concours
2020
Award amount
41000
Program id
RGPIN
Program name en
Discovery Grants Program - Individual
Program name fr
Programme de subventions à la découverte - individuelles
Group en
DISCOVERY RESEARCH
Group fr
RECHERCHE AXÉE SUR LA DÉCOUVERTE
Committee code
1507
Committee name en
Computer Science
Committee name fr
Sciences informatiques
Area of application code
802
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Information systems and technology
Area of application fr
Systèmes d'information et technologie de l'information
Research subject code
9999
Research subject group en
Not available
Research subject group fr
Not available
Research subject en
Non disponible
Research subject fr
Non disponible
Application title
Feature-Oriented Software Engineering
Keyword
Dynamic Analysis; Feature Composition; Feature Interactions; Reverse Engineering; Software Architecture; Software Modelling; Static Analysis; System Integration and Interoperability; System of Systems
Application summary
A software system is often thought of in terms of its constituent features, where each feature is an optional or incremental unit of functionality (e.g., undo, word count, and track changes are features in word processing software). Software developers use features as a criterion for decomposing their work into tasks that can be performed incrementally, in parallel, or by third-party vendors. Feature-oriented software engineering enables incremental development and rapid evolution of software systems. The downside is that integrating seemingly orthogonal features can result in feature interactions where one feature unexpectedly affects the behaviour of another (e.g., conflicting actions, emergent behaviours, violated assumptions). Interactions are common problems in feature-rich software products. As a notable example: in both of the Boeing 737 MAX aircraft crashes, a faulty input sensor led to multiple feature interactions in which the infamous MCAS feature overpowered other features related to the aircraft's pitch (including pilot-controlled features) and forced the aircraft into a nose dive. To be safe, software engineers need to manage how features behave when integrated together. This proposal investigates two avenues of research that address different aspects of the Feature Interaction Problem. The first focuses on establishing a precise system-wide analysis to detect feature interactions in large feature-rich software systems. Novel advancements will be analyses that (1) examine actual software rather than models or test results (2) are comprehensive in the types of interactions they detect, (3) scale to large software products, and (4) are adequately precise. The second research avenue pursues a more holistic approach to manage feature interactions, by means of a software architecture that the features plug into. The architecture coordinates and constrains how features can execute and communicate, thereby avoiding or resolving certain classes of interactions. An architectural solution to managing interactions has the potential of ensuring safe integration of features, thereby reducing the number of residual interactions that the engineer must detect and resolve. The result will be technologies and HQP trained in feature-oriented designs and analyses that realize the improvements in developer productivity and product quality that feature-oriented software engineering has always promised.