scholarly journals BRIDGING GAP OF USER GOAL REQUIREMENTS AND IMPLEMENTED APPLICATIONS BASED ON FEATURE MODEL

2013 ◽  
Vol 8 (2) ◽  
pp. 113
Author(s):  
Ahmad Nurul Fajar ◽  
Eko K. Budiardjo ◽  
Zainal A. Hasibuan
Keyword(s):  
Process Model ◽  
Model Development ◽  
Feature Modeling ◽  
Feature Model ◽  
Product Lines ◽  
User Requirement ◽  
Classification Feature ◽  
Software Product ◽  
Feature Importance ◽  
Support Software

Feature modeling is a conceptual thinking for identifying and classification feature in order for support software product lines. However, there are lack of the user goal requirements. It related with a technique for managing of features commonalities and variability. It has a hierarchy of features with variability and the purpose is to organize features. In practice of implemented applications, the feature model development lack of goal user requirement. The goal of user requirement in Indonesian government has described in document regulations. It should be a fundamental concern to develop e-government applications. However, In order to capture degree of software feature importance, some of features compared with implemented e-government applications. We have extracted some of features which can be compared with the implemented e-government applications. Our technique is extracted are derived from document regulations to business process model and feature model also. We Choose SIPKD and SIMDA applications which has implemented in Indonesian local government which has variation from one and another. We use extended AHP and S-AHP to find the prioritization of software features. The results are 80 features in SIPKD and 90 features in SIMDA. There are 65 features common and 25 variant features .This make un-optimization usage applications.

scholarly journals Features as transformations: A generative approach to software development

2016 ◽  
Vol 13 (3) ◽  
pp. 759-778
Author(s):  
Valentino Vranic ◽  
Roman Táborský
Keyword(s):  
Software Reuse ◽  
Feature Modeling ◽  
Feature Model ◽  
Product Lines ◽  
Generative Process ◽  
Model Driven ◽  
Software Artifacts ◽  
Model Configuration ◽  
Software Product ◽  
Selection Of

The objective of feature modeling is to foster software reuse by enabling to explicitly and abstractly express commonality and variability in the domain. Feature modeling is used to configure other models and, eventually, code. These software assets are being configured by the feature model based on the selection of variable features. However, selecting a feature is far from a naive component based approach where feature inclusion would simply mean including the corresponding component. More often than not, feature inclusion affects several places in models or code to be configured requiring their nontrivial adaptation. Thus, feature inclusion recalls transformation and this is at heart of the approach to feature model driven generation of software artifacts proposed in this paper. Features are viewed as transformations that may be executed during the generative process conducted by the feature model configuration. The generative process is distributed in respective transformations enabling the developers to have a better control over it. This approach can be applied to modularize changes in product customization and to establish generative software product lines by gradual refactoring of existing products.

scholarly journals Feature Model Configuration Based on Two-Layer Modelling in Software Product Lines

2019 ◽  
Vol 9 (4) ◽  
pp. 2648
Author(s):  
Elham Darmanaki Farahani ◽  
Jafar Habibi
Keyword(s):  
Product Line ◽  
Feature Model ◽  
Functional Requirements ◽  
Product Lines ◽  
Software Products ◽  
Model Configuration ◽  
Software Product ◽  
Software And Hardware ◽  
Application Requirements

The aim of the Software Product Line (SPL) approach is to improve the software development process by producing software products that match the stakeholders’ requirements. One of the important topics in SPLs is the feature model (FM) configuration process. The purpose of configuration here is to select and remove specific features from the FM in order to produce the required software product. At the same time, detection of differences between application’s requirements and the available capabilities of the implementation platform is a major concern of application requirements engineering. It is possible that the implementation of the selected features of FM needs certain software and hardware infrastructures such as database, operating system and hardware that cannot be made available by stakeholders. We address the FM configuration problem by proposing a method, which employs a two-layer FM comprising the application and infrastructure layers. We also show this method in the context of a case study in the SPL of a sample E-Shop website. The results demonstrate that this method can support both functional and non-functional requirements and can solve the problems arising from lack of attention to implementation requirements in SPL FM selection phase.

A Generic Process for the Design and Generation of Software Product Line Skeleton Architectures

2014 ◽  
Vol 24 (09) ◽  
pp. 1301-1335
Author(s):  
Maria Eugenia Cabello ◽  
Isidro Ramos ◽  
Oscar Alberto Santana ◽  
Saúl Iván Beristain
Keyword(s):  
Software Architecture ◽  
Software Product Line ◽  
Product Line ◽  
Feature Model ◽  
Software Systems ◽  
Reference Architecture ◽  
Product Lines ◽  
Model Driven ◽  
Software Product ◽  
And Behavior

This paper presents a process, a method and a framework for developing families of software systems in a domain. The process is generic (domain-independent) and produces skeleton software architectures as Software Product Lines. The genericity is supported by the metamodels (abstract languages) that are defined in order to describe the Reference Architecture (structure view, behavior view and variability view) of the system domain. A standardized Production Plan takes the Reference Architecture as input and produces the equivalent Skeleton Software Architecture (component-connector view) using a Feature Model configuration (describing the system to be) as output. This Skeleton Software Architecture includes the structure and behavior of the target software product. A framework has been implemented to support the approach. The process is applied, as an example, to the Diagnostic Expert Systems domain. Our approach is based on Model-Driven Engineering techniques and the Software Product Line paradigm. A domain analysis must be done in order to build the Reference Architecture.

