Enterprise Architecture

This document provides an overview of Enterprise Architecture, including activity diagrams, storyboards, sequence diagrams, class diagrams, and more. It explores the Zachman Framework and discusses the main objectives, functions, and technologies involved in Enterprise Architecture. The document also includes a bibliography for further reading.

Running head: ENTERPRISE ARCHITECTURE
Enterprise Architecture
Name of the Student:
Name of the University:
Author Note

1
ENTERPRISE ARCHITECTURE
Table of Contents
Point 1: Activity Daigrams.........................................................................................................2
Daigram 1: Registration process............................................................................................2
Daigram 2: Matchmaking process.........................................................................................3
Point 2: Story board...................................................................................................................4
Prototype 1: Home Page.........................................................................................................5
Prototype 2: Matchmaking.....................................................................................................6
Prototype 3: Profile................................................................................................................7
Portotype 4: Chats..................................................................................................................8
Point 3: Sequence Daigram........................................................................................................9
Daigram 1...............................................................................................................................9
Daigram 2.............................................................................................................................10
Daigram 3.............................................................................................................................11
Daigram 4.............................................................................................................................12
Point 4: Class Daigram.............................................................................................................13
Point 5: Entity Relationship Daigram......................................................................................13
Point 6: Basic Java code...........................................................................................................14
Point 7: Zachman Framework..................................................................................................16
Bibliography.............................................................................................................................20

2
ENTERPRISE ARCHITECTURE
Point 1: Activity Daigrams
Daigram 1: Registration process

3
ENTERPRISE ARCHITECTURE
Daigram 2: Matchmaking process

4
ENTERPRISE ARCHITECTURE
Point 2: Story board

5
ENTERPRISE ARCHITECTURE
Prototype 1: Home Page

6
ENTERPRISE ARCHITECTURE
Prototype 2: Matchmaking

7
ENTERPRISE ARCHITECTURE
Prototype 3: Profile

8
ENTERPRISE ARCHITECTURE
Portotype 4: Chats

9
ENTERPRISE ARCHITECTURE
Point 3: Sequence Daigram
Daigram 1

10
ENTERPRISE ARCHITECTURE
Daigram 2

11
ENTERPRISE ARCHITECTURE
Daigram 3

12
ENTERPRISE ARCHITECTURE
Daigram 4

13
ENTERPRISE ARCHITECTURE
Point 4: Class Daigram
Point 5: Entity Relationship Daigram

14
ENTERPRISE ARCHITECTURE
Point 6: Basic Java code
public class Admin
{
int adminID;
String username;
String password;
};
public class registration
{
int registrationID;
String firstName;
String lastName;
String address;
int Contact;
};
public class users
{
int userID;
String userName;
String password;

15
ENTERPRISE ARCHITECTURE
public register();
};
public class Registration
{
int registrationID;
String firstName;
String lastName;
String address;
int contact;
};
public class match extends users
{
int matchID;
int user;
public match (int user);
}
public class messages
{
public send ();
public receive ();

16
ENTERPRISE ARCHITECTURE
};
Point 7: Zachman Framework
The Zachman Framework is an easy to understand framework that is used for the
Valentinos system.
Data
(What)
Function
(How)
Networ
k
(Where
)
People
(Who)
Time
(When)
Motivatio
n (Why)
Objective/
Scope
The main
objective
of the
system is
making the
perfect
match in
between
two users
The
function
works after
the use of
data
entered by
the users in
the filters
applied in
the
application.
The
main
networ
k of the
system
is the
whole
of UK.
The people
of age
group 18 to
65 are
selected
here.
The
services
of the
applicati
on runs
througho
ut the
day 24x7
For
allowing
to meet the
individuals
with same
preferences
Business
Model
The main
objective is
manageme
nt of the
business
The system
helps in the
manageme
nt of the
operation
The
main
networ
k of the
system
The main
uses in the
system are
staffs in the
organizatio
The
services
of the
applicati
on runs
All the
business
related
operations
are carried

