<!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>ISO 16355 in Software-Intensive Business</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Felix Schönhofen</string-name>
          <email>felix.schoenhofen@bwi.uni-stuttgart.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sixten Schockert</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Georg Herzwurm</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Graduate School of Excellence advanced Manufacturing Engineering (GSaME)</institution>
          ,
          <addr-line>Stuttgart</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Stuttgart, Chair of Information Systems II (Software-Intensive Business)</institution>
          ,
          <addr-line>Stuttgart</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2018</year>
      </pub-date>
      <fpage>158</fpage>
      <lpage>163</lpage>
      <abstract>
        <p>The Software-Intensive Business represents a shift from value creation in development of new products to a trend towards cross-industry enterprise networks and collaboration, including almost every industry. This also has an impact on the entire development process of products and services as it will be even more important to understand the real customer's demand. ISO 16355 is a standard based on Quality Function Deployment (QFD) for converting fuzzy customer needs into more-specific functional requirements. This research-in-progress paper examines the question of how ISO 16355 can be potentially used to support the development of new Software-Intensive Products and Business models.</p>
      </abstract>
      <kwd-group>
        <kwd>Software-Intensive Business</kwd>
        <kwd>ISO 16355</kwd>
        <kwd>Software-Product-Service Systems</kwd>
        <kwd>Business Models</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Almost across all industries, the Software-Intensive Business represents a shift from
value creation in development, production and marketing of monolithic products to a
trend towards cross-industry enterprise networks and collaboration [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. So-called
Cyber-Physical-Systems open the door to the digital world, originally reserved mainly
for pure software companies, even for manufacturing industry producing goods that are
more tangible. Digital and analogue markets converge. The atomization of products and
services, e.g. as bundled microservices instead of apps, raises the number of products
and services and their providers. Thus, the strategy of offering only single products for
more or less one or few nearly homogenous types of customers is outdated and replaced
by hybrid product bundles offered on multi-sided markets. Platforms enable
cooperation (i.e. development and sales) of the value creation partners. The digitization is
leading to a sustainable change towards a common platform economy offering a huge
potential for innovative business models, creating and satisfying customer needs for
business success.
      </p>
      <p>
        For this new field of research a group of international selected researchers
established during a Dagstuhl seminar in May 2018 a new scientific discipline called
Software-Intensive Business (SIB) [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. SIB studies organizational arrangements within
and between organizations in conjunction with methods and tools for value creation,
capture, and delivery based on digital products and services [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. By analyzing the
Dagstuhl report, several challenges in Software-Intensive Business can be identified. We
have arranged them in Table 1 according to their main areas they affect within SIB: the
technical system (i.e. the cyber-physical system itself), the human/personnel side and
the ecosystem connecting different partners.
      </p>
      <p>
        From an economical point of view, companies try to take an advantage of this
changed situation by developing new disruptive products and services based on these
new possibilities. However, a product or product-service-bundle can only be effective
if it is able to serve real customer needs. Moreover, in order to guide the companies’
efforts towards a constantly evolving and sustainable business, it is essential to really
understand the potential customer needs. Not until this learning process is well
established, companies are able to benefit from the new solution space in an innovative and
promising way [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
2
      </p>
      <p>
        ISO 16355
The ISO 16355 offers a kit of methods and tools to assure customer or stakeholder
satisfaction by identifying their most important needs. It represents a quality approach,
whose main purpose is to establish a defined and repeatable product development
process, based on definable targets, the involvement of all relevant customers and
stakeholders and the focus on their real needs. ISO 16355 can be used independently of the
domain or industry and has been successfully applied for hardware, service and
software development [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. As cyber-physical systems usually combine all three of these
aspects as Industrial Software-Product-Service bundles [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], ISO 16355 has the
potential to offer a toolset for the SIB domain. Thus, this paper poses the question of how
ISO 16355 can be used to support the development of new Software-Intensive Products
and Business Models.
ISO 16355 is based on a set of six main principles [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]:
a) Prioritize information to focus
b) Understand how to cause good quality
c) Listen to the voice of the customer
d) Observe the customers situation
e) Capture information from other sources
f) Improve internal communications through the transformation of information
between perspectives
      </p>
      <p>
        Obviously, these six main principles address several different aspects. The principles
