<!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>Towards Applying the Normalized Systems Theory to IT Infrastructure Systems</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Antwerp University</institution>
          ,
          <addr-line>Antwerp</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The agile enterprise requires evolvability at all layers - business, application and infrastructure. IT infrastructure systems are the foundations of IT systems in general. Their evolution has a profound impact on applications and business capabilities. Normalized Systems Theory (NS) provides a method to evaluate the evolvability of modular systems. As IT infrastructure systems can be represented by a modular structure, NS can be used to study their evolvability. An artefact is being proposed, made up of a 4-step method and summary table, to study the evolvability of a modular system representing an IT infrastructure system by means of NS. Although the artefact has been successfully applied to some IT infrastructure systems and as such demonstrating NS can be applied to IT infrastructure systems, the 4-step method requires re nement and a more rigorous translation of the NS theorems into IT infrastructure equivalents. Further research on the subject is being proposed.</p>
      </abstract>
      <kwd-group>
        <kwd>IT infrastructure systems</kwd>
        <kwd>Normalized Systems</kwd>
        <kwd>modularity</kwd>
        <kwd>evolvability</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        The agile and morphogenic enterprise [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] requires the capability to cope with
constant change. Business organization, processes, applications and
infrastructure need to cope with the required agility.
      </p>
      <p>
        No application will run without IT infrastructure. IT infrastructure components
such as CPU, memory, operating system, are the bare necessities to run any
application. Changes and evolutions in the IT infrastructure can lead to serious
Combinatorial E ects - hidden coupling or dependencies in a system which
increase with the size of the system inducing a ripple e ect throughout the whole
IT landscape and breaking other IT infrastructure components, applications and
even business processes. Architecting and constructing IT infrastructure systems
which are resilient to those changes and have proven evolvability, are as
important as the creation of applications and business processes which have proven
1 Copyright by the paper's authors. Copying permitted for private and academic
purposes. In: Aveiro et al. (Eds.): Proceedings of the EEWC Forum 2017, Antwerp,
Belgium, 09-May-2017 to 11-May-2017, published at http://ceur-ws.org
evolvability. They are an integral part of the agile and morphogenic enterprise.
Normalized Systems (NS) ( see [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]) provides theorems to evaluate the
evolvability of modular structures. Using design science, a 4-step method has
been worked out to apply the NS theorems to a modular representation of an IT
infrastructure system. The artefact has been applied to several IT infrastructure
systems, demonstrating the feasibility to apply NS on IT infrastructure systems.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2 Proposal</title>
      <p>
        Design science identi es a method, a step approach to address a problem, as a
