<!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>Methodology to design management accounting information systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>S V Mkrtychev</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Togliatti State University</institution>
          ,
          <addr-line>14 Belorusskaya St., Togliatti, 445020</addr-line>
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <fpage>21</fpage>
      <lpage>28</lpage>
      <abstract>
        <p>The paper considers a methodology to design management accounting information systems (MAIS) based on the object-structured approach, which is an integration of ontological, automata and object-oriented approaches. The phases and stages of the proposed methodology are described. The UML design patterns utilized in this methodology are created drawing on technological ontology classes formalized with the use of the automata approach. This ensures the easy adaptation of MAIS to the specifics of managerial accounting and to the business processes workflow of a particular organization. The main advantage of this methodology is a possibility to implement a management strategy for organization's operational activities already at the stage of designing corresponding problem-oriented control systems through the development of a design patterns set with specified properties. The use of MAIS designed on the base of proposed methodology at the enterprises of textile and woodworking industries provides high efficiency of multi-stage manufacturing control.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>2. Background</title>
      <p>
        In modern practice of the MAIS design, at the stage of conceptual modeling, preference is given to the
Business Process Modeling (BPM) methodologies [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. The result of this modeling process is a
conceptual model that is a structural-functional (informal) description of MAIS.
      </p>
      <p>
        It should be noted that for a conceptual representation of MAIS, in addition to an informative
description, it is necessary to use more formalized models, for the creation of which it is recommended
to utilize methodologies based on Petri networks [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>
        However, these methodologies do not allow to fully reveal the features of managerial accounting in
complex production systems, since “the focus is on a clear and unambiguous specification of the
process and not on particular analysis technique” [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>
        To solve this problem, it is recommended to utilize UML design patterns at the stage of MAIS
logical modeling [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>
        As practice shows, preference should be given to native patterns reflecting the abstractions of the
studied subject area and connections between them, for identification of which modeling
methodologies based on the ontological approach are used [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>
        Thus, for the modeling of accounting information systems, the “Resources - Events - Agents”
(REA) ontology is used, which describes the accounting system as a virtual representation of the real
business process [
        <xref ref-type="bibr" rid="ref11">11, 12</xref>
        ].
      </p>
      <p>The advantages of the REA model include the easy conversion to a conceptual model of a MAIS
relational database (entity-relationship model), which makes this ontology successful for modeling
business processes in modern ERP-systems [13, 14].</p>
      <p>However, despite the fact that the philosophy of REA draws on the idea of reusable design
patterns, there is a problem of identification and formalization of the objects represented by REA
concepts within the scope of the subject domain [15].</p>
      <p>This limits the possibility of utilizing the REA ontology in modeling of MAIS for enterprises with
a strong specificity of manufacturing process.</p>
    </sec>
    <sec id="sec-2">
      <title>3. Solution approach</title>
      <p>To solve the described problem, I propose to utilize an object-structured approach to design MAIS.</p>
      <p>In [16] an object-structured analysis methodology is considered, the principles of which are based
on an ontology-driven approach representing the enhancement of a classical structured analysis
methodology for knowledge engineering.</p>
      <p>In [17] an approach to configuring MAIS for multi-stage production is described. This approach is
based on the presentation of a multi-stage production system in the form of an object-structured
model, the elements of which are virtual heirs to the following basic classes of the technological
ontology:



</p>
      <p>Class “Aggregate”, the objects of which change the state of a material flow element (raw
materials, production, document, et al.).</p>
      <p>Class “Warehouse”, the objects of which store material flow elements and register their
movement within a production process.</p>
      <p>Class “Controller”, the objects of which monitor the status of a material flow element and
control its movement within a production process.</p>
      <p>Class “Stage”, the objects of which are combinations of the above-described classes (for
example, "Warehouse-Aggregate-Warehouse").</p>
      <p>The rules for the above object classes behavior are determined by transaction axioms of the
enterprise ontology [18] and the rules for conducting managerial accounting in a particular
organization.</p>
      <p>Business processes are managed based on an event-driven principle with the adjustment to changes
in the status of the processing element of material or information flow.</p>
      <p>This model can be presented in the form of a directed graph and can be described quite simply
using an incidence matrix or an array [19].</p>
      <p>The physical implementation of the object-structured model of MAIS is a transaction of the
OLTPsystem that provides information processing during the production process.</p>
      <p>The advantage of MAIS object-structured models is the universality that is provided through their
isomorphism.</p>
      <p>Taking into account the well-known propositions of isomorphism and invariants of directed graphs
[20], the following statement of object-structured models isomorphism is proposed: the
objectstructured models of MAIS are isomorphic if the graphs of the models are isomorphic, and there exists
a bijection between the ontological classes, the heirs to which are objects denoting nodes and arcs of
object-structured models graphs.</p>
      <p>Thus, isomorphism verification for object-structured models of MAIS for similar business
processes is reduced to comparing the objects properties that are designated by the corresponding
elements of the graphs of the compared models as to their belonging to the same class of the
technological ontology.</p>
      <p>The concept of the object-structured approach proposed in this article is based on the integration of
ontological, automata and object-oriented approaches and seems more promising for modeling of
problem-oriented MAIS.</p>
    </sec>
    <sec id="sec-3">
      <title>4. Design methodology</title>
      <p>The MAIS design methodology consists of the following phases.</p>
      <sec id="sec-3-1">
        <title>4.1. Object-structured modeling</title>
        <p>Figure 1 shows an object-structured model for the system of N-stage processing of accounting
information.</p>
        <p>W = {W1, W2} – nodes denoting the objects of the “Warehouse” class.</p>
        <p>S = {S1, S2,..., SN} – a set of nodes denoting the objects of the “Stage” class.</p>
        <p>D = {D1, D2,..., DN+1} – a set of arcs loaded with the elements of information flow.</p>
        <p>The mathematical description of such a model can be represented as ordered arrays of the
following form:</p>
        <p>MW : array [1..2] of CW, MS : array [1..N] of CS and MD : array [1..N+1] of CD, where:
CW, CS, CD – the data types that determine the subsets of the indicators values, with which the
nodes or arcs of the graph are loaded, respectively (for example, item balances, statuses or movements
of goods or documents in warehouses and stages of the technological process).</p>
        <p>Array element indices are the numbers of nodes or arcs in a graph.</p>
      </sec>
      <sec id="sec-3-2">
        <title>4.2. Formalization of the elements of the object-structured model</title>
        <p>To formalize the elements of the object-structured model of MAIS, an automata approach is used [21].</p>
        <p>This approach is a variation of a process-oriented approach and is a representation of the
objectstructured model of MAIS as a system of interacting automata controlling the status of the processed
element of the material (information) flow, which is described as a finite-state automaton in
accordance with its life cycle.</p>
        <p>Table 1 presents an example of a product life cycle in a multi-stage production system.</p>
        <p>Status
1
2
3</p>
        <p>Description</p>
        <p>Raw material
Semi-finished product</p>
        <p>Finished product</p>
        <p>It should be noted that the automaton approach is not related to the specification of the UML
notation, which significantly limits its capabilities for creating design patterns and logical modeling of
MAIS.</p>
        <p>In [22] a method for designing operations of state-dependent object classes with the use of a UML
statechart diagram is proposed.</p>
        <p>The essence of this method can be described as follows: at the stage of designing a class based on a
finite-state automaton, the actions of the statechart diagram of the automaton, as a rule, are mapped
onto operations of the designed class.</p>
        <p>Thus, the statechart diagram of a finite automaton shows the actions and activities initiated as a
result of the transition of its states. In this case, it is meant that the actions, as a rule, are displayed on
the operation of the class.</p>
        <p>However, this method does not answer the question of how the properties of ontological classes are
related throughout the automata representations with the properties of the object classes created on
their basis.</p>
        <p>To solve this problem, in the proposed design methodology, object representations for the elements
of the object-structured model are created using the transformation of the automaton set-theoretic
description into the specifications of a UML class diagram.</p>
        <p>Let R be an automaton formalizing an element of the object-structured model of a MAIS.</p>
        <p>Then, the transformation of the set-theoretic description of the automaton R to the object model M
of the object-structured model MAIS element can be described as follows:</p>
      </sec>
      <sec id="sec-3-3">
        <title>M (NCO, SА, SO) → Ψ(R(NTO, ATO, VR)), where:</title>
        <p>


</p>
        <p>NTO - the name of the technological ontology class, the heir to which is an element of the
object-structured model.</p>
        <p>ATO – a set of attributes of the technological ontology class describing the state of the
automaton R (shown in Table 2).</p>
        <p>VR = (Nv, Lv) – functionality of the automaton R, where:
Nv – names of automata functions.</p>
        <p>Lv – the descriptions of algorithms that realize the automata functions, examples of which are
presented in Table 3.
Ψ – an operator transforming the elements of the automaton set-theoretic description into an
object model (presented in Table 4).
Controller</p>
        <p>Attribute
Item balance</p>
        <p>Item status
Item status control result</p>
        <p>Automaton
Warehouse
Aggregate
Controller</p>
        <p>Function name
Receipt/Expense the Item</p>
        <p>Change the Item Status
Control the Item Status</p>
        <p>Transition algorithm
Recalculating the item balance
Changing the status of the item
Controlling the status of the item</p>
      </sec>
      <sec id="sec-3-4">
        <title>4.3. Development of UML design patterns</title>
        <p>At this phase, the object models of the same type elements of the MAIS object-structured model are
integrated into groups with common classes of the technological ontology, based on which the design
patterns in the UML notation are created.</p>
        <p>The created patterns, at the stage of logical modeling, are utilized as superclasses to build
inheritance object models that are used to develop a relational data model and business logic of MAIS.</p>
        <p>Figure 2 illustrates design patterns of MAIS for multi-stage manufacturing.</p>
        <p>It should be noted that the utilization of the superclass concept at the stage of logical modeling of
the MAIS provides a stable model for the inheritance of the objects involved in the system - heirs to
the corresponding ontological class.</p>
        <p>Preference should be given to the superclasses, on the basis of which ready-made design patterns
will be created [23].</p>
        <p>It is also very important to pay attention to the principle of function interoperability for operations
of the selected object group and the used superclass.</p>
        <p>Otherwise, you should create both a new superclass, and a design pattern based on it.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>5. Advantages of the proposed methodology</title>
      <p>Advantages of the proposed methodology are:
5.1. Easy adaptation of MAIS object-structured models to the specifics of managerial accounting in a
particular organization.
This advantage is achieved due to the possibility of adapting the object-structured approach to the
features of the subject domain by modifying basic ontological classes or creating new ones.</p>
      <p>Thus, drawing on basic ontological classes of the technical ontology, ontological classes for the
MAIS design for operational insurance activities were developed [24]:




“Insurance Document” - an active document involved in the operational business process
(insurance policy, claim form, et al.).
“Insurance Operator” – a subclass of “Aggregate” representing a person involved in the
processing of insurance documents (agent, claims adjuster).
“Insurance Inspector” – a subclass of “Controller” representing a person who provides control
of insurance documents or the identification of potential risks and decision-making on whether
to accept or reject an application (underwriter, claims inspector).
“Insurance Portfolio” – a subclass of “Warehouse” representing a repository of insurance
documents (portfolio of the insured, portfolio of the insurer).</p>
      <p>Figure 3 shows examples of design patterns models and MAIS objects inheritance models for
operational insurance activities.</p>
      <p>It should also be noted that the use of polymorphic operations in design patterns provides flexibility
of reconfiguring the properties of inherited objects and, consequently, the easy adaptation of
objectstructured models to the specifics of the managerial accounting of a particular organization.
5.2. Easy integration of MAIS into EIS of an organization.</p>
      <p>It is important to note that MAIS objects, as a specialized component of the organization's EIS, should
be present in their representation also as a database and business logic objects (for example, in the EIS
of manufacturing enterprises these are directories of warehouses, aggregates, routes of technological
processes, etc.; in the EIS of insurance companies - directories of insurance agents, customers, data
accumulation registers, etc.).</p>
      <p>Thus, at the stage of physical modeling, the ease of the MAIS integration is achieved by the
building of its server modules on the EIS platform, for example, by adding the objects and connections
to its database structure, which are needed to support the required functionality and to ensure strong
database normalization.</p>
    </sec>
    <sec id="sec-5">
      <title>6. Conclusion</title>
      <p>The paper considers a design methodology for MAIS based on an object-structured approach.</p>
      <p>The integration of ontological, automata and object-oriented approaches within the
objectstructured approach allows us to expand its methodological possibilities to design effective MAIS.</p>
      <p>The main advantage of this methodology is a possibility to implement a management strategy for
organization’s operational activities already at the stage of designing corresponding problem-oriented
control systems through the development of a design patterns set with specified properties.</p>
      <p>Due to universality of the object-structured model used in the approach, MAIS is easily adapted to
the specifics of managerial accounting in a particular organization and to the integration into its EIS.</p>
      <p>Thus, based on the proposed methodology, a configuration of MAIS for multi-stage manufacturing
on the platform “1C: Enterprise 8.x” has been implemented. Utilizing virtual warehouses in MAIS as
real storage locations allowed us to increase the accuracy of calculations for normative production
losses and to organize managerial accounting thereof with the reference to individual stages of the
technological process. The use of this MAIS at the enterprises of textile and woodworking industries
provided high efficiency of multi-stage manufacturing control.</p>
      <p>The proposed methodology can be used to design MAIS in socio-economic organizations, for
instance, for multi-stage production systems and insurance activities.
[12] Geerts G and McCarthy W 2002 An ontological analysis of the economic primitives of the
extended-REA enterprise information architecture Int. J. of Acc. Inf. Sys. 3 (1) pp 1–16.
[13] Romney M and Steinbart P 2009 Accounting information system 11th ed Pearson International</p>
      <p>Editions
[14] Fallon R and Polovina S 2013 REA Analysis of SAP HCM; Some Initial Findings Proc. of the
3rd CUBIST Workshop p 31
[15] Hrby P 2006 Model-Driven Design Using Business Patterns (Berlin: Springer)
[16] Gavrilova T, Kurochkin M and Veremiev V 2004 Teaching Strategies and Ontologies for
Elearning Int. J. Inf. Theor. and App. 11 (1) pp 35–42
[17] Mkrtychev S 2014 Object-structured approach to modeling of problem-oriented management
accounting information systems Bulletin of the Tomsk Polytechnic University 325 (5) pp 66 –71
[18] Dietz J 2006 Enterprise Ontology: Theory and Methodology (Berlin: Springer)
[19] Mkrtychev S, Ochepovsky A and Enik O 2018 Configuration of management accounting
information system for multi-stage manufacturing J. Phys.: Conf. Ser. 1015 042039
[20] Rosen K 2012 Discrete Mathematics and Its Applications 7th ed (New York: McGraw-Hill)
[21] Shalyto A and Tukkel N 2001 SWITCH Technology: An Automated Approach to Developing</p>
      <p>Software for Reactive Systems Programming and Computer Software 27(5) pp 260–276
[22] Gomaa H 2011 Software modeling and design (Cambridge : University Press) p 578
[23] Larman C 2004 Applying UML and patterns: An Introduction to Object-Oriented Analysis and</p>
      <sec id="sec-5-1">
        <title>Design and Iterative Development (New Jersey: Prentice Hall) p 736</title>
        <p>[24] Mkrtychev S 2015 Methodology of modeling of problem-oriented management accounting
information systems in insurance Modern problems of science and education 1(1) p 174</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Bog</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sachs</surname>
            <given-names>K</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zeier</surname>
            <given-names>A</given-names>
          </string-name>
          and
          <string-name>
            <surname>Plattner</surname>
            <given-names>H 2011</given-names>
          </string-name>
          <article-title>Normalization in a Mixed OLTP and OLAP Workload Scenario 3rd TPC Technology Conference on Performance Evaluation &amp; Benchmarking</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Rom</surname>
            <given-names>A</given-names>
          </string-name>
          and
          <string-name>
            <surname>Rohde C 2007</surname>
          </string-name>
          <article-title>Management accounting and integrated information systems: A literature review Int</article-title>
          .
          <source>J. of Acc. Inf. Sys</source>
          . 8 pp
          <fpage>40</fpage>
          -
          <lpage>68</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Alikhani</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahmadi</surname>
            <given-names>N</given-names>
          </string-name>
          and
          <string-name>
            <surname>Mehravar</surname>
            <given-names>M 2013</given-names>
          </string-name>
          <article-title>Accounting information system versus management information system European Online J</article-title>
          .
          <source>of Nat. and Soc. Sci</source>
          .
          <volume>2</volume>
          (
          <issue>3</issue>
          ) pp
          <fpage>359</fpage>
          -
          <lpage>366</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Mia</surname>
            <given-names>L</given-names>
          </string-name>
          and
          <string-name>
            <surname>Chenhall</surname>
            <given-names>R 1994</given-names>
          </string-name>
          <article-title>The usefulness of management accounting systems, functional differentiation and managerial effectiveness Acc</article-title>
          .
          <source>Org. and Soc</source>
          .
          <volume>19</volume>
          (
          <issue>1</issue>
          ) pp
          <fpage>1</fpage>
          -
          <lpage>13</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Choe</surname>
            <given-names>J</given-names>
          </string-name>
          and
          <string-name>
            <surname>Langfield-Smith</surname>
            <given-names>K 2004</given-names>
          </string-name>
          <article-title>The effects of national culture on the design of management accounting information systems J</article-title>
          .
          <source>of Comp. Int. Man. 7</source>
          pp
          <fpage>3</fpage>
          -
          <lpage>24</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Panayiotou</surname>
            <given-names>N</given-names>
          </string-name>
          and
          <string-name>
            <surname>Tatsiopoulos</surname>
            <given-names>I 2013</given-names>
          </string-name>
          <article-title>Supporting the design of a management accounting system of a company operating in the gas industry with business process modeling Advances in production management systems, competitive manufacturing for innovative products</article-title>
          and services (Berlin: Springer) pp
          <fpage>686</fpage>
          -
          <lpage>692</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Kim</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangolly</surname>
            <given-names>J</given-names>
          </string-name>
          and
          <string-name>
            <surname>Elsas</surname>
            <given-names>P 2017</given-names>
          </string-name>
          <article-title>A framework for analytics and simulation of accounting information systems: A Petri net modeling primer Int</article-title>
          .
          <source>J. of Acc. Inf. Sys</source>
          .
          <volume>27</volume>
          pp
          <fpage>30</fpage>
          -
          <lpage>54</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Van der Aalst</surname>
            <given-names>W 2009</given-names>
          </string-name>
          <article-title>Transactions on Petri Nets and Other Models of Concurrency II Special Issue on Concurrency in Process-Aware Information Systems</article-title>
          (Eindhoven : Technical University) p
          <fpage>297</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Chen</surname>
            <given-names>H</given-names>
          </string-name>
          and
          <string-name>
            <surname>Morris B 2009 Using Design</surname>
            <given-names>Patterns</given-names>
          </string-name>
          ,
          <source>Analysis Pattern, and Case-Based Reasoning to Improve Information Modeling and Method Engineering in Systems Development Int. J. of App. Man. and Technol</source>
          .
          <volume>7</volume>
          (
          <issue>1</issue>
          ) pp
          <fpage>19</fpage>
          -
          <lpage>49</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Hammar</surname>
            <given-names>K 2017</given-names>
          </string-name>
          <string-name>
            <surname>Content Ontology Design Patterns: Qualities</surname>
          </string-name>
          , Methods, and Tools vol
          <volume>1879</volume>
          (Linköping: University Electronic Press)
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>McCarthy W 1982 The</surname>
            <given-names>REA</given-names>
          </string-name>
          <article-title>accounting model: A generalized framework for accounting systems in a shared data environment The Acc</article-title>
          .
          <source>Rev</source>
          .
          <volume>57</volume>
          pp
          <fpage>554</fpage>
          -
          <lpage>578</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>