Philosophy of Blockchain Technology - Ontologies

About the necessity and usefulness of developing a philosophy specific to the blockchain technology, emphasizing on the ontological aspects. After an Introduction that highlights the main philosophical directions for this emerging technology, in Blockchain Technology I explain the way the blockchain works, discussing ontological development directions of this technology in Designing and Modeling. The next section is dedicated to the main application of blockchain technology, Bitcoin, with the social implications of this cryptocurrency. There follows a section of Philosophy in which I identify the blockchain technology with the concept of heterotopia developed by Michel Foucault and I interpret it in the light of the notational technology developed by Nelson Goodman as a notational system. In the Ontology section, I present two developmental paths that I consider important: Narrative Ontology, based on the idea of order and structure of history transmitted through Paul Ricoeur's narrative history, and the Enterprise Ontology system based on concepts and models of an enterprise, specific to the semantic web, and which I consider to be the most well developed and which will probably become the formal ontological system, at least in terms of the economic and legal aspects of blockchain technology. In Conclusions I am talking about the future directions of developing the blockchain technology philosophy in general as an explanatory and robust theory from a phenomenologically consistent point of view, which allows testability and ontologies in particular, arguing for the need of a global adoption of an ontological system for develop cross-cutting solutions and to make this technology profitable. CONTENTS: Abstract Introducere Tehnologia blockchain - Proiectare - Modele Bitcoin Filosofia Ontologii - Ontologii narative - Ontologii de intreprindere Concluzii Note Bibliografie DOI: 10.13140/RG.2.2.24510.3360

Configurable Process Models as a Basis for Reference Modeling

Off-the-shelf packages such as SAP need to be configured to suit the requirements of an organization. Reference models support the configuration of these systems. Existing reference models use rather traditional languages. For example, the SAP reference model uses Eventdriven Process Chains (EPCs). Unfortunately, traditional languages like EPCs do not capture the configuration-aspects well. Consider for example the concept of "choice" in the control-flow perspective. Although any process modeling language, including EPCs, offers a choice construct (e.g., the XOR connector in EPCs), a single construct will not be able to capture the time dimension, scope, and impact of a decision. Some decisions are taken at run-time for a single case while other decisions are taken at build-time impacting a whole organization and all current and future cases. This position paper discusses the need for configurable process models as a basic building block for reference modeling. The focus is on the control-flow perspective. © Springer-Verlag Berlin Heidelberg 2006

A goal-oriented requirements modelling language for enterprise architecture

Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain

Coupling Performance Measurement and Collective Activity: The Semiotic Function of Management Systems. A Case Study

Theories about management instruments often enter dualistic debates between structure and agency: do instruments determine the forms of collective activity (CA), or do actors shape instruments to their requirements, or are instruments and concrete activity decoupled, as some trends of new institutionalist theory assume? Attempts to overcome the dualistic opposition between structure and activity stem from diverse sources: actors’ networks theory, structuration theory, pragmatism, theory of activity, semiotics. Performance measurement and management systems can be defined as structural instruments engaged in CA. As such they constrain the activity, but they do not determine it. Reciprocally, they are modified by the way CA uses them and makes sense of them. The central thesis of this paper will be that it is impossible to study the role of performance measurement as a common language in organizations independently from the design of the CA in which it is engaged. There is a not deterministic coupling between structure (i.e. management technical tools) and CA (i.e. business processes). The transformation of CA entails a transformation in the meaning of the “performance” concept, in the type of measurement required and in the performance management practices. The relationship between performance measurement and CA is studied here in the production division of a large electricity utility in France. The research extended over several years and took place when two new management systems were simultaneously implemented: a new management accounting system and an integrated management information system (ERP), both in the purchasing process. The new management accounting system was designed by the purchasing department; the new management information system was designed by the operational departments. Whereas the coherence between both projects could have been given by their common subordination to the rebuilding of CA (the purchasing process), their disconnection from concrete CA opened the possibility of serious dissonances between them. Both the new performance management system and the new ERP met difficulties to provide common languages, since the dimension of CA was taken for granted and consequently partly ignored in the engineering of both systems. When CA incurs radical transformations, actors’direct discursive exchanges about it, “collective activity about collective activity”, become necessary to ensure a flexible and not deterministic coupling between CA and new management systems. This reflexive and collective analysis of the process by actors themselves requires the establishment of “communities of process”, which can jointly redesign the CA and its performance measurement system. We conclude that performance measurement can be a common language as far as there is a clear and shared understanding of how CA should concretely take place and should be assigned to the different categories of actors.Business Process; Collective Activity; Community of Process; Management Instruments; Performance Measurement; Semiotics; Theory of Activity

Specifying Reusable Components

Reusable software components need expressive specifications. This paper outlines a rigorous foundation to model-based contracts, a method to equip classes with strong contracts that support accurate design, implementation, and formal verification of reusable components. Model-based contracts conservatively extend the classic Design by Contract with a notion of model, which underpins the precise definitions of such concepts as abstract equivalence and specification completeness. Experiments applying model-based contracts to libraries of data structures suggest that the method enables accurate specification of practical software

Bioconductor: open software development for computational biology and bioinformatics.

The Bioconductor project is an initiative for the collaborative creation of extensible software for computational biology and bioinformatics. The goals of the project include: fostering collaborative development and widespread use of innovative software, reducing barriers to entry into interdisciplinary scientific research, and promoting the achievement of remote reproducibility of research results. We describe details of our aims and methods, identify current challenges, compare Bioconductor to other open bioinformatics projects, and provide working examples