LESSON # 1

System Integration

& Architecture

IT 313

2/10/2023

System Integration & Architecture

1

Multiple Choice

Formed to work on project from beginning to end.

• Project Team

• Leader

• IS

• Project Designer

Multiple Choice

Hardware, software, data, people, and procedures that work together to produce quality information?

• Information System

• System

• System Analysis and Design

• Progress Bar

Open Ended

How are you feeling today!

Introduction

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.

2/10/2023

System Integration & Architecture

2

Introduction

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.

2/10/2023

System Integration & Architecture

3

What students need to know

Systems Integration (SI) process, approaches, drivers,

tools and techniques required for successful SI, critical
success factors, and best practices.

The course focuses on how a proposed system will be

integrated with other existing or planned systems.

It addresses the System Integration problem using

architectures as the basis and then addresses the
evaluation

of

the

architectures

in

terms

of

the

capabilities they provide.

2/10/2023

System Integration & Architecture

4

What students need to learn

The theory and practice of business process integration, legacy

integration, new systems integration, business-to-business integration,

integration of commercial-off-the-shelf (COTS) products, interface

control and management, testing, integrated program management,

integrated Business Continuity Planning (BCP).

5

Aims

To provide the students an understanding

of the technical and business process
issues involved in systems integration.

2/10/2023

System Integration & Architecture

6

Learning outcomes

On completion of this course, the students will be able

to:

Identify integration issues upfront in the process of

System Integration and should be able to identify the
best practices that ensure successful System
Integration.

Have an understanding of the technical and business

process issues involved in systems integration.

2/10/2023

System Integration & Architecture

7

Teaching and learning pattern

Teaching this course will be in lecture

form. A number of case studies will also
be used to illustrate some concepts as
mentioned in the indicative content.

2/10/2023

System Integration & Architecture

8

Key terminologies in this course

Various key terminologies shall be used
throughout this course as follows

 System

 Systems thinking

 System Integration

 System Architecture

 System Project

2/10/2023

System Integration & Architecture

9

System

An array of components designed to accomplish

a particular objective according to plan. Many
sub-systems many be designed which later on are
combined together to form a system which is
intended

to achieve a specific objective which

may be set by the Project manager.

2/10/2023

System Integration & Architecture

10

Systems thinking

 Is a way of understanding an entity in terms of its

purpose, as three steps

 The three major steps followed in systems thinking

1. Identify a containing whole (system), of which the thing

to be explained is a part.

2. Explain the behavior or properties of the containing

whole.

3. Explain the behavior or properties of the thing to be

explained in terms of its role(s)or function(s) within its
containing whole

(Ackoff, 1981)

2/10/2023

System Integration & Architecture

11

System Integration

Is the combination of inter-

related elements to
achieve a common
objective (s).

2/10/2023

System Integration & Architecture

12

System Architecture

The architecture of a system defines its high-

level structure, exposing its gross organization as
a collection of interacting components.

Elements needed to model a software

architecture include:

Components, Connectors, Systems, Properties and

Styles.

2/10/2023

System Integration & Architecture

13

What is a project?

 From the key terms described above, a

system developer and architects cannot do
anything without first establishing various
projects. These projects may be new or
existing.

 So it is inevitable to first understand what a

project is, factors that influence the project,
who the owners are and many more as
discussed below.

2/10/2023

System Integration & Architecture

14

2/10/2023

System Integration & Architecture

15

What Is a Project?

A project is a temporary endeavor undertaken to

accomplish a unique product or service

Attributes of projects

unique purpose

temporary

require resources, often from various areas

should have a primary sponsor and/or customer

involve uncertainty

Where do information Systems Projects

Originate (Sources of Projects)?

New or changed IS development projects come from problems,
opportunities, and directives and are always subject to one or more
constraints.
1.

Problems – may either be current, suspected, or anticipated.
Problems are undesirable situations that prevent the business from
fully achieving its purpose, goals, and objectives (users discovering
real problems with existing IS).

2.

An Opportunity – is a chance to improve the business even in the
absence of specific problems. This means that the business is
hoping to create a system that will help it with increasing its
revenue, profit, or services, or decreasing its costs.

3.

A Directive – is a new requirement that is imposed by
management, government, or some external influence i.e. are
mandates that come from either an internal or external source of
the business.

2/10/2023

System Integration & Architecture

16

17

2/10/2023

System Integration & Architecture

17
Projects Cannot Be Run in

Isolation

Projects must operate in a broad

organizational environment

Project managers need to take a holistic

or systems view of a project and
understand how it is situated within the
larger organization

2/10/2023

System Integration & Architecture

18

Stakeholders

Stakeholders are the people involved in or

affected by project activities

Stakeholders include

the project sponsor and project team

support staff

customers

users

suppliers

opponents to the project

Importance of Stakeholders

Project managers must take time to

identify, understand, and manage
relationships with all project
stakeholders

Using the four frames of organizations

can help meet stakeholder needs and
expectations

Senior executives are very important

stakeholders

2/10/2023

System Integration & Architecture

19

20

20

Understanding Organizations

We can analyze a formal organization using the
following 4 (four) frames; by Bolman and Deal

