SYSTEMS

INTEGRATION &
ARCHITECTURE
IT 312
REFERENCE MATERIAL:

Effective Methods for

Software and Systems
Integration

Boyd L. Summers
Author

Software and Quality Assurance Consultant in BL Summers Consulting.LLC

Technical Lead Engineer & Software Engineering and Quality
Assurance in
EFFECTIVE METHODS IN SYSTEMS
INTEGRATION & ARCHITECTURE Software Design &
Product Evaluation
Pillars of Success
Implementation
Chapter 11
Chapters 5-6

Software and
Introduction to Software Integration
Software System Delivery
Software and Chapter 7
Requirements Chapter 10
Systems Methods
Chapter 4
Chapter 1

Software and Software

Program and Project Systems Integration Subcontractor
Systems Design
Planning Chapter 8 Chapter 9
Chapter 3
Chapter 2
 R E
W A
FT
S O S
O OD
N T TH
I O M E
C T S
D U E M
O
R YS T
T
IN D S 1
N
A PT E R

H A
C
INTRODUCTION TO SOFTWARE AND SYSTEMS METHODS

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.
 Britannica Dictionary
DEFINITION OF TERMS
Software
Instructions that tell a computer what to do. It comprises the:
entire set of programs, procedures, and routines associated with the operation of a
computer system.
A set of instructions that directs a computer’s hardware to perform a task is called a
program, or software program.
The three main types of software are:
1.System software (controls a computer’s internal functioning, chiefly through an
operating system, and also controls such peripherals as monitors, printers, and storage
devices.) and
2.Application software, directs the computer to execute commands given by the user and
may be said to include any program that processes data for a user. It includes word
processors, spreadsheets, database management, inventory and payroll programs, and
many other “applications.”
3.Network software, which coordinates communication between the computers linked in
a network.
DEFINITION OF TERMS

Methods
different ways of approaching software
development and delivery. 
(Ex. Waterfall method, Agile method)
DEFINITION OF TERMS

System
system is an organized collection of parts (or subsystems) that are highly
integrated to accomplish an overall goal.
The system has various inputs, which go through certain processes to
produce certain outputs, which together, accomplish the overall desired
goal for the system.
So a system is usually made up of many smaller systems, or subsystems.
For example, an organization is made up of many administrative and
management functions, products, services, groups and individuals. If one
part of the system is changed, the nature of the overall system is
changed, as well.
DEFINITION OF TERMS
Integration
the act or process of uniting different things.
-Merriam Dictionary
Integration (in software integration)
The combining of subroutines, software modules or full programs with other
software components in order to develop an application or enhance the
functionality of an existing one. Often requiring a lot of source code modification,
developers, as well as IT staff, may spend a large amount of their time performing
software integration.
Example of Integrated software
Microsoft Office, which contains programs used in an office environment (Excel, Outlook, and Word). Each
suite included word processing, spreadsheet, organizer/scheduler, database, graphics, and e-mail programs—
all designed to work seamlessly together.
DEFINITION OF TERMS
Integration (in systems integration)
brings together multiple individual subsystems or sub-components with different
functions into one functional system in order to work as one entity. It ensures that
all components work together in harmony to preserve productivity and accurate
data analysis.

Example:
administration, data collection, and processing payments. ----these systems often
work separately, leading to lost time and even money. When systems are
connected, they operate smoothly and bring many more benefits than while
working separately.
DEFINITION OF TERMS

Example of System Integration:

Client’s Requirement: they need a payment management system that allows for
regular payment collection from users. Such integration was needed for this
system to operate properly.

Problem: Originally, the payment collection system was not connected to the
online payment gateway, so the gateway couldn’t be configured in the payment
collection system panel right away. That is why the integration was essential to
ensure data flow between the systems. The goal was to provide a solution that
would safely connect the systems and make them cooperate smoothly and
effectively.
DEFINITION OF TERMS

Solution: Integrate platform 1 that automates recurring payment

collection (i.e Lazada, shopee) and makes it possible to charge users
regularly with an online payment gateway (i.e. paymaya, gcash,
paypal) suitable for e-commerce and SaaS that allows customers to
make online payments.

Process: API integration, which helped users connect their cards.

Then, payments could be charged monthly (another implemented
functionality covered discounts and invoices.)
MAIN ADVANTAGES OF INTEGRATION:

Speeds up company processes

Increases work efficiency
Ensures effective information exchanges
Enables basic system operations.
S O F T WA R E A N D S Y S T E M S I N T E G R AT I O N M E T H O D S

To develop, operate, and maintain software and systems

integration capabilities inside work product facilities,
there must be a major discipline in supporting the
entire software life cycle (i.e., planning, systems,
requirements, design, builds, installations,
integration, subcontractors, quality, and delivery)
that does need to be completely understood.
The critical understanding and the start of the right
disciplines of these methods will empower and
achieve effective, flexible, and quality results in an
integration environment.

