<s>
In	O
information	O
systems	O
,	O
applications	B-Architecture
architecture	I-Architecture
or	O
application	B-Architecture
architecture	I-Architecture
is	O
one	O
of	O
several	O
architecture	B-Architecture
domains	I-Architecture
that	O
form	O
the	O
pillars	O
of	O
an	O
enterprise	O
architecture	O
(	O
EA	O
)	O
.	O
</s>
<s>
An	O
applications	B-Architecture
architecture	I-Architecture
describes	O
the	O
behavior	O
of	O
applications	B-Application
used	O
in	O
a	O
business	O
,	O
focused	O
on	O
how	O
they	O
interact	O
with	O
each	O
other	O
and	O
with	O
users	O
.	O
</s>
<s>
It	O
is	O
focused	O
on	O
the	O
data	O
consumed	O
and	O
produced	O
by	O
applications	B-Application
rather	O
than	O
their	O
internal	O
structure	O
.	O
</s>
<s>
In	O
application	B-Application
portfolio	I-Application
management	I-Application
,	O
applications	B-Application
are	O
mapped	O
to	O
business	O
functions	O
and	O
processes	O
as	O
well	O
as	O
costs	O
,	O
functional	O
quality	O
and	O
technical	O
quality	O
in	O
order	O
to	O
assess	O
the	O
value	O
provided	O
.	O
</s>
<s>
The	O
applications	B-Architecture
architecture	I-Architecture
is	O
specified	O
on	O
the	O
basis	O
of	O
business	O
and	O
functional	O
requirements	O
.	O
</s>
<s>
This	O
involves	O
defining	O
the	O
interaction	O
between	O
application	B-Application
packages	I-Application
,	O
databases	O
,	O
and	O
middleware	B-General_Concept
systems	I-General_Concept
in	O
terms	O
of	O
functional	O
coverage	O
.	O
</s>
<s>
Applications	B-Architecture
architecture	I-Architecture
tries	O
to	O
ensure	O
the	O
suite	B-Application
of	I-Application
applications	I-Application
being	O
used	O
by	O
an	O
organization	O
to	O
create	O
the	O
composite	O
architecture	O
is	O
scalable	B-Architecture
,	O
reliable	O
,	O
available	O
and	O
manageable	O
.	O
</s>
<s>
Applications	B-Architecture
architecture	I-Architecture
defines	O
how	O
multiple	O
applications	B-Application
are	O
poised	O
to	O
work	O
together	O
.	O
</s>
<s>
It	O
is	O
different	O
from	O
software	B-Architecture
architecture	I-Architecture
,	O
which	O
deals	O
with	O
technical	O
designs	O
of	O
how	O
a	O
system	O
is	O
built	O
.	O
</s>
<s>
One	O
not	O
only	O
needs	O
to	O
understand	O
and	O
manage	O
the	O
dynamics	O
of	O
the	O
functionalities	O
the	O
composite	O
architecture	O
is	O
implementing	O
but	O
also	O
help	O
formulate	O
the	O
deployment	B-Application
strategy	O
and	O
keep	O
an	O
eye	O
out	O
for	O
technological	O
risks	O
that	O
could	O
jeopardize	O
the	O
growth	O
and/or	O
operations	O
of	O
the	O
organization	O
.	O
</s>
<s>
Applications	B-Architecture
architecture	I-Architecture
strategy	O
involves	O
ensuring	O
the	O
applications	B-Application
and	O
the	O
integration	O
align	O
with	O
the	O
growth	O
strategy	O
of	O
the	O
organization	O
.	O
</s>
<s>
If	O
an	O
organization	O
is	O
a	O
manufacturing	O
organization	O
with	O
fast	O
growth	O
plans	O
through	O
acquisitions	O
,	O
the	O
applications	B-Architecture
architecture	I-Architecture
should	O
be	O
nimble	O
enough	O
to	O
encompass	O
inherited	O
legacy	O
systems	O
as	O
well	O
as	O
other	O
large	O
competing	O
systems	O
.	O
</s>
<s>
Applications	B-Application
can	O
be	O
classified	O
in	O
various	O
types	O
depending	O
on	O
the	O
applications	B-Architecture
architecture	I-Architecture
pattern	O
they	O
follow	O
.	O
</s>
<s>
To	O
create	O
patterns	O
,	O
one	O
needs	O
building	B-Architecture
blocks	I-Architecture
.	O
</s>
<s>
Building	B-Architecture
blocks	I-Architecture
are	O
components	O
of	O
software	O
,	O
mostly	O
reusable	O
,	O
which	O
can	O
be	O
utilized	O
to	O
create	O
certain	O
functions	O
.	O
</s>
<s>
Patterns	O
are	O
a	O
way	O
of	O
putting	O
building	B-Architecture
blocks	I-Architecture
into	O
context	O
and	O
describe	O
how	O
to	O
use	O
the	O
building	B-Architecture
blocks	I-Architecture
to	O
address	O
one	O
or	O
multiple	O
architectural	O
concerns	O
.	O
</s>
<s>
Application	O
patterns	O
can	O
describe	O
structural	O
(	O
deployment/distribution	O
-related	O
)	O
or	O
behavioural	O
(	O
process	O
flow	O
or	O
interaction/integration	O
-related	O
)	O
characteristics	O
and	O
an	O
application	B-Architecture
architecture	I-Architecture
may	O
leverage	O
one	O
or	O
a	O
mix	O
of	O
patterns	O
.	O
</s>
<s>
The	O
idea	O
of	O
patterns	O
has	O
been	O
around	O
almost	O
since	O
the	O
beginning	O
of	O
computer	O
science	O
,	O
but	O
it	O
was	O
most	O
famously	O
popularized	O
by	O
the	O
"	O
Gang	O
of	O
Four	O
"	O
(	O
GoF	O
)	O
though	O
many	O
of	O
their	O
patterns	O
are	O
"	O
software	B-Architecture
architecture	I-Architecture
"	O
patterns	O
rather	O
than	O
"	O
application	B-Architecture
architecture	I-Architecture
"	O
patterns	O
.	O
</s>
<s>
One	O
can	O
,	O
of	O
course	O
have	O
the	O
same	O
desktop	B-Application
application	I-Application
on	O
many	O
computers	O
,	O
but	O
they	O
do	O
not	O
interact	O
with	O
one	O
another	O
(	O
with	O
rare	O
exceptions	O
)	O
.	O
</s>
<s>
In	O
contrast	O
to	O
desktop	B-Application
applications	I-Application
(	O
which	O
are	O
single-user	O
)	O
,	O
client-server	O
applications	B-Application
are	O
almost	O
always	O
multi-user	O
applications	B-Application
.	O
</s>
<s>
This	O
pattern	O
also	O
include	O
some	O
behavioural	O
pattern	O
attributes	O
because	O
the	O
server	O
functions	O
must	O
be	O
designed	O
to	O
be	O
more	O
autonomous	O
and	O
function	O
in	O
an	O
asynchronous	O
dialog	O
with	O
the	O
other	O
functions	O
in	O
order	O
to	O
deal	O
with	O
potentially-significant	O
latency	O
that	O
can	O
occur	O
in	O
WAN	O
and	O
cloud	O
deployment	B-Application
scenarios	O
.	O
</s>
<s>
horizontal	O
scalability	B-Architecture
(	O
structural	O
pattern	O
)	O
:	O
a	O
pattern	O
for	O
running	O
multiple	O
copies	O
of	O
server	O
functions	O
on	O
multiple	O
computers	O
in	O
such	O
a	O
way	O
that	O
increasing	O
processing	O
load	O
can	O
be	O
spread	O
across	O
increasing	O
numbers	O
of	O
instances	O
of	O
the	O
functions	O
rather	O
than	O
having	O
to	O
re-deploy	O
the	O
functions	O
on	O
larger	O
,	O
more	O
powerful	O
computers	O
.	O
</s>
<s>
Cloud-native	O
applications	B-Application
are	O
fundamentally-based	O
on	O
horizontal	O
scalability	B-Architecture
.	O
</s>
<s>
The	O
right	O
applications	B-Application
pattern	O
depends	O
on	O
the	O
organization	O
's	O
industry	O
and	O
use	O
of	O
the	O
component	O
applications	B-Application
.	O
</s>
<s>
These	O
skills	O
include	O
an	O
understanding	O
of	O
application	O
modularization/distribution	O
,	O
integration	O
,	O
high	O
availability	O
,	O
and	O
scalability	B-Architecture
patterns	O
,	O
technology	O
and	O
trends	O
.	O
</s>
<s>
While	O
a	O
software	O
background	O
is	O
a	O
great	O
foundation	O
for	O
an	O
application	O
architect	O
,	O
programming	O
and	O
software	O
design	O
are	O
not	O
skills	O
required	O
of	O
an	O
application	O
architect	O
(	O
these	O
are	O
actually	O
skills	O
for	O
a	O
Software	O
Architect	O
,	O
who	O
is	O
a	O
leader	O
on	O
the	O
computer	B-General_Concept
programming	I-General_Concept
team	O
)	O
.	O
</s>
<s>
Application	O
modeling	O
Employs	O
modeling	O
as	O
a	O
framework	O
for	O
the	O
deployment	B-Application
and	O
integration	O
of	O
new	O
or	O
enhanced	O
applications	B-Application
,	O
uses	O
modeling	O
to	O
find	O
problems	O
,	O
reduce	O
risk	O
,	O
improve	O
predictability	O
,	O
reduce	O
cost	O
and	O
time-to-market	O
,	O
tests	O
various	O
product	O
scenarios	O
,	O
incorporating	O
clients	O
 '	O