21

2/10/2023

System Integration & Architecture

21

Understanding Organizations
We can analyze a formal organization using the
following 4 (four) frames; by Bolman and Deal

Structural frame:
Focuses on roles and
responsibilities,
coordination and control.
Organizational charts
help define this frame.

Human resources frame:
Focuses on providing
harmony between needs of
the organization and needs
of people.

Political frame:

Assumes organizations are
coalitions composed of
varied individuals and
interest groups. Conflict
and power are key issues.

Symbolic frame:

Focuses on symbols and
meanings related to events.
Culture is important.

2/10/2023

System Integration & Architecture

22
Structural frame:
Focuses on roles and
responsibilities,
coordination and control.
Organizational charts
help define this frame.

Human resources frame:
Focuses on providing
harmony between needs of
the organization and needs
of people.

Political frame:

Assumes organizations are
coalitions composed of
varied individuals and
interest groups. Conflict
and power are key issues.

Symbolic frame:

Focuses on symbols and
meanings related to events.
Culture is important.

Basic Organizational Structures

 Organizational structure depends on the company and/or the

project.

 The structure helps define the roles and responsibilities of the

members of the department, work group, or organization.

 It is generally a system of tasks and reporting policies in place to give

members of the group a direction when completing projects.

 A good organizational structure will allow people and groups to

work effectively together while developing hard work ethics and
attitudes.

 The four general types of organizational structure are functional,

divisional, matrix and project-based.

2/10/2023

System Integration & Architecture

23

2/10/2023

System Integration & Architecture

24

Basic Organizational Structures

25

2/10/2023

System Integration & Architecture

25
Project Phases and the Project Life Cycle

A project life cycle is a collection of

project phases

Project phases vary by project or industry,

but some general phases include

Initiation

Planning

Execution

Closure

26

2/10/2023

System Integration & Architecture

26
Phases of the Project Life Cycle

27

2/10/2023

System Integration & Architecture

27

Product Life Cycles

Products also have life cycles

The Systems Development Life Cycle (SDLC) is

a framework for describing the phases involved in
developing and maintaining information systems

Systems development projects can follow

Predictive models: The scope of the project can be

clearly articulated, and the schedule and cost can be
predicted.

Adaptive models: Projects are mission driven and

component based, using time-based cycles to meet target
dates.

2/10/2023

System Integration & Architecture

28
Predictive Life Cycle Models

 The waterfall Repetitions of iterative development are

referred to as sprints, which normally last thirty days. The
spiral model shows that software is developed using an
iterative or spiral approach rather than a linear approach.

 The incremental release model provides for progressive

development of operational software.

 The prototyping model is used for developing prototypes

to clarify user requirements.

 The RAD model is used to produce systems quickly

without sacrificing quality.

29

2/10/2023

System Integration & Architecture

29
Adaptive Life Cycle Models

 Extreme Programming (XP): Developers program in

pairs and must write the tests for their own code. XP
teams include developers, managers, and users.

 Scrum:

Repetitions of

iterative development are

referred to as sprints, which normally last thirty days.
Teams often meet every day for a short meeting, called a
scrum, to decide what to accomplish that day.

Works

best for object-oriented technology projects and requires
strong leadership to coordinate the work

30

2/10/2023

System Integration & Architecture

30

Distinguishing Project Life Cycles and

Product Life Cycles

The project life cycle applies to all projects, regardless of the

products being produced

Product life cycle models vary considerably based on the nature of

the product

Most large IT systems are developed as a series of projects

Project management is done in all the product life cycle phases

System Development Life Cycle

2/10/2023

System Integration & Architecture

31

2/10/2023

System Integration & Architecture

32

Requirements

2/10/2023

System Integration & Architecture

33

Requirements

A system cannot be analyzed, designed, implemented and

evaluated unless the problem is understood, and
requirements elicited.

Requirements are fundamental basis of all the system

development processes.

System architects will always base of the requirements

elicited by the system analyst to design an architectural
view of the system. Besides much as the system is
designed and there is need for integration.

2/10/2023

System Integration & Architecture

34

What are requirements?

Requirements are statements that identify the

essential needs of a system in order for it to have
value and utility.

2/10/2023

System Integration & Architecture

35

Characteristics of Good Requirements

2/10/2023

System Integration & Architecture

36

Characteristics of Good Requirements cont….

1. Precise and minimally constraint

- Describes what system should do, not how it does it.

- Uses shall to require an action, "Should" to state a goal

- If possible has a numeric target instead of qualitative term

2. Traceable & Testable

- Each requirements has a unique label

- Each requirement cleanly traces to acceptance test

- Requirement satisfaction has a feasible yes/no test

3. Supported within context of system

- Supported by rationale or community

- Uses consistent terminology

- Any conflicting requirements

2/10/2023

System Integration & Architecture

37

Requirements Life cycle

2/10/2023

System Integration & Architecture

38

The
User

Elicitatio
n Phase

Organisat
ion Phase

Analysis

Phase

Prototype

Phase
Transform

to spec

Raw
Req’ts

Organised

Req’ts

Analysed

Req’ts

Complete

user
Req’ts

SPECS

