Feature Oriented Domain Analysis Research Articles

Feature Model for Pet Health Application Domain using Feature Oriented Domain Analysis

Feature Model for Pet Health Application Domain using Feature Oriented Domain Analysis

Design of embedded software architecture for spacecraft electric propulsion system

With the rapid growth of the number of spacecraft tasks and the complexity of the system, spacecraft software development is faced with the challenges of high-quality and rapid delivery, increased complexity, and frequent changes in requirements. The reuse rate of software assets needs to be improved urgently. In order to realize cross-platform and cross-project reuse of software design, this paper studies the design of electric propulsion software architecture. Carry out requirements decomposition and subsystem division of electric propulsion systems for different platforms, extract common requirements and variability requirements at the system level and subsystem level based on the Feature-Oriented Domain Analysis method, and establish a requirements model. Based on the requirements model, an electric propulsion software architecture integrating “event-driven + components” is proposed, and the classic event-driven model of “publish-subscribe” is adaptively improved. The architecture has been instantiated and applied to 16 projects on 4 platforms, and the reuse rate of core assets has reached 70%. This paper has certain guidance and reference significance for spacecraft software asset reuse and platform construction.

Canvas Learning Management System Feature Analysis Using Feature-Oriented Domain Analysis (FODA)

The impact of Covid-19 on the world of education requires the implementation of online learning. Information and computer technology can provide solutions in education through the Learning Management System (LMS). Canvas LMS is a form of LMS that can be utilized by lecturers and students in online learning during the Covid-19 pandemic. In this study, researchers analyzed the features of Canvas LMS using the Feature-Oriented Domain Analysis (FODA) method. Researchers also conducted a mapping of canvas LMS features with the National Standard of Higher Education (SN Dikti). This study showed two stages of validation by Education and LMS experts to verify the results of the analysis. At the end of the course, we recommended a new LMS feature that complies with SN Dikti for Lecturer and Student users.

SGSC Framework: Smart Government in Supply Chain Based on FODA

Smart System has implemented in government sector. There are varies Implementation that was utilized by research activities for numerous domains is very broad. Besides that, the Industry, transportation and health, also where such a system is incredibly beneficial. This study discuss supply chain and governmental link issue, coordination of all stakeholder in supply chain has to reflect the government role. It support with the condition in Indonesian government environment is unique. It is a challenge to construct smart system based on Feature Oriented Domain Analysis (FODA) approach. It can produce software product line (SPL). We proposed framework for develop software product line for smart supply chain in government sector. It is used to enhance and improve the development of software systems by multiple software system developers. It will be a guidance for construct smart government, and more specificity in supply chain for government system area environment. It is called SGSC Framework. It consists of four layers, such as optimization layer, integration layer, supply chain layer and data layer.

Mapeamento de características de sites de compartilhamento de refeições baseado no Modelo 3C de Colaboração

This article aims to identify the features of sites containing meal sharing platforms, organized by professionals or by domestic cooks, in which users are looking for a gastronomic experience. The article presents a study and mapping of the features of sites from the domain analysis based on the technical Feature Oriented Domain Analysis (FODA) of the 3C collaboration model. This model organizes the activities of collaborative systems in the dimensions of communication, coordination and cooperation. The survey results contribute to the gastronomy business, highlighting the possibility of their implementation or interpretation to improve the type of gastronomic experience that leads to new consumption patterns. The 3C collaborative model assisted in the organizing process of the characteristics used in the meal-sharing platforms. Based on the analysis performed, it was possible to identify and understand the evolution of the characteristics as well as to contextualize the new forms of socialization and interaction among people around gastronomy, considering those that can be brought to the gastronomy business sites.

IBED: Combining IBEA and DE for optimal feature selection in software product line engineering