nonfunctional	O
needs/requirements	O
,	O
adds	O
test	O
design	O
decisions	O
to	O
the	O
development	O
process	O
as	O
necessary	O
,	O
evaluates	O
product	O
design	O
problems	O
.	O
</s>
<s>
An	O
applications	B-Application
architect	O
is	O
a	O
master	O
of	O
everything	O
application-specific	O
in	O
an	O
organization	O
.	O
</s>
<s>
An	O
applications	B-Application
architect	O
provides	O
strategic	O
guidelines	O
to	O
the	O
applications	B-Application
maintenance	O
teams	O
by	O
understanding	O
all	O
the	O
applications	B-Application
from	O
the	O
following	O
perspectives	O
:	O
</s>
<s>
The	O
above	O
analysis	O
will	O
point	O
out	O
applications	B-Application
that	O
need	O
a	O
range	O
of	O
changes	O
–	O
from	O
change	O
in	O
deployment	B-Application
strategy	O
for	O
fragmented	O
applications	B-Application
to	O
a	O
total	O
replacement	O
for	O
applications	B-Application
at	O
the	O
end	O
of	O
their	O
technology	O
or	O
functionality	O
lifecycle	O
.	O
</s>
<s>
It	O
gives	O
a	O
clear	O
picture	O
of	O
the	O
functionality	O
map	O
and	O
the	O
applications	B-Application
footprint	O
of	O
various	O
applications	B-Application
across	O
the	O
map	O
.	O
</s>
<s>
Every	O
organization	O
has	O
a	O
core	O
set	O
of	O
applications	B-Application
that	O
are	O
used	O
across	O
multiple	O
divisions	O
either	O
as	O
a	O
single	O
instance	O
or	O
a	O
different	O
instance	O
per	O
division	O
.	O
</s>
<s>
Create	O
a	O
solution	O
architecture	O
template	O
for	O
all	O
the	O
core	O
applications	B-Application
so	O
that	O
all	O
the	O
projects	O
have	O
a	O
common	O
starting	O
ground	O
for	O
designing	O
implementations	O
.	O
</s>
<s>
The	O
standards	O
in	O
architecture	O
world	O
are	O
defined	O
in	O
TOGAF	O
,	O
The	O
Open	O
Group	O
Architecture	O
Framework	O
describes	O
the	O
four	O
components	O
of	O
EA	O
as	O
BDAT	O
(	O
Business	B-Architecture
architecture	I-Architecture
,	O
Data	B-General_Concept
architecture	I-General_Concept
,	O
Application	B-Architecture
Architecture	I-Architecture
and	O
Technical	B-Architecture
architecture	I-Architecture
,	O
</s>
