27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

environment. Therefore, it is possible to deal with purpose<br />

for configuration files as functions of application. By relating<br />

purpose for configuration files and functions of application, it<br />

becomes possible to specify what combinations of setting item<br />

and parameter are required for execution of application.<br />

B. Errors of configuration files<br />

We focus on syntax error and semantic error of configuration<br />

files. Syntax error means that combinations of setting<br />

item and parameter are invalid, or dependencies between<br />

combinations are not satisfied. Semantic error means that<br />

configuration files do not meet requirements for configuration<br />

files. Factors of configuration file error are size and complexity<br />

of configuration files. Therefore, it is needed to solve these<br />

factors in order to make error-free configuration files.<br />

III. APPROACH<br />

We take an approach to manage variability of configuration<br />

files. Configuration files have variability in syntax and<br />

correspondence relations between requirements. Variability of<br />

syntax means combinations of setting item and candidate of<br />

parameter. Variability of correspondence relations between<br />

requirements and configuration files means that requirements<br />

also have variability and what combinations of setting item<br />

and parameter are required in order to perform requirement.<br />

Our approach consists of using a model and a consistency<br />

checking method. We propose configuration file model which<br />

organizes variability of configuration files. In particular, configuration<br />

file model represents candidates of combinations of<br />

setting item and parameter, constraints on making configuration<br />

files, requirements, and correspondence relations between<br />

requirements and configuration files. In order to check semantic<br />

error, we consider that requirements and correspondence<br />

relations between requirements and configuration files should<br />

be organized. Consistency checking method checks consistency<br />

between configuration file model and configuration files.<br />

Concept of our approach is shown in Fig. 1.<br />

use Alloy[1][4] in order to formalize and check the feature<br />

diagram. The details of configuration model and consistency<br />

checking method are shown in our previous work [9].<br />

IV. CONFIGURATION FILE MODEL<br />

A. Elements of configuration and relations<br />

Basic elements of configuration file model are setting item,<br />

parameter and requirement. Setting item and parameter are<br />

specific elements of each configuration file. Requirement is<br />

function of application. Requirement should be considered in<br />

order to specify what combination of setting item and parameter<br />

are described in a configuration file. Configuration file<br />

model includes following relations between basic elements.<br />

• Combination of setting item and parameter<br />

This combination shows valid candidates of parameter for<br />

each setting item.<br />

• Dependency between specific combinations of setting<br />

item and parameter<br />

This dependency shows that somecombinations of setting<br />

item and parameter may be required to describe other<br />

combination.<br />

• Relation between requirements<br />

This relation shows that some requirements may be<br />

required to perform other requirement.<br />

• Relation between requirement and combinations of setting<br />

item and parameter<br />

This relation shows candidates of combinations of setting<br />

item and parameter for execution of a requirement.<br />

The concept of configuration file model is shown in Fig. 2.<br />

Fig. 2.<br />

Concept of Configuration File Model<br />

Fig. 1.<br />

Approach of Our Method<br />

In order to clarify structure of configuration file model,<br />

configuration file model is described using the feature diagram<br />

[5] [3]. Requirements and configuration files are described by<br />

using the feature diagram. Correspondence relations between<br />

requirements and configuration files are described by correspondence<br />

relations between feature diagram of requirements<br />

and feature diagram of configuration files. In our method,<br />

a diagram that configuration file model is described by the<br />

feature diagram is called configuration model. Besides, we<br />

B. Definition of Configuration File Model<br />

The definition of configuration file model (CFM) is as<br />

follows.<br />

CFM =PN, PV, R, CR, Conf, Rel, RRel, Req<br />

The explanation of CFM is as follows. PN is set of names<br />

of setting item. PV is set of parameters. R is set of names of<br />

requirement. CR shows that what requirements are chosen by<br />

users or administrators for configuration file description. Conf<br />

means PN → 2 PV , and shows candidates of combination of<br />

setting item and parameter. Rel is subset of ( ( PN × PV )<br />

× (PN× PV ) ), and shows relations between combinations<br />

of setting item and parameter. RRel is subset of R × 2 R ,<br />

and shows relations between requirements. Req means R<br />

→ 2 (PN×PV) , and shows combinations of setting item and<br />

parameter that corresponding to a requirement.<br />

673

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!