Shared Conceptualisation of Business Systems, Information Systems and Supporting Software
01 Jan 2002-pp 109-120
TL;DR: The proposed approach enables to define all above listed systems in unified manner and to develop unified enterprise engineering environment that increases the reliability of design of enterprise systems because of the possibility to check consistency between business, information and software systems.
Abstract: This paper discusses a shared conceptualisation of business systems, information systems and supporting software. The main idea is to think of all above listed systems as different kinds of an abstract operational system. The paper proposes also a shared conceptualisation of business engineering, information systems engineering and supporting software engineering processes on the basis of systems engineering. The proposed approach enables to define all above listed systems in unified manner and to develop unified enterprise engineering environment that increases the reliability of design of enterprise systems because of the possibility to check consistency between business, information and software systems.
Citations
More filters
19 Sep 2005
TL;DR: The recent success with eGoverment services and the common architecture of eGovernment will be described hereunder.
Abstract: eGovernment in Estonia got started by developing a functional architecture that includes secure data transport backbone X-Road, distributed software systems and different hardware components like portals, elements of public key infrastructure (PKI), governmental databases and information systems. This is the very basis of hundreds of services that have been created today. The recent success with eGoverment services and the common architecture of eGovernment will be described hereunder.
23 citations
TL;DR: A methodical framework is proposed that defines a complete scheme to organize different level requirements and allows to flowdown requirements from business to software level preserving their business-orientation.
Abstract: In the context of enterprise engineering, strategic planning, information systems engineering, and software engineering activities should be tightly integrated. Traditional, interview-based requirements gathering and elicitation techniques are suited for this aim not enough well and often lead to the violation of the strategic alignment. The vision-driven requirements engineering has been proposed to solve this problem. The paper contributes to the further development of vision-driven requirements engineering techniques. It proposes a methodical framework that defines a complete scheme to organize different level requirements and allows to flowdown requirements from business to software level preserving their business-orientation.
19 citations
Cites methods from "Shared Conceptualisation of Busines..."
...An attempt to do this has been made in Caplinskas et al. (2002a, 2002b, 2003) using the system engineering paradigm....
[...]
TL;DR: Compared ontology-based reuse techniques in domain engineering and enterprise engineering demonstrates that both approaches still are not mature enough to solve practical reuse problems and, on the other hand, both propose ideas that can be used to develop more mature approach.
Abstract: The main purpose of the paper is to compare ontology-based reuse techniques in domain engineering and enterprise engineering. It discusses attempts to combine classical domain engineering techniques with ontology-based techniques as well as the attempts to incorporate ontologies in enterprise engineering process and demonstrates that, on the one hand, both approaches still are not mature enough to solve practical reuse problems and, on the other hand, both propose ideas that can be used to develop more mature approach. The main contribution of the paper is the detail description of the problems of ontology-based reuse of enterprise engineering assets.
13 citations
Cites background from "Shared Conceptualisation of Busines..."
...It may be done separating problem and system ontologies (Caplinskas et al., 2002a; Caplinskas et al., 2002b)....
[...]
TL;DR: The article shows that the main driver of unified software system development is not the new possibilities offered by IT, but the requirements imposed on BPM by the increasingly stronger impact of knowledge management (KM) with regard to the way business processes are executed.
Abstract: One of the results of the evolution of business process management (BPM) is the development of information technology (IT), methodologies and software tools to manage all types of processes – from traditional, structured processes to unstructured processes, for which it is not possible to define a detailed flow as a sequence of tasks to be performed before implementation. The purpose of the article is to present the evolution of intelligent BPM systems (iBPMS) and dynamic case management/adaptive case management systems (DCMS/ACMS) and show that they converge into one class of systems, additionally absorbing new emerging technologies such as process mining, robotic process automation (RPA), or machine learning/artificial intelligence (ML/AI). The content of research reports on iBPMS and DCMS systems by Gartner and Forrester consulting companies from the last 10 years was analysed. The nature of this study is descriptive and based solely on information from secondary data sources. It is an argumentative paper, and the study serves as the arguments that relate to the main research questions. The research results reveal that under business pressure, the evolution of both classes of systems (iBPMS and DCMS/ACMS) tends to cover the functionality of the same area of requirements by enabling the support of processes of different nature. This de facto means the creation of one class of systems, although for marketing reasons, some vendors will still offer separate products for some time to come. The article shows that the main driver of unified software system development is not the new possibilities offered by IT, but the requirements imposed on BPM by the increasingly stronger impact of knowledge management (KM) with regard to the way business processes are executed. Hence the anticipation of the further evolution of methodologies and BPM supporting systems towards integration with KM and elements of knowledge management systems (KMS). This article presents an original view on the features and development trends of software systems supporting BPM as a consequence of knowledge economy (KE) requirements in accordance with the concept of dynamic BPM.
6 citations
Cites background from "Shared Conceptualisation of Busines..."
...In the context of enterprise system development, business processes, information systems, and software systems should be tightly integrated (Caplinskas et al., 2002)....
[...]
01 Jan 2009
TL;DR: A model-driven framework for the semiautomatic implementation of business rules in enterprise resource planning systems based on the idea of combining business rules represented in natural language with decision tables and triggers in database systems is presented.
Abstract: Thes paper presents a model-driven framework for the semiautomatic implementation of business rules in enterprise resource planning systems. The framework is based on the idea of combining business rules represented in natural language with decision tables and triggers in database systems. To support the implementation of the framework, the formal language of templates, which captures patterns of busi- ness rules and enables their model-driven transformation to the triggers, is used. This allows a consistent implementation of business rules within ERP systems.
4 citations
Cites background from "Shared Conceptualisation of Busines..."
...According to Caplinskas et al. (2002), the business system of an enterprise to a great extent depends on the supporting information system (IS) and the software system (SS). therefore, a change in the business system (BS) results in a change of the IS and SS. the form of business rules varies in…...
[...]
References
More filters
Book•
01 Jan 1999TL;DR: In The Unified Modeling Language User Guide, the original developers of the UML provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning.
Abstract: In The Unified Modeling Language User Guide, the original developers of the UML--Grady Booch, James Rumbaugh, and Ivar Jacobson--provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning. Starting with a conceptual model of the UML, the book progressively applies the UML to a series of increasingly complex modeling problems across a variety of application domains. This example-driven approach helps readers quickly understand and apply the UML. For more advanced developers, the book includes a learning track focused on applying the UML to advanced modeling problems.With The Unified Modeling Language User Guide, readers will:Understand what the UML is, what it is not, and why it is relevant to the development of software-intensive systemsMaster the vocabulary, rules, and idioms of the UML in order to "speak" the language effectivelyLearn how to apply the UML to a number of common modeling problemsSee illustrations of the UML's use interspersed with use cases for specific UML features, andGain insight into the UML from the original creators of the UML.
6,634 citations
TL;DR: The ISA framework and its recent extensions are presented and it is shown how it can be formalized in the notation of conceptual graphs.
Abstract: John Zachman introduced a framework for information systems architecture (ISA) that has been widely adopted by systems analysts and database designers. It provides a taxonomy for relating the concepts that describe the real work to the concepts that describe an information system and its implementation. The ISA framework has a simple elegance that makes it easy to remember, yet it draws attention to fundamental distinctions that are often overlooked in systems design. This paper presents the framework and its recent extensions and shows how it can be formalized in the notation of conceptual graphs.
1,114 citations
01 Jan 2003
TL;DR: Bar attributes op1() op2() Abstract Operation (in italic) is defined to describe the operation of the Bar variable.
Abstract: public class Bar{ abstract public void op1(); public void op2(){} } Bar attributes op1() op2() Abstract Operation (in italic)
1,092 citations
TL;DR: The Enterprise Ontology was developed within the Enterprise Project, a collaborative effort to provide a framework for enterprise modelling, and was built to serve as a basis for this framework which includes methods and a computer tool set for enterprise modeling.
Abstract: This is a comprehensive description of the Enterprise Ontology, a collection of terms and definitions relevant to business enterprises. We state its intended purposes, describe how we went about building it, define all the terms and describe our experiences in converting these into formal definitions. We then describe how we used the Enterprise Ontology and give an evaluation which compares the actual uses with original purposes. We conclude by summarising what we have learned. The Enterprise Ontology was developed within the Enterprise Project, a collaborative effort to provide a framework for enterprise modelling. The ontology was built to serve as a basis for this framework which includes methods and a computer tool set for enterprise modelling. We give an overview of the Enterprise Project, elaborate on the intended use of the ontology, and give a brief overview of the process we went through to build it. The scope of the Enterprise Ontology covers those core concepts required for the project, which will appeal to a wider audience. We present natural language definitions for all the terms, starting with the foundational concepts (e.g. entity, relationship, actor). These are used to define the main body of terms, which are divided into the following subject areas: activities, organisation, strategy and marketing. We review some of the things learned during the formalisation process of converting the natural language definitions into Ontolingua. We identify and propose solutions for what may be general problems occurring in the development of a wide range of ontologies in other domains. We then characterise in general terms the sorts of issues that will be faced when converting an informal ontology into a formal one. Finally, we describe our experiences in using the Enterprise Ontology. We compare these with the intended uses, noting our successes and failures. We conclude with an overall evaluation and summary of what we have learned.
1,070 citations