17
ENTERPRISE ARCHITECTURE
operations
and the
manageme
nt of data
in the
system.
of the
business in
an efficient
way.
is the
whole
of UK.
n who
would be
working in
the system.
througho
ut the
day 24x7
in
multiple
shifts.
out
effeciently
by the
system.
Model of
the
Information
System
The
operation
of the
business of
the
organizatio
n is
managed
by the
system.
The
process of
analysis
and
matchmaki
ng is
automated
with the
use of the
matchmaki
ng
algorithm.
The
main
networ
k of the
system
is the
whole
of UK.
The main
uses in the
system are
staffs in the
organizatio
n who
would be
working in
the system.
The
services
of the
applicati
on runs
througho
ut the
day 24x7
All the
business
related
operations
are carried
out
effeciently
by the
algoritm
deployed in
the system.
Technology
Model
The
matching
of the users
in the
system are
improved
with the
The
process of
analysis
and
matchmaki
ng is
automated
The
main
networ
k of the
system
is the
whole
The people
of age
group 18 to
65 are
selected
here.
The
services
of the
applicati
on runs
througho
ut the
The
machmakin
g process is
caried out
more
accurately
with the

18
ENTERPRISE ARCHITECTURE
help of the
algorithm
with the
use of the
matchmaki
ng
algorithm.
of UK. day 24x7 deploymen
t of the
matchmaki
ng
algorithm
in the
systsem.
Detailed
representati
on
The system
has been
implement
ed for the
purpose of
matchmaki
ng in
between
the users of
the system.
The system
also
improves
the
matchmaki
ng by
making it
accurate.
The system
makes use
of
matchmaki
ng
algorithm
that helps
the
matchmaki
ng process
and
provides
the
appropriate
match for
the users
The
main
networ
k of the
system
is the
whole
of UK.
The
designers
and the
developers
are
involved
with the
system and
improveme
nt of the
effeceincy
of the
system
which
helps in the
matchmaki
ng process
of system
The
services
of the
applicati
on runs
througho
ut the
day 24x7
This helps
the
orgaization
improve
their
finances as
the system
would
draw more
and more
users to the
system due
to the
improved
matchmaki
ng options.

19
ENTERPRISE ARCHITECTURE
deployed.
(Working Systems)
Functioning
Enterprise
The data is
processed
by
collecting
the data
from the
filters that
are filled
up by the
users and
the
questionair
es answerd
by the
users.
The data is
recoredced
by the
system and
the analysis
is done
with the
help of the
matchmaki
ng
algorithm.
The result
is then
used for
serching
and the
sorted list
is
displayed
to the
users.
The
main
networ
k of the
system
is the
whole
of UK.
The
internal
staffs of
the
organizatio
n and the
users who
are
registered
on the
platform.
The
services
of the
applicati
on runs
througho
ut the
day 24x7
This helps
the
orgaization
improve
their
finances as
the system
would
draw more
and more
users to the
system due
to the
improved
matchmaki
ng options.

20
ENTERPRISE ARCHITECTURE
Bibliography
Bernaert, M., Poels, G., Snoeck, M. and De Backer, M., 2016. CHOOSE: Towards a
metamodel for enterprise architecture in small and medium-sized enterprises. Information
Systems Frontiers, 18(4), pp.781-818.
Hinkelmann, K., Gerber, A., Karagiannis, D., Thoenssen, B., Van der Merwe, A. and
Woitsch, R., 2016. A new paradigm for the continuous alignment of business and IT:
Combining enterprise architecture modelling and enterprise ontology. Computers in Industry,
79, pp.77-86.
Lapalme, J., Gerber, A., Van der Merwe, A., Zachman, J., De Vries, M. and Hinkelmann, K.,
2016. Exploring the future of enterprise architecture: A Zachman perspective. Computers in
Industry, 79, pp.103-113.
Romero, D. and Vernadat, F., 2016. Enterprise information systems state of the art: Past,
present and future trends. Computers in Industry, 79, pp.3-13.
Sandkuhl, K., Fill, H.G., Hoppenbrouwers, S., Krogstie, J., Leue, A., Matthes, F., Opdahl,
A.L., Schwabe, G., Uludag, Ö. and Winter, R., 2016, November. Enterprise modelling for the
masses–from elitist discipline to common practice. In IFIP Working Conference on The
Practice of Enterprise Modeling (pp. 225-240). Springer, Cham.
Vargas, A., Cuenca, L., Boza, A., Sacala, I. and Moisescu, M., 2016. Towards the
development of the framework for inter sensing enterprise architecture. Journal of Intelligent
Manufacturing, 27(1), pp.55-72.