<!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>From Unknown to Known Impacts of Organizational Changes on Socio-technical Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Marília Guterres Ferreira</string-name>
          <email>mferreira@inf.puc-rio.br</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Neil Maiden</string-name>
          <email>n.a.m.maiden@city.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Julio Cesar Sampaio do Prado Leite</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>City University London</institution>
          ,
          <addr-line>London</addr-line>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Pontifícia Universidade Católica do Rio de Janeiro (PUC-Rio)</institution>
          ,
          <addr-line>Rio de Janeiro</addr-line>
          ,
          <country country="BR">Brasil</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2015</year>
      </pub-date>
      <volume>978</volume>
      <fpage>31</fpage>
      <lpage>36</lpage>
      <abstract>
        <p>Keeping organizations and their Socio-technical System (STS) aligned over time is a complex endeavour. We believe understanding the organizational dynamics of changes, and of the impacts these changes will have, can support the evolution of STSs. Reasoning on the organizational changes in advance also supports the development of an STS more likely to be aligned to the dynamics of the organization. This work presents the design and the application of a Dynamic Organizational Framework (DOF), constituted of a dynamic organizational model (DOM) on which to base the reasoning, a database of questions (DBQ) to explore possible organizational impacts, and a method to reason on changes and impacts within goal models. We apply this framework to analyse the impacts of the introduction of a system into the customers' attendance process in a Post Office in London. First results show contributions towards to the awareness about the organization, and to the quality and accuracy of requirements.</p>
      </abstract>
      <kwd-group>
        <kwd>Socio-technical systems</kwd>
        <kwd>Software Evolution</kwd>
        <kwd>Requirements Engineering</kwd>
        <kwd>Organizational Model</kwd>
        <kwd>Organizational Alignment</kwd>
        <kwd>Goal Modelling</kwd>
        <kwd>Goal Analysis</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        In order to enhance their performance in a rapidly changing environment,
