Republic of the Philippines

Laguna State Polytechnic University

Province of Laguna
College of Computer Studies
ITEL305 – System Integration and Architecture 2
SEATWORK 1

Name: Danielle Love Zotomayor Score: _____/20

Section: BSIT WAM – 3B
Topic: UML Class Diagram Week No. 1

Course Code: ITEL-305 Term: 2nd Sem

Course Title: System Integration and Architecture 2 Academic Year: 2021-2022

General Direction:
1. Read the question carefully.
2. Attempt to answer all questions.
3. Make sure everything is set before submitting your activity.

Unified Modeling Language - Class

1. How do we achieve System Integration?

2. Describe a UML Class diagram.
3. Draw an example of a Class diagram;
a. Explain its structure.
b. With Java code to describe UML class diagram

Provide your answer below:

1. There are several steps for system integration. Each steps have each is important and
necessary for the systems to properly communicate and function with each other.

Step 1: Gathering of Information

The first step is to gather information such as requirements and expectations. We
should list the systems that needs to be integrated and further research the best
methods to be applied for each one.

Step 2: Analyze the gathered information

After we gathered all the needed and necessary information, it is time to analyze it.
This step requires deeper planning and involves breaking down the steps and structure
of the system integration. The focus of this goal is to know the measure how well will
the proposed system solve problems.

Step 3: Design

[ITEL305 – System Integration and Architecture 2]

Seatwork 01 Page 1 of 4
 Republic of the Philippines
Laguna State Polytechnic University
Province of Laguna
College of Computer Studies
ITEL305 – System Integration and Architecture 2
SEATWORK 1
Now that we assembled all the data and plans, the next process is to design and
wireframe (a blueprint or schematic that helps determine the structure of the software)
the structure of the integration. It starts with a strong foundation, then including of all
the other elements so they could function as a whole. It is key to make this step right,
because it can cause difficulties once the development begins, changes can be tedious,
time-consuming and expensive to make.

Step 4: Development
This step will take the design into a working and functioning software. Depending on
the difficulty of the integration, this step will take the longest to finish. This is where we
do the coding and the interface will be created. Once the development is finished, it is
ready for user-testing.

Step 5: User-testing
This step is where we will test the development project, this step needs to be done
carefully and thoroughly. One small mistake in the code will lead into bugs and errors.
This is where developers spend most of their time troubleshooting the bugs and errors
founded and goes through the entire program for re-testing.

Step 6: Implementation
The most awaited step. This step is the launching of the newly developed and tested
software. This will help to improve the operational efficiency of the developers.

Step 7: Maintenance
The last step of system integration is the tweaking, updating, and revisioning of the
software. This is recommended that the developer of the system integration makes
updates and changes needed to the software and this is commonly done each month.
Software monitoring can be done more often to ensure that everything is still working
well.

2. A Unified Modeling Language (UML) class diagram is graphical notation (a visual

programming language) used to make and visualize a object oriented systems. It is a
static structure diagram that describes the structure of the system by presenting the
systems; classes, attributes, methods (operation) and its relationships to other
objects.

[ITEL305 – System Integration and Architecture 2]

Seatwork 01 Page 2 of 4
 Republic of the Philippines
Laguna State Polytechnic University
Province of Laguna
College of Computer Studies
ITEL305 – System Integration and Architecture 2
SEATWORK 1
3.

a. It is represented in a rectangular shaped box divided into three parts. Classes are placed in
the top most part of the diagram, in the middle is the attributes of the class, and lastly at the
bottom is the methods (behaviors).
b.

[ITEL305 – System Integration and Architecture 2]

Seatwork 01 Page 3 of 4
 Republic of the Philippines
Laguna State Polytechnic University
Province of Laguna
College of Computer Studies
ITEL305 – System Integration and Architecture 2
SEATWORK 1

[ITEL305 – System Integration and Architecture 2]

Seatwork 01 Page 4 of 4