b)-e) seem to be distinct approaches to elicit the real customer needs. You can elaborate
them by listening, observing, analyzing and/or considering preferably all possible
sources. Accordingly, we summarize them as “Focusing on customer/stakeholder
needs”. The ISO 16355 recommends tools like User Personae and Gemba visits in this
area [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        Principle a) is about a more methodical approach to handle the captured information.
Customers pay the most for solutions to their most important problems. Thus, it is
essential to prioritize the information obtained from the customer/stakeholders according
to customer value. We deduce the second cluster “Prioritization” using e.g. tools like
the Analytic Hierarchy Process and the Kano model [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>Lastly, we have to take a closer look on principle f): Compared with the clusters we
concluded before, this principle deals not (only) with the contact to the external
stakeholders like the customers or partners. It is about the internal communications in
particular. There is a gaining in importance about this factor, especially in the context of
Software-Product-Service systems in Software-Intensive Business: There is a need to
synchronize all development areas and teams and – moreover – to generate mutual
understanding to improve the collaboration. So, the third cluster we worked out is
“Collaboration”. ISO 16355 suggests the joint building of cause-and-effect diagrams and
Lmatrices like the House of Quality in this area</p>
      <p>Figure 1 gives an overview of the identified ISO 16355 clusters adding some
examples of tools mentioned in ISO 16355.
In order to evaluate the general fit of ISO 16355 with Software-Intensive Business, we
compare the ISO 16355 - clusters composed of its main principles and corresponding
tools (Figure 1) with the challenges in Software-Intensive Business extracted from the
Dagstuhl report (Table 1).</p>
      <p>
        Regarding the first two entries in the first column, one have to consider concepts like
the Minimal Viable Product: In case there are little resources regarding time and
capacity, you have to focus on the really important requirements to satisfy the early users
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Apart from the general need to know the customer needs, it is essential to
understand which of them are the very most important ones regarding the customer
satisfaction and – based on this – to prioritize these top needs.
      </p>
      <p>Regarding data ownership the actors have to find a compromise between privacy and
need for data to solve the customers’ problem. Up to now, it is not possible to give a
“perfect answer” to this challenge, but at least you can say that a lot of communication
and collaboration could help to generate a trustful environment. This positive
environment should also be helpful to build a common sense of all development areas in the
CPS to make system integration smoother. Eventually, prioritization and collaboration
seem to be the most significant principles regarding the area of cyber-physical systems.</p>
      <p>The lack of knowledge is critical concerning the human aspects within SIB. The
mutual understanding of engineering and business benefit from communication and
collaboration. In a perceived uncertain and disruptive environment, the focus on the
solution-independent real customer needs can solve as a landmark. Nevertheless,
enterprises have to develop a positive attitude towards making change, not seldom even
requiring a bigger mind shift. Thus again, there is a need for intense collaboration and
communication.</p>
      <p>This positive attitude towards change is also required in the Ecosystem area:
potentially unwilling partners in the ecosystem have to be persuaded. An ecosystem-wide
change management, based on smoothly collaboration can serve as a solution. When
attempting to establish an ecosystem, it is important to subsidize one side of the market.
To accomplish this effectively, it is necessary to understand the needs of the
corresponding market side.</p>
      <p>Finally, one main problem field in the ecosystem research is the increased need for
coordination. ISO 16355’s cluster of collaboration is obviously needed for that. Table
2 gives an overview of the SIB challenges and the corresponding main clusters of ISO
16355.
As shown in this paper, the ISO 16355 and the field of Software-Intensive business
share very much the same spirit. The main challenges in SIB and the main clusters of
ISO 16355 overlap quite well.</p>
      <p>However, as an ongoing research project, this paper represents only the starting point
of a more in-depth analysis regarding the application of ISO 16355 in
Software-Intensive Business. Most likely, the tools of ISO 16355 have to be enhanced and tailored to
cope with the identified challenges in Software-Intensive Business. Due to its high
importance within SIB, especially the collaboration side seems to need more in-depth
analysis.</p>
      <p>
        In order to develop an approach within the paradigm of customer centricity [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] to
