• No results found

Integration of Software Systems. Miloš Cvetanović Faculty of Electrical Engineering University of Belgrade

N/A
N/A
Protected

Academic year: 2021

Share "Integration of Software Systems. Miloš Cvetanović Faculty of Electrical Engineering University of Belgrade"

Copied!
18
0
0

Loading.... (view fulltext now)

Full text

(1)

Integration of Software Systems

Integration of Software Systems

Miloš Cvetanović

Faculty of Electrical Engineering University of Belgrade

(2)

Agenda

Agenda

• Part one – Practical point of view

– Process: Identifying and Qualifying

– Customer Business and IT Requirements – Common Business Drivers

• Part two – Research point of view

(3)

Three

Three

-

-

Step Process

Step Process

(Identifying & Qualifying Opportunities)(Identifying & Qualifying Opportunities)

• Step One:

Understand business drivers and enterprise IT strategy • Step Two:

Identify customers’ specific requirements for integration (look for common business challenges)

• Step Three:

(4)

Step One

Step One

(Understand business drivers and enterprise IT strategy)(Understand business drivers and enterprise IT strategy)

• IT Strategy Segmentation

– “Frozen” (20%)

– “Packaged Simplicity” (25%)

– “Managed Heterogeneity” (45%) – “NextGen Architecture” (10%)

• Value of the platform

– Lower Total Cost of IT

– Improve IT Productivity and Responsiveness – Leverage Current and Future Assets

Simplified

Simplified

Unified

Unified

Extensible

Extensible

(5)

Integration Framework BMP WLI 2.1 (BEA) Post Status Workflow EAI Repository EIS Application Clients Portal Framework

Process Driven Integration

Process Driven Integration

Oracle Project Cost Oracle Apps. 11.0.3 Event Request (XML) Response (XML) JMS JMS App. Vie w (BEA)

AI for EAI (JCA

) Actional C ore AI for Ora c le Apps. Actional Adapter:

• Bi-directional (Services / Events) • XML Interface

• Adapters snap into Actional Core

Portal Browser Status Ap plet Browser

JSP getProjectSummaryWeb Service:

BusOp MDB

(6)

Step Two

Step Two

(Understand Customer Specific Integration Requirements)(Understand Customer Specific Integration Requirements)

• Core business process are overly manual and expensive • Application-to-Application connectivity exists

but is “hard wired” and inflexible

• Need to aggregate and present information from multiple systems (via a portal)

to partners, customers, employees • B2B interactions are costly

(7)

Types of Projects

Types of Projects

• Less Expensive • Faster • Leverage existing assets CRM CRM ERP ERP SCM SCM Legacy Legacy Customers Customers Employees Employees Partners Partners Custom Custom BUILD BUILD INTEGRATE INTEGRATE EXTEND EXTEND MANAGE MANAGE

(8)

Step Three

Step Three

(Position Integration as the solution based on best practices)(Position Integration as the solution based on best practices)

• TODO:

– Gather Background Information – Identify Pain Points

– Value Response

• Specific Projects

– Order Management and Processing

– Single View of Customer and Self Service – Business Process Improvement

• Manufacturing

(9)

Example: Order Management

Example: Order Management

Order Order Order Order Management Management System System CRM CRM System System Circuit Circuit Provisioning Provisioning Shipping Shipping System System ERP - PeopleSoft ERP - PeopleSoft CRM - Siebel CRM - Siebel

(10)

Gather Background Information

Gather Background Information

• Goal - See the whole picture. Complexity, “hard wired”

connections, manual steps lead to deals.

– Look for: Number of steps and apps in the process. – Look for: Manual steps, error and exception handling. – Ask: How is it all connected together?

– Ask: How are business factors (defined below) affecting the process?

• Please describe your order management process, including all software that provides application functionality and how it all works together.

• What business factors (mergers, acquisitions, out-sourcing, layoffs, competition, legislation) have affected or will affect the way you process orders?

(11)

Identify Pain Points

