DOCSLIB.ORG

Buenas Prácticas Para La Orquestación De Servicios BPM-SOA Para La

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Buenas Prácticas Para La Orquestación De Servicios BPM-SOA Para La MARCO DE REFERENCIA PARA LA ORQUESTACION DE SERVICIOS SOBRE ESBs OPEN SOURCE SUMINISTRANDO UN CONJUNTO DE BUENAS PRACTICAS QUE SIRVAN COMO INSTRUMENTO A UN ARQUITECTO DE SOFTWARE PARA LA IMPLEMENTACION DE UNA SOA Andrés Camilo Rojas Mariño David Alfonso Tafur Ramírez Universidad Piloto de Colombia Ingeniería de Sistemas Bogotá D.C. 2014 3 MARCO DE REFERENCIA PARA LA ORQUESTACION DE SERVICIOS PARA LA IMPLEMENTACION DE UNA SOA Coinvestigadores Andrés Camilo Rojas Mariño David Alfonso Tafur Ramírez Trabajo de tesis para optar por el título de Ingeniero de Sistemas Docente Investigador Ingeniero Andrés Mauricio Marín Restrepo Asesor metodológico: Sociólogo Ignacio Hernández Molina Universidad Piloto de Colombia Ingeniería de Sistemas Bogotá D.C. 2014 4 A nuestras familias, profesores y amigos quienes pusieron entre todos un grano de arena para hacer de este trabajo una realidad. 5 AGRADECIMIENTOS A nuestras familias quienes nos apoyaron a lo largo de nuestra carrera y a quienes les debemos nuestro trabajo y el fruto de lo que somos en este momento, sin su apoyo el desarrollo de nuestras carreras profesionales no hubiese sido el mismo. A nuestro director de tesis, Ing. Andres Mauricio Marín por su esfuerzo y dedicación, quien con sus conocimientos, su experiencia, su paciencia, su motivación, por sus consejos y el excelente desempeño de su profesión como docente ayudo a formarnos como personas e investigadores y ha logrado hacer de este proyecto una realidad. A la Universidad Piloto de Colombia por darnos la oportunidad de estudiar y ser profesionales. También nos gustaría agradecer a nuestros profesores los cuales durante toda la carrera profesional de Ingeniera de Sistemas aportaron con sus conocimientos aportaron en nuestro crecimiento en las diferentes áreas profesionales y de la vida. Son muchas las personas que han formado parte de nuestra vida profesional a las cuales nos encantaría agradecerles su amistad, consejos, apoyo, ánimo y compañía en los momentos más difíciles. Para ellos: Muchas gracias y que Dios los bendiga. Al profesor Ignacio Hernández Asesor de Tesis ya que nos hizo participes de sus enseñanzas y dejo un gran legado en nosotros. 6 CONTENIDO 1. Introducción ...................................................................................................................... 12 1.1 Problema ........................................................................................................................ 13 1.2 Justificación ................................................................................................................... 14 1.3 Alcance ........................................................................................................................... 15 1.4 Limites............................................................................................................................. 15 1.5 Objetivos......................................................................................................................... 16 1.5.1 Objetivos generales ............................................................................................... 16 1.5.2 Objetivos específicos ............................................................................................ 16 2. MARCO TEÓRICO ............................................................................................................. 16 2.1 Marco Histórico ............................................................................................................. 16 2.1.1 Service Oriented Architecture (SOA) .................................................................. 17 2.1.2 Orquestación de Servicios ................................................................................... 18 2.2 Técnicas de recolección de información ................................................................... 20 2.2.1 Método......................................................................................................................... 20 2.3 BPM ................................................................................................................................ 25 2.4 BPEL ............................................................................................................................... 26 2.4.1 Integrar Procesos ...................................................................................................... 27 2.4.2 Un Nuevo Estándar ................................................................................................... 28 2.4.3 Cómo Opera ............................................................................................................... 29 2.4.4 Procesos con Lógica del Negocio ........................................................................... 30 3. Desarrollo Metodológico .................................................................................................... 33 3.1. Enterprise Service Bus (ESB) .................................................................................... 33 3.1.1 Otras capacidades ofrecidas por un ESB .......................................................... 34 3.1.2 Arquitectura ESB ................................................................................................... 36 7 3.1.3 Procesamiento de Mensajes gestionados ......................................................... 36 3.1.4 El ESB en una arquitectura basada en Eventos y SOA .................................. 37 3.1.5 ESB open source ....................................................................................................... 38 3.2 ESB’S OPEN SOURCE ELEGIDOS PARA SU EVALUACION ............................ 38 3.2.1 Talend ESB ............................................................................................................. 38 3.2.2 Mule ESB ................................................................................................................ 39 3.2.3 Petals ESB .............................................................................................................. 40 3.2.4 Open ESB ............................................................................................................... 40 3.3 ESB Investigados y no elegidos ................................................................................. 41 3.3.1 Recopilación de información acerca de diferentes ESB................................ 42 3.3.2 Análisis de características y cualidades........................................................... 44 3.3.3 Apache ServiceMix .............................................................................................. 44 3.3.4 Apache Synapse .................................................................................................. 46 3.3.5 JBoss ESB ............................................................................................................ 47 3.3.6 NetKernel .............................................................................................................. 49 3.3.7 Petals ESB ............................................................................................................ 49 3.3.8 Spring Integration ................................................................................................ 51 3.3.9 Open ESB ............................................................................................................. 53 3.3.10 WSO2 ESB ........................................................................................................... 55 3.3.11 Mule Soft ESB ...................................................................................................... 57 3.3.12 UltraESB ............................................................................................................... 59 3.3.13 Red Hat Fuse ESB .............................................................................................. 61 3.3.14 Zato ESB................................................................................................................... 61 3.3.14 Talend ESB ........................................................................................................... 62 3.3.15 ChainBuilder ESB ................................................................................................ 63 3.3.16 Green Vulcano ESB ............................................................................................ 64 8 3.3.17 Revisión de los ESB más destacados .............................................................. 65 3.4 Criterios de evaluacion ............................................................................................... 65 3.5 Buenas Prácticas .............................................................................................................. 68 3.5.1 Planeación Y Diseño ................................................................................................. 68 3.5.2 Desarrollo E Implementación Del Servicio ............................................................ 68 3.5.3 Pruebas ....................................................................................................................... 69 3.5.4 Soporte Y Mantenimiento ......................................................................................... 69 3.6 Caso de Estudio ........................................................................................................... 69 3.7 Diseño Arquitectónico De La Solución .......................................................................... 70 3.8 Resultados ........................................................................................................................
Load more