valid artefact to apply to a problem (see [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ],[
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]). Applying the NS theorems
to an IT Infrastructure system has been translated into a method to check the
compliance of a relevant modular representation of an IT infrastructure system
with the 4 NS theorems, being:
      </p>
      <sec id="sec-2-1">
        <title>1. SoC : Separation of Concerns 2. SoS : Separation of State 3. VT : Version Transparency 4. IT : Instance Traceability</title>
      </sec>
      <sec id="sec-2-2">
        <title>The proposed artefact contains the following steps:</title>
        <p>{ Step 1: Create a relevant modular representation of the IT Infrastructure
system.
{ Step 2: For each module of the modular representation look for manifestations
of Concern, State, Version and Instance.
{ Step 3: Check if the manifestations found in Step 2 are compliant with the 4</p>
        <p>NS principles.
{ Step 4: If there is non-compliance with one or more of the 4 NS principles,
describe related Combinatorial E ects (CE).</p>
        <p>The results of the 4 steps can be represented in the following summary table:
The artefact can also be used in the opposite direction, meaning that based
on observed Combinatorial E ects (CE), the violation of one or more of the NS
principles can be identi ed and this violation can be associated to a
manifestation of Concern, State, Version and Instance in a module representing a function
and/or construction component of an IT infrastructure system.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Evaluation</title>
      <p>
        In [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] the artefact has been applied on 3 IT infrastructure systems, being
Housing (data center setup), Hosting (server hardware and an Operating System)
and Proxy (network proxy for N to 1 outbound network tra c). For Housing,
Hosting and Proxy, respectively 3 (Housing 1.0, 2.0 and 3.0), 2 (Hosting 1.0
and 2.0) and 1 implementation patterns have been investigated, resulting in 6
e ective use cases on which the artefact has been applied.
      </p>
      <p>
        These 6 use cases have been evaluated by an expert team (13 members) which
represent the Knowledge Base in the Design Science framework of Paul
Johannesson and Erik Perjons [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The expert team has been requested to evaluate
the correctness of the used IT infrastructure modular structure (step 1 for each
of the 6 uses cases), the correctness of the analyses (steps 2 to 4 for each of the
6 uses cases), and score the relevance of the artefact (did it provide additional
insight for each of the 6 uses cases). The results can be found in Fig 2.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4 Conclusion and further research</title>
      <p>The previous section shows that the proposed artefact can be used to apply NS
on IT infrastructure system, and can thus be used to test evolvability of the IT
infrastructure system. However, the di erent steps of the artefact method do
require extensive knowledge of the IT infrastructure system under investigation
and a good understanding of what the manifestations of Concern, State, Version
and Instance may look like in the IT infrastructure system.</p>
      <p>Further research is required to create a standardized meta model which can be
used to make a modular representation of an IT infrastructure system. A deeper
understanding of the meaning of Concern, State, Version and Instance in an
IT infrastructure system needs to be further investigated. Based on this deeper
understanding, the transformation of the 4 NS theorems into applicable
Normalized Infrastructure Systems Theorems (NIST) can be created. The current
artefact summary table must be improved by having a standardized way to
describe manifestations of Concern, State, Version, Instance and the description
of the CE. The proposed artefact improvements will lead to a more systematic
approach in applying the artefact.</p>
      <p>Once a transformation of the 4 NT theorems into applicable Normalized
Infrastructure Systems Theorems (NIST) is available, the research can shift
towards using those as input for an expander which will, based on a standardized
functional description of an IT infrastructure system, expand code which can
be deployed on a Software De ned Infrastructure Platform (like AWS, Azure,
Google), resulting in deployable and evolvable IT infrastructure systems.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Jan</surname>
            <given-names>A.P.</given-names>
          </string-name>
          <string-name>
            <surname>Hoogervorst - Enterprise Governance</surname>
          </string-name>
          and Enterprise Engineering - 2009
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>Herwing</given-names>
            <surname>Mannaert</surname>
          </string-name>
          ,
          <source>Jan Verelst - Normalized Systems - 2009</source>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Herwig</given-names>
            <surname>Mannaert</surname>
          </string-name>
          , Jan Verelst,
          <string-name>
            <surname>Peter De Bruyn - Normalized Systems</surname>
          </string-name>
          Theory:
          <article-title>From Foundations for Evolvable Software Toward a General Theory for Evolvable Design - 2016</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Herwig</given-names>
            <surname>Mannaert</surname>
          </string-name>
          , Jan Verelst,
          <article-title>Kris Ven - The transformation of requirements into software primitives: Studying evolvability based on systems theoretic stability - Science of Computer Programming</article-title>
          : Volume
          <volume>76</volume>
          , Issue 12 pp.
          <fpage>1210</fpage>
          ...1222 -
          <lpage>2011</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Herwig</given-names>
            <surname>Mannaert</surname>
          </string-name>
          , Jan Verelst,
          <source>Kris Ven - Towards evolvable software architectures based on systems theoretic stability - Software Practice and Experience:</source>
          Volume
          <volume>42</volume>
          , Issue 1, pp.
          <fpage>89</fpage>
          ...16 -
          <lpage>2012</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>Paul</given-names>
            <surname>Johannesson</surname>
          </string-name>
          , Erik Perjons - An Introduction to Design Science - 2014
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Hevner</surname>
            ,
            <given-names>A. R.</given-names>
          </string-name>
          and
          <string-name>
            <surname>March</surname>
          </string-name>
          , S. T. and
          <string-name>
            <surname>Park</surname>
          </string-name>
          , J. and
          <string-name>
            <surname>Ram</surname>
          </string-name>
          , S. - Design
          <source>Science in Information Systems Research - MIS Quarterly:</source>
          Volume
          <volume>38</volume>
          , Issue 1 pp.
          <fpage>75</fpage>
          ..105 -
          <lpage>2004</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Pe ers,
          <string-name>
            <given-names>K.</given-names>
            and
            <surname>Tuunanen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            and
            <surname>Rothenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.A.</given-names>
            and
            <surname>Chatterjee</surname>
          </string-name>
          ,
          <source>S. - A Design Science Research Methodology for Information Systems Research - Journal of Management Information Systems: Volume 24, Issue</source>
          <volume>3</volume>
          , pp.
          <fpage>45</fpage>
          ..77 -
          <lpage>2007</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Geert</given-names>
            <surname>Haerens - Master Thesis</surname>
          </string-name>
          :
          <article-title>Applying the Generalized Normalized Systems Theory to the Engie IT Reference Architecture Library - 2016</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>