Section: BS in Information Technology - 4A

Day: Thursday
Time: 5:00-8:00
COURSE OBJECTIVE :
• The course aims to teach student about system integration
issues, including integration in a system of systems and
federation of systems, role of architectures in systems
integration, performance and effectiveness.
• You will build upon the ICT knowledge gained throughout the
degree program by developing skills in enterprise architecture
planning (EAP) and in enterprise application integration (EAI).
COURSE OBJECTIVE :
• Using EAP, you will learn to create architectures that define and
describe the data, applications, and technology needed to support
organizations.
• In applying EAI, you will gain experience in creating strategic
business solutions using Web services and middleware to
integrate the functionality of an organization’s existing
applications, commercial packaged applications, and new code.
INTENDED LEARNING OUTCOMES :
1. To define different terminologies on software and systems integration.
2. To describe the basic concepts of software and systems integration
methods.
3. Define and explain key concepts, approaches, requirement, life cycles,
and strategies related to systems integration projects.
4. Describe and apply organizational and managerial issues related to
systems integration projects.
5. Explain and utilize key systems integration architecture, planning,
methodologies, and Technologies.
PREFACE :
“The need to transform today’s inflexible business environment to an agile
enterprise that can change direction rapidly has never been greater .Yet the
structures, processes, and systems that we have today are inflexible: They
are incapable of rapid change.”
▪ More computer hardware, or software, or packages, or staff, or
outsourcing is not the solution. They are part of the problem.
▪ This is not a computer problem. It is a business problem!
▪ Needed methods and technologies that enable senior managers—
together with their planners, business managers, business experts, and IT
staff—to work together to achieve business change, with each group
contributing its specific expertise.
SOME TECHNICAL WORDS:
▪ A COMPUTER PROGRAM is a set of instructions that tells a computer
what to do.
▪ Programs are also called a SOFTWARE; software comes in two broad
categories.
▪ SYSTEM SOFTWARE describes the programs that operate the
computer like operating systems.
▪ APPLICATION SOFTWARE describes the program that allows the user
to complete tasks such as creating documents, calculating paychecks
and playing games.
SOME TECHNICAL WORDS :
▪ HARDWARE are physical devices that make up a computer system.
▪ MACHINE LANGUAGE most basic circuitry level language that
computers use to control the operation of the switches represented by
1 and 0.
▪ HIGH LEVEL PROGRAMMING LANGUAGE allows you to use limited
keywords that’s serves as an identifier that performs task like read,
write and add.
▪ SYNTAX or rules of the language with limited vocabulary along with
set of rules on using that vocabulary.
SOME TECHNICAL WORDS :
▪ COMPILER is a software use to convert the high level language into a
machine code.
▪ SYNTAX ERROR is an error message every time a programmer commits
an error.
▪ METHODS provide effective methods for ensuring productivity-
enhancing processes and resources, and plan for problems that affect
integration environments.
▪ SOFTWARE - Software design, code and unit testing, plans, and testing
procedures combined with implemented systems, inform us that the
created software is being done correctly. It's key to "peer feedback".
SOME TECHNICAL WORDS :
▪ SYSTEMS ensure that software design and development standards are
allocated for systems to be developed and documented as ready for
the software combination and system integration.
▪ INTEGRATION compasses where applications, programs, firmware and
hardware can be merged to work together as one.
▪ ARCHITECTURE is defined as a formal description and representation of
a system's structure and behavior.
SYSTEM INTEGRATION:
- is defined as the process of connecting and bringing all components of
a subsystems into one system.
- It make sure that the whole system functions as required. It is process
of integrating all the components of a system either physical or virtual
components.
- The physicalcomponents is the hardware, machine systems, inventory
and etc. The virtual components composed of data stored in databases,
design and algorithms used in the software or applications.
SYSTEM ARCHITECTURE:
- is the conceptual model that defines the structure, behavior and flow of
a system.
- is the abstract, conceptualization-oriented, global, and focused to
achieve the mission and life cycle concepts of the system. It also
focuses on high-level structure in systems and system elements.
- It addresses the architectural principles, concepts, properties, and
characteristics of the system-of-interest. It may also be applied to more
than one system, in some cases forming the common structure,
pattern, and set of requirements for classes or families of similar or
related systems.
PROGRAM AND PROJECT PLANNING :
- Theaim of program and project planning is to provide the required
process steps within integration efforts to expand the planning for
programs and software design/development.
- This method of preparation would ensure and define successful
strategies and outcomes for carrying out software design/development
practices, processes, and implementing procedures that support
software and system integration activities.
SYSTEM DESIGN:
- The system design method is to analyze customer requirements and
develop a software design/development migration plan to define the
architecture, components, modules, interfaces, and data needed for a
designed system to meet specified needs.
- The method of designing systems is becoming increasingly relevant as
it offers the disciplines required and applied during life cycles of
software design/development.
SOFTWARE REQUIREMENTS:
- Definedand documented software requirements provide a systematic
approach to multiple-resource development.
- Functional software interfaces, performance, testing, and
manufacturing results with necessary plans, documentation, and
procedures become the basis for software design or development.
- This effective method is used for initial software requirements creation
and modifications to design baselines
ORIGIN OF INFORMATION SYSTEM PROJECTS :
To understand more the information system flow means you can look
into the details of an IS project. A new or changed IS development
projects come from problems, opportunities, and directives and are
always subject to one or more constraints.
ORIGIN OF INFORMATION SYSTEM PROJECTS :
• Problems may either be current, suspected, or anticipated. These are
undesirable situations that prevent the business from fully achieving its
purpose, goals, and objectives (users discovering real problems with existing
IS).
• Opportunities are chances 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.
• Directives are new requirements that are imposed by management,
government, or some external influence i.e. are mandates that come from
either an internal or external source of the business.
ORIGIN OF INFORMATION SYSTEM PROJECTS :
➢ In working on a project, it must operate in a broad organizational
environment and cannot be run isolated. The project managers need to
take a holistic or systems view of a project and understand how it is
situated within the larger organization.

➢ One important component to be considered is the stakeholders. These

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.
ORIGIN OF INFORMATION SYSTEM PROJECTS :
According to the Standish Group’s report “CHAOS 2001: A Recipe for
Success,” the following items help IT projects succeed, in order of
importance:

• Executive support • Standard software infrastructure

• User involvement • Firm basic requirements
• Experienced project manager • Formal methodology
• Clear business objectives • Reliable estimates
• Minimized scope
REFERENCES:
• SYSTEM INTEGRATION & ARCHITECTURE, Mr. Mubashir Ali Lecturer(Dept. of
Computer Science) [email protected]
• Nagmoti, 2020, “8 Common Types of Organizational Structures in Project
Management”, retrieved October 20, 2020 from
https://www.greycampus.com/blog/projectmanagement/common-types-of-
organizational-structures-in-project-management
• Admin, 2018, “4 Types of Organizational Structures”, retrieved October 18, 2020 from
https://online.pointpark.edu/business/types-of-organizational-structures/
• https://www.coursehero.com/file/63381843/INTRODUCTION-TO-SYSTEM-
INTEGRATION-AND-ARCHITECTUREdocx/
• https://dts.utah.gov/standard/systems-integration-architecture