felixfoertsch/Bachelorarbeit
1
0
Fork 0
mirror of https://github.com/felixfoertsch/Bachelorarbeit.git synced 2026-04-16 06:28:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

Change wording in membership

Browse Source
This commit is contained in:
Felix Förtsch
2020-06-26 18:43:40 +02:00
parent c7a08deb61
commit 2ce80b4c83
2 changed files with 52 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

53
Work/main.bib
View File

@@ -1,20 +1,65 @@
%% This BibTeX bibliography file was created using BibDesk.
%% https://bibdesk.sourceforge.io/
%% Created for Felix Förtsch at 2020-06-23 20:34:17 +0200
%% Created for Felix Förtsch at 2020-06-26 18:35:21 +0200
%% Saved with string encoding Unicode (UTF-8)
@article{pouchard2005iso,
Author = {Pouchard, Line Catherine and Cutting-Decelle, AF and Michel, Jean-Jacques and Grüninger, M},
Date-Added = {2020-06-26 18:34:39 +0200},
Date-Modified = {2020-06-26 18:34:39 +0200},
Journal = {IFAC Proceedings Volumes},
Number = {1},
Pages = {37--45},
Publisher = {Elsevier},
Title = {ISO 18629 PSL: A standardised language for specifying and exchanging process information},
Volume = {38},
Year = {2005}}
@article{iso2013iec,
Author = {International Organization for Standardization},
Date-Added = {2020-06-26 18:33:28 +0200},
Date-Modified = {2020-06-26 18:33:47 +0200},
Journal = {Geneva, Switzerland},
Title = {19510:2013, information technology object management group business process model and notation (ISO/IEC)},
Year = {2013}}
@article{iso2015iso,
Author = {International Organization for Standardization},
Date-Added = {2020-06-26 18:29:07 +0200},
Date-Modified = {2020-06-26 18:32:50 +0200},
Title = {19450:2015, Automation systems and integration—Object-Process Methodology (ISO/PAS)},
Year = {2015}}
@article{iso2005iec,
Author = {International Organization for Standardization},
Date-Added = {2020-06-26 18:28:03 +0200},
Date-Modified = {2020-06-26 18:32:33 +0200},
Number = {2},
Title = {19501:2005, Information technology - Open Distributed Processing-Unified Modeling Language (UML) Version (ISO/IEC)},
Volume = {1},
Year = {2005}}
@book{scheer2013aris,
Author = {Scheer, August-Wilhelm},
Date-Added = {2020-06-26 18:25:06 +0200},
Date-Modified = {2020-06-26 18:25:06 +0200},
Publisher = {Springer-Verlag},
Title = {ARIS—vom Geschäftsprozess zum Anwendungssystem},
Year = {2013}}
@misc{deliverable,
Date-Added = {2020-06-23 14:37:07 +0200},
Date-Modified = {2020-06-23 14:37:44 +0200},
Howpublished = {online},
Title = {Wikipedia: Deliverable},
Url = {https://en.wikipedia.org/wiki/Deliverable},
Urldate = {2020-06-23}}
Urldate = {2020-06-23},
Bdsk-Url-1 = {https://en.wikipedia.org/wiki/Deliverable}}
@misc{sutherland2017scrum,
Author = {Sutherland, Jeff and Schwaber, Ken},
@@ -340,10 +385,10 @@
Address = {[Geneva]},
Author = {International Organization for Standardization},
Date-Added = {2020-04-04 16:21:26 +0200},
Date-Modified = {2020-06-13 12:58:56 +0200},
Date-Modified = {2020-06-26 18:32:03 +0200},
Edition = {4th edition},
Publisher = {ISO Copyright office},
Title = {Quality management systems - fundamentals and vocabulary (ISO 9000:2015).},
Title = {ISO 9000:2015, Quality management systems - fundamentals and vocabulary},
Year = {2015},
Bdsk-File-1 = {YnBsaXN0MDDSAQIDBFxyZWxhdGl2ZVBhdGhZYWxpYXNEYXRhXxBNU291cmNlcy9JU08gMjAxNSBRdWFsaXR5IG1hbmFnZW1lbnQgc3lzdGVtcyAtIGZ1bmRhbWVudGFscyBhbmQgdm9jYWJ1bGFyeS5wZGZPEQJeAAAAAAJeAAIAAAZoYWNrT1MAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQkQAAf////8fSVNPIDIwMTUgUXVhbGl0eSBtI0ZGRkZGRkZGLnBkZgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/////wAAAAAAAAAAAAAAAAABAAMAAAogY3UAAAAAAAAAAAAAAAAAB1NvdXJjZXMAAAIAgS86VXNlcnM6ZmVsaXhmb2VydHNjaDpEZXZlbG9wZXI6QmFjaGVsb3JhcmJlaXQ6V29yazpTb3VyY2VzOklTTyAyMDE1IFF1YWxpdHkgbWFuYWdlbWVudCBzeXN0ZW1zIC0gZnVuZGFtZW50YWxzIGFuZCB2b2NhYnVsYXJ5LnBkZgAADgCMAEUASQBTAE8AIAAyADAAMQA1ACAAUQB1AGEAbABpAHQAeQAgAG0AYQBuAGEAZwBlAG0AZQBuAHQAIABzAHkAcwB0AGUAbQBzACAALQAgAGYAdQBuAGQAYQBtAGUAbgB0AGEAbABzACAAYQBuAGQAIAB2AG8AYwBhAGIAdQBsAGEAcgB5AC4AcABkAGYADwAOAAYAaABhAGMAawBPAFMAEgB/VXNlcnMvZmVsaXhmb2VydHNjaC9EZXZlbG9wZXIvQmFjaGVsb3JhcmJlaXQvV29yay9Tb3VyY2VzL0lTTyAyMDE1IFF1YWxpdHkgbWFuYWdlbWVudCBzeXN0ZW1zIC0gZnVuZGFtZW50YWxzIGFuZCB2b2NhYnVsYXJ5LnBkZgAAEwABLwAAFQACABT//wAAAAgADQAaACQAdAAAAAAAAAIBAAAAAAAAAAUAAAAAAAAAAAAAAAAAAALW}}

8
Work/main.tex
View File

@@ -731,11 +731,9 @@ Since \glspl{sco} are a social construct and are defined by the people of the or
\label{membership}
Within the \gls{oc} (see \autoref{context}), the most basic property is membership: Either being part of the organization and thus being a \class{Member} or not participating and being a \class{Non-Member}. \class{Members} of the \gls{sco} can play different roles in the \gls{oc}. \class{Non-Members} do not play roles within the organization, but can play external roles such as the role of a \class{Project\_Customer}. The membership status is typically used in the internal organizational procedures. For example: Someone might be required to be a full member to be allowed to vote in the Member Assembly, to be part of a project, or to become part of the Executive Board.
It is important to note that within \glspl{sco} the \class{Member} role can only be played by human beings. For this model this means a restriction to \class{Person}. The members are the defining group that fills all the organizational functions, works on the projects, and participates in the majority of processes. Even though membership does not have to be limited like this in general---there are many examples where organizations are members of other organizations---it is limited in this domain. Since \class{Member} are necessarily \textbf{always} human beings, we introduce the role as \relation{subclassOf} \class{Person}.
Members are the defining group that fills all the organizational functions, works on the projects, and participates in the majority of processes. Even though membership does not have to be limited like this in general---there are many examples where organizations are members of other organizations---it is limited in this domain. Within \glspl{sco} only human beings can be \class{Members} and since they are necessarily \textbf{always} human beings, we introduce this restriction by making \class{Member} \relation{subclassOf} \class{Person}.
%TODO: Text sagt member role, Person ist subclassOf Agent -> Paralleles Konzept
The \class{Non-Member} role, however, is not limited to only \class{Person}. In fact, everything and everyone that is not a \class{Member} is by definition a \class{Non-Member}. Furthermore, \gls{owl} supports negation in case it would be necessary to express non-membership. Therefore it is sufficient to model the class \class{Member} and omit \class{Non-Member}.
The \class{Non-Members}, however, are not limited to only being a \class{Person}. In fact, everything and everyone that is not a \class{Member} is by definition a \class{Non-Member}. Furthermore, \gls{owl} supports negation in case it would be necessary to express non-membership. Therefore it is sufficient to model the class \class{Member} and omit \class{Non-Member}.
\paragraph{Business Ranks}
\label{ranks}
@@ -801,7 +799,7 @@ Processes are a helpful concept when describing organizations: The latter are cr
Since processes are a commonly used concept in the business world, it is not surprising that many different methods and frameworks for modeling them have been developed. They often revolve around visual representations of all workflows that make up an organization. Combining process models with goals and measurements makes them a powerful tool for optimization and quality control. For example, ISO 9001 is an industry standard that uses a process approach as the foundation of measuring quality. \cite{iso-process-approach} Because process documentation contains a lot of data about organizations, it is also a valuable source for ontology development.
Widely known representations and methods include: Flowcharts, \gls{bpmn}, \gls{epc}, \gls{uml} Activity Diagrams, and \gls{opm}\footnote{Standardized as ISO~19450.}. There are also contributions rooted in ontology research, such as the \gls{bpmn} ontology (an \gls{owl} ontology for the \gls{bpmn} notation) \cite{2014foisbpmn}, the \gls{psl}\footnote{Developed by the \gls{nist} and standardized as ISO~18629.}, and process concepts as part of \gls{gfo} or \gls{bfo}.
Widely known representations and methods include: \gls{bpmn} \cite{iso2013iec}, \gls{epc} \cite{scheer2013aris}, \gls{uml} \cite{iso2005iec} Activity Diagrams, and \gls{opm} \cite{iso2015iso}. There are also contributions rooted in ontology research, such as the \gls{bpmn} ontology (an \gls{owl} ontology for the \gls{bpmn} notation) \cite{2014foisbpmn}, the \gls{psl} \cite{pouchard2005iso}, and process concepts as part of \gls{gfo} or \gls{bfo}.
Our intent is the representation of the most important processes of an \gls{sco} in a way that makes clear to the ontology user \underline{which} process have to be implemented, but leaves enough creative freedom in regards to \underline{how} to implement them.