organizations continuously change, frequently, guided by strategic management plans. In this
setting, organizational change creates new requirements for the deployed
sociotechnical system (STS), which, in turn, may also change the organization [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Over
time, an STS presents inconsistencies and lack of compliance with new
environmental requirements in which it was deployed, i.e. activities and business processes
through which the organization intends to generate value; in other words, its business
strategy. This lack of compliance is due to unforeseen impacts and demands the
evolution of the STS which is a difficult, complex, costly, and time-consuming process.
Our research aims to support stakeholders and organizational analysts in
understanding likely organizational impacts of proposed organizational changes, as strategic
changes, and then gain insights and reasoning on the impacts of these changes on the
Copyright © 2015 for this paper by its authors. Copying permitted for private and
academic purposes.
STS’ requirements evolution. Therefore we propose a Dynamic Organizational
Framework (DOF) constituted of a sequence of procedures supported by a Dynamic
Organizational Model (DOM), to understand organizational flow of impacts, and by a
Database of Questions (DBQ), to elicit knowledge from organizational analysts.
These techniques are meant to be used on information acquisition within the context
of goal and scenario modelling. We use goal-oriented requirements engineering,
specifically the i* framework, because it is suitable for modelling and analysis in
requirements engineering, then we can model and understand stakeholders’ underlying
motivations for systems, identify the relation between the system and the
organizational and business context, clarify and capture organizational changes, impacts and
requirements from the analysis [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        In order to augment our knowledge, we also apply scenario walkthroughs into the
organizational impacts to analyse and capture requirements. The idea behind these
impact scenarios walkthroughs is that people are better at identifying facts of
commission rather than omission. From this, impact scenario walkthroughs offer
stakeholders support to think about most likely impacts of organizational changes. If the
identified impact is relevant to the system being specified but not yet handled in the
specification, then a potential requirement change has been identified, and it is
suggested to the developers to acquire and document the relevant requirements [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>The Dynamic Organizational Framework</title>
      <p>
        A project introduces a new STS (the designed thing) into the organization (the
environment) and this introduction generates impact on the organization. Thus, the
Dynamic Organizational Framework aims to support the elicitation of organizational
changes and reasoning about potential impacts on and from both the organizational
and the STS. Hence, it is constituted of a sequence of activities assisted by a Dynamic
Organizational Model (DOM) and by a Database of Questions (DBQ). These support
tools were developed through extensive literature review, application in real cases and
recurrent refinements, summarized as follows. First, to understand the flow of
changes and impacts in organizations, we initially must understand the organization
itself. Hence, we based our model on Jay Galbraith’s Star Model, the most
widelyused and accepted organizational design framework [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. This model relies on the
following five dimensions of an organization: Strategy: determines the direction of the
organization; Structure: defines the placement of power and authority in the
organization, the location of decision-making power; Processes: outlines the flow of
information, cut across an organization structure and determines its functioning; Rewards:
influences the motivation of people to perform and address organizational goals;
People: defines and influences the employees’ mind-sets and skills to implement the
company’s chosen direction. Through exploratory literature review and applications
in real experiences, we identified elements for each of the five ends of the Star Model.
The resulting first version of the organizational model, then formed by organizational
dimensions and respective elements, was used as a base in a workshop to discuss
organizational changes brought up by a Learning Management System in a University.
Copyright © 2015 for this paper by its authors. Copying permitted for private and
academic purposes.
Data from the workshop showed a flow of changes and impacts within organizational
dimensions and the consequent need to incorporate organizational dynamics in the
model.
      </p>
      <p>
        Therefore, we conflated our model to the Configuration Model of Organizational
Culture (CMOC) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], making the necessary amendments. Besides dynamic
relationships, the CMOC also maps interactions from the organization with the external
environment, which demanded more research on their respective elements. Our final
DOM is depicted in Fig. 1. Now, each organizational dimension is connected by flow
of impacts (arrows left-to-right) and flow of adjustments (arrows right-to-left).
      </p>
      <p>BASIC
UNDERLYING
ASSUMPTIONS</p>
      <p>Invisible,
unconscious</p>
      <sec id="sec-2-1">
        <title>Culture</title>
        <p>Values
Beliefs</p>
        <p>Feelings
Assumptions
Symbols</p>
        <p>Myths
Ideologies</p>
        <sec id="sec-2-1-1">
          <title>Guidance</title>
          <p>In order to elicit knowledge from the stakeholders about organizational changes
and impacts, we constructed a database consisting of 88 questions (DBQ). These
questions are grounded on the organizational elements and organized in 10 sets,
corresponding to the 5 flows of impacts (arrows left-to-right in Fig. 1) and to the 5 flows of
adjustments (arrows right-to-left in Fig. 1) within the organizational dimensions. For
example, consider the generic organizational change “Sell new product X”. First we
identify the organizational dimension which better fits it: this is a new Strategy and by
it, we start our flow of reasoning according to the flow of impacts on the dimension
Copyright © 2015 for this paper by its authors. Copying permitted for private and
academic purposes.
Structure. For that, we apply questions from the set: Operationalization. One of the
questions is: “What new processes are needed to implement this new strategy?”.
Possible answer: “Sell product X”. Then, flow of impacts on Operations, set Patterns of</p>
        </sec>
        <sec id="sec-2-1-2">
          <title>Behaviours: “What are the activities needed to this new process?”, answer: definition</title>
          <p>of specific activities. Following, flow of impacts on Stakeholders, set Legitimacy</p>
        </sec>
        <sec id="sec-2-1-3">
          <title>Management: “What skills are needed from the employees closer to the change?”,</title>
          <p>identification of necessary skills. Now, we can start a flow of adjustments, regarding
the findings. Set: Cultural Pressure: “What operational adjustments are needed to
satisfy employees’ goals?”. Flow of adjustment, set Performance Assessment: “How
does the new functions relate to existing functions?”. And so on.</p>
          <p>We summarized the procedure steps of the DOF as follows:
1. Stimulating Organizational Awareness: to boost organizational awareness,
requirements engineers and organizational analysts model the As Is and start
modelling the To Be contexts using i*.</p>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>2. Identification of organizational changes: From the comparisons between the</title>
        <p>models, the participants identify the organizational changes (new elements in the
To Be models) between the two contexts.</p>
        <p>For each organizational change (new element):
3. Identification of the type of change: (i) Participants decide on one change (new
element); (ii) Using the DOM, participants chose one organizational dimension
that better represents the change (strategic, structural, operational, related to
people, related to market, or cultural);</p>
      </sec>
      <sec id="sec-2-3">
        <title>4. Identification of the flow of reasoning to follow: in order to stimulate a natural</title>
        <p>flow of reasoning, for each change participants can choose from either the flow of
impacts or the flow of adjustment, according to their own insights regarding the
DOM.
5. Identification of impacts: (i) According to the type of change and to the chosen
flow of reasoning, participants use the questions from the matching set in the DBQ
to identify the likely organizational impacts. (ii) When necessary, to facilitate the
reasoning of the participants, they construct As Is and To Be scenarios of key use
cases of the future system corresponding to the previously identified organizational
change. (iii) By (vertically) walking through the scenarios, once identified changes
between them, participants (horizontally) apply the questions, annotate the
organizational changes (the answers of the questions) and the organizational impacts
following the flow of reasoning they came
up.</p>
      </sec>
      <sec id="sec-2-4">
        <title>6. Identification of requirements</title>
        <p>changes: then, from the identification
of likely organizational impacts,
participants analyse the possible impacts
on the STS’ requirements.</p>
        <p>The procedure ends when analysts are
satisfied with the exploration of likely
impacts. The flow of reasoning can follow
unlimited flows of impacts and flow of adjustments since one change may bring
infinite impacts in different organizational dimensions. The last version of the DOF was
applied in a real case of organizational change occurred in a Post Office in London,
and the method of application is as follows: we present the As Is SR model in Fig. 2
and the To Be in Fig. 3. A summarized flow of reasoning is illustrated in Table 1.</p>
        <p>By the end of the study of the Post Office case, the authors identified 18 main
changes, explored 6 different flows of impacts, and identified 51 possible
organizational changes and consequent 40 STS’ requirements changes, which if implemented
correctly, will minimise undesirable effects of the impacts. The abstraction level of
the requirements varied, for example, we found a need for entire software to support
new services, as “Post and Go”, and we pointed 10 different specific indicators to be
extracted from data gathered by the STS. As the DOF is based on the participant’s
reasoning, the results and flows of impacts diverse from participant to participant,
since it is a representation of the perceptions of the person to whom the DOF is being
applied.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>
        In this paper we presented our Dynamic Organizational Framework (DOF) to elicit
and reason about organizational changes and impacts within goal models and scenario
Copyright © 2015 for this paper by its authors. Copying permitted for private and
academic purposes.
walkthroughs so that stakeholders can analyse the consequent impacts on STS
requirements. First results show contributions towards requirements quality and
accuracy; it brings a better understanding of organizational dimensions, elements and
impacts of organizational changes, contributes to organizational learning and
consequently enables the development of more powerful STS. In the future, we are going to
validate this proposal in other cases; make a thorough comparison with related
researches [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]; extend the model to address impacts on external organizations; develop
a tool to support the DOF; study creative techniques to boost thinking about impacts;
and apply the DOF to analyse the relationship between Software Transparency and
Power Dynamics in Organizations.
      </p>
      <p>How does this
Patterns of structure relate to
Behaviour the objectives of
the system?
Is any activity</p>
      <p>needed?
Is any activity</p>
      <p>needed?
Patterns of
Behaviour
Patterns of
Behaviour
Single-loop
learning</p>
      <p>Organizational</p>
      <p>Answer
i*
Controls attendance of
customers by counter
staff (Be served ||
counter reached)
The customer should
wait for counter call
The customer should
monitor for ticket and
counter number</p>
      <p>Impact</p>
      <p>Requirement
New
goal
(2)
New task</p>
      <p>(3)
New task
(4)</p>
      <p>N. A.</p>
      <p>STS shall call the
customer by number.</p>
      <p>STS shall print the
ticket with the queue
number accurately.</p>
      <p>Impact Scenarios Walkthrough (continuation)</p>
      <p>Total amount of Now it is STS shall calculate the
snDterouwecstoutrhrgeiasbnnriieznawg- ..c[sudesratvyoe|mmdeoornnst:hc|oyuenatre]r. pcoosntsotirbolle
.tt[oodtmaalyera|msm:oonutnht|yoefarc]u.stional measures? ..ubusiynigngseprrvoicdeusc.ts. thqoeufeftulhoeew. ...subeusriynviegndgseoprnrvoiccdoeuuscn.ttse.r</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Sousa</surname>
            ,
            <given-names>H. P.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Leite</surname>
            ,
            <given-names>J. S.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Modeling Organizational Alignment</article-title>
          . In S. I. Publishing (Ed.),
          <string-name>
            <surname>Conceptual</surname>
            <given-names>Modeling</given-names>
          </string-name>
          , (pp.
          <fpage>407</fpage>
          -
          <lpage>414</lpage>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Horkoff</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Interactive goal model analysis for early requirements engineering</article-title>
          . Requirements Engineering, (pp.
          <fpage>1</fpage>
          -
          <lpage>33</lpage>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Alexander</surname>
            ,
            <given-names>I. F.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Maiden</surname>
          </string-name>
          , N. (Eds.). (
          <year>2005</year>
          ). Scenarios, Stories, Use Cases:
          <article-title>Through the Systems Development Life-Cycle</article-title>
          . John Wiley &amp; Sons Inc.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Jay</surname>
            ,
            <given-names>R. G.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <article-title>Designing the customer-centric organization: A guide to strategy, structure, and process</article-title>
          . John Wiley &amp; Sons.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Dauber</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gerhard</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Yolles</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          (
          <year>2012</year>
          ).
          <article-title>A Configuration Model of Organizational Culture</article-title>
          .
          <source>SAGE Open 2.1 DOI: 10.1177/2158244012441482</source>
          ,
          <fpage>1</fpage>
          -
          <lpage>16</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Danesh</surname>
            ,
            <given-names>M. H.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Yu</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Architecting Enterprise Capabilities: Creating Dynamic Capabilities from IT and Software Architecture</article-title>
          .
          <source>Seventh International i* Workshop</source>
          . 1157. CEUR.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>