Requirement Life Cycle .. Cont..

 Elicitation Phase

The starting point of the requirement's engineering process is an

elicitation process that involves a number of people to ensure
consideration of a broad scope of potential ideas and candidate
problems

 Organisation Phase

In this step there is no transformation of the requirements, but

simple classification and categorization. For example, requirements
may be grouped into functional vs. nonfunctional requirements.

 Analysis Phase

This represents a transformation.

2/10/2023

System Integration & Architecture

39

Requirement Life Cycle .. Cont..

 Prototype Phase

In this way poorly understood requirements may be tested and

perhaps strengthened, corrected, or refined. This activity is
often done as a proof of concept and serves to induce
feedback from both the stakeholders and engineers.

 Requirements documentation and specification

This represents the requirements as the finished product of the

stakeholder requirements team. The requirements are compiled
into a requirements list or into some equivalent document
format. These collected requirements are then transformed
into a specification.

2/10/2023

System Integration & Architecture

40

Requirements

elicitation,

documentation, and

maintenance

2/10/2023

System Integration & Architecture

41

Requirements elicitation

Requirements determination addresses the

gathering and documenting of the true
and real requirements for the Information
System being developed.

Requirements is the wants and /or needs

of the user within a problem domain. elicit

2/10/2023

System Integration & Architecture

42

Requirements determination questions

Requirements determination questions

Who does it?

What is done?

Where is it done?

When is it done

How is it done

Why is it done?

2/10/2023

System Integration & Architecture

43

Systems Requirements

Characteristics or features that must be included

to satisfy business requirements

Outputs

Inputs

Processes

Timing

Controls

Volumes. sizes, and frequencies

Data/Information collected can be about; people,

organisation, work and work environment.

2/10/2023

System Integration & Architecture

44

Fact – Finding Methods

Sampling (of existing documentation, forms,

and databases).

Research and site visits. (Participation)
Observation of the work environment.
Questionnaires.
Interviews.
Prototyping.
JAD/Joint requirements planning (JRP).

2/10/2023

System Integration & Architecture

45

Types of Requirements

2/10/2023

System Integration & Architecture

46

Types of Requirements

User Requirements: these are statements in Natural language plus diagrams of services the system
provides, together with its operational constraints. These can be categorised into 2; functional requirements
and non-functional requirements

Functional requirements

Describe what the system should do

Non-functional requirements

Consists of Constraints that must be adhered to during development (design

and implementation)

Remember ‘Constraints.’

System requirements

What we agree to provide

Describes system services

Contract between Client and contractor

2/10/2023

System Integration & Architecture

47

Functional requirements

What inputs the system should accept

What outputs the system should produce

What data the system should store that other
systems might use

What computations the system should
perform

The timing and synchronization of the above

2/10/2023

System Integration & Architecture

48

Non-functional requirements

Non-functional requirements are global

constraints on a computer system

 e.g. development costs, operational costs, performance, reliability,

 The challenge of Non-functional

requirements:

 Hard to model

 Usually stated informally, and so are:

often contradictory,

difficult to enforce during development

difficult to evaluate for the customer prior to delivery

2/10/2023

System Integration & Architecture

49

Non-functional requirements

 Define system properties and constraints e.g.

reliability, response time and storage requirements.
Constraints are I/O device capability, system
representations.

 Process requirements may also be specified

mandating a particular programming language or
development method

 Non-functional requirements may be more critical

than functional requirements. If these are not met,
the system is useless.

2/10/2023

System Integration & Architecture

50

Examples of NFR

Interface requirements

how will the new system interface

with its environment?

User interfaces and “user-

friendliness”

Interfaces with other systems

Performance requirements

Time - response time

Throughput - transactions per second

2/10/2023

System Integration & Architecture

51

Examples of NFR

Security

permissible information flows

Or who can do what

Survivability – e.g. system will need to survive fire

natural catastrophes, etc

Operating requirements

physical constraints (size, weight),

personnel availability & skill level

accessibility for maintenance

environmental conditions

2/10/2023

System Integration & Architecture

52

Examples of NFR

Lifecycle requirements

Maintainability, Enhanciability, Portability, expected

market or product lifespan

limits on development

E.g. development time limitations, resource

availability and methodological standards.

Economic requirements

e.g. restrictions on immediate and/or long-term

costs.

2/10/2023

System Integration & Architecture

53

Requirements Documentation

There are basically two types of documents

released from the requirements elicitation phase.
These include;
User Requirements Specification Document
System requirements specification Document

2/10/2023

System Integration & Architecture

54

User Requirements Specification –

URS/URD

 The URS document outlines precisely what the User (or

customer) is expecting from this system.

 User Requirement Specification may incorporate the

functional requirements of the system or may be in a
separate document labelled the Functional
Requirements Specification - the FRS.

The URD has the following

information:

1.

Functional Requirements

2.

Non-Functional Requirements

2/10/2023

System Integration & Architecture

55

System Requirements Specification

Document

A detailed description of the system services.
What do we agree to provide?

A structured document setting out detailed

descriptions of the system services.

Written as a contract between client and

contractor.

2/10/2023

System Integration & Architecture

56