CTAP tiene entre sus fines la innovacioacute;n funcional; formal y productiva en los sectores de las Piedras Naturales y las Piedras Artificiales (Composite). En el 2010; CTAP puso en marcha una liacute;nea de investigacioacute;n y desarrollo de nuevos procesos y nuevos materiales coacute;mo eje estrateacute;gico para el sector; partiendo de la premisa de minimizar el impacto ambiental a traveacute;s de la reutilizacioacute;n de desechos de la extraccioacute;n y de residuos de fabricacioacute;n; para lo cual decidioacute; contar con Perry King y Santiago Miranda; titulares del estudio homoacute;nimo con sede en Milaacute;n. Partiendo desde la observacioacute;n de las nuevas modalidades de extraccioacute;n y las sucesivas fases de produccioacute;n; KMD puso en marcha; como punto de partida; un anaacute;lisis de las prestaciones y de los usos funcionales y formales que la arquitectura y el sector industrial dan a la piedra. El objetivo es obtener materiales ineacute;ditos en lo que se refiere a su concepcioacute;n; aplicaciones posibles y propiedades teacute;cnicas y esteacute;ticas.
#2342541 in eBooks 2014-02-11 2014-02-11File Name: B00I5QZ6PA
Review
0 of 2 people found the following review helpful. Perfect Dosage of SOABy Orange PeelI found this book to be just right. It explains the value of SOA and the basic architecture. It skirts the technical stuff; which is fine for this kind of book. I think its great for a manager or a consultant pitching SOA.I give it 4 instead of 5 due to the overuse of force field analysis and the lack of a point in the later chapters. More than half of the book is extremely useful. It would get 5 if they chopped out the useless stuff and the excessive use of force field analysis.9 of 9 people found the following review helpful. Best overview book Ive seenBy Nelson KingThere must be hundreds of books on Web services; most of them with chapters that read like alphabet soup (UDDI; SOAP; WSDL; etc.). Ive read quite a few of these books and its awfully easy to get lost in the details. Douglas Barrys Web Services and Service-Oriented Architectures; The Savvy Managers Guide; does something else: it gives you a genuinely useful high-level view.Barry makes a very important distinction: Web services (the term we hear about so much) are connections. Services are what these connections deliver. What is important in the long run are not the connections (Web services) but the goods they will provide (services of many kinds). As Barry and many others see it; the future of software is in the services that will be used to plug information (data) and programming into service-oriented applications.Managing both the connections and the services will be a principal task of IT in the coming years; and its Barrys contention that it can best be addressed by developing a service-oriented architecture. Much of the book is given over to discussing the nature of software architecture; what it means in the case of services; and how you would go about deciding what kind of architecture to use. This seems like esoteric stuff; but Barry does a very good job of removing excess jargon and inserting real-life analogies to clarify the topics.The author also uses his own experience and point of view to humanize what could be a mind-numbing onslaught of abstractions. Im particularly happy that he discusses the difficulties of implementing Web services and a service-oriented architecture - a reality check thats sorely missing from many other books.Personally I might quibble with his assumption that the technical difficulties of Web services and particularly the problem of arriving at standards will shortly be resolved. But this is; ultimately; a matter of timing. That Web services are going to be important and probably pivotal for software is generally accepted. Barry does an excellent job of explaining whats involved; why its important; and how to approach it-necessary background information for just about everybody involved in IT. Highly recommended5 of 6 people found the following review helpful. No Perfect AnswerBy Tim SFrom the start; I was happy to see that Barry wasnt one of those old school guys who tried something 10 years ago that didnt work; and had sworn off a similar endeavor forever as impossible. Hes been there - he just has moved on; just as computing and software technologies have changed and made a lot of our past experiences less relevant today.Neither is this book a recipe for perfection requiring strict adherence. His regular admonition to build for flexibility and his willingness to point out the flaws in conventional beliefs is a welcome departure from most architectural guides.I particularly enjoyed the discussion on middle-tier architectures and data caching. As service-oriented architectures mature; its highly unlikely they will succeed if all data access occurs in the enterprise tier. An SOA will encourage new applications and more sophisticated services; which will place even more stress on data access and responsiveness. Plus; the SOA infrastructure itself will require non-enterprise data for state management; diagnostics; object mapping and other functions that must be stored in the middle tier. This is a topic that cannot be avoided for an SOA that fulfills its long-term promise to the business. Barrys book is the only one I have found that deals with this reality in a straightforward; unemotional way.Given that most of the SOA failures are likely to occur in the planning and organiation of the team or teams involved; Im happy to see this kind of book now; when most companies are in the early stages. Lets let the standards firm up and the early implementations guide the "best practices" books which will no doubt come soon.
