Picture 1 of 11
Stock photo
Picture 1 of 11
Stock photo
Integrated Architecture Framework Explained : Why, What, How by Maarten Waage, Aaldert Hofman, Herman Hartman, Jack Van't Wout and Max Stahlecker (2010, Hardcover)
A
American Cache (277)
100% positive feedback
Price:
US $78.00
ApproximatelyPHP 4,357.16
+ $35.16 shipping
Returns:
30 days return. Buyer pays for return shipping. If you use an eBay shipping label, it will be deducted from your refund amount.
Condition:
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
About this product
Product Identifiers
PublisherSpringer Berlin / Heidelberg
ISBN-103642115179
ISBN-139783642115172
eBay Product ID (ePID)102845163
Product Key Features
Number of PagesXviii, 246 Pages
Publication NameIntegrated Architecture Framework Explained : Why, What, How
LanguageEnglish
Publication Year2010
SubjectSystems Architecture / General, Management Information Systems, Computer Science, Information Management
TypeTextbook
AuthorMaarten Waage, Aaldert Hofman, Herman Hartman, Jack Van't Wout, Max Stahlecker
Subject AreaComputers, Business & Economics
FormatHardcover
Dimensions
Item Weight23.5 Oz
Item Length9.3 in
Item Width6.1 in
Additional Product Features
Intended AudienceScholarly & Professional
Dewey Edition22
TitleLeadingThe
Number of Volumes1 vol.
IllustratedYes
Dewey Decimal004.22
Table Of ContentIAF Background, Value and Strategy.- IAF's Architecture.- IAF's Aspect Areas Explained.- IAF in Perspective with Other Frameworks and Methods.- Applying IAF and Using Its Outcomes.- Real Life Case Studies.- The Making of IAF.
SynopsisThis book relates the wealth of architecture experience Capgemini has gathered as a member of The Open Group - a vendor- and technology-neutral consortium - in developing, deploying, and using its Integrated Architecture Framework (IAF) since its 1993 origin., This book captures and communicates the wealth of architecture experience Capgemini has gathered as a member of The Open Group - a vendor- and technology-neutral consortium formed by major industry players - in developing, deploying, and using its "Integrated Architecture Framework" (IAF) since its origination in 1993. Today, many elements of IAF have been incorporated into the new version 9 of TOGAF, the related Open Group standard. The authors, all working on and with IAF for many years, here provide a full reference to IAF and a guide on how to apply it. In addition, they describe in detail the relations between IAF and the architecture standards TOGAF and Archimate and other development or process frameworks like ITIL, CMMI, and RUP. Their presentation is targeted at architects, project managers, and process analysts who have either considered or are already working with IAF - they will find many roadmaps, case studies, checklists, and tips and advice for their daily work., When I joined Capgemini back in 1996 I was amazed by investment that had been made in developing Enterprise Architecture, and at the root of this, the IAF methodology. Back in the mid 1990s the importance of architecture was dimly recognised but certainly it was not widely understood as a crucial element of successful enterprise wide IT implementation. A decade later with the huge growth in the role, the sophistication, and importance of Information Technology it has become recognized, and established for the value it brings. With this recognition has come various forms of 'standardization' ranging from the work of the Open Group and its moves to establish TOGAF as a common framework, together with ITAC to certify architects, through to a wide variety of product vendor architects, even to some industry sectors establishing their own architectures. Has this diminished, or even may be removed the need for IAF? Well it might have done if the world had stood still, but it hasn't. Simul- neously the range and complexity of technology has increased, the functionality has been extended to embrace new front office capabilities and most of all the externalization and globalization of business has added a whole new extra dimension. Standardization might have improved connections and interfaces, and in so doing produced 'systems' of apparently limitless extendibility, but it has done little to improve the necessary 'understanding'.
LC Classification NumberHF54.5-54.56
Be the first to write a review
