Scribd
Upload
23 views14 pages

Chapter4 Integration

Uploaded by

Trung Nguyễn
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
23 views14 pages

Chapter4 Integration

Uploaded by

Trung Nguyễn
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/ 14

8/15/2022

• Components, interfaces and integration


• Infrastructure, Middleware and Platforms
• Techniques – Data warehouses, extending
frameworks, wrappers, glue, facades
• Testing/evaluation/benchmarking
• System release: pilot and acceptance testing
and defect repair
• System support strategies and user support
plans

1
8/15/2022

 SI is essential to the development of large, complex


engineered systems.
 It is used for melding existing systems and new
technologies to form more capable systems that are
intended to take on additional tasks, exhibit
improved performance, and/or enhance existing
systems.
 SI requires the coordination of preexisting and
coexisting system components with newly developed
ones

 SIensures that specific hardware/software


components fit together smoothly in a stated
configuration

2
8/15/2022

 SIis a logical, objective procedure for


applying new and/or expanded performance
requirements in an efficient, timely manner
to the design, procurement, installation, and
operation of an operational configuration
consisting of distinct modules (or
subsystems), each of which may embody
inherent constraints or limitations.

 Logical, Objective Procedure. The SI process is


clear to external observers and all steps have a
built-in audit trail.
 Efficient and Timely. The SI process will not be
unduly burdened with delays and bureaucratic
procedures that increase cost to the client and
delay deployment of the system.
 Design, Procurement, Installation, and
Operation. The SI process will be employed
throughout the entire process.

3
8/15/2022

 Distinct Modules with Inherent Limits or


Constraints. The concept of distinct modules
with inherent limits or constraints is central to
the concept of SI.
 SI is necessary when the configuration to be
deployed includes devices with intimate
connections to other devices previously
deployed or to be deployed under a later
procurement, particularly if these devices were
designed and constructed de novo by
subcontractors with only partial design
responsibility for the overall system.

 The objectives for a systems integration engineering


methodology can be stated as follows:
1. To support problem understanding and communication
between all parties at all stages of development.
2. Enable capture of design and implementation needs
early, especially interface and interactive needs
associated with bringing together new and existing
equipment and software.
3. To support both a top-down and a bottom-up design
philosophy.

4
8/15/2022

4. To support full compliance with audit trail


needs, system-level quality assurance, and
risk assessment and evaluation.
5. To support definition and documentation of
all aspects of the program.
6. To provide a framework for appropriate
systems management application to all
aspects of the program.

 The client must define the SI requirements,


specifications, constraints, and variables in a
manner so as to provide the means for a SI
organization to deliver the necessary systems
and services required to fulfill the client
mission under the specific contract

 SI requires personnel who possess sound


technical and management skills that
combine to provide the ability to integrate
technology and operations with technical and
managerial direction.

10

5
8/15/2022

 Development and utilization of a strategic plan for


management and technical aspects of the program;
 Establishment of a complete audit trail;
 Assistance in meeting initially unrecognized needs
(including changes in system requirements);
 Avoidance of under- and over-procurement; and
utilization of risk management plans;
 Management of subcontractors to the same
specifications as employed on the prime contract;
and
 Provisions for future modification and expansion.

11

 Requirements definition and specification


 Feasibility analysis
 System architecture development
 Management plan: program and project plan
 Systems design: logical and physical design
 Implementation: design implementation, system
tests, and operational deployment
 Evaluation: system review and plan for
replacement/retirement

12

6
8/15/2022

13

 Definitionof requirements by use


 Review of requirements for ambiguity, conflict,
and other issues
 Development of systems specifications

The goal for requirements definition and


specification is to completely define and correctly
interpret the client's real needs.

14

7
8/15/2022

 Determine the likelihood of successful


system development and deployment
 Examine new technologies
 Assess risk and develop risk strategies

15

 Describe functional system architecture


 Specify required technical capabilities

16

8
8/15/2022

 Identify technical architecture alternatives


 Specify required configuration categories
 Prepare program and project plans (e.g.,
work breakdown structure)
 Prepare subcontractor management plan
 Prepare risk management plan

17

Logical and Physical Design


 Design approaches (e.g., top-down, bottom-
up, etc.)
 Use of CASE tools and other automated aids

18

9
8/15/2022

Design Implementation, System Tests, and


Operational Deployment
 Identify technical configuration
 Specify required configuration component
items
 Procurement from subcontractors
 Perform system tests
 System deployment

19

20

10
8/15/2022

System Review and Plans for


Replacement~retirement
 Review and evaluate system functioning
 Obtain, install, test, and accept modified
components
 Maintain, modify, augment, and enhance
systems
 Plan for system retirement/replacement.

21

 Conduct general studies of needs to realize


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.

22

11
8/15/2022

 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.

23

 ForSI management, some of the strategies


that will be necessary to compete in the SI
world of the future include:
 Strict control of overhead
 Increased knowledge of client businesses
 Proactive management to control costs and
increase market share

24

12
8/15/2022

 Isa special software


 Connect between software or applications
 Support for distributed applications
 May be is Transaction process system

25

 Speedup
 Increased Efficiency
 Security
 Middleware technologies can help by
providing a flexible layer between
applications and technologies.

26

13
8/15/2022

 Prohibitivelyhigh development costs


 There are few people with experience in the
market place
 The tools are not good enough
 Middleware products are not very mature

27

 Windows
 Unix/Linux
 Novellnetware
 Database flatform

28

14

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy