<!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>Beyond De-Facto Standards for Designing Human-Computer Interactions in Configurators</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Patrick Heymans</string-name>
          <email>patrick.heymans@unamur.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Jean-Marc Davril University of Namur Belgium</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <country>Maxime Cordy Skalup Belgium</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Tony Leclercq University of Namur Belgium</institution>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Namur Belgium</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2016</year>
      </pub-date>
      <fpage>21</fpage>
      <lpage>24</lpage>
      <abstract>
        <p>A web configurator is an application that allows its users to tailor a customizable product to their own needs by specifying their requirements through a graphical user interface. Configurators have been successfully applied to tangible products (e.g., cars, mobile phones) as well as intangible products like software (e.g., operating systems, ERPs) and services (e.g., insurance). A configurator user faces multiple decisions until she has addressed all the characteristics to be retained in the final product. In order to enable users to make the right decisions, with as low effort as possible, HCIs in configurators must be thoughtfully designed. Researchers have previously identified guidelines for HCI design by conducting empirical studies of existing configurators. In this vision paper we propose to draw HCI guidelines through a different approach, which consists in framing theories from the HCI community into the context of configuration models.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>ACM Classification Keywords</title>
      <p>H.5.2 [Information Interfaces and Presentation: User
Interfaces]: graphical user interfaces (GUI), standardization.</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <p>In many sectors, companies rely more and more on
masscustomization strategies with the aim of providing their
customers with products that meet their individual needs.
When growing their distribution at large scales, these
companies have to create product lines of highly variant
solutions. This shift from mass production of identical products
to mass customization of variant products has brought to
light important technological challenges related to sales
processes as it has become essential to help customers
determine their own products. To this end, companies often
rely on web configurators, which provide automated support
for customizing products. Configurators offer a controlled
environment that allow their users to gradually specify the
characteristics to be retained in the final product.
Configurators and recommender systems (RS) can be seen
as similar technologies as they both aim at helping their
users navigate large solution spaces. While the solution
space of a RS is made of a set of items, the solution space
of a configurator is defined by the set of all possible product
variants that can be derived through the configuration
process. From the customerâA˘ Z´s perspective, navigating the
solution space of an RS consists in browsing through the
different items, whereas within a configurator it consists in
selecting the characteristics that will eventually define the
final product. For both types of systems, it is crucial for HCIs
to be carefully designed so that the solution search is both
effective and efficient.</p>
      <p>
        Configurators often have to cope with many product
characteristics and components, as well as business rules and
technical constraints. This complexity can create a
decrease in customer value as users become exposed to an
overwhelming set of configuration choices to resolve.
Complex co-design processes can make vendors undesirable for
customers [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. It can also cause users to miss the product
that best suits their needs as they shift towards simplifying
decision heuristics [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. For these reasons, HCIs must be
carefully designed and should provide users with clear
explanations about the configuration task by using a language
that fit their cognitive expectations.
      </p>
      <p>In this vision paper, we focus on the need for guidelines to
help practitioners evaluate the quality of HCIs in
configurators. In Section 2, we show that previous works related
to this issue primarily consist in empirical studies of
existing systems. In Section 3, we discuss a new approach for
assessing the quality of HCIs in configurators, which is
embedded in theories from the field of HCI. Finally we propose
three research questions we plan to address in future work
to realize our vision.</p>
    </sec>
    <sec id="sec-3">
      <title>State of the Art</title>
      <p>
        Rogoll et al. [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] offer a comparison of twelve configurators
from the apparel industry in terms of usability and product
visualization. The authors aim at illustrating good and bad
practices in the design of configurators.
      </p>
      <p>
        Abbasi et al. [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] have conducted an empirical study of 111
web configurators coming from 21 different industrial
sectors reported in the Cyledge database1. The authors report
quantitative empirical results related to good and bad
practices in the design of HCIs, focusing on aspects that may
directly affect the end-user experience by causing
confusion, waste of time and errors.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] Rabiser et al. identify eight evaluation criteria, which
they refer to as user-guidance capabilities, through a
literature review on product derivation support in configurators.
The authors discuss the eight capabilities within the HCI
framework of cognitive dimensions of notations [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. They
then review how the DOPLER CW, a configuration tool,
supports these capabilities by analyzing the results of user
interviews.
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] Randall et al. analyze five principles to be taken into
account when designing user interfaces for configurators in
order to improve usability: (1) customize the customization
process, (2) provide starting points, (3) support incremental
refinement, (4) exploit prototypes to avoid surprises and (5)
teach the customer.
      </p>
    </sec>
    <sec id="sec-4">
      <title>Research Challenges</title>
      <p>
        Beyond De-Facto Standards
The existing work presented in Section 2 primarily relies on
empirical studies of existing configurators to identify good
and bad practices in HCI design. In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] Nielsen and
Loranger define de-facto standards as web elements that are
similarly designed on 80-100% of all websites. Streichsbier
et al. [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] have already put the usefulness of de-facto
standards for configurators into questions, as they observed a
lack of consistency in the use of web elements in
configurators. Even though their study focuses on particular types
of web elements and took place in 2009, when
configurators might not have been characterized as a widespread
technology, it still raises the question of whether alternative
approaches could bring valuable support to the design of
HCIs. We argue that methodologies other than inquiries for
de-facto standards remain under-explored.
      </p>
      <p>
        Towards Model-Based Evaluation