create innovative Software-Product-Service systems in the Software-Intensive
Business, the identified clusters of ISO 16355 have to be concretized. The result could be a
conceptual framework of ISO 16355 for Software-Intensive Business consisting of
three levels: the main principles/clusters, the conceptual/methodological approach (e.g.
focusing on dealing with fuzzy development tasks in an incremental procedure), and
detailed tools/instruments (e.g. incorporating tools for creativity management) [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Acatech (eds).:
          <string-name>
            <surname>Cyber-Physical Systems</surname>
          </string-name>
          . Innovationsmotoren für Mobilität, Gesundheit, Energie und Produktion. Heidelberg (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Brinkkemper</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abrahamsson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Maedche</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bosch</surname>
            ,
            <given-names>J</given-names>
          </string-name>
          . (eds.): Software Business, Platforms, and
          <article-title>Ecosystems: Fundamentals of Software Production Research</article-title>
          . In: Dagstuhl Reports,
          <volume>1</volume>
          ,
          <fpage>1</fpage>
          -
          <lpage>31</lpage>
          (to be published).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Herzwurm</surname>
          </string-name>
          , G.:
          <article-title>Research approach and strategy - Research of the Chair of Information Systems II of the University of Stuttgart</article-title>
          . https://www.bwi.uni-stuttgart.de/en/dept8/researchapproach-strategy/index.html,
          <source>last accessed</source>
          <year>2018</year>
          /10/05.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Bosch</surname>
          </string-name>
          , J.:
          <article-title>Transforming to a Software Business</article-title>
          , In: Dagstuhl Reports,
          <volume>1</volume>
          ,
          <fpage>5</fpage>
          -
          <lpage>6</lpage>
          (to be published).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bussler</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          : Innovation +
          <article-title>Velocity + Pivoting in software production: The new normal</article-title>
          .
          <source>In: Dagstuhl Reports</source>
          ,
          <volume>1</volume>
          ,
          <fpage>6</fpage>
          -
          <lpage>7</lpage>
          (to be published).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Sztipanovits</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Koutsoukos</surname>
            ,
            <given-names>X.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Karsai</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kottenstette</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Antsaklis</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goodwine</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baras</surname>
          </string-name>
          , J. und
          <string-name>
            <surname>Wang</surname>
          </string-name>
          ,
          <source>S. In: Proceedings of the IEEE</source>
          ,
          <volume>1</volume>
          (
          <issue>100</issue>
          ),
          <fpage>29</fpage>
          -
          <lpage>44</lpage>
          (
          <year>2012</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Mikusz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Cyber-Physical Systems as Service Systems: Implications for S-D Logic</article-title>
          .
          <source>In: The 2015 Naples Forum on Service</source>
          ,
          <fpage>1</fpage>
          -
          <lpage>19</lpage>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Schönhofen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petrik</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schockert</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herzwurm</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Analysis of platform-based Business Models using Quality Function Deployment</article-title>
          .
          <source>In: Proceedings of the 23rd International QFD Symposium</source>
          , ISQFD, Tokyo (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. ISO 16355-
          <article-title>1: Application of statistical and related methods ti new technology and product development process - Part 1: General Principles and Perspectives of Quality Function Deployment (QFD)</article-title>
          .
          <source>ISO 16355-1</source>
          :
          <fpage>2015</fpage>
          ,
          <string-name>
            <surname>Genf</surname>
          </string-name>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Mikusz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Towards an Understanding of Cyber-Physical Systems as Industrial SoftwareProduct-Service Systems</article-title>
          . In:
          <string-name>
            <surname>Procedia</surname>
            <given-names>CIRP</given-names>
          </string-name>
          ,
          <volume>16</volume>
          ,
          <fpage>385</fpage>
          -
          <lpage>289</lpage>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Patton</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>User Story Mapping: Discover the whole Story. Build the right product</article-title>
          .
          <source>O'Reilly and Associates</source>
          ,
          <string-name>
            <surname>Sabastopol</surname>
          </string-name>
          (
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Herzwurm</surname>
          </string-name>
          , G.:
          <article-title>Position Statement</article-title>
          .
          <source>In: Dagstuhl Reports</source>
          ,
          <volume>1</volume>
          , 12 (to be published).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Schönhofen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schockert</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herzwurm</surname>
          </string-name>
          , G.:
          <article-title>Towards a QFD approach for Software-Intensive Business</article-title>
          .
          <source>In: Proceedings of the 24th International Symposium on Quality Function Deployment ISQFD</source>
          <year>2018</year>
          ,
          <volume>144</volume>
          -
          <fpage>149</fpage>
          ,
          <string-name>
            <given-names>Hong</given-names>
            <surname>Kong</surname>
          </string-name>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>