Business architecture became a well-known tool for business transformations. According to a recent study by Forrester, 50 percent of the companies polled claimed to have an active business architecture initiative, whereas 20 percent were planning to engage in business architecture work in the near future. However, despite the high interest in BA, there is not yet a common understanding of the main concepts. There is a lack for the business architecture framework which provides a complete metamodel, suggests methodology for business architecture development and enables tool support for it. The ORGMaster framework is designed to solve this problem using the ontology as a core of the metamodel. This paper describes the ORG-Master framework, its implementation and dissemination. the presentation was given within the SOMET 2011 conference: http://www.somet.soft.iwate-pu.ac.jp/somet_11/ see the text in proceedings here: http://www.booksonline.iospress.nl/Content/View.aspx?piid=21454 Kudryavtsev, D., & Grigoriev, L. (2011). The ontology-based business architecture engineering framework. In proceedings of the 10th International Conference on Intelligent Software Methodologies, Tools and Techniques (SOMET), September 28-30, 2011, Saint-Petersburg, Russia. P. 233-252.

1. Ontology-based business architecture engineering framework Dmitry Kudryavtsev, Lev Grigoriev 20 11

4. TOGAF , Architecture Content Framework

5. Business Architecture (BA) definition “ Business Architecture (BA) is a formal blueprint of governance structures, business semantics and value streams across the extended enterprise. Business Architecture articulates the structure of an enterprise in terms of its: - capabilities, - business processes, - governance structure, and - business information. The business capability is “what” the organization does, The business processes , are “how” the organization executes its capabilities. In articulating the governance and information , the business architecture considers all external actors to an enterprise (including its customers, suppliers, and regulators), to ensure that flow in and out of the enterprise are captured. Business Architecture Working Group. Available at: http://www.omgwiki.org/bawg/doku.php ,

6. Available BA frameworks Component Business Model ARIS BMM DEMO

7. Evaluation criteria for the available BA frameworks

8. Comparison of the currently available Business Architecture frameworks* (1/2) * Extended and adapted from Glissmann S., Sanz J., Business Architectures for the Design of Enterprise Service Systems, Handbook of Service Science, P.P. Maglio, C.A. Kieliszewski, and J.C. Spohrer, eds., Boston, MA: Springer US, 2010, pp. 251-282

9. Comparison of the currently available Business Architecture frameworks (2/2)

11. The transition towards the ontology-based BA modeling Enterprise modeling languages (EML) EML 1 EML 2 EML n EML i Diagrammatic notation 1 Diagrammatic notation i Diagrammatic notation 2 Diagrammatic notation n Enterprise ontology Ontology is a formal, explicit specification of a shared conceptualization (Gruber, 1993)

12. Components of the ORG-Master architecture framework Ontology-based enterprise model {specialized and populated ontology} Output views / documents and diagrams Processing Input views / documents and diagrams Import Model level Meta-model level Creation and Acquisition Formalization Distribution Use Customization method Specifications of views (documents and diagrams) Methodology for enterprise model creation and use Enterprise Ontology Knowledge Process Metamodel

13. Main domains of the ORG-Master enterprise ontology

14. Fragment of the ORG-Master enterprise ontology Activities Result-oriented activities Homogeneous activities Elementary activities Regular activity Unique activity Value-added chain System of activities Functional (sub) system Process Version of the process Goal-oriented program Project Functional domain Function Action Task By type By area Managerial activities Value creating activities Support activities

15. Enterprise views and view specifications Based on the IEEE Std 1471-2000: IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE, New York. View specification (short / full)

16. Knowledge Process Creation and Acquisition Formalization Distribution Use Knowledge acquisition forms Analytical reports Structured Administrative documents Y Query answering Internal Representation Structured Administrative documents Х Local knowledge acquisition organizational models From knowledge acquisition forms to document-oriented views Ontology-based enterprise model

17. Knowledge Process Creation and Acquisition Formalization Distribution Use Text X Tables Y Text Y Graphics Y Internal Representation Tables X Graphics X Pseudo-Graphics From knowledge acquisition forms to document-oriented views Ontology-based enterprise model

18. The ORG-Master BA engineering method (overview) Goal Operations Structure Principles and rules Products and Services, Value chain, Functional systems, Processes, Activities Vision and mission, Concepts and Policies, Strategy and critical success factors (CSF), Key Performance Indicators (KPI) Actors, Roles structure, Organization structure, Responsibilities, Authority

19. The ORG-Master BA engineering method (details) Develop business concepts Describe value added chain Develop strategy Identify and classify functional systems and business-processes Define interaction of business processes Define KPI system Business process redesign Design organizational structure Strategy maps and critical success factors Needs Markets Customers Value added chain Owners of FS , subsystems and processes Purposes of FS , subsystems and processes Functional systems (FS) and subsystems, processes Business-process network Actors KPI system Redesigned business processes Organizational structure (with attributes: goals, measures, FS, processes) Mission, Vision, Concept s and policies

20. More details Identify and classify functional systems and business-processes Corporate system Kudryavtsev, D., & Grigoriev, L. (2011). Systemic approach towards enterprise functional decomposition. The proceedings of the Workshop “Convergence of Business Architecture, Business Process Architecture, Enterprise Architecture and Service Oriented Architecture” within the 13-th IEEE Conference on Commerce and Enterprise Computing (CEC), September 5-7, 2011, Luxemborg. P . 310-317. Business system Business- lines Functional systems Functional subsystem

21. The BA engineering tool Ontology-based enterprise model editor Ontology-based enterprise model Reporting and query module Documents Diagrams ORG-MASTER ® Modeling process wizard Integration wizard Diagram editor Query results Semi - structured data OWL

23. ORLAN: Types

24. ORLAN: Classifier (CL) for instance-level editing

25. ORLAN: Matrix (MX) for instance-level editing

26. ORLAN-OWL mapping

27. ORG-Master role in CPM & BPM systems Modeling ORG-MASTER ® Execution e.g. TIME-MASTER ® Monitoring e.g. Е- MASTER ® BPA (Business Process Analysis) BAM (Business Activity Monitoring) Business Process Management (BPM) Process Engine Strategy Monitoring Project Management ( internal projects ) Strategy Modeling Corporate performance management (CPM) Strategic goals & measures Development projects Operational goals and measures Processes

29. Implementation experience: business entities

37. The END Questions? 20 11 [email_address] , [email_address] http://www.bigc.ru/ http://www.spbstu.ru/