Available online at www.sciencedirect.com
Available
Available online
online atat www.sciencedirect.com
www.sciencedirect.com
Available online at www.sciencedirect.com^ĐŝĞŶĐĞŝƌĞĐƚ
^ĐŝĞŶĐĞŝƌĞĐƚ
^ĐŝĞŶĐĞŝƌĞĐƚ
^ĐŝĞŶĐĞŝƌĞĐƚ
Available
onlineScienceat www.sciencedirect.com
Procedia Computer
00 (2023) 000–000
Procedia Computer Science 00 (2023) 000–000^ĐŝĞŶĐĞŝƌĞĐƚ
Procedia Computer
Science 00 (2023) 000–000^ĐŝĞŶĐĞŝƌĞĐƚ

www.elsevier.com/locate/procedia
www.elsevier.com/locate/procedia
www.elsevier.com/locate/procedia
www.elsevier.com/locate/procedia

Procedia Computer Science 225 (2023) 609–616

www.elsevier.com/locate/procedia
www.elsevier.com/locate/procedia

Available online at www.sciencedirect.com
Procedia Computer
00 (2023) 000–000
Available
online atScience
www.sciencedirect.com

ScienceDirect

Procedia Computer Science 00 (2023) 000–000
Procedia Computer Science 00 (2023) 000–000

27th International Conference on Knowledge-Based and Intelligent Information & Engineering Systems
27th
and(KES 2023)
27th International
International Conference
Conference onon Knowledge-Based
Knowledge-Basedand Intelligent
Intelligent Information
Information && Engineering
Engineering Systems
Systems
27th International Conference on Knowledge-Basedand Intelligent Information & Engineering Systems(KES(KES 2023)
2023)(KES 2023)
27th International
Conferenceon Knowledge-BasedandUnicage
Intelligent Information& Engineering Systems
Data
DrivenProcess-BasedArchitecture
27th International
Conferenceon Knowledge-BasedandUnicage
Intelligent Information& Engineering Systems
Data
DrivenProcess-BasedArchitecture(KES 2023)
Data
DrivenProcess-BasedUnicage
Architecture(KES 2023)
Data Driven aProcess-BasedUnicage
Architectureba,b,Nobuaki Tounaka , Shuichiro Yamamoto , Buyanjargal Shirnen *abaProcess-Basedb, Buyanjargal
a,b, *
NobuakiTounaka, Shuichiro Yamamoto
Shirnena,b,
Data
DrivenUnicage
Architecture
NobuakiTounakaa, Shuichirob, Buyanjargal
a,b, *
Unversal Shell
ProgrammingLaboratory Ltd.,Yamamoto
3-3-3 Nishishimbashi,
Minato-ku ,Tokyo Shirnen
105-0003, Japan
NobuakiTounaka,
Shuichiro
Yamamoto,
Buyanjargal
Shirnen*
Data
DrivenProcess-BasedUnicage
Architecture
IPUT in Nagoyo,
4-27-1 Meieki,
Nakamura-ku,
Nagoya450-0002,
Japan105-0003, Japan
Unversal Shell ProgrammingLaboratory
Ltd., 3-3-3
Nishishimbashi,
Minato-ku,TokyoUnversal Shell ProgrammingLaboratory
Ltd.,
3-3-3
Nishishimbashi,
Minato-ku,Tokyo105-0003,
Japan
a LaboratorybNagoyaa,b,
IPUT in Nagoyo,
4-27-1 Meieki,
Nakamura-ku,
450-0002,
JapanShirnen
Unversal Shell
ProgrammingLtd.,Yamamoto
3-3-3
Nishishimbashi,
Minato-ku,TokyoNobuakiTounaka, Shuichiro, Buyanjargal
IPUT in Nagoyo,
4-27-1 Meieki,
Nakamura-ku,
Nagoya450-0002,
Japan105-0003, Japan *a
IPUT in Nagoyo,
4-27-1 Meieki,
Nakamura-ku, b
Nagoya450-0002, JapanShirnena,b, *Nobuaki Tounaka, Shuichiro
Yamamoto, Buyanjargal
a

b

a
a
a
a

b
b
b
b

