Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 3: SYSTEM INTEGRATION PLANNING AND MANAGEMENT - Coggle Diagram
Chapter 3: SYSTEM INTEGRATION PLANNING AND MANAGEMENT
System Integration Methodologies
System Integration (SI):
Requires coordination of preexisting and new system components.
Used for:
Melding existing systems with new technologies.
Forming more capable systems for additional tasks or improved performance.
Enhancing existing systems.
Essential for large, complex engineered systems.
Ensures specific hardware/software components fit smoothly in a stated configuration.
Definition of System Integration (SI):
Logical, objective procedure.
Applies new or expanded performance requirements.
Efficient and timely manner.
Covers design, procurement, installation, and operation.
Involves distinct modules or subsystems.
Each module may have inherent constraints or limitations.
Key Terms in SI Definition:
Logical, Objective Procedure:
Clear to external observers with a built-in audit trail.
Efficient and Timely
: Avoids delays and bureaucratic procedures to reduce costs and deployment time.
Design, Procurement, Installation, and Operation:
Employed throughout the entire process.
Distinct Modules with Inherent Limits or Constraints:
Central to SI concept, essential when deploying configurations with devices having intimate connections.
Roles of System Integrator (SI):
Coordination of pre-existing and newly developed system components.
May lead to significant system growth, merging of systems, or combining of fragments with off-the-shelf components.
Tactical level involvement in ensuring specific hardware/software components fit in the stated configuration (also known as "configuration management").
Strategic level involvement in interpreting sponsor's performance needs into technical specifications and ensuring system requirements are met.
Planning and Project Management
SI Personnel Needs and Technical Areas:
Client defines SI requirements, specifications, constraints, and variables.
SI organization delivers necessary systems and services to fulfill client mission.
Personnel need sound technical and management skills.
Skills combine to integrate technology and operations with managerial direction.
Systems Integration Life Cycle:
Management Plan
Risk calculations, project execution plan, alternative listing.
System Architecture Development
Creation of system architecture plan for integration.
Blueprint of integration plan and proposed architecture.
Systems Design
Creation of logical and physical designs.
Preliminary and detailed designs, system tests.
Feasibility Analysis
Complete analysis of the project for decision-making.
Implementation
Design implementation, system tests, operational deployment.
Requirement's Definition and Specification
Detailed requirements listing from the customer.
Efficiency in framing requirements for both systems.
Evaluation
System review and plan for replacement/retirement.
Checking, maintaining, modifying, and enhancing components.
Objectives of System Integration (SI) Methodology:
Support problem understanding and communication throughout development stages.
Enable early capture of design and implementation needs, especially interface and interactive requirements.
Support both top-down and bottom-up design approaches.
Ensure full compliance with audit trail needs, system-level quality assurance, and risk assessment.
Facilitate definition and documentation of all program aspects.
Provide a framework for appropriate systems management application across the program.
Business Drivers and Requirements Specifications
Requirements Definition and Specifications:
Definition of requirements by use.
Review of requirements for ambiguity, conflict, and other issues.
Development of systems specifications.
Goal: Completely define and correctly interpret the client's real needs.
Functional Activities of Systems Integrators:
Conduct general studies of needs for improved system performance.
Develop detailed specifications and designs.
Conduct risk studies and implement risk minimization strategies.
Perform system analysis and design.
Develop hardware and software design.
Employ project planning and control.
Perform business management and accounting.
Develop and nurture relationships with customers and subcontractors.
Develop hardware design and specification.
Carry out configuration management.
Accomplish testing.
Implement technology-based solutions to business needs.
Train users of new systems.
Integration Strategy Specifications
Systems Integration Strategies for Success:
Strict control of overhead
Increased knowledge of client businesses
Proactive management to control costs and increase market share
Integration by Level of System: Vee Model:
System Definition (top-down branch): Successive levels of decomposition corresponding to the physical architecture of systems and system elements.
Integration (bottom-up branch): Opposite approach of composition, i.e., a level-by-level approach.
Integration Strategy:
Based on the architecture of the system.
Relies on the way the architecture of the system has been designed.
Several possible integration approaches/techniques may be used individually or in combination.
Selection of integration techniques depends on factors like the type of system element, delivery time, order of delivery, risks, constraints, etc.
Integration Techniques:
Global Integration (Big-Bang Integration):
All delivered implemented elements are assembled in only one step.
Integration "with the Stream":
Delivered implemented elements are assembled as they become available.
Incremental Integration:
In a predefined order, one or a very few implemented elements are added to an already integrated increment of implemented elements.
Subsets Integration ("Functional Chains Integration"):
Implemented elements are assembled by subsets, and then subsets are assembled together. A subset is an aggregate.
Top-Down Integration:
Implemented elements or aggregates are integrated in their activation or utilization order.
Bottom-Up Integration:
Implemented elements or aggregates are integrated in the opposite order of their activation or utilization.
Criterion Driven Integration:
The most critical implemented elements compared to the selected criterion are first integrated. Criteria are generally related to risks.