Addressing Non-Functional Properties in Feature Models: A Goal-Oriented Approach

2014 ◽  
Vol 24 (10) ◽  
pp. 1439-1487 ◽  
Author(s):  
Mehdi Noorian ◽  
Mohsen Asadi ◽  
Ebrahim Bagheri ◽  
Weichang Du
Keyword(s):  
Functional Properties ◽  
Product Line ◽  
Feature Model ◽  
Software Systems ◽  
Feature Models ◽  
Target Domain ◽  
Product Lines ◽  
Software Products ◽  
Software Product ◽  
Goal Models

Software Product Line (SPL) engineering is a systematic reuse-based software development approach which is founded on the idea of building software products using a set of core assets rather than developing individual software systems from scratch. Feature models are among the widely used artefacts for SPL development that mostly capture functional and operational variability of a system. Researchers have argued that connecting intentional variability models such as goal models with feature variability models in a target domain can enrich feature models with valuable quality and non-functional information. Interrelating goal models and feature models has already been proposed in the literature for capturing non-functional properties in software product lines; however, this manual integration process is cumbersome and tedious. In this paper, we propose a (semi) automated approach that systematically integrates feature models and goal models through standard ontologies. Our proposed approach connects feature model and goal model elements through measuring the semantic similarity of their annotated ontological concepts. Our work not only provides the means to systematically interrelate feature models and goal models but also allows domain engineers to identify and model the role and significance of non-functional properties in the domain represented by the feature model.

scholarly journals Evolving feature model configurations in software product lines

2014 ◽  
Vol 87 ◽  
pp. 119-136 ◽  
Author(s):  
Jules White ◽  
José A. Galindo ◽  
Tripti Saxena ◽  
Brian Dougherty ◽  
David Benavides ◽  
...  
Keyword(s):  
Software Product Lines ◽  
Feature Model ◽  
Product Lines ◽  
Software Product

Zeitskalen-Trennung und Simulation bei der Entwicklung hybrider Leistungsbündel/Time Scale Separation and Simulation for the development of hybrid Product Service Systems

2015 ◽  
Vol 105 (07-08) ◽  
pp. 541-548
Author(s):  
T. Steckel ◽  
W. Nüßer
Keyword(s):  
Process Model ◽  
Service Systems ◽  
Product Lines ◽  
Scale Separation ◽  
Time Scale Separation ◽  
Product Service ◽  
Software Product ◽  
Early Validation ◽  
Development Processes ◽  
Product Service Systems

Bei der effizienten Entwicklung hybrider Leistungsbündel gilt es, existierende Entwicklungsprozesse in Unternehmen zu berücksichtigen. Es wird ein Vorgehensmodell beschrieben, das zur besseren Einbettung in bestehende Prozesse bekannte Modelle aus Maschinenbau und Software-Engineering integriert, den gesamten Lebenszyklus der Leistungsbündel abbildet und Simulationstechniken zur frühzeitigen Validierung von Anforderungen und Konzepten verwendet.   An efficient development of product service systems (PSS) has to account for already existing development processes in companies. Models for the development of PSS currently available can be adapted to better fit into company processes. We propose a process model which is in line with typical processes characteristics found in many engineering companies. It spans the whole lifecycle of PSS and makes use of concepts known from software product lines. Additionally, we integrate simulation technics to address the well-known requirement of early validation.

Using Fault Propagation Analyses for Early Elimination of Unreliable Design Alternatives of Complex Cyber-Physical Systems

2012 ◽  
Author(s):  
Nikolaos Papakonstantinou ◽  
Seppo Sierla ◽  
Irem Y. Tumer ◽  
David C. Jensen
Keyword(s):  
Nuclear Reactor ◽  
Feature Modeling ◽  
Feature Model ◽  
Component Model ◽  
Source Information ◽  
Fault Propagation ◽  
Product Lines ◽  
Design Alternatives ◽  
Software Engineers

The Functional Failure Identification and Propagation (FFIP) framework has been proposed in prior work to study the reliability of early phase designs of complex systems. For the specified functionality, a model of mechanical, electrical and software components has been defined to support simulation and discovery of fault propagation paths. The advantage of this approach has been the possibility to identify unreliable designs before high cost design commitments have been made. However, a weakness is that the results are specific to the component model that is created for the purpose of running the FFIP simulations; it is unclear how the results would change if different modeling choices would have been made. Further, the usefulness of the method in design has been limited to evaluating reliability rather than actively finding more robust design alternatives. In order to address these weaknesses, the FFIP component model needs to incorporate a capability to describe design alternatives. The feature modeling syntax and semantics, which has been successfully used by software engineers to describe customer variations in product lines, is applied here to specify alternative mechanical, electrical and software features of a cyber-physical system. In the concept phase, all plausible design alternatives are described with a feature model. FFIP analyses can be performed for each valid configuration of this model, and all alternatives that are found unreliable are removed. The result is a restricted feature model, comprising significantly fewer design alternatives, that is delivered as source information for the detailed design phase. A toolchain for performing these analyses is presented, integrating open source feature modeling and configuration tools to the FFIP environment. The methodology is illustrated with a case study from boiling water nuclear reactor design.

Sign in / Sign up

Export Citation Format

Share Document