Unversal Shell Programming Laboratory Ltd., 3-3-3 Nishishimbashi, Minato-ku ,Tokyo 105-0003, Japanaa
Abstract
IPUT in Nagoyo,
4-27-1 Meieki,
Nakamura-ku,
Nagoya450-0002,
Japan105-0003, Japan
Unversal Shell bProgrammingLaboratory
Ltd., 3-3-3
Nishishimbashi,
Minato-ku,Tokyob
IPUT in Nagoyo, 4-27-1 Meieki, Nakamura-ku, Nagoya 450-0002, Japan
Abstract
Abstract
Digital transformation necessitates the creation of business value or innovation using digital technology in every industry. Enterprises are
Abstract
facing an
unprecedented
business environment
andcompetition
forresources andmarket,which
forces them
to beindustry.
more adaptive.
Digitalnecessitates
the
of
value
or
using
digitaltechnology
inEnterprises
areDigital transformationtransformationnecessitates
the creation
creationof businessbusinessvaluealso
or innovation
innovation
using
digitaltechnology
in everyeverysystem
industry.
Enterprises
Consequently,
their Enterprise
Information
Systems(EIS) must
be adaptive.
The
conventional
informationarchitecture
hasarehigh
Abstract
facingunprecedented
business
environment
andcompetition
andmarket,which
forces
them
to
be
more
adaptive.
Digitalantransformationnecessitates
the creationof businessvalueforor resources
innovation
using
digitaltechnology
in everyindustry.
Enterprises
arefacinganunprecedented
business
environment
andcompetition
forresourcesandmarket,which
forces
them
to
be
more
adaptive.
dependencies
betweentheirapplication
components
torealizetheloosely-coupled,
microservice
applicationarchitecture
required forhas highAbstract
Consequently,
theirEnterprise
Information
Systems
(EIS)
must
also
be
adaptive.
The
conventional
information
systemarchitecture
facinganunprecedented
business
environment
andcompetition
forresourcesandmarket,which
forces
them
to
be
more
adaptive.
Consequently,Intheir
Information
Systems (EIS) mustalso be adaptive.
The
conventional
information
systemarchitecture
hasconsists
highadaptiveness.
thisEnterprise
paper,
we
proposeacomponents
loosely-coupled,
process-based
enterprise
information
systemarchitecture- Unicage- whichdependencies
betweentheirapplicationtotheloosely-coupled,
microservice
applicationarchitecture
requiredforConsequently,
theirEnterprise
Information
Systems
(EIS)
must
also
be adaptive.
The
conventional
information
systemarchitecture
highDigitaltransformationnecessitates
the creationof businessvalueor
innovation
using
digitaltechnology
in everyindustry.
Enterprises
aredependencies
betweentheirapplication
components
to realize
realizetheloosely-coupled,
microservice
applicationarchitecture
required
forhasofbusiness,application,
data,
and
technology
architectures,
especiallyforenterpriseEnterprise
Resource
Planning
system,
with
only
input
and
outputadaptiveness.
In
thispaper,
we
proposealoosely-coupled,
process-based
information
systemarchitecture
Unicagewhich
consists
facinganunprecedented
business
environment
andcompetition
forresourcesandmarket,which
forces
them
to
be
more
adaptive.
Digitaldependencies
transformation
betweennecessitates
theirapplicationthecreationcomponentsofbusinesstorealize
value
the
or
loosely-coupled,innovation
using
microservice
digitaltechnology
applicationinevery
architectureindustry.
requiredEnterprisesforareadaptiveness.
In
thispaper,
we
proposealoosely-coupled,
process-based
enterprise
information
systemarchitecture
Unicagewhich
consists
data-based
building
blocks.
Asanda result,
enables
Full
Cycle
Development.
We
also
proposeaPlanningmodel
forthetoarchitectureusing
ArchiMate.
ofbusiness,application,
data,
technology
architectures,
especiallyEnterprise
Resource
system,
with
only
input
and
outputConsequently,
Information
Systems
(EIS)
must
also
befor
adaptive.
conventional
information
systemarchitecturehighfacingadaptiveness.
an unprecedented
Intheir
thisEnterprise
paper,
business
weproposeenvironment
ait loosely-coupled,
anda competition
process-based
for resources
enterpriseand Themarket,information
which
systemforcesthemarchitecturebemore- Unicage
adaptive.
- whichconsistsofbusiness,application,
data,
and
technology
architectures,
especiallyforEnterprise
Resource
Planning
system,
with
only
input
andhasoutputdata-based
building
blocks.
Asaresult,itenables
a
Full
Cycle
Development.
We
also
propose
a
model
for
the
architectureusing
ArchiMate.
Consequently,ofbusiness,application,
theirEnterprise
data,
and
Information
technology
Systemsarchitectures,
(EIS)
must
especially
also
be
for
adaptive.
Enterprise
The
Resource
conventional
Planning
information
system,systemwith
onlyarchitecture
input
and
has
outputhighdependencies
betweentheirapplication
components
torealizetheloosely-coupled,
microservice
applicationarchitecture
requiredfordata-based
building
blocks.
Asaresult,itenables
a
Full
Cycle
Development.
We
also
propose
a
model
for
the
architectureusing
ArchiMate.
© 2023 The
Authors.
Publishedby Elsevier
B.V.
Keywords:
Data
DrivenEnterpriseArchitecture,
Microservice
Architecture,
Data Driven
Process
Design, TOGAF,
ArchiMate.
adaptiveness.
Inthisblocks.
paper,
we
proposeait
loosely-coupled,
process-based
enterprise
informationarchitecture- Unicage- whichdependencies
data-based
building
betweentheirAsapplicationa result,
components
enablesa Fullto realize
Cycle
the
Development.
loosely-coupled,We
also
microservice
proposea systemmodelapplicationforthearchitecturearchitecture
requiredusing
ArchiMate.
for consists
This
is anData
open
accessarticleunder
CC
BY-NC-ND
license(https://creativecommons.org/licenses/by-nc-nd/4.0)
Keywords:
EnterpriseArchitecture,
Microservice
Architecture,
Data
DrivenProcess
Design, TOGAF,ofbusiness,application,
data,
technology
architectures,
especiallyforEnterprise
Resource
Planning
system, with- Unicage
only input
and output
adaptiveness.
InDriven
thispaper,
weand
proposeatheloosely-coupled,
process-based
enterprise
information
systemArchiMate.
architecture- whichconsists
Keywords:
Data
DrivenEnterpriseArchitecture,
Microservice
Architecture,
Data
DrivenProcess
Design, TOGAF,
ArchiMate.
Peer-review
underresponsibility
ofit enables
thescientificcommittee
ofDriven
the27th
Conference
on only
Knowledge
BasedofKeywords:
business,Data
application,
Drivenblocks.
Enterprisedata,
Architecture,technology
Microservice
architectures,
especially
DataforEnterprise
Process
Resource
Design, TOGAF,
ArchiMate.
system,with
input
output anddata-based
building
Asanda result,
a FullArchitecture,
Cycle
Development.
We
alsoInternational
proposeaPlanningmodel
forthe architectureusing andArchiMate.
data-based
building
blocks.and
As aEngineeringresult, it enables
a Full Cycle Development. We also propose a model for the architecture using ArchiMate.
Intelligent
Information
Systems
1.
Introduction

Keywords:
Data Driven Enterprise Architecture, Microservice Architecture, Data Driven Process Design, TOGAF, ArchiMate.
1.
Introduction
1.
Introduction
Keywords:
Data Driven Enterprise Architecture, Microservice Architecture, Data Driven Process Design, TOGAF, ArchiMate.

1. Introduction
The objective of the latest EA is business transformation, not the overall optimization of IT systems. Furthermore, since the
The
the
EA
not
IT
Furthermore,
since
the
objectiveof EA isoftransformation,
thetransformation,business capability-based
EA optimization
development ofmethodstarts implementing
The objective
objective
ofbusinessthe latest
latestEA isis businessbusinesstransformation,
not thethe overall
overall
optimizationofIT systems.
systems.
Furthermore, parts
since thatthe1.
Introduction
The objective
ofbusinessthe latest
EA is Activities
businesstransformation,
not the overall
optimizationofIT
systems.
Furthermore,since thattheobjectiveofEA
istransformation,thebusiness
capability-based
EA
development
methodstartsimplementing
parts
generatebusinessvalue
instages.
thatdonotgeneratebusiness
value
are
not
recommended.
Thus,architecture
objectiveof EA is business transformation, the business capability-based EA development method starts implementing parts that1.
Introduction
objectiveof EA
iscontinuous,
businesstransformation,
the thatbusiness
capability-based
EA development
methodstarts (ADM)
implementing
partsoverthat
generatebusinessvalue
instages.
Activities
donotgeneratebusiness
value
are
not
recommended.
Thus,architecturedevelopment
isacyclicalprocess,
andinexecutingtheArchitecture
Development
Methodrepeatedly
generatebusinessofvalue
in stages.
that do not generatebusinessoptimization
value are notrecommended.
Thus, architecture
The objective
the latest
EA
is Activities
businesstransformation,
not thethe Architecture
overallof IT
systems.(ADM)
Furthermore,sinceoverthegeneratebusinessvalue
inActivities
that
do anot
generatebusinessvalue
aremicroservice
notrecommended.
Thus,architecturedevelopment
isaa continuous,
cyclicalprocess,andDevelopment
Methodrepeatedly
time.
accepts
thestages.
iterativemodel,
which
criticalofoptimization
Agile.
In
architecture,
microservices
development
is[3]continuous,
cyclicalprocess,
and ininis executing
executingtheDevelopment(ADM)
repeatedly
TheTOGAF
objectiveofthe latest
EA
is business
transformation,
notcomponent
the Architecture
overallof
IT Method
systems.
Furthermore,sinceovertheobjectiveofEA
isbusinesstransformation,thebusiness
capability-based
EA
development
methodstartsimplementing
parts
that
developmentis[3]a continuous,
cyclical model,
process,
andcoupledinis executing
the Architecture
Development
Method
(ADM)
over
time.
TOGAF
acceptstheiterative
which
aa criticalcomponent
Agile.
In
microservice
architecture,
microservices
thatcorrespondtobusiness
capabilities
are loosely
to promote
DX.EA
Toof
achieve
this,itmethod
is necessary
todesignrepeatedly
andimplement
time.
TOGAF
[3]
acceptstheiterativemodel,
whichiscriticalcomponentof
Agile.
In
microservice
architecture,
microservices
objectiveofEA
isbusinesstransformation,thebusiness
capability-based
development
startsimplementing
parts
that
generatebusinessvalue instages.
Activities
thatcoupleddonotbusinessvalue this,aremicroservice
notrecommended.
Thus,architecture
time.
TOGAF
[3]
acceptstheiterativemodel,
which
is aarchitectures,
criticalcomponentofachieve
Agile.
In
architecture,
microservices
thattodatabusiness
capabilities
aretogenerate
promote
DX.
To
it
is
to
designimplement
overallbusiness,andinapplication,
andloosely
technology
which
consisting
EA as suggested
byand
TOGAF
core
that correspondcorrespondbusiness
capabilities
arelooselypromoteDX.
Toareachieve
this,itthe
is necessary
necessarytodesignandimplement
generatebusinessvalue
stages.
Activities
thatdoexecuting
nottogeneratebusinessvalue
are not
recommended.
Thus,architecturedevelopment
is toa datacontinuous,
cyclicalprocess,
andcoupledinthe Architecture
Development
Method(ADM)
repeatedly
over
that
correspondtobusiness
capabilities
arelooselycoupledtopromoteDX.
To
achievethis,itisnecessarytodesignandimplement
overallbusiness,andapplication,andtechnology
architectures,
which
are
consisting
the
EA
as
suggested
by
TOGAF
core
architecture
layers,inthelooselycoupledmanner.
This
type
of
architecture
enablestheflexibility
toiterative
development
suchasoverallbusiness,data
andapplication,andtechnology
architectures,
which
are
consisting
the
EA
as
suggested
by
TOGAF
core
developmentis[3]a continuous,
cyclical model,
process,which
and inis executing
the Architecture
Development
Method(ADM) repeatedly
over
time.
TOGAF
acceptstheiterative
aarchitectures,
criticalcomponentof Agile.
In
microservice
architecture,overallbusiness,dataandbecause
application,andmanner.
technology
which
are
consisting
the theEAtobusinessasiterative
suggestedby microservices
TOGAF
core
architecture
layers,inthelooselycoupled
This
type
of
architecture
enablestheflexibility
development
such
as
Agile
or
TOGAF
ADM
it
considers
only
input
and
output(IO)
information
to/from
process.
The
IO
data
architecture
layers,inthelooselycoupledmanner.
This
type
of
architecture
enablestheflexibility
toiterative
development
such
as
time.
TOGAF
[3]
acceptstheiterativemodel,
whichisacriticalcomponentof
Agile.
In
microservice
architecture,
microservices
thatcorrespondto businesscapabilities
aremanner.
looselycoupledtoof
promoteDX.informationToachieve
this,
it is necessary
to designandTheimplementarchitecture
layers,inalsothebecause
looselycoupledThis
typearchitecture
enablestheflexibility
tobusiness
iterative
development
such
as
Agile
or
TOGAF
ADM
it
considers
only
input
and
output(IO)
to/fromtheprocess.
IO
data
drivenarchitectureadvantages
systemdevelopers
toachieve
a
full
cycle
systemdevelopment
since
itrequiresonly
Agileorbusiness,
TOGAF
ADM
becauseit considers
onlycoupled
inputarchitectures,andoutput (IO)
to/fromthebusiness
process.
The
IO coredata
thatcorrespondtodatabusiness
capabilities
areloosely
to promote
DX.information
Toareachieve
this,itthe
is necessary
to designand
implement
overallandapplication,andtechnology
which
consistingEA
assuggested
by
TOGAF
Agile
orarchitecture
TOGAF
ADM
becauseitevery
considers
only
input and
output(IO)
information
to/from
the application
businesssince
process.
The IO only
data
drivenalso
advantages
systemdevelopers
toachieve
a
full
cycle
systemdevelopment
itrequires
understanding
input
and
outputinbusiness
processwhich
directly
maps
to
an
IO
data-based
component.
driven architectureadvantages
systemdevelopers
toofachievea fullenables
cycle
systemdevelopmentsince
it requires
only
overallbusiness,data
andloosely
application,andmanner.
technology
architectures,
which
are
consistingtheEAtoasiterative
suggested
by
TOGAF
core
architecture
layers,inalsothecoupledThis typearchitecturetheflexibility
development
suchasdrivenarchitecturealso
advantages
systemdevelopers
to achieve
aBasedfull cycle
systemdevelopment
sincerequiresonly
understanding
outputineverybusiness
processwhich
directly
maps
to
an
IO
data-based
application
component.
Basedon layers,
theinputfactinandmentioned
above,
we
proposeDatatype
DrivenProcess(DDPB)
Architecture
consisting
ofitloosely
coupledunderstanding
input
and
every
business
processwhich
directlymaps
toan the
IO to/from
data-based
component.
architecture
theoutputlooselyin
coupledmanner.
This
ofoutputarchitecture
enables
flexibility
toapplication
iterative
development
such
as
Agile
or
TOGAF
ADM
becauseitconsiders
only
input
and
(IO)
information
thebusiness
process.
The
IO
data
understanding
input
and
outputbusiness,ineverywebusiness
processwhich
directlymaps toanlayers.
IO data-based
application
Basedonmentioned
above,
propose
Data
Process
Based(DDPB)
Architecture
consistingof
coupledbuilding
blocksthatcomposeandDriventechnology
architecture
We alsoillustrate
acomponent.
practicaltoBasedon thethe factfactmentioned
above,
weapplication,
propose
Data
DrivenProcess(DDPB)
Architecture
consisting
ofitloosely
looselycoupledAgileorarchitecture
TOGAF
ADM
becauseit considers
only
input
and
output(IO)
information
to/fromthe businessprocess.
ThemodelIO onlydata
drivenalso
advantages
systemdevelopers
to achieve
aBasedfull
cycle
systemdevelopment
sincerequires
Based
onthe
thearchitecture
fact
mentioned
above,
weapplication,
propose
Data
DrivenProcess
Based(DDPB)
Architecture
consistingof loosely
coupledbuilding
blocksthatcomposebusiness,andtechnology
architecture
layers.
We
alsoillustrateapractical
model
toimplement
withArchiMate[1].
buildingarchitecture
blocksinputthat andcomposebusiness,application,
and whichtechnology
architecture
Wedevelopment
also illustrate
acomponent.
practical
model
todrivenalso
advantages
systemdevelopers
to achievea mapsfull cycle
systemsince
it requires
only
understanding
outputineverybusiness
process
directly
to anlayers.
IO
data-based
buildingthat thecomposebusiness,application,and technology
architecture
layers.
We alsoapplication
illustrate
a practicalmodel toimplementthearchitecturewithArchiMateIn the blocks
following,
relatedresearchwill[1].
be explainedin Section
2. maps
Next, toSection3data-based
proposes
DDPB
EnterpriseArchitecture
implementthearchitecturewithArchiMate[1].
understanding
input
and
outputineverybusiness
processwhich
directlyan
IO
application
component.
Based
on
the
fact
mentioned
above,
we
propose
Data
DrivenProcess
Based(DDPB)
Architecture
consistingoflooselycoupledimplement
the architecturewithArchiMate
[1].
In
the
relatedresearch
will
be
in
2.
Next,
Section3
proposes
DDPB EnterpriseArchitecturemodel
by following,ArchiMate.
Then,
Section
4 explains
concreteapplication
exampleof the DDPB
architecture.
Section5 describes
theIn thethefollowing,
relatedresearchwill
beaexplained
explained
in Section
Section2.
Next, (DDPB)
Section
3Architecture
proposes
EnterpriseArchitecture
Basedon
the fact
mentioned
above,
weapplication,
propose
Data
ProcessBasedconsistingof loosely
coupledbuilding
blocksthat thecomposebusiness,
andDriventechnology
architecture
layers.
Wearchitecture.
also DDPB
illustrate
a practicalmodel
toIn thefollowing,therelatedresearchwill
beaexplainedin Section
2.
Next, Section
3 proposes
DDPB
EnterpriseArchitecturemodelbyArchiMate.
Then,
Section4
explains
concreteapplication
exampleofthe
DDPB
Section5
describes
thediscussion,
andSection6
summarizes
this
paper
and
mentions
futureissues.
model byblocks
ArchiMate.
Then,with
Section
4 explains
concreteapplication architecture
example of the
DDPB
Section5 describes
buildingthat compose
business,application,and technology
layers.
Wearchitecture.
also illustrate
a practicalmodelthetoimplementthearchitecture
ArchiMate[1]. aaandmodel
by ArchiMate.
Then,
Section4 thisexplains
concreteapplication
example of the DDPB architecture. Section 5 describes thediscussion,
andSection6
summarizes
paper
mentions
futureissues.
discussion,andarchitecture
Sectionsummarizes
thiswillpaper
and mentions
future issues.
implementthewith researchArchiMate[1].
In the following,
the 66related
be explainedin Section
2. Next, Section 3 proposes DDPB Enterprise Architecture
discussion,and Section
summarizes
this paper
and mentions
future issues.
Inthefollowing,therelatedresearchwillbeexplained
inSection
Next, Section
3 proposes
DDPB EnterpriseArchitecture
model by ArchiMate. Then, Section 4 explains a concrete application 2.
exampleof the DDPB
architecture.
Section 5 describes
the
model
by ArchiMate.
Section 4 this
explains
concreteapplication
example of the DDPB architecture. Section 5 describes thediscussion,and SectionThen,
6 summarizes
paperaandmentions
future issues.
discussion,and author.
Section
6 +81-3-3432-1174;
summarizes thisfax:
paper
and mentions future issues.
* CorrespondingTel.:+81-3-3432-1174.
address:author.
s-buyan@usp-lab.com* E-mail
Corresponding
Tel.: +81-3-3432-1174; fax: +81-3-3432-1174.
* Corresponding author. Tel.: +81-3-3432-1174; fax: +81-3-3432-1174.
E-mail address:author.
s-buyan@usp-lab.com
Tel.: +81-3-3432-1174; fax: +81-3-3432-1174.
* Corresponding
E-mail address: s-buyan@usp-lab.com
1877-0509© 2023 The
Authors. Published by ELSEVIER B.V.
E-mail address:s-buyan@usp-lab.com
This
is an open
accessunder
the CC BY-NC-ND
license* Corresponding
author.
Tel.:+81-3-3432-1174;
fax: +81-3-3432-1174.
1877-0509© 2023
Thearticle
Authors.
Publishedby ELSEVIER
B.V.(https://creativecommons.org/licenses/by-nc-nd/4.0)
1877-0509 © 2023 The Authors. Published by ELSEVIER B.V.
Peer-review
responsibilityofthescientificcommittee
ofB.V.
KES
International
E-mailaddress:s-buyan@usp-lab.com* Corresponding
author.
Tel.:+81-3-3432-1174;
fax:+81-3-3432-1174.
This
is an open
accessarticleunder
CC BY-NC-ND
license(https://creativecommons.org/licenses/by-nc-nd/4.0)
1877-0509
©2023
2023
The
Authors.
PublishedbyElsevier
1877-0509©underThe
Authors.
Publishedby ELSEVIER
B.V.
This
is an open
accessarticleunderthe
CC BY-NC-ND
license(https://creativecommons.org/licenses/by-nc-nd/4.0)
E-mailaddress:s-buyan@usp-lab.com
Peer-review
underresponsibilityof thescientificcommittee
of KESInternational
This
open
accessunder
the CCBY-NC-ND
license (https://creativecommons.org/licenses/by-nc-nd/4.0)
This
isisanan
open
accessarticlearticle
under
CC BY-NC-ND
license(https://creativecommons.org/licenses/by-nc-nd/4.0)
thePeer-review
underresponsibilityof thescientificcommittee
of KESInternational
1877-0509©under
2023
The Authors.
Published
byofELSEVIER
B.V.
Peer-review
underresponsibilitythescientificPeer-review
responsibilityofthe scientificcommittee
of KEScommittee
International of the 27th International Conference on Knowledge Based
1877-0509© 2023
The
Authors.
Publishedby
ELSEVIER
B.V.
This
an openaccessarticleundertheandCC BY-NC-ND
license(https://creativecommons.org/licenses/by-nc-nd/4.0)
andisIntelligent
Information
Engineering
Systems
Peer-review
underresponsibilityof the scientificcommittee
of KESInternationalThis
is an open
accessarticle under
CC BY-NC-ND
license(https://creativecommons.org/licenses/by-nc-nd/4.0)
10.1016/j.procs.2023.10.046
Peer-review under responsibility of the scientific committee of KES International

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616

610

Author name / Procedia Computer Science 00 (2023) 000–000

2. Related work
Steven H. Spewak [2] suggested a Business-Driven or Data-Driven Information System Architecture as Enterprise Architecture
Planning (EAP). It recommends that data be defined before applications, and data dependency determines the sequence for
implementing application systems. Data must be provided at a reasonable, affordable cost. The DBMS is merely a tool for accessing
and storing data and simply using it cannot fulfill the promises of Database Management Systems. With EAP, the first architecture
defines all the data needed to support the business. When that is completed, the second architecture defines the applications needed
to manage that data.
TOGAF [3] suggests Architecture Development Method (ADM) which is iterative, over the whole process within phases in
Requirements Management. In the ADM, phase C involves Information Systems Architectures, referring to Steven Spewak's
Enterprise Architecture Planning (EAP) as a data-driven approach.
Yamamoto [4] proposed a concrete evaluation framework to compare EA frameworks and concluded that TOGAF is the mostpowerful EA framework. However, for the model and method features, TOGAF lacks clear description on model and methodarchitects who conduct tailoring of model and method for organizations, although tailoring tasks are explained.
TOGAF [3] points out that the majority of Enterprise Architecture frameworks focus on the specific set of deliverables while
relatively silent about the methods to be used to generate them.
Yamamoto [5] proposed the approach to visualize the business value, business model, and business process using ArchiMate.
In the approach, Yamamoto proposed the integrated models in ArchiMate notation.
Yamamoto [6] proposed the Data Driven Process Design Method (DDPDM) which focuses on elimination of the businessprocess which does not creates business value or overlapping the process.
Netflex [7] proposed a model that says “Operate what you built” or a Full Cycle Software Development. It mentioned that the
purpose of the software life cycle is to optimize “time to value” by converting ideas into working products and services forcustomers. Developing and running a software service involves a full set of responsibilities, which can create inefficiencies acrossthe entire life cycle when segmented. Full Cycle Developers are responsible for the full software life cycle, from design to support,
by combining all of these ideas together into a single development team equipped with amazing developer productivity tools.
CRIBB [8], James P. Houghton [9], João M.P. Moreira [10] mentioned or evaluated the technology performance of Unicage
Architecture.
3. Data Driven Process-Based Unicage Architecture (UA)The UA architecture complies with TOGAF [3] and Table 1. describes its core building blocks for the core architecture layers
as in the TOGAF, to propose a practical model for EIS implementation. The ArchiMate metamodels based on TOGAF ArchiMate
Metamodels for the core layers are explained in the following chapters. As shown in Table 1., a business process design maps
directly to Application and Technology building blocks since each block is designed based on IO data or information, which allows
the Microservice Architecture and Full Cycle Development. Having the business process analyzed and designed means having thedata and application design ready at time, which allows efficiency of development cycle and the full cycle development available.
We here exclude the UA development method.
Table 1. Data Driven Process-Based Unicage Architecture (UA) Core Building BlockTOGAFUA CoreNote

Core Elements

Building Block Definition(IO: Input and Output)

Business Architecture

IO data-based business process

Consider a business process as a function with an input and output data;
The processes are connected through information or data only. Analyze
and design it with Data Driven Process Design Method [6].

Data Architecture

Name indexed text file

Conform to data architecture design principles, file and directoryindexing convention in the UA development method.

Application Architecture

IO data-based application component

Implement as-is business process into an application component. The
components are connected through data only as so the businessprocesses.

Technology Architecture

IO data-based command

A command is the smallest building block with the same IO data-based
structure as a business process and application component. The
command has a sophisticated single functionality to process an input
data, being able to be implemented by any programming language.

Architecture
Development Method

UA development method

Composed of Lean and Agile principles with UA, Full Cycle
Development, project management method, and programming standard
including error handle, low-code, code description, and directory tree
conventions.

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616
Author name / Procedia Computer Science 00 (2019) 000–000

611

Fig. 1. Business Architecture Metamodel in ArchiMate

3.1. Business Architecture Model in UA
The BA is along with TOGAF BA and the UA suggests the building block for implementation of business process. Fig 1.
illustrates the relationship between EA and EIS vendor, especially in terms of business process analysis and design. The UA has
principles in its EIS development.
••••

Principle 1: Profit oriented.
Principle 2: Goal oriented and goal optimized overall development process toward Principle 1.
Principle 3: Enterprise Architecture Development team be assembled of full cycle developers with a mission realizing Principle2.
Principle 4: Analyze and design every business process as an IO process.

The UA applies Data Driven Process Design Method [6] to analyze and design any business process conforming to Principle 4.
3.2. Data Architecture Model in UA
Based on the principles below, the entire data leaves a complete chronological record of the workings of EIS. This makes it
easier to find out the cause of a problem when it occurs, since all the workings of the system can be visualized retroactively. Table
2. shows the data type, their application, and the data management capability. Having the few data types and the data management
tool realized by data IO-based commands which are also used to realize an application component, allows an EIS developer lesslearning cost. Without using a middleware for data management, it also allows developers less learning and operation cost, andless cost for entire EIS development, which also supports EAP[2] suggestion.
•••

Principle 1: Allow redundancy, eliminate the unnecessary.
Principle 2: Any data will NOT be overwritten, updated, or deleted, but spawned.
Principle 3: Avoid data dependency.
Table 2. Data type in UA
Data type

Artifact

Application

Data management

Logical/layout data

Plain text file

Design, Coding, Documentation

Data IO-based software commands

Data

Plain text fileBusiness application

Data IO-based software commands

Media

BinaryBusiness application

Data IO-based software commands

612

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616

Author name / Procedia Computer Science 00 (2023) 000–000

The data architecture metamodel for the UA is depicted in Fig 2. which is along with the TOGAF metamodel.

Fig. 2. Data Architecture Metamodel in ArchiMate

3.3. Application Architecture Model in UA
An application component consists of component, liner, and command as shown in Fig. 3. A liner is a collection of commands
which are connected by Unix Pipe and it expresses a stage that comprises a application component or a business process. Any
application, liner, or command is connected through data object only. In other words, the application architecture is Microservice
Architecture or loosely coupled. An IO-based application component matches its serving business process in structure with thesame IO data, which implies that the business process design is ready so is the application design. The application component also
conforms to the following principles in terms of code understandability, code simplicity, data management, and system
maintenance.
••••

Principle 1: Write a description for input and output file layout into/from a command.
Principle 2: Write a single command with input data in a line.
Principle 3: Write a description for each liner and application component/business process.
Principle 4: Applications that create data should be implemented before applications that use data.

The application component realized by the UA meets the following criterion that EAP [2] suggests, due to the IO data-based
microservice application and technology architecture.
•••

Criterion 1: It should be understandable. The application definitions make sense and are easily understoodby people throughout the enterprise.
Criterion 2: It should be complete. Applications support most business functions and every data entity is being
managed; and it should be consistent with no overlap or duplication of application capabilities.
Criterion 3: It should be stable. Each application definition is based solely on the business model and data architecture andis independent of who uses the application, how the application works, where the application is located, or when the application
is operated.

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616
Author name / Procedia Computer Science 00 (2019) 000–000

613

Fig. 3. Application Architecture Metamodel in ArchiMate

3.4. Technology Architecture Model in UA
Fig. 4 shows the Technology Architecture Model in which the IO data-based command lies at its core. The commands are
implemented with the core libraries of an operation system based on POSIX (Portable Operating System Interface). The command
can be implemented in any programming language and it executes sophisticated data processing algorithm while providing simple
coding syntax or interface such as below. The command serves as a software cushion implementing complex algorithm which may
take a long line of codes if it is implemented in a computer programming language.
•

Command syntax: {command}, {parameters}, {data}

The command or tool must comply with the following principles.
• Principle 1: Use only core and sophisticated POSIX libraries to implement the command.
• Principle 2: Keep the command syntax normalized as in the command syntax above.
• Principle 3: Keep the number of commands as few as possible. Thus, try combination of commands to solve any required dataprocessing before creating a new command.
In appreciation to the software cushion and principles above, the Technology Architecture in UA meets the criteria that EAP [2]suggests to apply open-systems concepts, meaning that operating systems should be as follow.
• Portable: run across multiple vendor platforms.
• Scalable: run across a wide power range from small to large computers.
• Interoperable: run in a heterogeneous environment.
• Compatible: preserve the investment in existing software and enable technology advances to be integrated with othercomponents.
Table 3. explains the taxonomy of a command set and Fig 4. proposes the technology architecture model in ArchiMate.

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616

614

Author name / Procedia Computer Science 00 (2023) 000–000
Table 3. IO Data-based Command category
Category name

Usage

Data manipulation

Data selection, delete, sort, join, split

Calculation

Mathematical, statistical, summary, comparison

Formatization

Data conversion, string manipulation

Input and output controller

Data retrieving, sending

System process control

Job control, system collaboration, access control

Fig. 4. Technology Architecture Metamodel in ArchiMate

4. Case study
4.1. Liquor Shop Problem
We apply the UA to a software design problem to demonstrate its adaptability, illustrating in ArchiMate. The problem is calleda Liquor Shop Problem [6] and it challenges a software design to realize an order and inventory management process in the shop
warehouse. Table 4. describes a flow of the management processes from receiving a container with liquor, dispatching an order of
liquor, and empty container management to contact a customer who places the order.
Table 4. Liquor shop order and inventory management process
Process actor

Business process

Warehouse manager

Receive a logistic container andplace it in the warehouse.

Hand over a container receipt to an order dispatcher.

Receive 10 orders per day.

Request a warehouse manager to pick up liquor from the container to fill
each order. The request is made through a telephone or a request form.

Order dispatcher

Output or input information to next process
A product receipt information: {Container number, Delivery date, Liquor
name, Amount of liquor}

An order information: {Liquor name, Amount, Delivery address}
A request form information: {Order number, Delivery address, Container
number, Liquor name, Amount, Mark for empty container}
Make a phone call to a customer if ordered liquor is out of inventory or
insufficient amount to fill and note that in an inventory shortage list.
A shortage list information: {Delivery address, Liquor name, shortage
amount}Order dispatcher

Checks if the liquor in the
shortage list is received.

Request a warehouse manager to fill the order in the shortage list once theinsufficient liquor is received.

Order dispatcher

Check a container if it isscheduled to be empty.

Notify the container information to the warehouse manager to keep thenumber of containers in the warehouse as few as possible.

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616
Author name / Procedia Computer Science 00 (2019) 000–000

615

We assume the business processes in the problem analyzed and optimized by DDPDM [6] which results in optimizing the numberof processes from 10 to 8, and have the result in the proposing ArchiMate metamodels.

Fig.5.Liquor shop order and inventory management processes in ArchiMate

Fig.6. A process implementation in the UA in ArchiMate

4.2. ArchiMate Notation
Fig 5. illustrates the order and inventory management processes after applying DDPDM [6]. For the simplicity of ArchiMate
model, the “Liquor brands in container” data object is duplicated. Fig 6. demonstrates the UA capability implementing a part ofthe processes.
5. Discussion
5.1. Novelty
The major enterprise architecture frameworks define a set of deliverables of the framework while a practical implementation ofbuilding blocks is relatively mentioned less. This paper proposed the building blocks to implement the core architecture layers
recommended by TOGAF [3] and demonstrated its adaptability through a case study.
5.2. EffectivenessThe proposed architecture has been effectively applied to analyze business processes based on IO data and implement
application components directly mapping to the business processes, connecting through data only. It has also shown that thearchitecture is a microservice or loosely coupled architecture. The proposed metamodels along with TOGAF architecture layer
metamodels in ArchiMate has also used to demonstrate the adaptability of the architecture on the case study.

616

Nobuaki Tounaka et al. / Procedia Computer Science 225 (2023) 609–616

Author name / Procedia Computer Science 00 (2023) 000–000

5.3. Limitation
Although the proposed architecture has effectively applied to the case study with ArchiMate illustration, and adopted by many
enterprises, the architecture is designed for ERP, especially. An integrated ArchiMate metamodel for the entire architecture isneeded to illustrate. Furthermore, a quantitative evaluation on its effectiveness shall be conducted.
6. Conclusion
In this paper, we proposed the data driven enterprise architecture with practical implementation blocks with ArchiMate
metamodels. Future work includes more case studies illustrated with proposed ArchiMate models and designing an integrated
ArchiMate metamodel for the entire architecture.

References[1] Phillip Beauvoir & Jean-Baptiste Sarrodie. (2022) “Archi -archimate modelling”, Archi version:4.9.3 supporting the ArchiMate® 3.1 language.
[2] Steven H. Spewak and Steven C. Hill. (2008) “Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology”, John Wiley& Sons, Inc.
[3] The Open Group. (2018) “The TOGAF® Standard, Version 9.2”
[4] Shuichiro Yamamoto, Nada Ibrahem Olayan, Shuji Morisaki. (2018) “Another Look at Enterprise Architecture Framework”, Journal of Business Theory andPractice: Vol. 6, No. 2, 2018.
[5] Shuichiro Yamamoto. (2020) “A DX Visualization Approach Using ArchiMate”, IPSJ SIG Technical Report: Vol.2020-SE-204 No.18.
[6] Shuichiro Yamamoto, Junko Hosomi. (2022) “A Proposal on Data Driven Process Design Method”, IEICE Technical Report KBSE2022-24: vol. 122, no.
139,79-84.
[7] Philip Fisher-Ogden, Greg Burrell, and Dianne Marsh. (2018) “Full Cycle Developers at Netflix – Operate What You Build”, Netflix Technology Blog.
[8] COMPUTATIONAL RESEARCH in BOSTON and BEYOND (CRIBB). (2013) “How to Analyze 50 Billion Records in Less than a Second without Hadoop
or Big Iron”, https://math.mit.edu/crib/2013/aug2.html[9] James P. Houghton et al. (2017) “Tracking the evolution of conversational clusters in social media”, https://doi.org/10.1177/0049124117729705[10] João M.P. MoreiraHelena GalhardasHelena GalhardasMiguel PardalMiguel Pardal. (2018) “LeanBench: comparing software stacks for batch and query
processing of IoT data”, DOI: 10.1016/j.procs.2018.04.067