<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Intentional Models based on Measurement Theory</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andre Rifaut</string-name>
          <email>andre.rifaut@tudor.lu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Public Research Centre Henri Tudor</institution>
          ,
          <addr-line>29, av. J. F.Kennedy, L-1855 Luxembourg-Kirchberg</addr-line>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2011</year>
      </pub-date>
      <fpage>144</fpage>
      <lpage>149</lpage>
      <abstract>
        <p>Metrics and measures have always been the subject of quite a lot of research works in the Requirements Engineering (RE) community, including about intentional models of Goal-Oriented RE (GORE) such as those of i*. However, using recent developments of the Measurement Theory, in this paper we show that the concept of Measurement Framework (MF) for soft-systems is useful for the analysis of business service systems that need long-term service agreements based on consistent measurements at all stages of their life-cycle (from inception to operation). We show that with two kinds of goals and softgoals based on MF, it is possible to improve (a) the elicitation of functional and non- functional requirements, (b) the structure of the i* models, and (c) the consistency between run-time measurements and the model-based assessments of business services at early stages of RE.</p>
      </abstract>
      <kwd-group>
        <kwd>goal-oriented requirements engineering</kwd>
        <kwd>measurement theory</kwd>
        <kwd>measurement framework</kwd>
        <kwd>business service</kwd>
        <kwd>service level management</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        IT based business systems are enablers to create business opportunities across