Identify Pain Points

• Goal: Find problems that need fixing with technology. Some solutions

may be organizational.

– Look for: Inefficiencies such as manual steps, re-entering, etc.

– Look for: Inflexibility due to rigid applications or “hard wired” integration, not

able to change or change quickly

– Look for: Reliability problems, high support costs, brittleness

– Look for: Missing functionality: self serve order management, ability to sell

new products/solutions, direct access to distributors

• What are your plans for your order management process, replace some or all functionality, add capabilities, reduce manual steps, or leave as is? • What areas are you looking to improve in your order management

process? (time delays, errors, manual steps, lost orders, exceptions, cost)

• How do these problems affect your business? (high costs, customer satisfaction, loss of business, risk, limit growth, limit expansion to new markets)

(12)

Value Response

Value Response

• The key is to deliver examples

of solutions succeeding in this area

– Greatly improved order management processes – An ROI and payback in short period

• We would like to explore further how we can benefit you in the same way. Who would you like me to work with on your staff to begin this process?

(13)

Methodology based upon RE principles

(14)

Methodology overview

Methodology overview

• Interdisciplinary work

– Integration of Software Systems – Reverse Engineering

– Organization Science (coordination theory)

• Recovering all mandatory dependencies among software systems that we integrate • Mathematical Model (CSP)

– Compatibility testing (WRIGHT) – Deadlock freedom – Simulations (FDR Tool) Usage Rules Model RE principles Coordination Theory Software Integration Techniques (adapters)

(15)

Coordination Theory

Coordination Theory

• Dependencies Space – Usability – Accessibility – Prerequisite – Resource sharing – User sharing

• Managing dependencies with coordination processes • Design Space

– Design choices → Space dimensions

– Variations in each Design choice → Values along a Space dimension

• Mapping between

Dependency Design Space Coordination Design Space

(16)

Taxonomy

Taxonomy

• Criteria 1 (scope of integration):

– Inter-company Integration – Intra-company Integration

• Criteria 2 (type of service, market type):

– Vertical Integration – Horizontal Integration

• Criteria 3 (level of integration):

– Data Level Integration

– Presentation Level Integration – Method Level Integration

• Criteria 4 (communication type):

– Indirect Integration – Direct Integration

(17)

Partial cognition of software systems

Partial cognition of software systems

• In which business processes

particular software systems participate? • Which resources are used

by particular activity, and in which role?

• In which activities are access rights defined for particular resource, and in which role? • What interdependencies exist

among activities of a particular role?

• Which roles use particular activity, and when? • How control flow reaches particular activity?

(18)

Thank you for your attention!

Thank you for your attention!

Miloš Cvetanović

Faculty of Electrical Engineering University of Belgrade

References

Related documents

The emphasis here is on the relationships between the strategic direction of the enterprise and Technology Architecture components, allowing technology planners to

Business Architecture • Mission • Vision • Operating Model Enterprise Architecture • Aligning Business Strategy to IT Strategy Information Architecture • Data

The rGO electrode, a Pt mesh, and a saturated calomel electrode (SCE) were used as the working, counter and reference electrodes, respectively.. After that, 4 M NaOH was added into

in hadith, Ouzon conducts critical interpretation on case example that is recorded in hadiths codification in Ṣaḥīḥ al-Bukhārī, through models of criticism; in

Besides allowing for fast and easy online computation, the estimates based on adjacent triangles are more robust in the face of non-linearities than other existing robust

data, 349–350 prob.; empirical formula from percent composition, 345 prob.; energy of a photon, 143 prob.; energy units, convert, 518 prob.; equilibrium constant expression

The study is using independent variables named Saudi Education Enrollment Index (SEEI), Saudi Infant Mortality Rate (SIMR), Saudi Gross Fixed Capital Formation (SGFCF),

Daily life Daily life Manufacture Manufacture fertiliser fertiliser Manufacture Manufacture detergents detergents Manufacture Manufacture pesticides pesticides Manufacture