Software configuration, which aims to customize the software for different users (e.g., Linux kernel configuration), is an important and complicated task. In software product line engineering (SPLE), feature oriented domain analysis is adopted and feature model is used to guide the configuration of new product variants. In SPLE, product configuration is an optimal feature selection problem, which needs to find a set of features that have no conflicts and meanwhile achieve multiple design objectives (e.g., minimizing cost and maximizing the number of features). In previous studies, several multi-objective evolutionary algorithms (MOEAs) were used for the optimal feature selection problem and indicator-based evolutionary algorithm (IBEA) was proven to be the best MOEA for this problem. However, IBEA still suffers from the issues of correctness and diversity of found solutions. In this paper, we propose a dual-population evolutionary algorithm, named IBED, to achieve both correctness and diversity of solutions. In IBED, two populations are individually evolved with two different types of evolutionary operators, i.e., IBEA operators and differential evolution (DE) operators. Furthermore, we propose two enhancement techniques for existing MOEAs, namely the feedback-directed mechanism to fast find the correct solutions (e.g., solutions that satisfy the feature model constraints) and the preprocessing method to reduce the search space. Our empirical results have shown that IBED with the enhancement techniques can outperform several state-of-the-art MOEAs on most case studies in terms of correctness and diversity of found solutions.

Технология создания семейства приложений на основе анализа предметной области

The theme of code reuse in software development is still important. Sometimes it is hard to find out what exactly we need to reuse in isolation of context. However, there is an opportunity to narrow the context problem, if applications in one given domain are considered. Same features in different applications in one domain have the same context respectively so the common part must be reused. Hence, the problem of domain analysis arises. On the other hand, there is metaCASE-techonology that allows to generate code of an application using diagrams, which describe this application. The main objective of this article is to present the technology for application family creation which connects the metaCASE-techonology and results of domain analysis activity. We propose to use some ideas of FODA (feature-oriented domain analysis) approach for domain analysis and use feature diagrams for describing of variability in a domain. Then we suggest to generate metamodel of the domain-specific visual language, based on feature diagram. After that based on generated metamodel domain-specific visual language editor is generated with the aid of metaCASE-tool. With this language user can connect and configure existing feature implementations thus producing an application. This technology supposed to be especially useful for software product lines.

An OCL-Based Formal Model for Cloud Forensics

Cloud Computing is gaining acceptance and increasing in popularity. However, digital forensics within Cloud becomes difficult. This paper proposes an extensible semantic model using OCL (Object Constraint Language) for cloud digital forensics data. We give a brief introduction to Trusted Digital Forensics, and then detail the modeling process using OCL and FODA (Feature Oriented Domain Analysis). Therefore, a feature tree can be built with semantic logical relation in order to get the overall semantic description of features in the forensic domain of digital data.

Feature Modeling and Variability Modeling Syntactic Notation Comparison and Mapping

Feature Model (FM) became an important role in Software Product Line Engineering (SPLE) field. Many approaches have been introduced since the original FM came up with Feature Oriented Domain Analysis (FODA) introduced by Kang in 1990. The main purpose of FM is used for commonality and variability analysis in domain engineering, to optimize the reusable aspect of software features or components. Cardinality-based Feature Model (CBFM) is one extension of original FM, which integrates several notations of other extensions. In CBFM, feature model defined as hierarchy of feature, with each of feature has a cardinality. The other notation to express variability within SPLE is Orthogonal Variability Model (OVM). At the other hand, OMG as standard organization makes an effort to build standard generic language to express the commonality and variability in SPL field, by initiate Common Variability Language (CVL). This paper reports the comparison and mapping of FODA, CBFM and OVM to CVL where need to be explored first to define meta model mapping of these several approaches. Furthermore, the comparison and mapping of those approaches are discussed in term of R3ST (read as “REST”) software feature model as the case study.

Study on Feature Modeling Based on Ontology

Feature-oriented domain analysis has become a more popular method for domain analysis today. However, feature model the main products of feature-oriented domain analysis method is very difficult to translate into the form of machine recognition. Moreover, it can't model detection. Feature model based on ontology can make up for these shortcomings, so this paper will study on feature modeling based on ontology. The main contents of this paper are: relationship between feature model and ontology, feature modeling framework based on ontology, the advantage and disadvantage of feature model based on ontology and general feature model.

A formal framework for software product lines

ContextA Software Product Line is a set of software systems that are built from a common set of features. These systems are developed in a prescribed way and they can be adapted to fit the needs of customers. Feature models specify the properties of the systems that are meaningful to customers. A semantics that models the feature level has the potential to support the automatic analysis of entire software product lines. ObjectiveThe objective of this paper is to define a formal framework for Software Product Lines. This framework needs to be general enough to provide a formal semantics for existing frameworks like FODA (Feature Oriented Domain Analysis), but also to be easily adaptable to new problems. MethodWe define an algebraic language, called SPLA, to describe Software Product Lines. We provide the semantics for the algebra in three different ways. The approach followed to give the semantics is inspired by the semantics of process algebras. First we define an operational semantics, next a denotational semantics, and finally an axiomatic semantics. We also have defined a representation of the algebra into propositional logic. ResultsWe prove that the three semantics are equivalent. We also show how FODA diagrams can be automatically translated into SPLA. Furthermore, we have developed our tool, called AT, that implements the formal framework presented in this paper. This tool uses a SAT-solver to check the satisfiability of an SPL. ConclusionThis paper defines a general formal framework for software product lines. We have defined three different semantics that are equivalent; this means that depending on the context we can choose the most convenient approach: operational, denotational or axiomatic. The framework is flexible enough because it is closely related to process algebras. Process algebras are a well-known paradigm for which many extensions have been defined.

An elementary theory of product-line variations

Abstract The primary aim of a software product-line is to maximise reuse of software components by managing the variability in component functionalities and product configurations. Feature oriented domain analysis (FODA) diagrams are a formalism for modelling the variability in a software product-line, and are used as a tool for managing a product-line and planning its evolution. This paper presents an elementary theory of variations in a product-line, leading up to a technique for extracting FODA diagrams from legacy product-lines. The theory is elementary in the sense that it is built using very simple mathematical structures, making minimal assumptions on the structure of product-lines. Examples drawn from the automotive domain are used to illustrate the theoretical developments.

Developers' social networks - tools analysis based on the 3Cs model

Social networks SNs have the potential to fundamentally change the nature of our social lives and interactions, both personally and at the community level. They affect the way people interact no matter who they are students, instructors, lawyers, programmers, or distributed developers, and no matter where they are co-located or geographically distributed. SNs can be either general purpose social networks GSNs that attract diverse audiences or specific purpose social networks SSNs dedicated to the interests of a group or a small community. This article focuses on a popular type of the specific purpose SNs which are the developers' social networks DSNs. This article defines social networks and developers' social networks. Also, it outlines social networks' evolution, and gives examples of existing social media tools and social networks targeted at developers and software development communities. It compares DSNs to GSNs, and bases its comparison on a new set of common metrics. Finally, it applies the feature-oriented domain analysis FODA and 3Cs collaboration model to classify and analyse the collaborative tools supported in DSNs.

Transformation from LEL to UML

Product Lines have emerged as a well-known approach for software reuse. Requirements of product line are organized into features in Feature Oriented Domain Analysis approach. Feature models are widely used to model the information gathered during domain analysis and it is not simply comprehensible to stakeholders. During the early stages of software development the interaction with stakeholders is mainly inconvenient. For this explanation, natural language (Language Extended Lexicon) is still widely used to model requirements information. It is in general understandable by stakeholders thus encouraging their participation but LEL does not provide design level of a system. To obtain design level of a system there is need to transform LEL symbols to UML class diagram as its elements are in abstract form representing blue print of a system. To achieve this transformation we describe in this paper a transformation process to derive a UML class diagram from natural language oriented requirement model, known as Language Extended. General Terms Language Extended Lexicon, UML class diagram, Feature Models

Constraints

Drawing from an analogy between features based Product Line (PL) models and Constraint Programming (CP), this paper explores the use of CP in the Domain Engineering and Application Engineering activities that are put in motion in a Product Line Engineering strategy. Specifying a PL as a constraint program instead of a feature model carries out two important qualities of CP: expressiveness and direct automation. On the one hand, variables in CP can take values over boolean, integer, real or even complex domains and not only boolean values as in most PL languages such as the Feature-Oriented Domain Analysis (FODA). Specifying boolean, arithmetic, symbolic and reified constraint, provides a power of expression that spans beyond that provided by the boolean dependencies in FODA models. On the other hand, PL models expressed as constraint programs can directly be executed and analyzed by off-the-shelf solvers. This paper explores the issues of (a) how to specify a PL model using CP, including in the presence of multi-model representation, (b) how to verify PL specifications, (c) how to specify configuration requirements, and (d) how to support the product configuration activity. Tests performed on a benchmark of 50 PL models show that the approach is efficient and scales up easily to very large and complex PL specifications.