Start with the right disciplines. ! In the software industry/companies, military and aerospace program and projects do
become effective by the implementation of achievable schedules, sound processes, and
working solutions for software and systems integration.
START WITH THE RIGHT DISCIPLINE.
- BOYD L. SUMMERS
Methods: Provide effective methods to ensure processes and tools improve productivity and prepare
for the challenges that have an impact on integration environments

Software: Software design, code and unit test, plans, and test procedures integrated with
applied systems, tell us that the software developed is done right. “Peer reviews” are key.
Methods
Systems: Accomplish allocation of software design and engineering practices for systems to
be defined and documented as ready for the combination of software and systems integration.

Integration: This is the compass to combine software, systems, firmware, and hardware to
work together as one.
START WITH THE RIGHT DISCIPLINE. - BOYD L. SUMMERS
Effective
Right design, test, and procedure

Methods Software

Well-defined and documented Working software and systems

Systems Integration

ROCK SOLID
 The purpose of program and project planning is to
provide the necessary process/steps to scope out
1.2 PROGRAM AND PROJECT PLANNING
--PROGRAM
-PROJECT
-PLANNING
-SENIOR MANAGEMENT
-PROGRAM AND PROJECT PLANNING
-PLANNED SCHEDULES
-DEVELOPMENT PLAN
planning for systems and software design/
development within integration efforts.
-TEAMWORK
-TEAM OF CONDUCT
-CASE STUDY

This type of planning will ensure and establish

effective plans and results for performing the
disciplines for software design/development,
processes, and procedures for the implementation
supporting software and systems integration
activities.
 P L A N N I N G A N D E N G I N E E R I N G TA S K

Software Risk
Engineering Communication Planning Management Deployment
Tasks
1.2  PROGRAM Systems design X
AND PROJECT Requirements X
PLANNING Design X
Configuration X
control
The planning and engineering Integration X
task presented here explains the Delivery X
disciplines and methods
pertaining to communication, Subcontractor X
planning, risk management, and Quality product X
deployment. evaluations X
 The method for systems design is to analyze
customer requirements and develop a software
1.3  SYSTEMSDESIGN design/development migration plan for defining
-SYSTEM DESIGN DEFINITION
-SYSTEM ENGINEERING PLAN
-SOFTWARE ARCHITECTURE EVALUATION
the architecture, components, modules, interfaces,
and necessary data for a designed system to
satisfy specified requirements.

The systems design method is increasingly

important as it provides the disciplines required
and implemented during software
design/development life cycles.
 Defined and documented software requirements
provide a systematic approach to development
from multiple resources.
The results of functional software interfaces,
1.4  SOFTWARE performance, verification, and production with
REQUIREMENTS
-DEFINITION OF SOFTWARE REQUIREMENT required plans, documentation, and procedures
-REQUIREMENTS AND DOCUMENTATION
-MANAGING REQUIREMENTS TOOL
-RELEASED SOFTWARE REQUIREMENTS
become the basis for software design or
development.
This effective method is applied for initial
development of software requirements and
changes to requirement baselines.
You can easily stay on track and ensure that all the deadlines are being followed throughout the project life cycle. A well-defined project scope
management helps avoid common issues like: Constantly changing requirements. Pivoting the project direction when you are already mid-way.
It provides the team with guidelines for making decisions about change requests during the project.
 The software design/development definition is that of
a systematic approach for the creation of software
1.5  SOFTWARE design and its development to reflect design and
DESIGN/ software definitions applicable to the work product.
DEVELOPMENT The resulting method defines details about the work
-DEVELOPMENT PLAN
-SOFTWARE DESIGN DECISIONS
-PEER REVIEWS
product architecture, behavior, components, and
-SOFTWARE DESIGN/DEV SUGGESTIONS
TWO SOFTWARE DESIGN/DEVELOPMENT METHODS:
CONCURRENT SOFTWARE DESIGN/DEVELOPMENT
interfaces. The software requirements are established
AND LEAN SOFTWARE DESIGN/DEVELOPMENT,
-IMPLEMENTATION OF AGILE SOFTWARE PROCESSES, between the elements of the design/development.
-CONFIGURATION MANAGEMENT
-CMMI PROCESSES,
-LEAN AND SIX SIGMA TOOLS AND PHILOSOPHIES
The documented program and project plan provide
SOFTWARE COMPANIES
traceability according to software-defined processes
and procedures.

The software architecture document provides a comprehensive overview of the architecture of the software system. It serves as a communication medium between the software architect and
other project team members regarding architecturally significant decisions which have been made on the project.
 The importance of software implementation