Recommended publications
  • SOA Using Open ESB, BPEL, and Netbeans” > Focus Is to Explain How WSDL, BPEL, JBI, Open ESB, Java EE Work Together
    SSOOAA uussiinngg OOppeenn EESSBB,, BBPPEELL,, aanndd NNeettBBeeaannss SSaanngg SShhiinn JJaavvaa TTeecchhnnoollooggyy EEvvaannggeelliisstt SSuunn MMiiccrroossyysstteemmss,, IInncc.. 1 Three Talks I Did on SOA Here • NetBeans Day: “Tools for Simplifying SOA” > Focus is to show how to use NetBeans for building a simple Composite application • GlassFish Day: “Open ESB and GlassFish” > Focus is to show more advanced features such as Intelligent Event Processing module for building a composite application • Sun Tech Day: “SOA using Open ESB, BPEL, and NetBeans” > Focus is to explain how WSDL, BPEL, JBI, Open ESB, Java EE work together 2 Agenda • Composite Applications • BPEL • Services • JBI • Java EE Service Engine • Open ESB • Open ESB runtime, tools, and sample apps • Demo 3 CCoommppoossiittee AApppplliiccaattiioonnss Traditional Application Development • Point technologies, products, and APIs > For example: EJB, Spring, Hibernate, JSF, Servlets, Struts, etc. • Lots of glue written by developers > Requires a great deal of expertise & time > Inflexible 5 Composite Applications • A way to compose applications from reusable parts • Composite applications employ SOA principles > Features exposed as Web services > Standards-based interaction between services > Are themselves composable 6 WWSSDDLL TTuuttoorriiaall ((OOppttiioonnaall PPrreesseennttaattiioonn)) Why WSDL? • Enables automation of communication details between communicating partners – Machines can read WSDL – Machines can invoke a service defined in WSDL • Discoverable through registry
    [Show full text]
  • Refactoring of ESB-Based Systems on the Clouds
    UNIVERSITYOFTARTU FACULTY OF MATHEMATICS AND COMPUTER SCIENCE Institute of Computer Science Mariana Kukhtyn Refactoring of ESB-based systems on the clouds Master's thesis (30 ECTS) Supervisor: Satish Srirama, Ph.D. Author: .......................................... \....." June 2011 Supervisor: .................................... \....." June 2011 Professor: ...................................... \....." June 2011 TARTU 2011 `The one thing that matters is the effort. It continues, whereas the end to be attained is but an illusion of the climber, as he fares on and on from crest to crest; and once the goal is reached it has no meaning." Antoine de Saint-Exupry, The Wisdom of the Sands UNIVERSITY OF TARTU Abstract Faculty of Mathematics and Computer Science Institute of Computer Science Master of Science Refactoring of ESB-based systems on the cloud by Mariana Kukhtyn Nowadays enterprises are facing new, unprecedented press for competitiveness: the speed of service providing, price of inaccuracy, possibility to use applications from desktops, notes and other mobile devices. These new conditions force business to search for addi- tional resources and configurations for providing better services. Thus, we are arguing to find general hints for uniting enterprises, cloud computing and distributed middleware software in one system in order to fulfill this goal. ESB-based systems and Service Oriented Architecture taken as one of its cases are as- sessed in concern to their possible aplication and profit-usage on the remote servers. In this work, for the first time different vision of distributed ESB-systems (Federated, In- ternet and proper Distributed) are described, prooving that idea is not new but different research groups focus on different features. Statistics data on cloud application is used to object widely-spread statements on cloud security and finance-efficiency.
    [Show full text]
  • Survey on the Run-Time Systems of Enterprise Application Integration Platforms Focusing on Performance
    Received: 11 September 2018 Revised: 10 November 2018 Accepted: 14 November 2018 DOI: 10.1002/spe.2670 SURVEY PAPER Survey on the run-time systems of enterprise application integration platforms focusing on performance Daniela L. Freire Rafael Z. Frantz Fabricia Roos-Frantz Sandro Sawicki Department of Exact Sciences and Engineering, Unijuí University, Ijuí-RS, Summary Brazil Companies are taking advantage of cloud computing to upgrade their business Correspondence processes. Cloud computing requires interaction with many kinds of applica- Rafael Z. Frantz, Department of Exact tions, so it is necessary to improve the performance of software tools that allow Sciences and Engineering, Unijuí keeping information on all these applications consistent and synchronised. Inte- University, Ijuí-RS 98700-000, Brazil. Email: [email protected] gration platforms are specialised software tools that provide support to design, implement, run, and monitor integration solutions, which aim to orchestrate a Funding information Coordenação de Aperfeiçoamento de set of applications so as to promote compatibility among their data or to develop Pessoal de Nível Superior, Grant/Award new functionality on top of the current ones. The run-time system is the part Number: 73318345415 and of the integration platform responsible for running the integration solutions, 88881.119518/2016-01; Fundação de Amparo à Pesquisa do Estado do Rio which makes its performance the uttermost important issue. The contribution Grande do Sul, Grant/Award Number: of this article is two-fold: a framework and an evaluation of integration plat- 17/2551-0001206-2 forms. The former is a framework composed of ten properties grouped into two dimensions to evaluate the run-time systems focusing on performance.
    [Show full text]
  • Architecture of Mule and Servicemix 42 3 ■ Setting up the Mule and Servicemix Environments 72 4 ■ the Foundation of an Integration Solution 111
    Open Source ESBs in Action Open Source ESBs in Action EXAMPLE IMPLEMENTATIONS IN MULE AND SERVICEMIX TIJS RADEMAKERS JOS DIRKSEN MANNING Greenwich (74° w. long.) For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact: Special Sales Department Manning Publications Co. Sound View Court 3B Fax: (609) 877-8256 Greenwich, CT 06830 Email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed elemental chlorine-free Development Editor: Jeff Bleil Manning Publications Co. Copyeditors: Liz Welch, Tiffany Taylor Sound View Court 3B Typesetter: Denis
    [Show full text]
  • ESB and SOA Infrastructure
    eBook ESB and SOA Infrastructure The Enterprise Service Bus (ESB) is a form of plumbing that enables effective SOA implementation. But understanding the ESB remains an industry-wide quest. Open source consultant Jeff Genender lists a message bus first on his list of the basic building blocks of a successful SOA infrastructure. And yet, some recent Forrester survey results show that first-time SOA infrastructure purchases maybe shifting from ESBs to other SOA technologies. Read this eBook to learn more about ESBs including: • The role of ESBs in application integration • Tips on open source and SOA infrastructure from Jeff Genender • Forrester's take on where the ESB fits in today's enterprise architecture Sponsored By: SearchSOA.com eBook ESB and SOA Infrastructure eBook ESB and SOA Infrastructure Table of Contents The ESB and its role in application integration architecture Working with ActiveMQ – Tips from TSSJS presenter Jeff Genender part one On SOA infrastructure – Tips from TSSJS presenter Jeff Genender part two Forrester analysts: SOA still strong Resources from FuseSource Sponsored By: Page 2 of 10 SearchSOA.com eBook ESB and SOA Infrastructure The ESB and its role in application integration architecture By Alan Earls Although enterprise service busses (ESBs) are not new, they can continue to be a nexus for confusion. After many years and many implementations, what they do, how they do it and whether specific products can help create a SOA are all still matters of contention. Chris Harding, a forum director for SOA and client computing at The Open Group, argues that there isn’t always clarity regarding the nature of ESBs.
    [Show full text]
  • Proof of Concept Implementation of an Enterprise Service Bus for Health Information Exchanges
    PHILIPPINE ENGINEERING JOURNAL PC Zuñiga, et al 49 PEJ 2020; Vol. 41, No. 1: 49-66 Proof of Concept Implementation of an Enterprise Service Bus for Health Information Exchanges Philip Christian Zuniga, Joseph Benjamin Del Mundo, Edgardo Felizmenio, Marie Jo-anne Mendoza and Rose Ann Zuniga Computer Security Group, Department of Computer Science, University of the Philippines - Diliman Abstract – Integration of health systems is one of the biggest problem in eHealth today. There are a lot of systems, yet they were developed using different platforms and technologies, making them virtually impossible to connect. In this paper, we discussed how to implement an ESB as the integration platform for health data. We identified use cases and functional requirements. Logical and deployment architecture were developed, and an actual proof of concept of an ESB is developed. Experiments were also done to determine the overhead caused by the ESB. Some of the functionalities of the ESB were examined to determine their individual overheads. Keywords: Enterprise Service Bus, Interoperability, Health Information Exchange, OpenHIE. I. INTRODUCTION During the past few years, the healthcare industry has witnessed a growth in the development of Health Information Systems. Hospitals, both public and private, rural health clinics, and even individual clinics of medical practitioners have been developing or acquiring their own Electronic Medical Records (EMRs), and Hospital Information Systems (HIS). The goal of these systems is to ensure a secure, organized and effective way of collecting and storing patient data [1]. The increase in the number of edge applications leads to the increase of patient data that are stored separately and independently, depending on the application that collected the data.
    [Show full text]
  • Porovnání Výkonu Switchyard a Jiných OSS ESB Implementací
    MASARYKOVA UNIVERZITA FAKULTA INFORMATIKY Û¡¢£¤¥¦§¨ª«¬­Æ°±²³´µ·¸¹º»¼½¾¿Ý Porovnání výkonu SwitchYard a jiných OSS ESB implementací BAKALÁRSKA PRÁCA Pavol Bako Brno, 2013 Prehlásenie Prehlasujem, že táto bakalárska práca je mojím pôvodným autorským die- lom, ktoré som vypracoval samostatne. Všetky zdroje, pramene a literatúru, ktoré som pri vypracovaní používal alebo z nich ˇcerpal,v práci riadne citu- jem s uvedením úplného odkazu na príslušný zdroj. Pavol Bako Vedúci práce: Mgr. Marek Grác i Kl’úˇcovéslová SOA, ESB, SCA, servisne orientovaná architektúra, service oriented archi- tecture, enterprise service bus, integraˇcnýsystém, výkonnostné testovanie, podniková zbernica služieb ii Pod’akovanie Chcel by som sa pod’akovat’ pánovi JiˇrímuPechancovi, ktorý ma sprevá- dzal po celú dobu práce, a ktorý mal strpenia na moje otázky. Takisto by som sa chcel pod’akovat’, že mi umožnil po dobu niekol’ko mesiacov pra- covat’ na bakalárskej práci v priestoroch spoloˇcnostiRed Hat vo svojej do- stupnosti a umožnil mi tak efektívnejšie riešit’ problémy. iii Obsah 1 Úvod ................................... 1 2 Služobne orientovaná architektúra (SOA) ............. 3 2.1 Integraˇcnésystémy a SOA pravidlá . 3 2.1.1 Point-to-point model . 4 2.1.2 Hub-and-spoke model . 5 2.1.3 Bus model (ESB) . 6 2.1.4 SCA OASIS architektúra . 6 3 Podniková zbernica služieb (ESB) .................. 7 3.1 Charakteristika posielania správ . 7 3.2 Prehl’ad základných vlastností . 7 3.3 Hl’adanie definície ESB . 9 4 Metodika testovania .......................... 10 4.1 Scenáre testovania a prostredie testovania . 10 4.1.1 DirectProxy . 11 4.1.2 CBRProxy . 11 4.1.3 XSLTProxy . 13 4.2 ESB Performance framework .
    [Show full text]
  • Kuali Student Advanced Camp
    Kuali Student Advanced CAMP June 19-20, 2008 Jens Haeusser Director, Strategy Information Technology Objectives . At the end of this session you will have seen . The Kuali Student technical architecture vision . The results of our efforts to date . The working relationships in place to support our efforts Kuali Student – Advanced CAMP June 19-20 2 Agenda . Kuali Student’s Vision . Our vision for Phase I and Phase II (July 2007 – May 2008) . Our execution of the vision . Kuali Student Architecture . Web Services Stack . Development Infrastructure . Our Current Challenges . Relationships with vendors, open source, and Kuali . On the Leading Edge While Remaining Flexible . Getting Validation of Our Work Kuali Student – Advanced CAMP June 19-20 3 Background . Modular, standards-based next generation student system . Community Source project with a 5 year timeline . UBC, Berkeley, Florida, Maryland, San Joaquin Delta, Southern California . MIT, Cambridge . Person centric system . Service Oriented Architecture . Enables integration at diverse institutions . Allows schools to implement their practices Kuali Student – Advanced CAMP June 19-20 4 Functional Vision . Support end users by anticipating their needs . Wide range of learners and learning activities. Wide range of business processes . Easier to change business processes. Reduce time staff spend on routine task Kuali Student – Advanced CAMP June 19-20 5 Technical Vision . SOA and Web Services . SOA Design Methodology . SOA Governance . Web Services: SOAP, WSDL, XML Schema . Web Services
    [Show full text]
  • Towards Distributed Information Access Possibilities and Implementation
    Towards Distributed Information Access Possibilities and Implementation Victor de Graaff i ii Towards Distributed Information Access Alternatives and Implementation Master thesis Author: Victor de Graaff University: University of Twente Master: Computer Science Track: Software Engineering Internal Supervisors: Dr. Luís Ferreira Pires Dr. ir. Marten van Sinderen External Supervisors: ing. Gerke Stam, TSi Solutions iii iv Preface This thesis describes the results of a Master of Science assignment at the Software Engineering group at the University of Twente. This assignment has been carried out from February to November 2009 at TSi Solutions in Enschede, The Netherlands. I would like to thank all the people who gave me support while writing this thesis. In the first place these people are my girlfriend Susanne Jeschke and my daughter Melissa. They have supported me through the last piece of my Bachelor and my entire Master course by taking my mind off work every night and weekend, as far as my deadlines allowed them to. They have given me the chance to spend countless hours on my work, my classes, and later my thesis, while they went to all the activities and appointments a young child has. I can truly say that I could never have finished my studies without their support, understanding and patience. Another great influence has been the supervision of Luís Ferreira Pires, Marten van Sinderen and Gerke Stam. Luís managed to keep the balance in my work between quality and steady progress. On top of that, Luís taught me a lot on writing objective texts by rephrasing or pointing out sentences which were subjective or too popular.
    [Show full text]
  • Performance Comparison of Jboss Integration Platform Implementations
    Masarykova univerzita Fakulta}w¡¢£¤¥¦§¨ informatiky !"#$%&'()+,-./012345<yA| Performance comparison of JBoss integration platform implementations Master Thesis Elena Medvedeva Brno, May 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Elena Medvedeva Advisor: Mgr. Marek Gr´ac,Ph.D. ii Acknowledgement I would like to thank my technical supervisor from Red Hat, Ing. Pavel Mac´ıkfor sharing his vast experience in the field of performance testing, and for valuable pieces of advice given to me during the preparation of this work. I am grateful to my supervisor Mgr. Marek Gr´ac,Ph.D. for the comments and consultations. Besides, I want to thank all my colleagues who work with me in the JBoss Fuse QA team, for support, and the company Red Hat, which provided me the opportunity to write this thesis. iii Abstract We present the results of our investigation in the field of performance testing of JBoss integration platforms to compare performance of JBoss Fuse and SwitchYard. We design a basic set of performance scenarios to cover basic usage patterns of integration platforms. We formalize the scenarios that are already implemented for SwitchYard, and we develop three new sce- narios. All fifteen scenarios are implemented for JBoss Fuse using Per- fCake and tweaked to be optimal from the performance point of view. In addition performance test execution is automated in distributed en- vironment using Jenkins and SmartFrog.
    [Show full text]
  • Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Trepo - Institutional Repository of Tampere University Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis Examiner: Prof. Tommi Mikkonen Examiners and topic approved in the council meeting of Faculty of Information Technology on April 3rd, 2013. II TIIVISTELMÄ TAMPEREEN TEKNILLINEN YLIOPISTO Tietotekniikan koulutusohjelma Hänninen, Arttu: Enterprise Integration Patterns in Service Oriented Systems Diplomityö, 58 sivua Kesäkuu 2014 Pääaine: Ohjelmistotuotanto Tarkastajat: Prof. Tommi Mikkonen Avainsanat: Enterprise Integration Patterns, Palvelukeskeinen arkkitehtuuri (SOA), Viestipohjainen integraatio Palvelupohjaisen integraation toteuttaminen mihin tahansa tietojärjestelmään on haas- tavaa, sillä integraatioon liittyvät järjestelmät voivat muuttua jatkuvasti. Integraatiototeu- tusten tulee olla tarpeeksi joustavia, jotta ne pystyvät mukautumaan mahdollisiin muu- toksiin. Toteutukseen voidaan käyttää apuna eri sovelluskehyksiä, mutta ne eivät vält- tämättä takaa mitään standardoitua tapaa tehdä integraatio. Tätä varten on luotu joukko ohjeita (Enterprise Integration Patterns, EIP), jotka kuvaavat hyväksi havaittuja tapoja tehdä integraatioita. Tässä työssä keskitytään näiden mallien tutkimiseen ja siihen, miten niitä voidaan hyödyntää yritysjärjestelmissä. Jotta tutkimukseen saadaan konkreettinen vertailutulos, erään järjestelmän integraatioratkaisu tullaan päivittämään uuteen. Uusi ratkaisu hyödyntää sovelluskehystä,
    [Show full text]
  • Kuali Student Service System: Technical Architecture Phase 1 Recommendations
    Kuali Student Service System Technical Architecture Phase 1 Recommendations Kuali Student Service System Technical Architecture Phase 1 Recommendations December 31 2007 Kuali Student Technical Team Technical Architecture Phase 1 deliverables 2/14/2008 1 Kuali Student Service System Technical Architecture Phase 1 Recommendations Table of Contents 1 OVERVIEW ........................................................................................................................ 4 1.1 REASON FOR THE INVESTIGATION ................................................................................... 4 1.2 SCOPE OF THE INVESTIGATION ....................................................................................... 4 1.3 METHODOLOGY OF THE INVESTIGATION .......................................................................... 4 1.4 CONCLUSIONS ............................................................................................................... 5 1.5 DECISIONS THAT HAVE BEEN DELAYED ............................................................................ 6 2 STANDARDS ..................................................................................................................... 7 2.1 INTRODUCTION .............................................................................................................. 7 2.2 W3C STANDARDS .......................................................................................................... 7 2.3 OASIS STANDARDS ......................................................................................................
    [Show full text]