According to Junker [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], a configuration task can be defined
by (1) the functional and technical properties of the product
and the relationships between them, and (2) the user
requirements regarding the functional properties. These
constituents form the configuration model, which specifies the
set of all possible final products. More specifically, it defines
the set of all possible sequences of configuration choices
a user can make before she reaches a valid final product.
In other words, when engineers work on the acquisition of
domain knowledge and write down the configuration model,
they are specifying all the different ways a user can
navigate the solution space.
      </p>
      <p>On the other hand, HCIs allow users to communicate their
configuration choices to the system, and are thus the mean
by which users navigate the solution space. HCIs can be
seen as the interface through which users can relate to the
configuration model. This idea leads us to question whether
recommending practitioners with concrete HCI designs
based on particular patterns found in configuration models
can be a viable approach.</p>
      <p>The idea of inferring design guidelines from the properties
of configuration models will require to understand how the
available domain-specific knowledge should be taken into
consideration in design decisions.</p>
      <p>In order to investigate these ideas, instead of performing
crossdomain studies of existing configurators, we propose
to frame relevant HCI theories in the context of both
configuration modeling and domain-driven design. To this end, we
plan to address the following research questions through
future work:
RQ1 How should domain specific knowledge drive the
evaluation of configurator HCIs?
RQ2 Which theories from the field of HCI should be
considered for inquiring HCI design recommendations
based on the properties of configuration models?
RQ3 What are the types of tools that could assist
practitioners in assessing the enforcement of the elicited
recommendations?</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Ebrahim</given-names>
            <surname>Khalil</surname>
          </string-name>
          <string-name>
            <surname>Abbasi</surname>
          </string-name>
          , Arnaud Hubaux, Mathieu Acher, Quentin Boucher, and
          <string-name>
            <given-names>Patrick</given-names>
            <surname>Heymans</surname>
          </string-name>
          .
          <year>2013</year>
          .
          <article-title>The anatomy of a sales configurator: An empirical study of 111 cases</article-title>
          .
          <source>In International Conference on Advanced Information Systems Engineering</source>
          . Springer,
          <fpage>162</fpage>
          -
          <lpage>177</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Alan</given-names>
            <surname>Blackwell</surname>
          </string-name>
          and
          <string-name>
            <given-names>Thomas</given-names>
            <surname>Green</surname>
          </string-name>
          .
          <year>2003</year>
          .
          <article-title>Notational systems-the cognitive dimensions of notations framework</article-title>
          .
          <source>HCI Models</source>
          , Theories, and
          <article-title>Frameworks: Toward an Interdisciplinary Science</article-title>
          . Morgan Kaufmann (
          <year>2003</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Benedict</surname>
            <given-names>GC</given-names>
          </string-name>
          <string-name>
            <surname>Dellaert and Stefan Stremersch</surname>
          </string-name>
          .
          <year>2005</year>
          .
          <article-title>Marketing mass-customized products: Striking a balance between utility and complexity</article-title>
          .
          <source>Journal of Marketing Research</source>
          <volume>42</volume>
          ,
          <issue>2</issue>
          (
          <year>2005</year>
          ),
          <fpage>219</fpage>
          -
          <lpage>227</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Nikolaus</given-names>
            <surname>Franke</surname>
          </string-name>
          and
          <string-name>
            <given-names>Martin</given-names>
            <surname>Schreier</surname>
          </string-name>
          .
          <year>2010</year>
          .
          <article-title>Why Customers Value Self-Designed Products: The Importance of Process Effort and Enjoyment</article-title>
          .
          <source>Journal of Product Innovation Management</source>
          <volume>27</volume>
          ,
          <issue>7</issue>
          (
          <year>2010</year>
          ),
          <fpage>1020</fpage>
          -
          <lpage>1031</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Ulrich</given-names>
            <surname>Junker</surname>
          </string-name>
          . Configuration.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Jakob</given-names>
            <surname>Nielsen</surname>
          </string-name>
          and
          <string-name>
            <given-names>Hoa</given-names>
            <surname>Loranger</surname>
          </string-name>
          .
          <year>2006</year>
          .
          <article-title>Prioritizing web usability</article-title>
          .
          <source>Pearson Education.</source>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Rick</given-names>
            <surname>Rabiser</surname>
          </string-name>
          , Paul Grünbacher, and
          <string-name>
            <given-names>Martin</given-names>
            <surname>Lehofer</surname>
          </string-name>
          .
          <year>2012</year>
          .
          <article-title>A qualitative study on user guidance capabilities in product configuration tools</article-title>
          .
          <source>In Proceedings of ASE '12. IEEE</source>
          ,
          <fpage>110</fpage>
          -
          <lpage>119</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>Taylor</given-names>
            <surname>Randall</surname>
          </string-name>
          , Christian Terwiesch, and
          <string-name>
            <surname>Karl T Ulrich</surname>
          </string-name>
          .
          <year>2005</year>
          .
          <article-title>Principles for user design of customized products</article-title>
          .
          <source>California Management Review</source>
          <volume>47</volume>
          ,
          <issue>4</issue>
          (
          <year>2005</year>
          ),
          <fpage>68</fpage>
          -
          <lpage>85</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Timm</given-names>
            <surname>Rogoll</surname>
          </string-name>
          and
          <string-name>
            <given-names>Frank</given-names>
            <surname>Piller</surname>
          </string-name>
          .
          <year>2004</year>
          .
          <article-title>Product configuration from the customerâ A˘ Z´s perspective: A comparison of configuration systems in the apparel industry</article-title>
          .
          <source>In International Conference on Economic, Technical and Organisational aspects of Product Configuration Systems</source>
          , Denmark. Citeseer.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>Clarissa</given-names>
            <surname>Streichsbier</surname>
          </string-name>
          , Paul Blazek, Fabian Faltin, and
          <string-name>
            <given-names>Wolfgang</given-names>
            <surname>Fruhwirt</surname>
          </string-name>
          .
          <year>2009</year>
          .
          <article-title>Are de-facto standards a useful guide for designing human-computer interaction processes? The case of user interface design for web based B2C product configurators</article-title>
          .
          <source>In System Sciences</source>
          ,
          <year>2009</year>
          . HICSS'
          <volume>09</volume>
          . 42nd Hawaii International Conference on.
          <source>IEEE</source>
          , 1-
          <fpage>7</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>