Scribd
Upload
6 views22 pages

Chapter 1 - Lesson

The document outlines methods and strategies for systems integration and architecture, emphasizing the importance of program and project planning throughout the software life cycle. It covers key elements such as teamwork, software design and development, implementation, and integration testing, highlighting the need for clear communication and structured processes. Additionally, it discusses the roles of software subcontractors and the significance of product evaluation during the integration activities.

Uploaded by

artkaine lopero
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views22 pages

Chapter 1 - Lesson

The document outlines methods and strategies for systems integration and architecture, emphasizing the importance of program and project planning throughout the software life cycle. It covers key elements such as teamwork, software design and development, implementation, and integration testing, highlighting the need for clear communication and structured processes. Additionally, it discusses the roles of software subcontractors and the significance of product evaluation during the integration activities.

Uploaded by

artkaine lopero
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

ITP622:

Systems Integration &


Architecture
Lesson 2: Systems Integration
Methods and Strategies
Systems Integration Methods & Strategies

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
Systems Integration Methods & Strategies

Effectivity Methods Software

Systems Integration
Program and Project Planning
The purpose of program and project planning is to provide the necessary
process steps to scope out planning for systems and software design/
development within integration efforts.
Program and Project Planning

Planned Schedules: The planned schedule defines tasks and processes to be


conducted for implementation of those tasks and processes. The schedules that
are planned affect team capabilities for risk assessment, configuration control,
and quality.
Program and Project Planning
Development Plan: The critical items pertaining to a documented development
plan consist of planned schedules and provide engineering information and
direction for the production of software. All major software design/development
activities require consistency in accordance with the steps outlined in the use of
development planning, including the following:

○ Definition of entry and exit criteria for the software design/development

○ Review and assessment of the work product and task requirements


Program and Project Planning

Development Plan: (continued)

o Definition or updates of the process for each software activity

o Development or update of the estimating process

o Development of initial cost and schedule estimation and risks

o Preparation of detailed implementation plans


Program and Project Planning

Team Work: An important element in all software programs and projects is


teamwork, the coordination and communication within teams applied to meet
work expectations. By having trust among teams, a cohesiveness is maintained
in the work environment, and planning schedules becomes much easier to
coordinate and implement within the team.
Program and Project Planning

When struggles with everyday challenges and problems are ignored, a team may
use the required team action cycle shown below.
Program and Project Planning

Team Code of Conduct: It is okay for a team to fail but to be right at least 80% of
the time. Teams that have the privilege and are able to provide clear
communication and their own opinions seem to be successful. When one person
speaks, listen and treat that person with respect.
Program and Project Planning

Change from an individual to become a team player as shown below:


Effective Methods Flow
Systems Design

The method for systems design is:

● to analyze customer requirements and develop a software design/development


migration plan for defining 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.
Software Requirements
Defined and documented software requirements provide a systematic approach
to development from multiple resources. The results of from performance,
verification, and production with required plans, documentation, and
procedures become the basis for software design or development.

○ Functional requirements
○ Non-Functional requirements
○ Business requirements
○ Technical requirements
○ User requirements
Software Design/Development

Software design/development is a systematic process of creating software


applications, systems, or products by defining their requirements. Software
design and development requires collaboration between software engineers,
product managers, designers, and stakeholders to ensure that the final product
meets the desired goals and objectives.
Software Implementation

Software implementation refers to the process of installing, configuring, and


integrating a software system into an organization's existing technology
infrastructure, making it available for end-users to use. Software
implementation is a requirement for informal and formal integration testing in a
development, integration facilities, or the software systems integration facility
(S/SIF).
Software Integration

All software delivered or implemented by software integration or testing is


processed through a configuration and controlled software library system that
maintains the official status accounting for each delivery. The integration tasks
require that software design/development and test processes be in place to
ensure integration is ready for team troubleshooting and checkout.
Software and Systems Integration

The software and systems integration method provides a consistent approach to


effective integration activities. The software units, components, and subsystems
are assembled in accordance with defined and documented integration
procedures to ensure that the software and systems elements are assembled
properly. The integration levels and the development plan (DP) for software
determine if constructed elements are ready and subject to verification or
validation activities.
Software Subcontractor

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 contract and effective.
The subcontractor presentation to the customer must be understood from the
start of the presentation to the end.
Software & Systems Integration Delivery

When it is time for software and systems integration delivery, the delivery
requires integration testing to be performed to provide assurance that both
software and systems are integrated and working together. The integration
practices ensure that units tested are complete and documented prior to the
official delivery for the customer.
Product Evaluation

An effective product evaluation method provides the necessary process steps to


conduct and perform continuous evaluations of software work products during
the design/development life cycle and integration activities. Numerous product
evaluation tools and checklists are developed with associated scheduled
processes to perform required audits and evaluations.
THANK YOU ACTIVITY
• Divide students into 2 groups:

Scenario 1 (Software Design & Development): group 1


Imagine you're part of a software development team tasked with creating a mobile
banking application. Discuss the key steps you would take during the design and
development process. How would you collaborate with different team members
(engineers, designers, stakeholders)? What challenges might you face, and how would
you overcome them?
Scenario 2 (Software & Systems Integration): group 2
You are working on integrating a new inventory management system with a company’s
existing e-commerce platform. Discuss the steps involved in the integration process.
How would you ensure that all components (software, components, and subsystems)
work seamlessly together? What role does documentation play in this process, and how
do you ensure that the integration is verified and validated?

You might also like