Wiley 978-0-470-14111-3 Datenblatt PDF herunterladen

CHAPTER

INTRODUCTION

As human beings, we are passionate about new ideas that promise to transform our lives and

create new opportunities. We also tend to rapidly replace old technologies with new ones. Ours

is a versatile society that runs on tomorrow’s software piled on top of the technology layers of

yesterday and today.

Try to imagine the next breakthrough that will supersede today’s examples of human

ingenuity. Will it be miniature software installed on microwave ovens or refrigerators that monitors

a diet prescribed by a personal nutritionist? Could it be a smart software component that not only

designs itself but also architects its own operating production environment? Or perhaps a virtual

software development platform that enables business and technology personnel to jointly build

applications with goggles and gloves?

These futuristic software concepts would probably contribute yet another layer to our

already complex computing environments, one requiring resources to maintain and budgets to

support. This layer would sit on top of technological artifacts accumulated over the past few

decades that are already difﬁcult to manage.

Not long after the new millennium, discontent over interoperability, reusability, and other

issues drove the software community to come up with the service-oriented architecture (SOA)

paradigm. Even readers who are not familiar with SOA will probably agree that it is rooted in tra-

ditional software development best practices and standards. To fulﬁll the promise of SOA, superb

governance mechanisms are necessary to break up organizational silos and maximize software

asset reusability. The SOA vision also addresses the challenges of tightly coupled software and

advocates an architecture that relies on the loose coupling of assets. On the ﬁnancial front, it

tackles budgeting and return-on-investment issues. Another feature that beneﬁts both the techno-

logical and business communities is a reduction of time to market and business agility. Indeed,

the list of advantages continues to grow.

But does the promise of SOA address software diversity issues? Does it offer solutions

to the integration and collaboration hurdles created by the accumulation of generations of het-

erogeneous computing landscapes? Will the SOA vision constitute yet another stratum of ideas

and technologies that will be buried beneath future innovations? Will SOA be remembered as a

hollow buzzword that failed to solve one of the most frustrating technological issues of our time?

Or will it serve as an inspiration for generations to come?

It is possible that SOA may fail to deliver on its promise, but if it does, we, business

and IT personnel, must shoulder some of the blame. SOA may turn out to be little more than a

technological ﬁre drill if we are ambivalent about the roles and responsibilities of legacy software

in our existing and future organizational strategies; if we fail to tie together past, present, and future

software development initiatives; and if we disregard the contributions of previous generations

of architectures to today’s business operations. Indeed, the idea of properly bridging new and old

software technologies is a novel one. But what about establishing a more holistic view of the

technological inventory that we have been building up for years? Can we treat all our software

COPYRIGHTED MATERIAL

1 2 3 4 5 6 ... 27 28

Inhaltsverzeichnis

Seite 1 - COPYRIGHTED MATERIAL

CHAPTER1INTRODUCTIONAs human beings, we are passionate about new ideas that promise to transform our lives andcreate new opportunities. We also tend t

Seite 2 - 2 Ch. 1 Introduction

10 Ch. 1 IntroductionANALYSIS SERVICE: A UNIT OF ANALYSIS. A modeling process must offer a platform on whichsolution propositions to organizational co

Seite 3

Modeling Services Introduction: A Metamorphosis Embodiment 11•Is bound by a service-oriented contract that depicts its interfaces and other importantr

Seite 4 - 4 Ch. 1 Introduction

12 Ch. 1 Introductionfrom a conceptual service to analysis, to design, and ﬁnally to solution service. Note that asolution service can also revert to

Seite 5

Modeling Services Introduction: A Metamorphosis Embodiment 13Analysis Service Solution ServiceSolution ReevaluationGranularity Alignment Functionality

Seite 6 - 6 Ch. 1 Introduction

14 Ch. 1 IntroductionDesign ServiceSolution ServiceTransaction RemodelingRevision to Service Visibility and Accessibility Modification to External St

Seite 7

Service-Oriented Modeling Disciplines: Introduction 15Service-Oriented ConceptualizationService-Oriented Discovery and Analysis Service-Oriented Busi