Value Based Pricing in the Context of Software Product Line Engineering

The Feature Oriented Reuse Method (FORM), an successor of the famous Feature Oriented Domain Analysis (FODA) method, has broaden the focus of Product Line Engineering methodologies to business concerns, especially marketing. It uses the information gathered at the marketing and product planning steps to further improve the engineering of software product lines. A drawback of the FORM is, that it does not contribute much value to concerns directly related to the marketing, such as the price of a product, the management of licenses and the settlement of some features of a product of the product line. The paper is going to show a way to extend the FORM to additionally cover the whole set of features of the product line, which carrying value for the customer, not only the parts implemented by software - the functional requirements. Namely, it focuses on the introduction of economical aspects to the domain engineering. The specialization of the original FORM is called EconFORM. The specialization is introduced by formalizing the value based pricing approach of Nagle and Hogan to a process description. This description can than be used to be integrated into a Product Line Engineering approach such as FORM. A conclusion wraps the discussion up and raises questions for future research.

Evaluating formal properties of feature diagram languages

Feature diagrams (FDs) are a family of popular modelling languages, mainly used for managing variability in software product lines. FDs were first introduced by Kang et al. as part of the feature-oriented domain analysis (FODA) method back in 1990. Since then, various extensions of FODA FDs were devised to compensate for purported ambiguity and lack of precision and expressiveness. Recently, the authors surveyed these notations and provided them with a generic formal syntax and semantics, called free feature diagrams (FFDs). The authors also started investigating the comparative semantics of FFD with respect to other recent formalisations of FD languages. Those results were targeted at improving the quality of FD languages and making the comparison between them more objective. The previous results are recalled in a self-contained, better illustrated and better motivated fashion. Most importantly, a general method is presented for comparative semantics of FDs grounded in Harel and Rumpe's guidelines for defining formal visual languages and in Krogstie et al.'s semiotic quality framework. This method being actually applicable to other visual languages, FDs are also used as a language (re)engineering exemplar throughout the paper.

Generic semantics of feature diagrams

Feature Diagrams (FDs) are a family of popular modelling languages used to address the feature interaction problem, particularly in software product lines, FDs were first introduced by Kang as part of the FODA (Feature-Oriented Domain Analysis) method back in 1990. Afterwards, various extensions of FODA FDs were introduced to compensate for a purported ambiguity and lack of precision and expressiveness. However, they never received a formal semantics, which is the hallmark of precision and unambiguity and a prerequisite for efficient and safe tool automation. The reported work is intended to contribute a more rigorous approach to the definition, understanding, evaluation, selection and implementation of FD languages. First, we provide a survey of FD variants. Then, we give them a formal semantics, thanks to a generic construction that we call Free Feature Diagrams (FFDs). This demonstrates that FDs can be precise and unambiguous. This also defines their expressiveness. Many variants are expressively complete, and thus the endless quest for extensions actually cannot be justified by expressiveness. A finer notion is thus needed to compare these expressively complete languages. Two solutions are well-established: succinctness and embeddability, that express the naturalness of a language. We show that the expressively complete FDs fall into two succinctness classes, of which we of course recommend the most succinct. Among the succinct expressively complete languages, we suggest a new, simple one that is not harmfully redundant: Varied FD (VFD). Finally, we study the execution time that tools will need to solve useful problems in these languages.

Addressing quality attributes in domain analysis for product lines

Feature-oriented domain analysis (FODA) is a widely accepted domain analysis method for modelling common and variant requirements for product lines. Goal-oriented analysis, on the other hand, focuses on quality attribute (QA) analysis in single system development. To address QAs in the product line context, the authors extended FODA with concepts of goal-oriented analysis. Their integrated modelling framework improves the current state-of-the art of product line research and practice in two ways. Firstly, during the design of a product line architecture, the proposed framework allows developers to record design rationale in the form of interdependencies among variant features and QAs. Secondly, during system construction, the framework helps developers evaluate the impact of variant features selected for a target system on QAs of that system. In this way, developers and customers can come up with realistic overall requirements for the target system early, avoiding possible expensive rework in later stages of the software lifecycle. The proposed QA modelling framework is illustrated with examples from the computer aided dispatch domain.