Principles of Integration

IT31032 SYSTEM INTEGRATION AND ARCHITECTURE

Thilina Samarasinghe
Lecturer | MBA(Gen) | MSc (CyberSec) | BSc (Hons) | CCNA
 Instructions to the reader

• Green Color Links – Read to brush your Knowledge

• Red Color Links – Read for exam purposes

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

Why we integrate systems (Purpose of System Integration)

Organizations choose system integration mainly to boost productivity and enhance the quality of their operations
and projects.

Key aspects of system integration:

• It's a project: Integration is managed like a structured project.
• Collaboration is essential: Team members need to work closely together.
• Project management is key: A manager oversees the process to ensure smooth execution.
• Success depends on teamwork: The project’s success relies on everyone’s cooperation.
• Relying on others: Teams depend on each other’s expertise and contributions.
• Teamwork matters: Effective teamwork ensures the integration runs smoothly.
• Regular reporting: Team members need to keep others informed of progress and challenges.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 Stakeholders

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

.

Who are operational/ project stakeholders

• Definition of stakeholders:

o Individuals or organizations directly involved in the project or affected by its execution and outcome.

• Positive or negative impact:

o Stakeholders may benefit or face consequences from the project’s success or failure.

• Who are stakeholders?

o People or groups with an interest in the project.

o Those who stand to gain or lose based on the project’s results.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 Types of Stakeholders in Project Management
• Internal Stakeholders
• Stakeholders within the organization.
• Examples:
• Team members
• Managers
• Executives
• External Stakeholders
• Stakeholders outside the organization.
• Examples:
• Customers
• Users
• Suppliers
• Investors

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

The stakeholders in each project will vary depending on the type of project and industry, but here are a few
examples of the types of stakeholders in project management you might need to consider:

•Project manager​ •Company owners​ •Consultants​​

•Team members​ •Investors​ •Customers​​
•Managers​ •Sponsors​ •End users​​
•Resource managers​ •Financiers
•Executives​ •Suppliers​
•Senior management •Vendors​

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 Principles of
Integration

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 core guidelines that should be followed when combining different parts or systems into a unified
whole

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

Principles of Integration

• The principle of Alignment

• The principle of Partitioning
• The principle of Induction
• The principle of Limitation
• The principle of Forethought
• The principle of Planning
• The principle of Loss

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

1. The principle of Alignment:

• Synchronization of Components:

o Ensures all parts and subsystems work together seamlessly.

o Focuses on both functional behavior and overall system goals.

• Alignment of Strategies:

o Aligns business strategies, stakeholder interests, and project objectives.

o Leads to improved outcomes in product or service development.

Project Results
Business Strategies Stakeholder Requirements

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

Key Points on Project Strategies and Enterprise Goals

• Alignment of Strategies:
• Project strategies are designed to achieve positive project outcomes.
• Enterprise Objectives:
• Projects help fulfill the enterprise's goal of generating revenue and profitability.
• Two Main Business Requirements:
• Revenue and Profitability:
• Projects must provide financial returns aligned with enterprise policies.
• Operational Efficiency:
• Projects must function effectively within constraints such as time, cost, and resources.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 Constraints and Realities of Projects:
• Scope: Clearly defined project deliverables.
• Cost: Budget limitations.
• Time: Strict deadlines.
• Risk: Managing uncertainties.
• Resources: Availability of materials and manpower.
• Quality: Meeting the desired standards.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

Key Points on Integrating Stakeholder Requirements and Ideas

1. Integration of Stakeholder Strategies:

• Combine various stakeholder strategies into a comprehensive integration plan.

2. Stakeholder Perspectives on Projects:

• Deliverables: Provide a product or service within budget and schedule constraints.

• Political or Social Needs: Address societal or political concerns.

• Safety and Survival: Respond to critical safety or survival issues.

• Efficiency: Speed up processes to serve more people or needs.

• Waste Reduction: Minimize resource wastage.

• Environmental Impact: Ensure operations are environmentally friendly.

• Technological Advancements: Integrate modern technologies to enhance functionality.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |
2. The principle of Partitioning:

Simple Points on Partitioning and Integration

• Breaking Down Complex Systems:

• Split a large system into smaller, easier-to-manage parts.

• This makes integration and maintenance simpler.

• Independent Development (Work on Parts Separately):

• Each part can be built, tested, and combined on its own.

• Boundary Contiguity (Clear Boundaries):