Seite 8 - 8 Ch. 1 Introduction

16 Ch. 1 IntroductionService-Oriented Conceptualization ActivitiesAttribution AnalysisConceptual Service IdentificationEXHIBIT 1.10 SERVICE-ORIENTED C

Seite 9 - XHIBIT 1.4 MODELING SERVICES

Service-Oriented Modeling Disciplines: Introduction 17Service-Oriented Discovery and Analysis ActivitiesService Typing and ProfilingService AnalysisSe

Seite 10

18 Ch. 1 IntroductionService-Oriented Business Integration ActivitiesContextual BusinessIntegrationStructural Business IntegrationBusinessIntegration

Seite 11

Service-Oriented Modeling Disciplines: Introduction 19Service-Oriented Design ActivitiesService Relationship Modeling LogicalStructure ModelingService

Seite 12 - 12 Ch. 1 Introduction

2 Ch. 1 Introductionassets equally in terms of their analysis, design, and architectural value propositions? Can weunderstand their collaborative cont

Seite 13

20 Ch. 1 Introductiondesign paradigm must also present business and technical functionality that services offer to theirsubscribed consumers. Therefor

Seite 14 - 14 Ch. 1 Introduction

Modeling Environments 21architecture imperatives may include service-oriented assets, such as third-party vendor products,existing services, middlewar

Seite 15

22 Ch. 1 Introductionalso facilitates their corresponding modeling discipline activities. For example, the conceptualmodeling environment provides a s

Seite 16 - 16 Ch. 1 Introduction

Service-Oriented Modeling Framework 23•Coordinating analysis sessions to enable analysis operations such as service decomposi-tion, aggregation, and u

Seite 17

24 Ch. 1 IntroductionAbstractionPracticeRealizationPracticeConceptualEnvironmentServiceConceptualizationDisciplineConceptualArchitectureDisciplineBusi

Seite 18 - 18 Ch. 1 Introduction

Service-Oriented Modeling Framework 25Separating Concerns and Generalizing Problems. The service-oriented abstraction practiceenables practitioners to

Seite 19

26 Ch. 1 Introductionwithin the abstraction practice domain. Here we are commissioned to align our serviceswith business strategies and structures suc

Seite 20 - 20 Ch. 1 Introduction

Summary 27aligned with business imperatives. Here the realization practice is concerned more with thebusiness integration-modeling portion and less wi

Seite 21 - Modeling Environments 21

Seite 22

Service-Oriented Modeling: What Is It About? 3by employing analysis, design, and architectural disciplines that are driven by a modeling strategythat

Seite 23

4 Ch. 1 Introductionapproved and agreed on, can later serve as the foundation for the ultimate service constructionprocess.EVERYBODY’S LANGUAGE: A UNI

Seite 24

Driving Principles of Service-Oriented Modeling 5The visualization process that we pursue enables us to model relationships, structures, andbehaviors

Seite 25

6 Ch. 1 Introductionhuman qualities. This “literate modeling” approach obviously enhances the strategies that arepursued during business initiatives a

Seite 26 - 26 Ch. 1 Introduction

Service-Oriented Modeling Process Stakeholders 7SOA intermediaries, gateways, universal description, discovery and integration (UDDI) registries,and e

Seite 27 - Endnotes

8 Ch. 1 IntroductionBusiness Modeling View Technological Modeling View Service-Oriented Modeling ProcessSOA Governance and Center of ExcellenceEXHIB

Seite 28

Modeling Services Introduction: A Metamorphosis Embodiment 9Conceptual Service Design ServiceAnalysis ServiceEXHIBIT 1.4 MODELING SERVICESthat can be

Kommentare zu diesen Handbüchern

Keine Kommentare

Wiley 978-0-470-14111-3 Datenblatt

Stöbern Sie online oder laden Sie Datenblatt nach Bücher Wiley 978-0-470-14111-3 herunter. Wiley Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture Benutzerhandbuch

Inhaltsverzeichnis

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Bücher Wiley 978-0-470-14111-3