SOA made simple : (Record no. 41667)

MARC details
000 -CABECERA
Campo de control de longitud fija 08861nam a2200337 a 4500
003 - IDENTIFICADOR DEL NÚMERO DE CONTROL
Identificador del número de control AR-sfUTN
008 - DATOS DE LONGITUD FIJA--INFORMACIÓN GENERAL
Códigos de información de longitud fija 170717s2012 ||||| |||| 00| 0 eng d
020 ## - NÚMERO INTERNACIONAL ESTÁNDAR DEL LIBRO
ISBN 9781849684163
040 ## - FUENTE DE LA CATALOGACIÓN
Centro transcriptor AR-sfUTN
041 ## - CÓDIGO DE LENGUA
Código de lengua del texto eng
080 ## - NÚMERO DE LA CLASIFICACIÓN DECIMAL UNIVERSAL
Clasificación Decimal Universal 004.738.52 D569
Edición de la CDU 2000
100 1# - ENTRADA PRINCIPAL--NOMBRE DE PERSONA
Nombre personal Dikmans, Lonneke
245 10 - MENCIÓN DE TÍTULO
Título SOA made simple :
Resto del título Discover the true meaning behind the buzzword that is Service Oriented Architecture /
Mención de responsabilidad Lonneke Dikmans, Ronald Van Luttikhuizen.
260 ## - PUBLICACIÓN, DISTRIBUCIÓN, ETC.
Lugar de publicación, distribución, etc. Birmingham :
Nombre del editor, distribuidor, etc. Packt Publishing,
Fecha de publicación, distribución, etc. 2012
300 ## - DESCRIPCIÓN FÍSICA
Extensión 270 p.
336 ## - TIPO DE CONTENIDO
Fuente rdacontent
Término de tipo de contenido texto
Código de tipo de contenido txt
337 ## - TIPO DE MEDIO
Fuente rdamedia
Nombre del tipo de medio sin mediación
Código del tipo de medio n
338 ## - TIPO DE SOPORTE
Fuente rdacarrier
Nombre del tipo de soporte volumen
Código del tipo de soporte nc
505 80 - NOTA DE CONTENIDO CON FORMATO
Nota de contenido con formato CONTENIDO<br/>Chapter 1: Understanding the Problem 7<br/>The importance of information 8<br/>Example – insurance company 8<br/>Mismatch between business and IT 9<br/>Duplication of functionality and data 10<br/>Example – insurance company 11<br/>Process silos 13<br/>Example – utility companies 14<br/>Example – international software company 15<br/>Example – insurance company 17<br/>Strategies to stay ahead 17<br/>Example – a software company 18<br/>Architecture as a tool 19<br/>Layering of architecture 22<br/>Models 23<br/>Requirements 24<br/>Architecture ontology 24<br/>Enterprise architecture 25<br/>Reference architecture 27<br/>Solution architecture 28<br/>Project architecture 29<br/>Software architecture 29<br/>Service Oriented Architecture 30<br/>Summary 30<br/>Chapter 2: The Solution 31<br/>What is a service? 32<br/>Elements of a service – contract, interface, and implementation 32<br/>Example – let's have breakfast 33<br/>Example – ordering a passport 35<br/>Consumer and provider 35<br/>From sunny-side-up eggs to IT 36<br/>Example – international software company revisited 38<br/>Consumer and provider 43<br/>Drivers for services 45<br/>Common myths 45<br/>Every service has to be automated by software 46<br/>Every service is a web service 46<br/>Consumers of services are always IT systems 46<br/>Putting it together – what is SOA? 46<br/>Solutions 47<br/>Example – utility company 47<br/>International software company – changing existing processes 49<br/>Functional duplication – rationalizing application landscapes 51<br/>Standardization – enabling change 53<br/>Summary 54<br/>Chapter 3: Service Identification and Design 55<br/>Service identification 56<br/>Top-down 56<br/>Example of top-down service identification 59<br/> Bottom-up 60<br/>Meet in the middle 60<br/>I have identified my services, now what? 61<br/>Service design 61<br/>Provide value 62<br/>Meaningful 62<br/>Implementation hiding 63<br/>Trust 63<br/>Idempotent 63<br/>Isolated 63<br/>Interoperable 64<br/>Isolation 65<br/> Example: print service 65<br/>Trust 66<br/>Security 66<br/>Fault-prevention and handling 67<br/>Idempotency 69<br/>Idempotency and statefulness 70<br/>Granularity 73<br/>How big should my lasagna be? 75<br/>Classification 76<br/>Reusability 76<br/>Example – reusability 78<br/>Example – good or bad service? 82<br/>Service definition revisited 87<br/>Summary 88<br/>Chapter 4: Classification of Services 89<br/>Service classification revisited 89<br/>Example – insurance company 90<br/>Other classifications 92<br/>Actor type 93<br/>Channel 93<br/>Organizational boundaries 93<br/>Security level 94<br/>Architectural layer 94<br/>Combining classifications 95<br/>Why classify your services? 96<br/>Composability 97<br/>Aggregation versus orchestration 97<br/>Example – DocumentService as a composite service 98<br/>Elementary services 98<br/>Realization 98<br/>Composite services 99<br/>Where to put the composition logic? 99<br/>Implementation 100<br/>Example 1 – database link 100<br/>Example 2 – service invocation 102<br/>Process services 103<br/>Implementation 104<br/>Isolation and composition – a contradiction? 104<br/>Passing information from smaller to larger services 105<br/>Summary 109<br/>Chapter 5: The SOA Platform 111<br/>Overview 112<br/>Services 113<br/>Implementation 114<br/>Using existing software 114<br/>Build the implementation 114<br/>Interfaces 115<br/>Proprietary interfaces 115<br/>Web services 115<br/>Contracts and Policies 117<br/>Events 118<br/>Interfaces for events 119<br/>Service composition 120<br/>Enterprise Service Bus 120<br/>Business Process Management 122<br/>Case Management 123<br/>Business rules 125<br/>User interface 127<br/>Integrated user interfaces 129<br/>Information mismatch 130<br/>Security 131<br/>Applying security in your SOA 133<br/>Service registry and service repository 134<br/>Canonical Data Model 134<br/>Design tooling 136<br/>Development tooling 137<br/>Example – Order-to-cash revisited 139<br/>Designing the solution 139<br/>Developing the solution 140<br/>Running the solution 141<br/> Summary 141<br/>Chapter 6: Solution Architectures 143<br/>Comprehensive suite or best of breed 143<br/>Comparison 145<br/>Oracle 149<br/>Services 149<br/>Events 149<br/>Oracle Event Processing (OEP) 150<br/>Business Activity Monitoring (BAM) 150<br/>Service composition 150<br/>Oracle Service Bus 150<br/>Oracle SOA Suite 151<br/>Oracle BPM Suite 152<br/>Business rules 153<br/>User interface 153<br/>Security 154<br/>Registry and repository 154<br/>Design tooling 154<br/>Design tooling for developers 154<br/>Design tooling for business analysts 154<br/>Development tooling 155<br/>Test tooling 155<br/>Testing transformations 155<br/>SCA testing framework 156<br/>Testing from the console 156<br/>Deployment tooling 156<br/>Deployment from the IDE 156<br/>Deployment from the console 157<br/>Deployment using scripting 157<br/>Monitoring 157<br/>Error handling 158<br/>IBM 158<br/>Services 158<br/>Events 158<br/>WebSphere Operational Decision Management 159<br/>IBM Business Monitor 159<br/>Service composition 159<br/>IBM WebSphere Enterprise Service Bus 159<br/>IBM Business Process Manager 160<br/>Business rules 161<br/>User interface 161<br/>Security 161<br/>Registry and repository 162<br/> Design tooling 162<br/>Services 163<br/>Composite services 163<br/>Development tooling 163<br/>Test tooling 163<br/>Deployment tooling 163<br/>Deployment from the IDE 163<br/>Deployment from the web interface of the server 164<br/>Deployment scripts 164<br/>Monitoring 164<br/>Error handling 164<br/>Microsoft 165<br/>Services 165<br/>Events 165<br/> Message-oriented middleware 165<br/>Complex Event Processing (CEP) 165<br/>Business Activity Monitoring 165<br/>Service composition 166<br/>BizTalk Server 166<br/>Windows Server AppFabric 166<br/>Business rules 167<br/>User interface 167<br/>Security 168<br/>Registry and repository 168<br/>Design tooling 168<br/>Development tooling 168<br/>Test tooling 168<br/>Deployment tooling 168<br/>BizTalk Server 169<br/>Monitoring 169<br/>Error handling 169<br/>Summary 170<br/>Chapter 7: Creating a Roadmap, How to Spend Your Money and When? 171<br/>Organize the SOA effort 171<br/>Business case – benefits for different stakeholders 175<br/> Business case explained 175<br/>Company as a whole 177<br/>Example 1 – insurance company WATB needs shorter time to market 177<br/>Example 2 – insurance company TPIR needs to decrease operational cost 180<br/>IT 182<br/>Example – insurance company TMS needs to consolidate systems 182<br/>Departmental benefits 185<br/>Example – insurance company X wants to cut cost 185<br/>Analysis of the scenarios 188<br/>Approaches 190<br/>Example – Document Management Service 190<br/>Top-down identification 191<br/>Bottom-up identification 192<br/>Meet in the middle 192<br/>Roadmap 193<br/>Work packages 193<br/>Service by service 194<br/>Process by process 194<br/>Feature by feature 194<br/>System by system 195<br/>Comparison 195<br/> Maturity and stages 197<br/>Stage 0: Starting with SOA 198<br/>Stage 1: Newlyweds 198<br/>Stage 2: Live 198<br/>Stage 3: Growing up 198<br/>Stage 4: Experience 199<br/>Stage 5: Maintenance 199<br/>Summary 201<br/>Chapter 8: Life Cycle Management 203<br/>Service stages 203<br/>Versioning of services 205<br/>Type of change – contract, interface, and implementation 206<br/>Changing the contract 206<br/>Changing the interface 207<br/>Changing the implementation 207<br/>Versioning schemes 208<br/>Versioning and life cycle stages 209<br/>Making the version explicit for service consumers 210<br/>Communicating change 212<br/>Tooling 213<br/>Standards 215<br/> Information needed 216<br/>Find services 216<br/>Troubleshooting 216<br/>Change process 217<br/>Registries and repositories in your IT landscape 218<br/> Enterprise architecture tools 218<br/>Business Process Management tool 219<br/>Configuration Management Database 219<br/>Bug and issue tracker system 220<br/>ESB 220<br/>Business Activity Monitoring 221<br/>Infrastructure monitoring 221<br/>Summary 221<br/>Chapter 9: Pick your Battles 223<br/>Governance 223<br/>Architecture process 225<br/>Ad hoc business need 225<br/>Define the solution 226<br/>Deviations 227<br/>Integration in the solution architecture 227<br/>Planned feature 228<br/>Pick your battles 229<br/>Development process 230<br/>Pick your battles 232<br/>Operations 233<br/>Pick your battles 235<br/>Change management 237<br/>Pick your battles 238<br/>Summary 239<br/>Chapter 10: Methodologies and SOA 241<br/>Demand management 242<br/>Methodology 243<br/>Impact of SOA 244<br/>Project management 246<br/>Methodology 246<br/>Impact of SOA 248<br/>Software development 249<br/>Methodology 250<br/>Impact of SOA 251<br/>Application management 251<br/>Methodology 252<br/>Impact of SOA 253<br/>IT service and operations management 254<br/>Methodology 254<br/>Impact of SOA 255<br/>Summary 257<br/>Index 259
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia ARQUITECTURA ORIENTADA A SERVICIOS (INFORMATICA)
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia COMPUTACION EN NUBES
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia GESTION DE LOS RECURSOS DE INFORMACION
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia SISTEMAS DE INFORMACION GERENCIAL
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia WEB SERVER
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia WEB
650 ## - PUNTO DE ACCESO ADICIONAL DE MATERIA--TÉRMINO DE MATERIA
Término de materia INTERNET
700 1# - PUNTO DE ACCESO ADICIONAL--NOMBRE DE PERSONA
Nombre personal Van Luttikhuizen, Ronald
942 ## - ELEMENTOS DE PUNTO DE ACCESO ADICIONAL (KOHA)
Tipo de ítem Koha Libros
Esquema de clasificación Clasificación Decimal Universal
999 ## - NÚMEROS DE CONTROL DE SISTEMA (KOHA)
-- 41667
-- 41667
Holdings
Estado Estado perdido Tipo de préstamo Localización permanente Ubicación/localización actual Fecha de adquisición Origen de la adquisición Número de inventario Total Checkouts ST completa de Koha Código de barras Date last seen Número de copias Tipo de ítem Koha
      Facultad Regional Santa Fe Facultad Regional Santa Fe 02/02/2018 Compra Exp. Nº 16/2013 PID 25/0139 (Tymoschuk) 10843   004.738.52 D569 10843 02/02/2018 02/02/2018 Libros