is a requirement for informal and formal
integration testing in a development,
integration facilities, or the software systems
1.6  SOFTWARE
integration facility (S/SIF).
IMPLEMENTATION
-CONFIGURATION MANAGEMENT AND TOOLS
-SOFTWARE MEDIA AND DATA
-FUTURE TRENDS
The software implementation method for
testing provides assurance that engineering
builds function as expected to enable smooth
execution for verification and test activities.
 An incremental software and test approach
adds the functions incrementally in a series
of engineering builds.
The software design/ development matures
1.6  SOFTWARE through a series of engineering builds.
IMPLEMENTATION As software is tested and demonstrated, build
plans are modified for subsequent builds
based on lessons learned from previous
engineering builds, troubleshooting, and
checkout.
 All software delivered or implemented by
software integration or testing is processed
through a configuration and controlled
1.7  SOFTWARE software library system that maintains the
INTEGRATION official status accounting for each delivery.
-SOFTWARE INTEGRATION STRATEGY
-DEVELOPMENT FACILITY
-SOFTWARE INTEGRATION SETUP AND LOG
-SOFTWARE TEST COMPLETION
-INTEGRATION VERIFICATION AND VALIDATION
-CONFIGURATION REVIEWS AND AUDITS The integration tasks require that software
design/development and test processes be in
place to ensure integration is ready for team
troubleshooting and checkout.
 The software and systems integration method
provides a consistent approach to effective integration
activities.
1.8  SOFTWARE AND The software units, components, and subsystems are
SYSTEMS assembled in accordance with defined and
INTEGRATION documented integration procedures to ensure that the
-S/SI PLAN
-S/SI FACILITY
-INTEGRATION SETUP
software and systems elements are assembled
-FORMAL ENGINEERING BUILD properly.
-TEST TEAM
-QUALITY PARTICIPATION IN S/SI
-EFFECTIVE METHODS FOR S/SI
The integration levels and the development plan (DP)
for software determine if constructed elements are
ready and subject to verification or validation
activities.
 The software subcontractor roles and responsibilities
describe how a program and projects can benefit and
rely on outside companies’ resources to provide
required software and hardware products to be under
1.9  SOFTWARE contract and effective.
SUBCONTRACTOR
-PROGRAM AND PROJECT
SELECTION The subcontractor presentation to the customer
-SUBCONTRACTOR APPROACH
-SOFTWARE SUBCONTRACTOR PLAN must be understood from the start of the presentation
to the end. Questions can be asked by the customer
to ensure that answers meet the needs for reliability
and support.
 Chapter 1 Introduction to Software and Systems Methods

When it is time for software and systems

integration delivery, the delivery requires
integration testing to be performed to provide
1.10  SOFTWARE AND
SYSTEMS
assurance that both software and systems are
INTEGRATION integrated and working together.
DELIVERY
-SOFTWARE MEDIA AND DATA DELIVERY
-FIRST ARTICLE INSPECTION
-FUNCTIONAL AND PHYSICAL CONFIGURATION The integration practices ensure that units
AUDIT
tested are complete and documented prior to
the official delivery for the customer.
 An effective product evaluation method
provides the necessary process steps to conduct
1.11  PRODUCT and perform continuous evaluations of software
EVALUATION work products during the design/development
-QUALITY ASSURANCE
-PRODUCT EVALUATION SCHEDULE life cycle and integration activities.
-ARTIFACTS
-AUDIT FINDINGS
-CORRECTIVE ACTIONS
-QUALITY METRICS
-QUALITY MANAGEMENT SYSTEM Numerous product evaluation tools and
-SOFTWARE PROCESS
-STRESS MANAGEMENT TECHNIQUES checklists are developed with associated
-SOLVING QUALITY ISSUES
scheduled processes to perform required audits
and evaluations.
 Defined software disciplines include an
approach or method during the software life
cycle for a program and projects to provide a
plan from start-up to final delivery to the
customer.
1.12  CONCLUSION

Many methods were discussed but the

number one method is “quality first”; the
other methods come in second and so on as
illustrated in the next slide.
EFFECTIVE
METHODS FLOW
 Many program and project meetings are called by senior
managers; in attendance are software and hardware engineers.
In those types of meetings, the hardware teams will sit on one
side of the table, and the software team will sit on the
opposite side.
That situation is unique, but that is how it is at times. The senior
1.12  CONCLUSION managers and program and project managers attend meetings
and discuss with the two teams that the software or system is
not working correctly when it is time for delivery to
integration facilities.
There is finger-pointing, and both teams may blame the
opposite team for the problem. The senior manager then
points to the program and project managers and says, “Fix
this problem.”
 That is why effective methods for software
and systems integration need to have
hardware and software designers working
together to solve issues that could have an
1.12  CONCLUSION impact on integration, quality, and delivery
schedules to the customer.
END