Skip to content

Commit c73ca74

Browse files
jgelukjgeluk
committed
Added "EKG Foundation" chapter
1 parent 444b521 commit c73ca74

File tree

2 files changed

+193
-0
lines changed

2 files changed

+193
-0
lines changed

‎ekg-mm/chapters/ekg-foundation.tex‎

Lines changed: 192 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,192 @@
1+
\chapter{EKG Foundation}
2+
\label{ch:ekg-foundation}
3+
\index{EKG Foundation}
4+
\index{EKGF}
5+
6+
This document\,---\,the \glsfirst{ekgmm}\,---\,is one of the key "artifacts" produced by the \glsxtrfull{ekgf}.
7+
8+
\paragraph{Vision \& Expectation Management}
9+
10+
It captures our thinking around \myuline{the vision of \gls{ekg}},
11+
how it affects your business and what can be expected of it at certain levels of capability maturity.
12+
13+
\paragraph{\Glsfmtlongpl{nfr}}
14+
15+
The \gls{ekgmm} is therefore seen as the overall framework for all \enquote{\glspl{nfr}}\,---\,requirements\,---\,%
16+
clustered per capability\,---\,that are not \myuline{directly} related to any given "use case".
17+
18+
\paragraph{\glsfmtlong{uct}}
19+
20+
For instance, if it is your company's strategy to be able to have real-time risk-insights at all levels
21+
of your organization then we can separate the specific functional requirements of that very large "use case" from
22+
all the \glspl{nfr} that would come into place around your data management and governance practices, the state of
23+
your technology landscape, the culture of your organization and so forth.
24+
In this example, the use case "Real-time risk management"\,---\,as the top-level strategic use case\,---\,would be
25+
broken down into various "sub-use cases" resulting in a so-called \enquote{\glsfirst{uct}}.
26+
Each node in that tree represents some functionality\,---\,a capability so you will.
27+
How does this relate to the \gls{ekgmm}? Well, per use case in that tree structure you can determine how realistic
28+
it is to actually be able to implement that use case in relation to the level of maturity of the organization as a
29+
whole and more specifically in relation to any of the capabilities that are being covered in this document.
30+
31+
\paragraph{Use Cases replace Silos}
32+
33+
There is another major point to make about the \glsxtrfull{uct} is that it is the backbone component-structure
34+
of your \gls{ekg}.
35+
In a way you could see them as the \gls{ekg}'s equivalent of your current siloed application- and data-landscape.
36+
Rather than building a new silo everytime for every new use case, you would "build" new use cases in the \gls{ekg}.
37+
Use cases are "logical silos" in that sense. In a data-centric \gls{ekg} world, there are no more independent
38+
"applications" that are run as separate systems.
39+
Just this particular change alone has major implications on how things are organised.
40+
The \gls{ekgmm} covers these\,---\,and many other\,---\,implications.
41+
42+
\paragraph{Capabilities as use cases}
43+
44+
The \gls{ekgmm} is about the generic capabilities and how they may evolve over time and how some of them are
45+
required to be available at a certain level of maturity.
46+
That being said, almost every capabality that we describe in this document is in itself also a use case.
47+
Many if not most of these capabilities will more and more depend on high quality detailed and "holistic" data.
48+
49+
\paragraph{Other artifacts}
50+
51+
\begin{basedescript}{%
52+
\desclabelstyle{\multilinelabel}
53+
\desclabelwidth{3cm}
54+
}
55+
\item[EKG/Manifesto] The EKG/Manifesto is a combination of long term vision statements\,---\,the "Why"\,---\,%
56+
combined with the underlying principles for \gls{ekg}\,---\,the "How".
57+
\item[EKG/Method] The assumption is that each organization in a data-intensive industry will end up owning their
58+
own \gls{ekg}\,---\,possibly shared across organizations\,---\,and therefore requires
59+
oversight by a group of people\,---\,however organised\,---\,that we call
60+
the \gls{ekg:coe}.
61+
62+
EKG/Method describes all the practices of the \gls{ekg:coe}, from inception to production.
63+
\item[EKG/Catalog] The EKG/Catalog describes all the common use cases (and some of their "sub-use cases")
64+
for \gls{ekg}. The goal is to also publish these use cases on the ekgf.org website under the
65+
so-called "use case portal" and make them available for download as modules, basically
66+
the same kind of ecosystem of reusable components as any other successful technology-stack
67+
has.
68+
This is comparable to what \href{https://central.sonatype.org/}{"Maven Central"} is for the
69+
Java world or what \href{https://docs.npmjs.com/about-npm}{"npmjs.com"} is for the
70+
JavaScript world.
71+
\end{basedescript}
72+
73+
\paragraph{Use Case Central}
74+
75+
One of the primary goals that the foundation is working towards to is\'---\'as briefly mentioned above\'---\'to publish
76+
use cases on the \href{https://ekgf.org}{ekgf.org} website, initially just as a searchable catalog of use cases,
77+
just text basically, but soon after as a graph, as part of an \gls{ekg}.
78+
Some members of the foundation\,---\,in particular \agnos and \eccenca\,---\,already have \gls{ekg} infrastructure
79+
running in production that allows them to run "no-code" or "\gls{low-code}" use cases as full transactional applications.
80+
The idea is to standardise this, to publish use cases as "reusable components", with all their dependencies, ready
81+
for immediate deployment, just like one would do in the Java/JVM world or in the JavaScript world or with any
82+
other successful technology stack.
83+
84+
\paragraph{Portals}
85+
86+
The foundation is still in its start-up phase, depending on its corporate members for funding
87+
(see Appendix \nameref{appendix:ekgf-corporate-members}).
88+
Plans are to invest in the development of a more advanced website that consists of various "portals" focussing
89+
on serving a specific need for a specific audience:
90+
91+
\begin{basedescript}{%
92+
\desclabelstyle{\multilinelabel}
93+
\desclabelwidth{2cm}
94+
}
95+
\item[Use Cases]
96+
\begin{itemize}
97+
\item Short term:
98+
\begin{itemize}
99+
\item Audience: Business Executive, Vendor
100+
\begin{itemize}
101+
\item Understand the business problems that can, and have, been addressed;
102+
\item Use a framework for structuring projects
103+
\item Get directed to relevant reuse points in other portals (e.g. for ontologies)
104+
\end{itemize}
105+
\end{itemize}
106+
\item Long term:
107+
\begin{itemize}
108+
\item Audience: Executive, Vendor, Knowledge Graph Engineer
109+
\begin{itemize}
110+
\item Identify, select, download \& provision production-ready use cases.
111+
\end{itemize}
112+
\end{itemize}
113+
\end{itemize}
114+
\item[Best Practices]
115+
\begin{itemize}
116+
\item Audience: Project Lead, Consultant, any role in the \gls{ekg:coe}
117+
\begin{itemize}
118+
\item Reduce the risk and cost associated with new \gls{ekg} projects
119+
\end{itemize}
120+
\item Audience: Vendor
121+
\begin{itemize}
122+
\item understand how to develop, sell and deploy their products (and services)
123+
to maximize applicability and success
124+
\end{itemize}
125+
\end{itemize}
126+
\item[Software]
127+
\begin{itemize}
128+
\item Audience: Architect, Vendor, Academic
129+
\begin{itemize}
130+
\item Access reusable software curated for EKG purposes (may be hosted externally)
131+
\end{itemize}
132+
\item Audience: Vendor, Academic
133+
\begin{itemize}
134+
\item Position existing products or components to increase uptake
135+
\end{itemize}
136+
\end{itemize}
137+
\item[Ontologies]
138+
\begin{itemize}
139+
\item Audience: Modeler
140+
\begin{itemize}
141+
\item Assess ontologies curated as reusable for \gls{ekg} use cases
142+
\item Apply tooling to automate ontology development and measurement
143+
\end{itemize}
144+
\item Audience: Academic
145+
\begin{itemize}
146+
\item Access a set of ontologies for research, analysis, or extension
147+
\end{itemize}
148+
\end{itemize}
149+
\item[Datasets]
150+
\begin{itemize}
151+
\item Audience: Analyst
152+
\begin{itemize}
153+
\item Access reusable RDF resources curated for EKG purposes (may be hosted externally)
154+
\end{itemize}
155+
\item Audience: Analyst, Vendor
156+
\begin{itemize}
157+
\item Make use of data resources for demonstration and experimentation
158+
\end{itemize}
159+
\end{itemize}
160+
\item[Member Directory \& Services]
161+
\begin{itemize}
162+
\item Connect with people \& parties with the knowledge to help
163+
(see also appendix \nameref{appendix:ekgf-corporate-members})
164+
\item Promote your knowledge and skills
165+
\end{itemize}
166+
\end{basedescript}
167+
168+
\paragraph{Persona Stories}
169+
170+
The foundation recognises different types of "personas" that it needs to serve:
171+
172+
\begin{basedescript}{%
173+
\desclabelstyle{\multilinelabel}
174+
\desclabelwidth{2cm}
175+
}
176+
\item[\texttt{<as a>}] \texttt{<I want to>}
177+
\item[Business Executive] realize the benefits and minimize the risks of \gls{ekg} by having access to
178+
proven methods, best practices and a community of experts.
179+
\item[Vendor] make it easy for organizations to understand and successfully adopt my product across
180+
multiple industry sectors.
181+
\item[Modeler] have access to a proven and consistent set of deployable use cases,
182+
models \& ontologies that can be used with my organization’s \gls{ekg}.
183+
\item[Technical Architect] have access to components and interfaces with supporting technology architectures
184+
that I can assemble and deploy within my environment.
185+
\item[Consultant] have access to\,---\,and contribute to\,---\,\gls{ekg}-related best practices
186+
(e.g. \glsfmtshort{ekgmethod} \& \glsfmtshort{ekgmm}) as well as a community of
187+
potential customers and skilled associates.
188+
\item[Academic] The chance to make a meaningful and recognized contribution that builds upon
189+
frameworks to address pressing business needs.
190+
\item[\glsxtrshort{ekg} Engineer] be informed about best practices, role descriptions, education
191+
\& certifications.
192+
\end{basedescript}

‎ekg-mm/parts/0-intro.tex‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ \part{Intro}
88
% \renewcommand{\thesubsubsection}{\thesubsection.\arabic{subsubsection}}
99

1010
\input{../ekg-mm/chapters/ekg-mm-executive-summary.tex}
11+
\input{../ekg-mm/chapters/ekg-foundation.tex}
1112
%
1213
% Adding the "strategic objectives" chapter in draft mode
1314
%

0 commit comments

Comments
 (0)