• Problems become easier to handle when the parts are well-defined and fit together properly.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

2. The principle of Partitioning:

Simple Points on Partitioning and Integration

• Balancing Perspectives (Focus on Both Big and Small Issues)

• Looking at the big picture is important, but don’t ignore smaller problems along the way.

• Simplicity Equals Success:(Keep It Simple):

• The simpler the approach, the higher the chance of successful integration.

• Decomposition of High-Level Concepts (Breaking Down Ideas):

• Turn complex ideas into small, clear steps to make them easier to understand and implement.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

3. The principle of Induction:

• Learning from Success:

o Draw general patterns or guidelines from successful integration instances.

o These can guide future integration efforts and help define best practices.

• Inductive Reasoning in Integration:

o Use inductive reasoning to guide integration management.

o This involves applying insights from specific cases to broader situations.

• Recursive Thinking:

o Recursive thinking means breaking down large problems into smaller, simpler problems.

o These smaller problems should have the same structure as the larger one, making them easier to solve.
Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |
3. The principle of Induction:

Key Points on Inductive Reasoning

• Definition of Inductive Reasoning:

• A method of reasoning where a general principle is derived from a set of specific observations.

• It involves making broad generalizations based on individual instances.

• Inductive vs. Deductive Reasoning:

• Inductive reasoning goes from the specific to the general.

• Deductive reasoning goes from general information to specific conclusions.

• Main Difference:

• Inductive reasoning builds conclusions based on observed patterns, while deductive reasoning applies

established principles to draw conclusions.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |
Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |
 You may have come across inductive logic examples that come in a set of three statements.
These start with one specific observation, add a general pattern, and end with a conclusion.

Stage Example 1 Example 2

Specific observation Nala is an orange cat and she Baby Jack said his first word at
purrs loudly. the age of 12 months.
Pattern recognition Every orange cat I’ve met purrs All observed babies say their
loudly. first word at the age of 12
months.
General conclusion All orange cats purr loudly. All babies say their first word at
the age of 12 months.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

Key Points on Deductive Reasoning

• Definition of Deductive Reasoning:

• A logical approach that progresses from general ideas to specific conclusions.

• It is often contrasted with inductive reasoning, which moves from specific observations to general

conclusions.

• Also Known As:

• Deductive reasoning is also called deductive logic or top-down reasoning.

• Structure of Deductive Reasoning:

• It typically follows a "premise-premise-conclusion" format.

• You begin with a premise, add another premise, and form a conclusion based on them.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 Premise​ All insects have exactly six legs.​
Premise​ Spiders have eight legs.​
Conclusion​ Therefore, spiders are not insects.​

Premise​ Blue litmus paper turns red in the presence of acid.​

Premise​ The blue litmus paper turned red after I dropped some
liquid on it.​
Conclusion​ Therefore, the liquid is acidic.​

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

4. The principle of Limitation:

• Acknowledging Constraints:

o System integration must consider budget, time, resources, and technological limitations.

o Effective integration involves making informed decisions within these constraints.

• Importance of Architecture:

o The success of integration depends on how well the architecture captures stakeholder

requirements.

• Potential Failure in Architecture:

o Some architects may fail to capture the full scope of requirements, leading to incomplete

integration.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

5. The principle of Forethought

• Integration as a Key Activity:

o Integration is a primary and essential activity, not just an afterthought after development.

• Proactive Thinking:

o It's important to consider potential challenges, risks, and future changes during the integration process.

o This proactive approach helps to mitigate issues and ensures the long-term viability of the system.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

6. The principle of Planning

• Creating a Comprehensive Plan:

o A detailed integration plan outlines tasks, responsibilities, timelines, and milestones.

o A well-structured plan guides the integration process and helps manage potential complexities.

• Importance of Completion Date:

o Knowing the completion date is essential for effective integration planning.

• Focus on Task Duration:

o Instead of focusing solely on task completion, prioritize task duration for better integration planning.

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

 7. The principle of Loss

Recognizes that system integration may involve

sacrificing certain aspects, such as legacy functionalities
or standalone capabilities, in favor of achieving overall
system efficiency, performance, and compatibility.

• For every action there is a loss

• That loss is quantifiable.

• When two objects are integrated, energy is expended .

• spend or use up (a resource such as money or energy).

Thilina Samarasinghe | MBA(Gen) | MSc (CyberSec) | BSc (Hons) |

THANK YOU