\documentclass{article}
\usepackage[affil-it]{authblk}
\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
\usepackage{url}
\usepackage{hyperref}
\hypersetup{colorlinks=false,pdfborder={0 0 0}}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}

\newcommand{\keywords}[1]{\par\addvspace\baselineskip
\noindent\keywordname\enspace\ignorespaces#1}



\begin{document}

\title{Springer LNCS LaTeX template}


\author{Paul Johannesson}
\affil{Stockholm Universitet }



\date{\today}

\maketitle

The abstract should summarize the contents of the paper and should
contain at least 70 and at most 150 words. It should be written using the
\emph{abstract} environment.
\keywords{We would like to encourage you to list your keywords within
the abstract section}



\section{Introduction}

\section{Introduction}
%
Conceptual modelling can be viewed as the activity of analysing, describing and representing some existing domain, typically an organizational one. The goal is to create a correct representation of the domain that can be used as the basis for the design of an information system supporting the activities of the organization. However, this view is often too limited in its focus on the purely descriptive aspects of conceptual modelling. When creating a model for an organization, it is generally required to take a future-oriented perspective, meaning that the model to be produced should not only be descriptive but also prescriptive. It should be able to specify how people are enabled, allowed and constrained to act and interact in the domain. For this purpose, the model needs to represent processes, rules and regulations that determine how people can interact. In other words, institutional concerns come to the foreground when designing prescriptive models for organizational domains.

Institutions have been defined as "systems of established and prevalent social rules that structure social interactions" \cite{Hodgson2006-bz}. Institutional theory defines institutions as regulative, normative and cultural-cognitive structures, also called institutional pillars, that provide stability and meaning to social life \cite{Scott2003-tc}. In the following, we focus on the formal aspects of institutions, in particular formal rule systems.

Institutions are created and maintained through communication between people. In line with a communicative view on institutions, John Searle \cite{Searle2010-gr,Searle1997-it} has investigated how institutional reality is constructed by means of communication acts (speech acts). Searle acknowledges that there is a material world that exists independently of human beings and their beliefs, and asks "how can we account for social facts within that ontology?", \cite[p. 7]{Searle1997-it}. This question can partially be answered by the fact that humans have a capacity for collective intentionality, where they share intentions, \cite{Searle2005-kr}. Through collective intentionality, they are able to assign functions to things, in particular functions that have little to do with the physical properties of the tool or medium that mediate the function. Such functions are called status functions by Searle. For example, people can assign the function of being money to pieces of paper or the function of being American president to a person. According to Searle, \cite{Searle2006-wq}, status functions mark the difference between material and institutional reality, where the latter is a matter of status functions and institutional facts, not physical things. Furthermore, institutional facts such as money, property, government and marriage cannot exist without the use of language, which means that communication is constitutive for institutional reality. 

Recently, researchers have investigated how an understanding of institutions and communicative action can help in the design of conceptual models, \cite{Beynon-Davies2017-pf,March2014-se,Bergholtz2013-pu}. The present paper has the same goal, as it intends to describe and characterize how institutional aspects should inform conceptual modeling in the context of information systems design. In order to achieve this goal, we propose a set of guidelines for designing a domain model based on institutional aspects of a domain. As a basis for the guidelines, we introduce an institutional ontology in Section 2 that describes key notions of institutions, including actors, rules, rights, contracts, and processes; this ontology is a revision and extension of previous work, \cite{Bergholtz2013-pu,Bergholtz2015-mk}. Being familiar with the ontology can itself help modellers to construct conceptual models that take institutional aspects into account. But doing this requires a "creative leap", as there is a gap between the notions of the ontology and domain model notions. In order to bridge this gap, the paper introduces a number of guidelines in Section 3 that support a modeller in identifying classes in a domain model starting from an analysis of the institutional aspects of the domain. This can be viewed as making the conceptual modelling activity explicitly aware of institutions.

\section{The Institutional Ontology}
The proposed institutional ontology is divided into three levels, see Figure 1. The bottom level (white in the figure) is the material level that represents material entities, such as human beings and other physical entities, as well as physical actions. The middle level (yellow in the figure) is the institutional facts level that represents institutional phenomena. The top level (blue in the figure) is the rule level that includes rules, as well as groupings of rules, that govern how entities are created and can interact at the institutional facts level. The ontology is depicted as a UML class diagram (multiplicities are 0..* if not otherwise indicated).

\subsection*{Institutional Rights}
Institutions are used to enable, regulate, and constrain human interaction. In order to do so, rights are created and allocated among people, thereby setting up relationships of power and obligations between them. Rights are always relational involving at least two agents, e.g., an obligation of one agent to deliver some goods to another agent. Additionally, a right can include other entities that are the objects of the right, such as the goods in the above example. 

One of the most well-known classifications of rights is the one proposed by \cite{Hohfeld1913-qx}, who distinguishes between four kinds of rights: claims, privileges, powers and immunities. A \textit{claim} means that one agent is required to act in a certain way for the benefit of another agent, e.g., a person can have a claim on a company to deliver a product. An agent has a \textit{privilege} to perform an action if she is free to carry it out without interference from other agents, e.g., a privilege to enter a premise. A \textit{power} is the ability of an agent to create or modify claims, privileges or powers, e.g., the ability to transfer ownership. \textit{Immunities} are about restricting the power of agents to create rights for other agents. In the institutional ontology, rights are modeled by the classes Right Kind and Institutional Right. 




\subsection*{Institutional Entities}
Institutional entities are entities that are created by an institution through communicative action. An \textit{institutional entity} is either a right, an entity that can have rights, an entity that is the object of a right, or a grouping of rights.
Institutional entities are often based on some other pre-existing entity. The institutional entity is said to be grounded in that other entity \cite{Masolo2011-qd}, e.g., a student (an institutional entity) can be grounded in a human being (a physical entity). A number of different kinds of institutional entities can be distinguished.

\begin{description} 

\item [Institutional Subject] An \textit{institutional subject} is an institutional entity that can have claims and is directly or indirectly grounded in a human being. 

\item [Institutional Thing] An \textit{institutional thing} is an institutional entity that cannot have claims and is grounded in a physical entity or another institutional thing. 

\item [Institutional Information] \textit{Institutional information} is an institutional entity that cannot have claims and is grounded in informational content, e.g., a text or an image. 

\item [Institutional Right] An \textit{institutional right} is an institutional entity that represents a claim, a privilege or a power.

\item [Institutional Contract] An \textit{institutional contract} is an institutional entity that groups together a number of rights, e.g., a sales contract.
\end{description}


You are strongly encouraged to use \LaTeXe{} for the
preparation of your camera-ready manuscript together with the
corresponding Springer class file \verb+llncs.cls+. Only if you use
of your manuscript.


The \LaTeX{} source of this instruction file for \LaTeX{} users may be
used as a template. This is
located in the ``authors'' subdirectory in
entitled \texttt{typeinst.tex}. There is a separate package for Word 
users. Kindly send the final and checked source
and PDF files of your paper to the Contact Volume Editor. This is
usually one of the organizers of the conference. You should make sure
that the \LaTeX{} and the PDF files are identical and correct and that
only one version of your paper is sent. It is not possible to update
files at a later stage. Please note that we do not need the printed
paper.


We would like to draw your attention to the fact that it is not possible
to modify a paper in any way, once it has been published. This applies
to both the printed book and the online version of the publication.
Every detail, including the order of the names of the authors, should
be checked before the paper is sent to the Volume Editors.


\subsection{Checking the PDF File}


Kindly assure that the Contact Volume Editor is given the name and email
address of the contact author for your paper. The Contact Volume Editor
uses these details to compile a list for our production department at
SPS in India. Once the files have been worked upon, SPS sends a copy of
the final pdf of each paper to its contact author. The contact author is
asked to check through the final pdf to make sure that no errors have
crept in during the transfer or preparation of the files. This should
not be seen as an opportunity to update or copyedit the papers, which is
not possible due to time constraints. Only errors introduced during the
preparation of the files will be corrected.


This round of checking takes place about two weeks after the files have
been sent to the Editorial by the Contact Volume Editor, i.e., roughly
seven weeks before the start of the conference for conference
proceedings, or seven weeks before the volume leaves the printer's, for
post-proceedings. If SPS does not receive a reply from a particular
contact author, within the timeframe given, then it is presumed that the
author has found no errors in the paper. The tight publication schedule
of LNCS does not allow SPS to send reminders or search for alternative
email addresses on the Internet.


In some cases, it is the Contact Volume Editor that checks all the final
pdfs. In such cases, the authors are not involved in the checking phase.


\subsection{Additional Information Required by the Volume Editor}


If you have more than one surname, please make sure that the Volume Editor
knows how you are to be listed in the author index.


\subsection{Copyright Forms}


The copyright form may be downloaded from the ``For Authors"
(Information for LNCS Authors) section of the LNCS Website:
to the Contact Volume Editor, either as a scanned pdf or by fax or by
courier. One author may sign on behalf of all of the other authors of a
particular paper. Digital signatures are acceptable.


\section{Paper Preparation}


Springer provides you with a complete integrated \LaTeX{} document class
(\texttt{llncs.cls}) for multi-author books such as those in the LNCS
series. Papers not complying with the LNCS style will be reformatted.
This can lead to an increase in the overall number of pages. We would
therefore urge you not to squash your paper.


Please always cancel any superfluous definitions that are
not actually used in your text. If you do not, these may conflict with
the definitions of the macro package, causing changes in the structure
of the text and leading to numerous mistakes in the proofs.


If you wonder what \LaTeX{} is and where it can be obtained, see the
``\textit{LaTeX project site}'' (\url{http://www.latex-project.org})
and especially the webpage ``\textit{How to get it}''
(\url{http://www.latex-project.org/ftp.html}) respectively.


When you use \LaTeX\ together with our document class file,
your text is typeset automatically in Computer Modern Roman (CM) fonts.
Please do
than the preset fonts, kindly submit these with your files.


Please use the commands \verb+\label+ and \verb+\ref+ for
cross-references and the commands \verb+\bibitem+ and \verb+\cite+ for
references to the bibliography, to enable us to create hyperlinks at
these places.


For preparing your figures electronically and integrating them into
your source file we recommend using the standard \LaTeX{} \verb+graphics+ or
\verb+graphicx+ package. These provide the \verb+\includegraphics+ command.
In general, please refrain from using the \verb+\special+ command.


Remember to submit any further style files and
fonts you have used together with your source files.


\subsubsection{Headings.}


Headings should be capitalized
(i.e., nouns, verbs, and all other words
except articles, prepositions, and conjunctions should be set with an
initial capital) and should,
with the exception of the title, be aligned to the left.
Words joined by a hyphen are subject to a special rule. If the first
word can stand alone, the second word should be capitalized.


Here are some examples of headings: ``Criteria to Disprove
Context-Freeness of Collage Language", ``On Correcting the Intrusion of
Tracing Non-deterministic Programs by Software", ``A User-Friendly and
Extendable Data Distribution System", ``Multi-flip Networks:
Parallelizing GenSAT", ``Self-determinations of Man".


\subsubsection{Lemmas, Propositions, and Theorems.}


The numbers accorded to lemmas, propositions, and theorems, etc. should
appear in consecutive order, starting with Lemma 1, and not, for
example, with Lemma 11.


\subsection{Figures}


For \LaTeX\ users, we recommend using the \emph{graphics} or \emph{graphicx}
package and the \verb+\includegraphics+ command.


Please check that the lines in line drawings are not
interrupted and are of a constant width. Grids and details within the
figures must be clearly legible and may not be written one on top of
the other. Line drawings should have a resolution of at least 800 dpi
(preferably 1200 dpi). The lettering in figures should have a height of
2~mm (10-point type). Figures should be numbered and should have a
caption which should always be positioned \emph{under} the figures, in
contrast to the caption belonging to a table, which should always appear
your source.


Please center the figures or your tabular material by using the \verb+\centering+
declaration. Short captions are centered by default between the margins
and typeset in 9-point type (Fig.~\ref{fig:example} shows an example).
The distance between text and figure is preset to be about 8~mm, the
distance between figure and caption about 6~mm.


To ensure that the reproduction of your illustrations is of a reasonable
quality, we advise against the use of shading. The contrast should be as
pronounced as possible.


If screenshots are necessary, please make sure that you are happy with
the print quality before you send the files.

Please define figures (and tables) as floating objects. Please avoid
using optional location parameters like ``\verb+[h]+" for ``here".


In the printed volumes, illustrations are generally black and white
(halftones), and only in exceptional cases, and if the author is
prepared to cover the extra cost for color reproduction, are colored
pictures accepted. Colored pictures are welcome in the electronic
version free of charge. If you send colored figures that are to be
printed in black and white, please make sure that they really are
legible in black and white. Some colors as well as the contrast of
converted colors show up very poorly when printed in black and white.\selectlanguage{english}
\begin{figure}[h!]
\begin{center}
\includegraphics[width=0.70\columnwidth]{figures/eijkel2/default-figure}
\caption{{\textbf{\label{fig:example}} One kernel at $x_s$ (\emph{dotted kernel}) or two kernels at
$x_i$ and $x_j$ (\textit{left and right}) lead to the same summed estimate
at $x_s$. This shows a figure consisting of different types of
lines. Elements of the figure described in the caption should be set in
italics, in parentheses, as shown in this sample caption.%
}}
\end{center}
\end{figure}

\subsection{Formulas}


Displayed equations or formulas are centered and set on a separate
line (with an extra line or halfline space above and below). Displayed
expressions should be numbered for reference. The numbers should be
consecutive within each section or within the contribution,
with numbers enclosed in parentheses and set on the right margin --
which is the default if you use the \emph{equation} environment, e.g.,

\begin{equation}
  \psi (u) = \int_{o}^{T} \left[\frac{1}{2}
  \left(\Lambda_{o}^{-1} u,u\right) + N^{\ast} (-u)\right] dt \;  .
\end{equation}

Equations should be punctuated in the same way as ordinary
text but with a small space before the end punctuation mark.


\subsection{Footnotes}


The superscript numeral used to refer to a footnote appears in the text
either directly after the word to be discussed or -- in relation to a
phrase or a sentence -- following the punctuation sign (comma,
semicolon, or period). Footnotes should appear at the bottom of
the
normal text area, with a line of about 2~cm set
immediately above them.\footnote{The footnote numeral is set flush left
and the text follows with the usual word spacing.}


\subsection{Program Code}


Program listings or program commands in the text are normally set in
typewriter font, e.g., CMTT10 or Courier.

{\it Example of a Computer Program}
\begin{verbatim}
program Inflation (Output)
  {Assuming annual inflation rates of 7%, 8%, and 10%,...
   years};
   const
     MaxYears = 10;
   var
     Year: 0..MaxYears;
     Factor1, Factor2, Factor3: Real;
   begin
     Year := 0;
     Factor1 := 1.0; Factor2 := 1.0; Factor3 := 1.0;
     WriteLn('Year  7% 8% 10%'); WriteLn;
     repeat
       Year := Year + 1;
       Factor1 := Factor1 * 1.07;
       Factor2 := Factor2 * 1.08;
       Factor3 := Factor3 * 1.10;
       WriteLn(Year:5,Factor1:7:3,Factor2:7:3,Factor3:7:3)
     until Year = MaxYears
end.
\end{verbatim}
%
\noindent
{\small (Example from Jensen K., Wirth N. (1991) Pascal user manual and
report. Springer, New York)}


\subsection{Citations}
For citations in the text please use
\LaTeX 's \verb|\cite| mechanism.


\subsection{Page Numbering and Running Heads}


There is no need to include page numbers. If your paper title is too
long to serve as a running head, it will be shortened. Your suggestion
as to how to shorten it would be most welcome.


\section{LNCS Online}


The online version of the volume will be available in LNCS Online.
Members of institutes subscribing to the Lecture Notes in Computer
Science series have access to all the pdfs of all the online
publications. Non-subscribers can only read as far as the abstracts. If
they try to go beyond this point, they are automatically asked, whether
they would like to order the pdf, and are given instructions as to how
to do so.


Please note that, if your email address is given in your paper,
it will also be included in the meta data of the online version.

\selectlanguage{english}
\FloatBarrier
\bibliographystyle{plain}
\bibliography{bibliography/converted_to_latex.bib%
}

\end{document}

