SIA 101: SYSTEM INTEGRATION & ARCHITECTURE

NIPSCBC-CLASS-BSIT HECEL L.
BORJA
ST
1 SEM 2021-2022
Instructor II

Module 3, Lesson 1

SYSTEM INTEGRATION & ARCHITECTURE

(Good for 2 week (6 hours)

Course description:

This course focuses on the integration of information systems in

organizations, the process by which different computing systems and software
application are linked together physically or functionally. It examines the strategies
and methods for blending a set of interdependent systems into a functioning or
unified whole, thereby enabling two or more applications to interact and exchange
data seamlessly. The course will explore tools and techniques for systems
integration as well as proven management practices for integration projects.
Credit Hours: 3

Pre-Requisite: none

Instructions to students:

1. This training module is designed for you to understand what is database system;
2. Read carefully and participate actively in this learning process;
3. An assessment after the comprehension and capability after reading this module;
4. Stay home, be safe.

Submission/requirements:

This module shall be retuned in the NIPSC Batad Guard house upon
completion of this module.

HECEL L. BORJA
INSTRUCTOR II
1
NIPSC-BATAD CAMPUS
A.Y 2020-2021
I. INTRODUCTION

In this module, Many systems are built to easy, improve and transform
organizations.
Some organizations have many departments which run systems which are
independent of each other.
And systems built sometimes, may not have an abstract view (architecture)
which leads to failure of system interoperability.
There is need to have architectural view of the system as a priority to help in
the design to avoid the likeliness of system failure.
Besides after the system has been designed and developed in consideration
of the size of the organization, i.e. most especially when the organization is large,
need is required to integrate such systems to ensure flexibility, Speed, Cost ,
Standardization, Data integrity, reliability and robustness.
This can help Information Technology (IT), energy, and financial services
industry among others to have an easy to use integrated system.

II. LEARNING OUTCOMES

Upon completion of this module, the students must have:

1. Identify the System Architect;

2. Learn the system architecture;
3. Understand the IT Architecture Concepts.

III. LEARNING CONTENTS

Topics

Systems Architectures

Architecture

The word “architecture” is derived from the Greek word “architecton”, which means
master mason or master builder

•Webster’s Dictionary defines architecture as:

•The art or science of designing or building structures

•The structure (in terms of components, connections, and constraints) of a product,

process, or element – The Art of Systems Architecting

•An Architecture is the highest-level concept of a system in its environment - IEEE

HECEL L. BORJA
INSTRUCTOR II
2
NIPSC-BATAD CAMPUS
A.Y 2020-2021
 • Architecture – The fundamental organization of a system embodied in its
components, their relationships to each other and to the environment and
the principles guiding its design and evolution - P141 Standard

• Systems Architecture – The fundamental and unifying system structure

defined in terms of system elements, interfaces, processes, constraints, and
behaviors – INCOSE SAWG

• Architecture – The organizational structure of a system of CSCIs, identifying

its components, their interfaces and a concept of execution among them

• The architecture of a system defines its high-level structure, exposing its

gross organization as a collection of interacting components.

• Components needed to model a software architecture include:

- Components, Connectors, Systems, Properties and Styles.

IT Architecture Concepts

Components

– The computational elements and data stores of the system

– May have multiple interfaces, called ports

– Ports define a point of interaction between a component and its

environment

Connectors

– Model interactions among components

– Runtime perspective: connectors mediate the communication and

coordination activities between components

– Connectors may have interfaces that define the roles played by the
participants in the interaction

Systems

– Graphs of components and connectors

– Tend to be hierarchical – components and connectors may represent

subsystems that have their own internal architectures

– Bindings map the interfaces of one level of a system to another

HECEL L. BORJA
INSTRUCTOR II
3
NIPSC-BATAD CAMPUS
A.Y 2020-2021
Properties

– Represent the non-structural information about the parts of an

architecture description

– Example: a connector can be a function call, or a network interaction

– Properties can be attached to any architectural element

Style

– An architectural style represents a family of related systems

– Defines the design vocabulary (and constraints) for the components,

connectors, ports, roles, bindings and properties.

System Architect

The architect is a member of the team that is responsible for designing and building
a system

The architect’s contribution comes in the very early stages of the systems
engineering process

– When the operational concept is defined

– The basic structure of the system is conceptualized

A system architect, not only knows about the individual components, but also
understands the interrelationships among the components

Systems Architecting

Systems Architecting has been defined as the process of creating complex,

unprecedented systems

Building systems in today’s world is tenuous at best

– Requirements of the marketplace are ill-defined

– Rapidly evolving technology provides new services at a global level

instantly

– Uncertainty is increasing about they way the system will be used, the
components that will be incorporated and the interconnections that will
be made.

HECEL L. BORJA
INSTRUCTOR II
4
NIPSC-BATAD CAMPUS
A.Y 2020-2021
Systems Architecting - 2

Generating a system architecture as part of the systems engineering process can

be seen as a deliberate approach to deal with the uncertainty that characterizes
these complex, unprecedented systems

Traditional Approach to System Architecting

Many methodologies have been developed to support a traditional system

development model

– Define the requirements

– Consider several options

– Emerge with a well-defined design through a process of elimination

– Based on structured analysis and design

Traditional Approach to System Architecting – 2

Effective when the requirements are well defined and remain essentially constant
during the system development period

– Cannot handle change well

If the implementation of the system is long – on the order of years – the

requirements change because of changing needs and new technology offers
different alternatives and opportunities

The Traditional Approach

HECEL L. BORJA
INSTRUCTOR II
5
NIPSC-BATAD CAMPUS
A.Y 2020-2021
Evolutionary Approach

• New approach that is emerging with roots in software systems engineering

• Deals with uncertainty in requirements and in technology, especially for

systems with a long development time and expected long life cycle

– Evolutionary development

– Build-a-little, Test-a-little

• Requirements are allowed to be more abstract and therefore subject to

interpretation

• Alternative solutions are explored and pursued further as new technology

options become available

Evolutionary Approach – 2

• Intermediate designs are saved

• Some intermediate designs are implemented as prototypes but not

operationally implemented while others are implemented in traditional ways

• Advantages of Object-Oriented approach:

– Allows flexibility in the design as it evolves over time

• Disadvantages of Object-Oriented approach:

HECEL L. BORJA
INSTRUCTOR II
6
NIPSC-BATAD CAMPUS
A.Y 2020-2021
 – Requires some early elimination of technology alternatives in the
absence of reliable information

Evolutionary Approach

Select, Build, and Field

At any time in the development process, when there is a need to build a system, the
available solution that best meets the current requirements is selected and
implemented using any systems engineering approach.

Select, Build, and Field

The Challenge of Coping With Change

HECEL L. BORJA
INSTRUCTOR II
7
NIPSC-BATAD CAMPUS
A.Y 2020-2021
If the implementation is long, then the situation shown next prevails, with the
unfortunate consequences that very little, if any, from the work on Option A is used
for Option B.

How to Define an Architecture

Defining an architecture, especially of an information system, requires the following

items to be described:

– Processes exist that need to take place in order that the system
accomplish its intended functions

– The individual processes transform either data or materials that “flow”

between them

– The processes or activities or operations follow rules that establish the

conditions under which they occur

– The components that will implement the design (hardware, software,

personnel, and facilities must be described).

How to Define an Architecture – 2

Define the Functional Architecture

– A functional architecture is:

HECEL L. BORJA
INSTRUCTOR II
8
NIPSC-BATAD CAMPUS
A.Y 2020-2021
 • A set of activities or functions that are arranged in a specific
order and when activated, achieves a set of requirements

• Divide and allocate the functional requirements into different

sub-functions and modes of operation

How to Define an Architecture – 3

Define the Physical Architecture

– A physical architecture is:

• A representation of the physical resources

• Expressed as nodes that constitute the system and their

connectivity

• Expressed in the form of links

How to Define an Architecture – 4

Define the technical architecture

– A minimal set of rules governing the arrangement, interaction, and

interdependence of the parts or elements that must ensure that a
conformant system satisfies a specified set of requirements

– Provides the framework upon which engineering specifications can be

derived, guiding the implementation of the system

– Analogous to the building code that provides guidance for new

buildings to be able to connect to the existing infrastructure by
characterizing the attributes of that infrastructure.

Operational Concept

An important task in the architecture development process is to define the

operational concept

– A concise statement that describes how the goal will be met

– How will the system look and act in the operational environment

Operational Concept Definition Parts

– How the system operates

– Where in the operating environment the system will be distributed

– How long the system must operate

HECEL L. BORJA
INSTRUCTOR II
9
NIPSC-BATAD CAMPUS
A.Y 2020-2021
 – How effective the system’s performance must be.

Operational Concept – 2

• An operational concept is a shared vision from the perspective of the

system’s stakeholders of how the system will be:

– Developed

– Produced

– Deployed

– Trained

– Used and maintained

– Refined

– Retired

Operational Concept – 3

The operational concept includes a collection of scenarios – one for each group of
stakeholders for each relevant phase of the system’s lifecycle

– Each scenario addresses one way that a particular stakeholder will

want to use, deploy, fix, etc., the system and how the system will
respond to a produce a desired end

– Scenario - a sequence of events which might occur that includes the

interaction of the product with its environment and users, as well as
the interaction among its product components.

Executable Model

The functional, physical, and technical architectures are static representations that
attempt to describe the dynamic behavior of the architecture.

In order to analyze the behavior of the architecture and evaluate the performance
characteristics, an executable model is needed.

Architecture Development Process

The architecture development process consists of three phases:

HECEL L. BORJA
INSTRUCTOR II
10
NIPSC-BATAD CAMPUS
A.Y 2020-2021
  Analysis Phase – The static representatives of the functional and
physical architectures are obtained using the operational concept to
drive the process and the technical architecture to guide it

 Synthesis Phase – The static constructs are used, together with

descriptions of the dynamic behavior of the architecture to obtain the
executable operational X-architecture (X = executable property)

 Evaluation Phase – Measures of performance (MOP) and measures of

effectiveness (MOE) are obtained.

The Three-Phase Process of Architecture Development

IV. Learning Activities

Note:

(Note: please provide another sheet of paper to answer. Do not answer the module)
be sure you can picture your finished activity, put a module and lesson number in
every activity and send it to me via facebook messenger (sherm ayupan avenir
lacabe) or you can hand in your activity to the guard house when you returned in
school.

“No Copy, Paste of answer”

5 points each

1. Define the following IT Architecture Concepts.

2. Differentiate the evolutionary approach and evolutionary approach 2.

HECEL L. BORJA
INSTRUCTOR II
11
NIPSC-BATAD CAMPUS
A.Y 2020-2021
V. Enrichment Activities
1. Define the Physical Architecture

1. References:

https://itgirls1426.wordpress.com/attend-event/third-year/system-integration-and-
architecture/
https://muele.mak.ac.ug/course/view.php?id=1563

End of Module 3, Lesson 1

HECEL L. BORJA
INSTRUCTOR II
12
NIPSC-BATAD CAMPUS
A.Y 2020-2021