
By Jack van't Wout, Maarten Waage, Herman Hartman, Max Stahlecker, Aaldert Hofman
This booklet captures and communicates the wealth of structure adventure Capgemini has amassed as a member of The Open team – a seller- and technology-neutral consortium shaped via significant gamers – in constructing, deploying, and utilizing its “Integrated structure Framework” (IAF) on the grounds that its origination in 1993. this day, many components of IAF were included into the recent model nine of TOGAF, the similar Open staff regular. The authors, all engaged on and with IAF for a few years, right here offer an entire connection with IAF and a consultant on tips to observe it. furthermore, they describe intimately the family members among IAF and the structure criteria TOGAF and Archimate and different improvement or strategy frameworks like ITIL, CMMI, and RUP. Their presentation is concentrated at architects, venture managers, and method analysts who've both thought of or are already operating with IAF – they'll locate many roadmaps, case reports, checklists, and suggestions and suggestion for his or her day-by-day work.
Read or Download The Integrated Architecture Framework Explained: Why, What, How PDF
Similar management information systems books
These days, internet functions are nearly omnipresent. the internet has turn into a platform not just for info supply, but in addition for eCommerce structures, social networks, cellular providers, and allotted studying environments. Engineering net functions consists of many intrinsic demanding situations as a result of their disbursed nature, content material orientation, and the requirement to lead them to on hand to a large spectrum of clients who're unknown prematurely.
Integration Models: Templates for Business Transformation
This ebook presents a confirmed method of EAI, providing examples from real perform, and exploring the stairs to keep on with for its daily implementation. initially designed for corporations present process major merger and acquisition task, Integration versions have advanced right into a operating toolkit for bridging the space among enterprise and technical versions.
Service Engineering: Entwicklung und Gestaltung innovativer Dienstleistungen
Die schnelle und effiziente Realisierung innovativer Dienstleistungen stellt zunehmend einen Erfolgsfaktor für die Wettbewerbsfähigkeit von Dienstleistungsunternehmen dar. Dienstleistungen werden in der Praxis jedoch oft "ad hoc", d. h. ohne systematische Vorgehensweise, entwickelt. Das Konzept des "Service Engineering" beschreibt Vorgehensweisen, Methoden und Werkzeugunterstützung für die systematische Planung, Entwicklung und Realisierung innovativer Dienstleistungen.
Extra resources for The Integrated Architecture Framework Explained: Why, What, How
Example text
Why’ Business ‘What’ Information Information systems Technology infrastructure ‘How’ ‘With what’ To answer the first question: IAF was originally designed to support the creation of architectures for Capgemini’s business. Capgemini’s business is all about business and technology transformation. So the topics we need to address are: 1. The structure of the business itself, otherwise we will not be able to understand which technology is needed to support or enable the business; 2. The way in which the business wants to process its information, as information processing is what the supporting technology does; 3.
This has been solved by the introduction of domains. A group of services is a component for which a solution as a whole exists, and that can function as a whole. In general each architecture will only contain one group for each required set of services. 11 Policy and Collaboration Contracts To create an architecture that works, there has to be a balance between supply and demand. In other words, the services have to be able to supply what the service consumers demand from them. An example will clarify the importance: If a pizza restaurant can bake 10 pizza’s a time, and it receives one customer that orders 8 pizzas, all is fine.
Actually this way of documentation can be used to describe functional and nonfunctional aspects of anything. The service describes what can be delivered (functional aspects) and how it should behave (non-functional aspects). The collaboration contract describes the way in which it is to be delivered in terms of the communication mechanism to be used and the syntax and semantics of how it can be requested. The communication mechanism effectively defines how fast, how secure, how often etc things can happen.