Valentinos System: Enterprise Architecture Project & UML Models

This project provides a comprehensive enterprise architecture for the Valentinos system, a matchmaking service. It includes detailed use case diagrams, activity diagrams illustrating the registration and matchmaking processes, and storyboards presenting prototypes for the home page, timeline, contacts, and notifications. The project also features sequence diagrams with corresponding class diagrams to model system interactions, a comprehensive class diagram detailing system entities, and an entity-relationship diagram derived from the class diagram. Furthermore, basic Java code snippets are provided, and the Zachman Framework is applied to analyze the system from various perspectives, including data, function, network, people, time, and motivation. The document concludes with a bibliography of relevant sources.

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.........................................................................................................3
Detailed Use Case Daigram...................................................................................................3
Daigram 1: Registration process (Use Case activity Daigram).............................................4
Daigram 2: Matchmaking process (Business Case Activity Daiagram)................................4
Point 2: Story board...................................................................................................................5
Prototype 1: Home Page.........................................................................................................6
Prototype 2: Timeline.............................................................................................................7
Prototype 3: Contacts.............................................................................................................8
Portotype 4: Notification........................................................................................................9
Point 3: Sequence Daigram......................................................................................................10
Daigram 1.............................................................................................................................10
Class Daigram......................................................................................................................10
Daigram 2.............................................................................................................................11
Class Diagram......................................................................................................................11
Daigram 3.............................................................................................................................12
Class Daigram......................................................................................................................12
Daigram 4.............................................................................................................................13
Class Daigram......................................................................................................................13
Point 4: Class Daigram.............................................................................................................14
Detailed Class Daigram........................................................................................................15
Point 5: Entity Relationship Daigram......................................................................................16

2
ENTERPRISE ARCHITECTURE
Point 6: Basic Java code...........................................................................................................16
Point 7: Zachman Framework..................................................................................................18
Bibliography.............................................................................................................................24

3
ENTERPRISE ARCHITECTURE
Point 1: Activity Daigrams
Detailed Use Case Daigram
The use case daigram for the Valentinos has been described here. The main actors
identified from the system are the users of the system, the administrator, the executive
management, the matching administrator and the finnance department. The different actors
have different roles.

4
ENTERPRISE ARCHITECTURE
Daigram 1: Registration process (Use Case activity Daigram)
The regitsration process of the users have been described in this daigram. The users
interact with both the admin and system in this scenario.
Daigram 2: Matchmaking process (Business Case Activity Daiagram)

5
ENTERPRISE ARCHITECTURE
This daigram describes the business case for the organization which is to improve the
matchmaking process for the users that would help the organiations improve the overall
business procedures.
Point 2: Story board
Storyboard1
The storyboard provides the details of all the major process and the flow of trhe
process that might take place in the application. The mobile application of the valentinos
organization has been selected here for the description of the story board. The registartion
process is beimng dicusses here in this story board process.

6
ENTERPRISE ARCHITECTURE
Storyboard 2
The second story provides the details of the tinmeline. The user selects an user from
the timeline and send request.
Storyboard 3

7
ENTERPRISE ARCHITECTURE
The third storyboard is used for user to view trhe contacts in the system. They would
also be able to see the messages in the system and reply to them if they wish to do so.
Storyboard 4
The fourth storyboard is used for the notifying the users about the matching request
that they have got.

8
ENTERPRISE ARCHITECTURE
Prototype 1: Home Page
This is the homepage in which the user would be able to register himself and take part
in the matchmaking options.

9
ENTERPRISE ARCHITECTURE
Google is selected as the platform for logging into the system.

10
ENTERPRISE ARCHITECTURE
This page lets the user selects the user profile for logging into the system. The users
selects acount for logging into the system.

11
ENTERPRISE ARCHITECTURE
The user is registered into the system.