Mapping Features to Reusable Components: A Problem Frames-Based Approach

Problem Frames-Based Approach to Achieving Quality Attributes in Software Product Line Engineering

“…Details of how the mapping between a problem frames model and a feature model is conducted and how a problem frames model is utilized during the whole SPLE process to develop components are described in [6]. The focus of this paper is on how a problem frames model is used to explore issues with domain assumptions, and we refer readers to [6] for more on how to map between the two models.…”

“…This mapping allows features (tend to be relatively abstract) to be refined into a recognizable software development problem (i.e., problem frames), for example, required behavior frames and commanded behavior frames which are then systematically developed into components using the frames' known analysis solutions [6], [9]. This problem framesbased approach is an improvement to feature-oriented SPLE because of its high opportunities for reuse of practical software problem patterns when mapping features to components as early as feature modeling.…”

“…The focus of this paper is on how a problem frames model is used to explore issues with domain assumptions, and we refer readers to [6] for more on how to map between the two models. As a simple example (Fig.…”

“…To deal with this problem, we propose to use a problem frames-based approach [6] which allows features to be mapped to problem frames. From these mappings, functional requirements and their related domain concerns are elicited and uncovered.…”

“…Consequently, it is believed to have some advantage over other SPLE methods in which problem frames are not utilized. Some of those benefits can be that assets (i.e., reusable components) are developed from features with shorter development time and higher reliability as a direct consequence of reuse of problem patterns [3], [6].…”