business entities boundaries that belong to complex business constellations. Being
able to analyze those opportunities contributed to the successful application of the
requirements engineering activities based on i*, in particular with the use of the
concepts and analysis techniques based on the Strategic Dependency Diagrams and
the Strategic Rationale Diagrams. However, for the business services, which are
means often used in those business constellations, agreements between the service
stakeholders (e.g. the service provider and the service client) must be faithful to what
actually happens during the service performance. This is why those agreements, often
called service-level agreements, must be based on empirically valid measurements. If
not, some party will assess negatively its business collaborations and can find other
business services offered on the market. Progress of our current research projects is
reported with an example of a case study followed in the Construction Sector [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>Section 2 motivates the objectives of the research in the context of GORE, before
presenting in Section 3 our method based on measurement frameworks (MF). We
conclude and explain future works in Section 4.</p>
      <p>Note that this paper uses some terminology of Measurement Theory that may
conflict with GORE terminology (e.g. about model-based evaluations).
As explained in the introduction, it is necessary to have consistent assessments of the
business services at the different stages of their life-cycle, from requirements
engineering to operation. Empirically valid measurements should be the basis of all
assessments used thorough the life-cycle of the business services.</p>
      <p>
        Recent developments in Measurement Theory for soft-systems can be used to
support the development of RE techniques in i* that focus on those empirically valid
measurements provided at run-time. Our aim is to provide RE support for complex
measurements having an empirical validity in the context of GORE for business
services. This aim has come up from needs identified during more than 6 years of
research in related contexts: RE for risk management [
        <xref ref-type="bibr" rid="ref11">12, 10</xref>
        ], RE for regulated
business [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and RE for business service management systems [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. In all three
aforementioned research contexts there is a negotiation process occurring between
stakeholders (business managers, IT service providers, auditors, regulators) and based
on empirically valid measurements of attributes of IT based business systems.
      </p>
    </sec>
    <sec id="sec-2">
      <title>3 Scientific contributions</title>
      <sec id="sec-2-1">
        <title>3.1 Measurement Theory</title>
        <p>
          Since long Measurement Theory [
          <xref ref-type="bibr" rid="ref12">13</xref>
          ] has formalized measurement concepts in the
context of the measurement of physical phenomena, such as the length of an object. In
short, measurement systems are composed of procedures and artifacts (e.g. a wood
yardstick) that can assign a measurement result, i.e. a time-varying or
timeindependent profile, (e.g. 11”) to an attribute (e.g. the length) of the target empirical
phenomena (e.g. a sheet of paper). The measurement process is a faithful
operationalization of the measurement model of the attributes. All this, called
measurement framework (MF), becomes more complex for the measurement of
“softsystems” [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] (to contrast with physical systems), such as organizational processes
(e.g. a set of business processes). In that context what is a measurement? Actually, it
is mainly the same: an empirically valid assignment of a value to an attribute of the
target system (e.g. a set of business process).
        </p>
        <p>The recent developments have pointed out three important characteristics of
measurements (see Fig. 1): measurements must be empirical, objective, and
intersubjective. Briefly, “empirical” means that the (empirical) attribute must be clearly
identified; “objective” indicates that the measurement model must respect all
(empirical) properties of the attribute (e.g. measured length must respect the size
ordering); and “inter-subjective” expresses the fact that the measurement model (and
scales) is a belief shared by everybody using (or referring to) the MF. All three
characteristics make a distinction between measures, evaluations, and preferences
(see Fig. 1). Measures and evaluations must be empirically validated. During RE
elicitation processes sometimes we have to model attributes of systems that are not
yet scientifically well understood. For instance, the usability attribute of IT
applications: do we have a precise definition of what “usability” is? Research is still
needed for validating empirical and objective measurements of usability. According
to the Fig. 1, if neither empirical, nor objective, a wide place for (implicit) preferences
is left in those models.</p>
        <p>This motivates us to define specific types of softgoals and goals: when their
description is complete, those types of goal and softgoals can be specified on the basis
of measurement frameworks. For those two specific types of goals and softgoals, a
distinction can be made between them: the fulfillment of a goal is measured, whereas
the fulfillment of a softgoal is evaluated. (For now on in this paper, we consider only
goals and softgoals of these types.)</p>
      </sec>
      <sec id="sec-2-2">
        <title>3.2 Practical uses of those measurement characteristics.</title>
        <p>
          Our research works present two methods: one [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ] for extracting and structuring
compliance (textual) requirements from regulation through the use of a MF and
another [
          <xref ref-type="bibr" rid="ref10">11</xref>
          ] for translating those requirements into rigorous requirements modeled in
i* also with the help of a MF. Two other works ([
          <xref ref-type="bibr" rid="ref4 ref6">6, 4</xref>
          ]) show how to derive
requirements when using MF.
        </p>
        <p>
          A partial view on the case study in the Construction Sector [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] is shown in Fig. 2.
At the top, is the model of a generic MF, ISO/IEC 15504 [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] defining the
measurement of assurance management of any business process in terms of its
purpose and outcomes (15504 terminology distinguishing softgoals from goals; 15504
indicators are not explained). Then, the middle part shows this generic MF that is
instantiated into a specific MF ([
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]) for assurance management of business services.
        </p>
        <p>Finally, at the bottom, both MF are instantiated to the specificities of the
collaborative work needed in construction projects, in this case, the sharing of documents and
expertise. The three horizontal lanes at the bottom separate the high-level strategic
diagram, the MF resulting from the instantiation of the two preceding MF and one
“solution” (at the very bottom). The actors and their dependencies are not shown. The
solution describes functional requirements that are derived from the measurement.
The evaluation procedure imposed by the MF rigorously structures the arguments of
the model-based assessments: see the shaded area on the evidences showing that the
goal “reactions time are monitored” of the MF (i.e. an outcome) will be fulfilled.</p>
        <p>Using goals and softgoals based on MF has practical consequences for RE
activities and requirements models. First, the measurement model of the MF provides
constructive insights to derive functional and non-functional requirements (see the
top and middle models). Second, our specific kind of goals and softgoals basically
imposes an expected measurement profile to the result of a MF that can be applied to
detailed requirements of alternatives solutions. This increases the structure of large i*
models respecting the separation of concerns of the different MF. This is sketched at
the bottom of the Fig. 2. The separation of concerns can be expressed with (a) the
attributes (and their MF); (b) the measurement profiles; (c) the solution (as
measurement target). Third, the MF provides a complete specification of a
measurement system that can be implemented and used at runtime for an objective
measurement of the fulfillment of goals and softgoals. (Those measurement systems
can also be used during operational tests.)
s
e
s
o
p
r
u
P
s
e
m
o
c
t
u
O
s
e
s
o
p
r
u
P
s
e
m
o
c
t
u
O
R
ieuq trSa i-hgH
rem teg Lve
ten ic le
s</p>
        <p>Fourth, the same measurement specifications can be used for creating the
arguments of model-based assessments of the fulfillment of goals and softgoals as
explained in Sec. 3.1. (Measurements are made at run-time, whereas model-based
assessments provide expected measurement results.) However, when carefully made
the results of the assessments will be consistent with the results of the measurements.
(Those model-based assessments can also be used for model-based simulations.)</p>
        <p>As seen in the example, the design method is based on the insertion of soft-system
measurements between the strategic goals and the solutions. This creates a valid
relationship between the (elicited) measurement profiles and alternatives of functional
(and also non-functional) requirements. For a bottom-up design process it is possible
to collect arguments and evidences from the analyzed solution and derive the
measurement results of the model-based evaluation defined by the MF. For a
topdown elicitation, measurement results of model-based evaluations can be imposed in
order to derive the requirements on the basis of refinement patterns (cfr. KAOS by A.
van Lamsweerde) or strategies (cfr. MAP by C.Rolland) that generate alternative
solutions (not shown). For instance, concerning monitoring activities (outcome 2.1.3),
in the selected measurement profile the monitored activities can include the sharing of
documents and exclude the sharing of expertise. The advantage of this design method
is to benefit from the constructive insights given by the MF of the soft-systems.</p>
      </sec>
      <sec id="sec-2-3">
        <title>3.3 Discussion.</title>
        <p>
          In recent overviews [
          <xref ref-type="bibr" rid="ref1 ref7">1, 7</xref>
          ] of the model-based techniques for assessing GORE models,
nothing is said about the empiricity and objectivity of the measurements used. Those
three aspects are independent of any category of statements used in RE (functional/
non-functional; requirement/assumption; belief/desire/intention; “precise”/“vague”
statements, etc.). For each statement of the requirements model, the importance level
of each three aspects depends on its use during the life-cycle of the “system to-be”:
indeed, those aspects must be compatible with the measurements methods used in
analyses or assessments needed from early requirements activities to system
operation. For instance, what is the level of the three aspects in the annotations of models
elements with qualitative/quantitative values and their propagation/aggregation?
Softsystems measurements [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] are built on top of indicators linked to goals/softgoals with
the aim to strengthen the validity of the same links found in software engineering or
business process improvement methods, or in RE models ([
          <xref ref-type="bibr" rid="ref1 ref7">1, 7</xref>
          ]).
        </p>
        <p>Using the same MF for requirements analysis and for defining the specifications of
the measurement system and method, and for performing the actual measurements
during system operation, this provides a greater consistency between the argument
structure used in the requirements model, and the argument structure used at run-time.</p>
      </sec>
      <sec id="sec-2-4">
        <title>4 Conclusions, Ongoing and future work</title>
        <p>
          In this paper we have shown that the recent developments of Measurement Theory
adapted to GORE methods, in particular i*, gives a sound basis for an interesting type
of goals and softgoals to guide the elicitation and analysis of functional and
nonfunctional requirements of business services. To benefit from the scientific knowledge
of a number of MF defined, improved and validated by the scientific community
(often using social sciences research techniques), the efficiency of the proposed
methods should be improved by providing tools supporting (a) the import of
measurements frameworks into a knowledge base, (b) the definition of refinement
patterns and strategies needed by the elicitation activities, (c) the assessment of the
requirements models [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] on the basis of the measurements frameworks. (This last
issue is similar to other engineering domains.) Ontology-based Software Engineering
and Multi-Criteria Decision Theory provide techniques that depart from searching
solutions to hard problems (e.g. searching inconsistent scenarios or plans), but aim at
classifying and characterizing solutions of under-constrained problems that often
occur in very early requirements engineering (see e.g DDP by M.S. Feather).
Acknowledgments. This work is supported by the project MOTIVATE of the
National Research Fund, Luxembourg.
        </p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Horkoff</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mussbacher</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Peyton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E..:</given-names>
          </string-name>
          <article-title>Evaluating Goal Models within the Goal-Oriented Requirement Language</article-title>
          ,
          <source>International Journal of Intelligent Systems</source>
          , Vol.
          <volume>25</volume>
          , pp.
          <fpage>841</fpage>
          -
          <lpage>877</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Barafort</surname>
          </string-name>
          et al.:
          <article-title>ITSM Process Assessment Supporting ITIL (TIPA</article-title>
          ), van Haren Publishing, Zaltbommel, The Netherland,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Di Renzo</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hillairet</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Picard</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rifaut</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bernard</surname>
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hagen</surname>
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reinard</surname>
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Operational risk management in financial institutions - Process assessment in concordance with Basel II</article-title>
          .
          <source>Software Process: Improvement and Practice</source>
          <volume>12</volume>
          (
          <issue>4</issue>
          ):
          <fpage>321</fpage>
          -
          <lpage>330</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Dubois</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kubicki</surname>
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ramel</surname>
            <given-names>S.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Rifaut</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Capturing and Aligning Assurance Requirements for Business Services Systems</article-title>
          ,
          <source>International Workshop on Business System Management and Engineering</source>
          . June 28, (
          <year>2010</year>
          ).
          <source>Málaga (Spain).</source>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Finkelstein</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Widely, strongly and weakly defined measurement</article-title>
          ,
          <source>Measurement</source>
          <volume>34</volume>
          (
          <year>2003</year>
          ), Elsevier, pp.
          <fpage>39</fpage>
          -
          <lpage>48</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Grandry</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dubois</surname>
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Picard</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rifaut</surname>
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Managing the Alignment between Business and Software Services Requirements from a Capability Model Perspective</article-title>
          .
          <source>ServiceWave</source>
          (
          <year>2008</year>
          ):
          <fpage>171</fpage>
          -
          <lpage>182</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Horkoff</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <article-title>Analysing goal models: different approaches and how to choose among them</article-title>
          ,
          <source>SAC</source>
          <year>2011</year>
          ;
          <fpage>675</fpage>
          -
          <lpage>682</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. ISO, ISO/IEC 15504: Information Technology - Process
          <source>Assessment: Part1 to 5</source>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Rifaut</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Goal-Driven Requirements Engineering for Supporting the ISO 15504 Assessment Process</article-title>
          ,
          <source>LNCS 3792, Proc. Int. Conf. EUROSPI</source>
          , Budapest, Hungary. (
          <year>2005</year>
          )
          <fpage>10</fpage>
          .
          <string-name>
            <surname>Rifaut</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Picard</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Di</surname>
          </string-name>
          Renzo B.:
          <article-title>ISO/IEC 15504 Process Improvement to Support Basel II Compliance of Operational Risk Management in Financial Institutions</article-title>
          .
          <source>In: Proc. Conf. SPICE</source>
          <year>2006</year>
          ,
          <string-name>
            <surname>Luxembourg</surname>
          </string-name>
          (
          <year>2006</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          11.
          <string-name>
            <surname>Rifaut</surname>
            <given-names>A</given-names>
          </string-name>
          and
          <string-name>
            <surname>Dubois</surname>
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>Using Goal-Oriented Requirements Engineering for Improving the Quality of ISO/IEC 15504 based Compliance Assessment Frameworks:</article-title>
          <source>In Proc. IEEE Intl. Conf. On Requirements Engineering</source>
          , Barcelona, IEEE Press (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          12.
          <string-name>
            <surname>Rifaut</surname>
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Di Renzo</surname>
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Picard</surname>
            <given-names>M.</given-names>
          </string-name>
          : ISO/IEC 15504,
          <article-title>a Basis for Generally Accepted Sound Process Models in Financial Institutions: A Case Study about Venture Capital Fund Management</article-title>
          .
          <source>In: Proc. Conf. SPICE</source>
          <year>2008</year>
          , Nuremberg, (
          <year>2008</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          13.
          <string-name>
            <surname>Rossi</surname>
          </string-name>
          , G.:
          <article-title>On some key concepts and terms in measurement having a cross-disciplinary impact</article-title>
          ,
          <source>12th IMEKO TC1 &amp; TC7 Joint Symposium on Man Science &amp; Measurement, September</source>
          ,
          <fpage>3</fpage>
          -
          <lpage>5</lpage>
          ,
          <year>2008</year>
          , Annecy, France
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>