Martin Abadi, Luca Cardelli Procedural languages are generally well understood and their formal foundations cast in the forms of various lambda-calculi. For object-oriented languages however the situation is not as clear-cut. In this book the authors propose and develop a different approach by developing object calculi in which objects are treated as primitives.

Using object calculi,the authors are able to explain both the semantics of objects and their typing rules and demonstrate how to develop all of the most important concepts of object-oriented programming languages: self, dynamic dispatch, classes, inheritance, protected and private methods, prototyping, subtyping, covariance and contravariance, and method specialization.

Many researchers and graduate students will find this an important development of the underpinnings of object-oriented programming.

Jim Arlow, Ila Neustadt "This book manages to convey the practical use of UML 2 in clear and understandable terms with many examples and guidelines. Even for people not working with the Unified Process, the book is still of great use. UML 2 and the Unified Process, Second Edition is a must-read for every UML 2 beginner and a helpful guide and reference for the experienced practitioner." —Roland Leibundgut, Technical Director, Zuehlke Engineering Ltd. "This book is a good starting point for organizations and individuals who are adopting UP and need to understand how to provide visualization of the different aspects needed to satisfy it. " —Eric Naiburg, Market Manager, Desktop Products, IBM Rational Software This thoroughly revised edition provides an indispensable and practical guide to the complex process of object-oriented analysis and design using UML 2. It describes how the process of OO analysis and design fits into the software development lifecycle as defined by the Unified Process (UP). UML 2 and the Unified Process contains a wealth of practical, powerful, and useful techniques that you can apply immediately. As you progress through the text, you will learn OO analysis and design techniques, UML syntax and semantics, and the relevant aspects of the UP. The book provides you with an accurate and succinct summary of both UML and UP from the point of view of the OO analyst and designer. This book provides *Chapter roadmaps, detailed diagrams, and margin notes allowing you to focus on your needs*Outline summaries for each chapter, making it ideal for revision, and a comprehensive index that can be used as a reference New to this edition: *Completely revised and updated for UML 2 syntax*Easy to understand explanations of the new UML 2 semantics*More real-world examples*A new section on the Object Constraint Language (OCL)*Introductory material on the OMG's Model Driven Architecture (MDA) The accompanying website provides *A complete example of a simple e-commerce system*Open source tools for requirements engineering and use case modeling*Industrial-strength UML course materials based on the book

Len Bass, Paul Clements, Rick Kazman This award-winning book, substantially updated to reflect the latest developments in the field, introduces the concepts and best practices of software architecture—how a software system is structured and how that system's elements are meant to interact. Distinct from the details of implementation, algorithm, and data representation, an architecture holds the key to achieving system quality, is a reusable asset that can be applied to subsequent systems, and is crucial to a software organization's business strategy. Drawing on their own extensive experience, the authors cover the essential technical topics for designing, specifying, and validating a system. They also emphasize the importance of the business context in which large systems are designed. Their aim is to present software architecture in a real-world setting, reflecting both the opportunities and constraints that companies encounter. To that end, case studies that describe successful architectures illustrate key points of both technical and organizational discussions. Topics new to this edition include: *Architecture design and analysis, including the Architecture Tradeoff Analysis Method (ATAM) *Capturing quality requirements and achieving them through quality scenarios and tactics *Using architecture reconstruction to recover undocumented architectures *Documenting architectures using the Unified Modeling Language (UML) *New case studies, including Web-based examples and a wireless Enterprise JavaBeans (EJB) system designed to support wearable computers *The financial aspects of architectures, including use of the Cost Benefit Analysis Method (CBAM) to make decisions If you design, develop, or manage the building of large software systems (or plan to do so), or if you are interested in acquiring such systems for your corporation or government agency, use Software Architecture in Practice, Second Edition, to get up to speed on the current state of software architecture.

Martin van den Berg, Marlies van Steenbergen Is your enterprise architecture making a difference? Does it contribute to the goals of your company? Are the architects your best paid employees? If you are striving for a full-hearted yes to these questions, this is the book for you.

Building an Enterprise Architecture Practice provides practical advice on how to develop your enterprise architecture practice. The authors developed different tools and models to support organizations in implementing and professionalizing an enterprise architecture function. The application of these tools and models in many different organizations forms the basis for this book. The result is a hands-on book that will help you to avoid certain pitfalls and achieve success with enterprise architecture.

A lot of organizations nowadays have a team of enterprise architects at work but struggle with questions like:

• How do I show the added value of enterprise architecture?

• How do I determine what specific architectures are necessary for my organization?

• What steps do I need to take to improve my enterprise architecture practice?

• How do I fulfill the role of enterprise architect?

These questions are answered in this book and illustrated with a lot of best practices.

After reading the book the reader will have a better understanding of what makes enterprise architecture successful and will possess the tools to analyse his own situation and build an enterprise architecture practice accordingly.

——————————————————————————————————————————————————

This book clearly describes how to establish an architecture practice that delivers value for an organization. The authors demonstrate a wealth of experience and a deep understanding of the multifaceted nature of this challenging task and they provide sound advice on how to avoid the many pitfalls that may be encountered along the way.

Recognising that there is no 'one-size-fits-all' approach, they show how to deploy a range of practical tools and approaches that will enable each organization to create its own road map to success. In particular, their Maturity Matrix is invaluable for balancing architecture priorities and targeting improvements. The book makes a significant contribution to the professionalization of the architect role.

Sally Bean, Enterprise Architecture Consultant

——————————————————————————————————————————————————

Too many books on enterprise architecture leave one in a state of mental fuzziness: After reading them, the reader has learned a lot of impressive words but still does not know how to design an enterprise architecture. This step by step guide to DYA is different.

It provides pragmatic guidelines for developing enterprise architecture and presents a maturity model that helps the users of DYA to state realistic goals and to outline feasible steps to achieve these goals. Particularly useful is the emphasis on a coherent enterprise architecture vision, including the value added by the architecture. I warmly recommend this book to practicing enterprise architects.

Prof. Dr. Roel Wieringa, Universiteit Twente

Martin van den Berg, Marlies van Steenbergen This book provides practical advice on how to develop an enterprise architecture practice. The authors developed different tools and models to support organizations in implementing and professionalizing an enterprise architecture function. Coverage applies these tools and models to a number of different organizations and, as a result, will help readers avoid potential pitfalls and achieve success with enterprise architecture.

Ludwig Von Bertalanffy

Jan Bosch Features real-life case studies covering control and real-time systems, networking, and telecommunications industry examples to illustrate how the method and processes work in practice. Provides a systematic approach that employs both qualitative and quantitative techniques for assessments, and more. Softcover.

Frederick P. Brooks Making Sense of Design

Effective design is at the heart of everything from software development to engineering to architecture. But what do we really know about the design process? What leads to effective, elegant designs? The Design of Design addresses these questions.

These new essays by Fred Brooks contain extraordinary insights for designers in every discipline. Brooks pinpoints constants inherent in all design projects and uncovers processes and patterns likely to lead to excellence. Drawing on conversations with dozens of exceptional designers, as well as his own experiences in several design domains, Brooks observes that bold design decisions lead to better outcomes.

The author tracks the evolution of the design process, treats collaborative and distributed design, and illuminates what makes a truly great designer. He examines the nuts and bolts of design processes, including budget constraints of many kinds, aesthetics, design empiricism, and tools, and grounds this discussion in his own real-world examples—case studies ranging from home construction to IBM's Operating System/360. Throughout, Brooks reveals keys to success that every designer, design project manager, and design researcher should know.

John Seely Brown, Paul Duguid To see the future we can build with information technology, we must look beyond mere information to the social context that creates and gives meaning to it.

For years pundits have predicted that information technology will obliterate the need for almost everything-from travel to supermarkets to business organizations to social life itself. Individual users, however, tend to be more skeptical. Beaten down by info-glut and exasperated by computer systems fraught with software crashes, viruses, and unintelligible error messages, they find it hard to get a fix on the true potential of the digital revolution.

John Seely Brown and Paul Duguid help us to see through frenzied visions of the future to the real forces for change in society. They argue that the gap between digerati hype and end-user gloom is largely due to the "tunnel vision" that information-driven technologies breed. We've become so focused on where we think we ought to be-a place where technology empowers individuals and obliterates social organizations-that we often fail to see where we're really going and what's helping us get there. We need, they argue, to look beyond our obsession with information and individuals to include the critical social networks of which these are always a part.

Drawing from rich learning experiences at Xerox PARC, from examples such as IBM, Chiat/Day Advertising, and California's "Virtual University," and from historical, social, and cultural research, the authors sharply challenge the futurists' sweeping predictions. They explain how many of the tools, jobs, and organizations seemingly targeted for future extinction in fact provide useful social resources that people will fight to keep. Rather than aiming technological bullets at these "relics," we should instead look for ways that the new world of bits can learn from and complement them.

Arguing elegantly for the important role that human sociability plays, even-perhaps especially-in the world of bits, The Social Life of Information gives us an optimistic look beyond the simplicities of information and individuals. It shows how a better understanding of the contribution that communities, organizations, and institutions make to learning, working and innovating can lead to the richest possible use of technology in our work and everyday lives.

Frank Buschmann, Kevlin Henney, Douglas C. Schmidt The eagerly awaited Pattern-Oriented Software Architecture (POSA) Volume 4 is about a pattern language for distributed computing.

The authors will guide you through the best practices and introduce you to key areas of building distributed software systems. POSA 4 connects many stand-alone patterns, pattern collections and pattern languages from the existing body of literature found in the POSA series. Such patterns relate to and are useful for distributed computing to a single language. The panel of experts provides you with a consistent and coherent holistic view on the craft of building distributed systems.Includes a foreword by Martin FowlerA must read for practitioners who want practical advice to develop a comprehensive language integrating patterns from key literature.

Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal Pattern-oriented software architecture is a new approach to software development. This book represents the progression and evolution of the pattern approach into a system of patterns capable of describing and documenting large-scale applications. A pattern system provides, on one level, a pool of proven solutions to many recurring design problems. On another it shows how to combine individual patterns into heterogeneous structures and as such it can be used to facilitate a constructive development of software systems. Uniquely, the patterns that are presented in this book span several levels of abstraction, from high-level architectural patterns and medium-level design patterns to low-level idioms. The intention of, and motivation for, this book is to support both novices and experts in software development. Novices will gain from the experience inherent in pattern descriptions and experts will hopefully make use of, add to, extend and modify patterns to tailor them to their own needs. None of the pattern descriptions are cast in stone and, just as they are borne from experience, it is expected that further use will feed in and refine individual patterns and produce an evolving system of patterns.

Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Robert Nord, Judith Stafford Helps you decide what information to document and then, with guidelines and examples, shows you how to express an architecture in a form that everyone can understand. An important reference on the shelf of the software architect.

Paul Clements, Rick Kazman, Mark Klein Detailed case studies demonstrate the value and practical application of the ATAM, SAAM and the ARID methods to real-world systems. A must have for software engineers.

Jim Conallen Provides a guide to building robust, scalable, and feature-rich Web applications using proven objectoriented techniques. Written for the project manager, architect, analyst, designer, and programmer of Web applications. Examines the unique aspects of modeling Web applications with the Web Application Extension for the UML. DLC: Web site development.

Microsoft Corporation There are a considerable number of options available to architects and developers when it comes to Web service security. The WEB SERVICE SECURITY guide helps developers and architects make the most appropriate security decisions in the context of the solution's requirements. This asset contains reliable, accurate guidance on how to design and implement secure Web services.

George Coulouris, Jean Dollimore, Tim Kindberg The new edition of this bestselling title on Distributed Systems has been thoroughly revised throughout to reflect the state of the art in this rapidly developing field. It emphasizes the principles used in the design and construction of distributed computer systems based on networks of workstations and server computers.

Tom Demarco This classic book of tools and methods for the analyst brings order and precisions to the specification process as it provides guidance and development of a structured specification. Covers functional decomposition; data dictionary; process specification; system modeling; structured analysis for a future system. Suitable for practicing systems analysts.

Jan L.G. Dietz If one thing catches the eye in almost all literature about (re)designing or (re)engineering of enterprises, it is the lack of a well-founded theory about their construction and operation. Often even the most basic notions like "action" or "process" are not precisely defined. Next, in order to master the diversity and the complexity of contemporary enterprises, theories are needed that separate the stable essence of an enterprise from the variable way in which it is realized and implemented.

Such a theory and a matching methodology, which has passed the test of practical experience, constitute the contents of this book. The enterprise ontology, as developed by Dietz, is the starting point for profoundly understanding the organization of an enterprise and subsequently for analyzing, (re)designing, and (re)engineering it. The approach covers numerous issues in an integrated way: business processes, in- and outsourcing, information systems, management control, staffing etc.

Researchers and students in enterprise engineering or related fields will discover in this book a revolutionary new way of thinking about business and organization. In addition, it provides managers, business analysts, and enterprise information system designers for the first time with a solid and integrated insight into their daily work.

Gary Doucet, John Gøtze, Pallab Saha, Scott Bernard The book introduces the idea of Coherency Management, and asserts that this is the primary outcome goal of an enterprise's architecture. With submissions from over 30 authors and co-authors, the book reinforces the idea that EA is being practiced in an ever-increasing variety of circumstances - from the tactical to the strategic, from the technical to the political, and with governance that ranges from sell to tell. The characteristics, usages, value statements, frameworks, rules, tools and countless other attributes of EA seem to be anything but orderly, definable, classifiable, and understandable as might be hoped given heritage of EA and the famous framework and seminal article on the subject by John Zachman over two decades ago. Notably, EA is viewed as an Enterprise Design and Management approach, adopted to build better enterprises, rather than a IT Design and Management approach limited to build better systems.

Ramez Elmasri, Shamkant B. Navathe

Thomas Erl This is a comprehensive tutorial that teaches fundamental and advanced SOA design principles, supplemented with detailed case studies and technologies used to implement SOAs in the real world. ***We'll have cover endorsements from Tom Glover, who leads IBM's Web Services Standards initiatives; Dave Keogh, Program Manager for Visual Studio Enterprise Tools at Microsoft, and Sameer Tyagi, Senior Staff Engineer, Sun Microsystems. All major software manufacturers and vendors are promoting support for SOA. As a result, every major development platform now officially supports the creation of service-oriented solutions. Parts I, II, and III cover basic and advanced SOA concepts and theory that prepare you for Parts IV and V, which provide a series of step-by-step "how to" instructions for building an SOA. Part V further contains coverage of WS-* technologies and SOA platform support provided by J2EE and .NET.

Eric Evans

Martin Fowler Martin Fowler is a consultant specializing in object-oriented analysis and design. This book presents and discusses a number of object models derived from various problem domains. All patterns and models presented have been derived from the author's own consulting work and are based on real business cases.

Martin Fowler Noted software engineering expert, Martin Fowler, turns his attention to enterprise application development. He helps professionals understand the complex—yet critical—aspects of architecture. Enables the reader to make proper choices when faced with a difficult design decision.

Martin Fowler Pressured with tight deadlines, application developers do not have the luxury of keeping completely up-to-date with all of the latest innovations in software engineering. Once in a great while, a tremendous resource comes along that helps these professionals become more efficient. The first two editions of UML Distilled have been perennial best-sellers because of their concise, yet thorough, nature. This eagerly-anticipated third edition allows you to get acquainted with some of the best thinking about efficient object-oriented software design using the latest version of the industry-standard for modeling software: UML 2.0. The author has retained the book's convenient format that has made it an essential resource for anyone who designs software for a living. The book describes all the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them. A true treasure for the software engineering community.

Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts As the application of object technology-particularly the Java programming language-has become commonplace, a new problem has emerged to confront the software development community. Significant numbers of poorly designed programs have been created by less-experienced developers, resulting in applications that are inefficient and hard to maintain and extend. Increasingly, software system professionals are discovering just how difficult it is to work with these inherited, "non-optimal" applications. For several years, expert-level object programmers have employed a growing collection of techniques to improve the structural integrity and performance of such existing software programs. Referred to as "refactoring," these practices have remained in the domain of experts because no attempt has been made to transcribe the lore into a form that all developers could use. . .until now. In Refactoring: Improving the Design of Existing Software, renowned object technology mentor Martin Fowler breaks new ground, demystifying these master practices and demonstrating how software practitioners can realize the significant benefits of this new process.

With proper training a skilled system designer can take a bad design and rework it into well-designed, robust code. In this book, Martin Fowler shows you where opportunities for refactoring typically can be found, and how to go about reworking a bad design into a good one. Each refactoring step is simple-seemingly too simple to be worth doing. Refactoring may involve moving a field from one class to another, or pulling some code out of a method to turn it into its own method, or even pushing some code up or down a hierarchy. While these individual steps may seem elementary, the cumulative effect of such small changes can radically improve the design. Refactoring is a proven way to prevent software decay.

In addition to discussing the various techniques of refactoring, the author provides a detailed catalog of more than seventy proven refactorings with helpful pointers that teach you when to apply them; step-by-step instructions for applying each refactoring; and an example illustrating how the refactoring works. The illustrative examples are written in Java, but the ideas are applicable to any object-oriented programming language.

Erich Gamma, Richard Helm, Ralph Johnson, John M. Vlissides Four top-notch authors present the first book containing a catalog of object-oriented design patterns. Readers will learn how to use design patterns in the object-oriented development process, how to solve specific design problems using patterns, and gain a common vocabulary for object-oriented design.

T S Graves Enterprise-architecture is often described as part of IT, but its real scope is much wider - the structure of everything the enterprise is and does. This book introduces a new approach to tackle this broader role for whole-of-enterprise architecture, using a systematic, iterative process for architecture development. Topics include how to bridge the business/IT divide; how to link architecture with business strategy; and how to improve balance between manual, machine and IT-based processes.

Tom Graves For more than a decade, enterprise architecture has been comfortably ensconced within the IT domain. Yet in many organisations, the gap between business and IT is a gaping chasm, whilst some other silos are more like separate worlds. To gain the best business benefits from architecture, it's time to move out, bridging the silos to link everything the enterprise is and does. This book provides a structured 'conversion course' for IT-architects wanting to get to grips with the much broader scope of enterprise-scale architecture. Topics covered include: - how to leverage existing skills with IT-architecture tools such as Zachman, TOGAF and PRINCE2; - how to resolve differences of structure and scope between IT-architecture and enterprise architecture; - how to adapt existing IT-centric frameworks and methodologies for this broader role; - how to align architecture with enterprise-wide governance; - how to define, create, share and update the appropriate architectural information. If you want to take your enterprise-architecture skills to a whole new level, this is one book you'll definitely need. Tom Graves has been an independent consultant for almost three decades, in knowledge management, business transformation and enterprise architecture. Also recognized as a pioneer of desktop publishing, his clients in Europe, Australia and the USA have include banking, utilities, logistics, engineering, media, telecoms, research, defence and government. He has a special interest in architecture for non-IT-centric enterprises, and integration between IT-based and non-IT-based services.

Tom Graves A service-oriented architecture is fundamental to many new IT applications, from Web 2.0 to social software and cloud-computing. Yet everything is a service: we can apply the same principles to every aspect of the service-oriented enterprise. This book explores how enterprise architecture and viable services link together to create a simpler yet far more powerful view of the enterprise, as a dynamic, unified whole. The techniques described can be used in business transformation, workflow mapping, system design and much else besides, in every type of enterprise - including those in which there is little or no IT at all. Topics covered include: - how to identify and describe the right delivery services, infrastructure services, management services and pervasive services you need for your enterprise - how to distinguish between services you can safely outsource, and services you need to keep in-house - how to enhance service quality, interdependence and completeness - how to pinpoint and map the information-flows you need for service-management and service-performance - how to construct function-models and service-models of your enterprise, as a base for service-mapping - how to use services to support agility and innovation across the entire enterprise If you want to apply the full power of the service-oriented enterprise to your own business context, this is one book you'll definitely need. Tom Graves has been an independent consultant for almost three decades, in business transformation, enterprise architecture and knowledge management. His clients in Europe, Australia and the USA cover a broad range of industries including banking, utilities, logistics, engineering, media, telecoms, research, defence and government. He has a special interest in architecture for non-IT-centric enterprises, and integration between IT-based and non-IT-based services.

Tom Graves When you're doing enterprise architecture, what should you actually do, in what sequence, for what business purpose? What skills and leadership do you need? What results should you expect? And how can you prove the business value of what you do? For process and practice in the real enterprise, methodologies and frameworks such as TOGAF, FEAF and Zachman will all help, but it's these practical concerns that often matter most. And that's what this book will show you. Topics covered include: - how to extend existing IT-centric architecture to the whole of the enterprise - how to identify business vision, values, structure and purpose, and include these as core anchors for your enterprise architecture - how to map business functions, services, information-systems and process flows across the whole enterprise - how to respond to changes in strategy, regulation, market and environment - how to plan for business-continuity, disaster-recovery and risk-management - how to tackle intractable 'wicked problems' in the business context - how to keep maintaining and extending the agility and value of the architecture If you want to bring your enterprise architecture practice to its full business potential, this is one book you'll definitely need. Tom Graves has been an independent consultant for almost three decades, in business transformation, enterprise architecture and knowledge management. His clients in Europe, Australia and the USA cover a broad range of industries including banking, utilities, logistics, engineering, media, telecoms, research, defence and government. He has a special interest in architecture for non-IT-centric enterprises, and integration between IT-based and non-IT-based services.

Tom Graves All of architecture comes down to one simple idea: things work better when they work together, with clarity, with elegance, on purpose. Yet how do we express that 'one idea' in practice, within our organisations? With what results, and for what business-value? This book describes the down-to-earth detail of everyday enterprise architecture, to show what architects actually do to deliver value fast, across the entire enterprise. Working step by step through a real ten-day architecture-project, this book explores the activities that underpin sensemaking, strategy, structures and solutions in the real-time turmoil of an enterprise-architect's everyday work. Topics covered include: - how to use enterprise-architecture to tackle executive-level business-problems - how to develop an agile architecture practice that can keep pace with the real-time pressures of the real business world - how to identify the business-reasons and business-value for each activity - how to thrive on the inherent uncertainties of the architecture process - how to use context-space maps to guide sensemaking and solution-design - how to apply architecture ideas and activities to describe what actually happens in a real enterprise-architecture project - how to enhance architectural skills, judgement and awareness, for continuous improvement across the enterprise and in the architecture itself If you want your enterprise to flourish and prosper in the midst of relentless change, this is one book you'll definitely need. Tom Graves has been an independent consultant for more than three decades, in business transformation, enterprise architecture and knowledge management. His clients in Europe, Australasia and the Americas cover a broad range of industries including banking, utilities, manufacturing, logistics, engineering, media, telecoms, research, defence and government. He has a special interest in architecture for non-IT-centric enterprises, and integration between IT-based and non-IT-based services.

Nigel Green, Carl Bate Do you speak "business" or "IT"? Perhaps you speak a little of both. In today's connected world, where business and IT are fused, chances are that if you're a business or IT executive, or someone working to transform a business, you speak a little of both. But what if there was a "third" language? A common language that was natural for both "business" and "IT," straightforward enough to use, yet sophisticated enough to work in today's connected world? What if such a language only comprised a handful of words? With such a language, the "loss in translation" between the business and IT would happen less, because both would be using the same language. With such a language, business outcomes and transformations would become much more achievable. This handbook describes what this language is-the language of Information Systems for the 21st century.

Terry Halpin, Tony Morgan Information Modeling and Relational Databases, second edition, provides an introduction to ORM (Object-Role Modeling)and much more. In fact, it is the only book to go beyond introductory coverage and provide all of the in-depth instruction you need to transform knowledge from domain experts into a sound database design. This book is intended for anyone with a stake in the accuracy and efficacy of databases: systems analysts, information modelers, database designers and administrators, and programmers.

Terry Halpin, a pioneer in the development of ORM, blends conceptual information with practical instruction that will let you begin using ORM effectively as soon as possible. Supported by examples, exercises, and useful background information, his step-by-step approach teaches you to develop a natural-language-based ORM model, and then, where needed, abstract ER and UML models from it. This book will quickly make you proficient in the modeling technique that is proving vital to the development of accurate and efficient databases that best meet real business objectives.

*Presents the most indepth coverage of Object-Role Modeling available anywhere, including a thorough update of the book for ORM2, as well as UML2 and E-R (Entity-Relationship) modeling.

*Includes clear coverage of relational database concepts, and the latest developments in SQL and XML, including a new chapter on the impact of XML on information modeling, exchange and transformation.

* New and improved case studies and exercises are provided for many topics.

* The book's associated web site provides answers to exercises, appendices, advanced SQL queries, and links to downloadable ORM tools.

David C. Hay This book is a compendium of the various analysis techniques that have developed over the last thirty years, organized in terms of an architectural framework. Each technique has a place in the framework, and this placement enables coherent comparison of them all, identifying the strengths and weaknesses of each. Project development teams often spend too little time learning about the actual business problems a system must address. Without a clear understanding of these issues, organizations can easily develop off-target solutions, miss critical windows of opportunity, and get overrun by their competition. On the other hand, development teams that follow a proven process tend to get it right from the beginning, avoiding the costs of repairing or re-releasing software later in the life cycle. Requirements and Analysis is the process of defining your system. This involves obtaining a clear understanding of the problem space—such as business opportunities, user needs, or the marketing environment—and then defining an application or system to solve that problem. Rational Requirements and Analysis solutions help you build it right from the beginning.Foreword by Barbara von Halle, Spectrum Technology Group Inc.

David C. Hay In recent years, companies and government agencies have come to realize that the data they use represent a significant corporate resource, whose cost calls for management every bit as rigorous as the management of human resources, money, and capital equipment. With this realization has come recognition of the importance to integrate the data that has traditionally only been available from disparate sources.

An important component of this integration is the management of the "metadata" that describe, catalogue, and provide access to the various forms of underlying business data. The "metadata repository" is essential keeping track both of the various physical components of these systems, but also their semantics. What do we mean by "customer?" Where can we find information about our customers?

After years of building enterprise models for the oil, pharmaceutical, banking, and other industries, Dave Hay has here not only developed a conceptual model of such a metadata repository, he has in fact created a true enterprise data model of the information technology industry itself.

* A comprehensive work based on the Zachman Framework for information architecture-encompassing the Business Owner's, Architect's, and Designer's views, for all columns (data, activities, locations, people, timing, and motivation)
* Provides a step-by-step description of model and is organized so that different readers can benefit from different parts
* Provides a view of the world being addressed by all the techniques, methods and tools of the information processing industry (for example, object-oriented design, CASE, business process re-engineering, etc.)
* Presents many concepts that are not currently being addressed by such tools - and should be

Gregor Hohpe, Bobby Woolf Text provides a catalog of sixty-five patterns, with real-world solutions that demonstrate the formidable power of messaging and help you design effective messaging solutions for your enterprise. DLC: Telecommunication—Message processing.

IIBA, Kevin Brennan Business analysis is the set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals. Business analysis involves understanding how organizations function to accomplish their purposes and defining the capabilities an organization requires to provide products and services to external stakeholders. It includes the definition of organizational goals, understanding how those goals connect to specific objectives, determining the courses of action that an organization has to undertake to achieve those goals and objectives, and defining how the various organizational units and stakeholders within and outside of that organization interact. A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) contains a description of generally accepted practices in the field of business analysis. The content included in this release has been verified through reviews by practitioners, surveys of the business analysis community, and consultations with recognized experts in the field. In less than five years, the BABOK® Guide has been recognized around the world as a key tool for the practice of business analysis and become a widely-accepted standard for the profession, with over 200,000 copies downloaded from the IIBA® website. Version 2.0 represents a major advance on that standard, and will become an essential reference for business analysis professionals.

John Jeston, Johan Nelis Business Process Management: Practical Guidelines to Successful Implementations provides organizational leadership with an understanding of Business Process Management and its benefits to an organization. This book also gives Business Process Management practitioners a framework and a set of tools and techniques that provide a practical guide to successfully implementing Business Process Management projects and provides a holistic approach and the necessary details to deliver a Business Process Management project.

Business Process Management: Practical Guidelines to Successful Implementations delivers:

* a proven in-depth step-by-step framework for the Business Process Management practitioner.

* insights into how to embed Business Process Management within an organization to ensure a continuous business process involvement culture.

* practical tools, explanations and assistance in the successful implementation of a BPM project.

* more than 50 case studies to illustrate various steps and aspects of the framework.

* an overall view and understanding of Business Process Management and the move towards a process-centric organization.

* Encompasses best practices and an overview of the most important tools and methods
* An in -depth framework for the Business Process Management practitioner.
* Insights into how to embed Business Process Management within an organization to ensure a continuous business process improvement culture.
* Practical tools, explanations and assistance in the successful implementation of a BPM project.
* Includes in excess of 50 case studies to illustrate various points in the book.

Theresa Kushner, Maria Villar, Richard Hagle About Managing Your Business Data: From Chaos to Confidence As a business person, you probably have more data and more kinds of data available than than ever before. But has it helped? Sometimes, maybe. But, for many executives it also has just been more fuel to feed the fire of their love/hate relationship with it. You love it when it gives you good information about which markets to pursue or how to compete more effectively. But you hate it when you can t get sales figures in time or worse still, when they don t reflect reality. This book was written for the executive who wants to understand the lifeblood of his/her company, wants to be able to make better decisions, and knows that managing information is the best way to protect and grow a business. This book is designed to help you as a business leader think about the use of data and its impact on your daily operation. In 2 sections and 12 chapters it provides practical guidance balance the use of hard facts and your professional instincts; how to identify and focus on the numbers that matter for your organization; how to overcome the obstacles to getttinga complete view of your customer; how to meet risk and security standards; 12 steps to effective business performance manangement; and how to grow a data culture and how to make data work for you. Newly minted MBAs are known for saying, Just give me your number. Savvvy managers know that it s not that simple. They also know that it s not that difficult. Managing Your Business Data provides the wise counsel that every executive can use to manage his or her organization s data more productively.

Marc Lankhorst An enterprise architecture tries to describe and control an organisation’s structure, processes, applications, systems and techniques in an integrated way. The unambiguous specification and description of components and their relationships in such an architecture requires a coherent architecture modelling language.

Lankhorst and his co-authors present such an enterprise modelling language that captures the complexity of architectural domains and their relations and allows the construction of integrated enterprise architecture models. They provide architects with concrete instruments that improve their architectural practice. As this is not enough, they additionally present techniques and heuristics for communicating with all relevant stakeholders about these architectures. Since an architecture model is useful not only for providing insight into the current or future situation but can also be used to evaluate the transition from ‘as-is’ to ‘to-be’, the authors also describe analysis methods for assessing both the qualitative impact of changes to an architecture and the quantitative aspects of architectures, such as performance and cost issues.

The modelling language presented has been proven in practice in many real-life case studies and has been adopted by The Open Group as an international standard. So this book is an ideal companion for enterprise IT or business architects in industry as well as for computer or management science students studying the field of enterprise architecture.

David Luckham After thoroughly introducing the concept, the book moves on to a more detailed, technical explanation of CEP, featuring the Rapid event pattern language, reactive event pattern rules, event pattern constraints, and event processing agents. Offers practical advice on building CEP-based solutions that solve real world IS/IT problems. Softcover.

Mark W. Maier If engineering is the art and science of technical problem solving, systems architecting happens when you don’t yet know what the problem is. The third edition of a highly respected bestseller, The Art of Systems Architecting provides in-depth coverage of the least understood part of systems design: moving from a vague concept and limited resources to a satisfactory and feasible system concept and an executable program. The book provides a practical, heuristic approach to the "art" of systems architecting. It provides methods for embracing, and then taming, the growing complexity of modern systems.

New in the Third Edition:

Five major case studies illustrating successful and unsuccessful practicesInformation on architecture frameworks as standards for architecture descriptionsNew methods for integrating business strategy and architecture and the role of architecture as the technical embodiment of strategyIntegration of process guidance for organizing and managing architecture projectsUpdates to the rapidly changing fields of software and systems-of-systems architectureOrganization of heuristics around a simple and practical process model

 A Practical Heuristic Approach to the Art of Systems Architecting

Extensively rewritten to reflect the latest developments, the text explains how to create a system from scratch, presenting invention/design rules together with clear explanations of how to use them. The author supplies practical guidelines for avoiding common systematic failures while implementing new mandates. He uses a heuristics-based approach that provides an organized attack on very ill-structured engineering problems. Examining architecture as more than a set of diagrams and documents, but as a set of decisions that either drive a system to success or doom it to failure, the book provide methods for integrating business strategy with technical architectural decision making.

Roger L. Martin Most companies today have innovation envy. They yearn to come up with a game-changing innovation like Apple's iPod, or create an entirely new category like Facebook. Many make genuine efforts to be innovative-they spend on R&D, bring in creative designers, hire innovation consultants. But they get disappointing results.

Why? In The Design of Business, Roger Martin offers a compelling and provocative answer: we rely far too exclusively on analytical thinking, which merely refines current knowledge, producing small improvements to the status quo.

To innovate and win, companies need design thinking. This form of thinking is rooted in how knowledge advances from one stage to another-from mystery (something we can't explain) to heuristic (a rule of thumb that guides us toward solution) to algorithm (a predictable formula for producing an answer) to code (when the formula becomes so predictable it can be fully automated). As knowledge advances across the stages, productivity grows and costs drop-creating massive value for companies.

Martin shows how leading companies such as Procter & Gamble, Cirque du Soleil, RIM, and others use design thinking to push knowledge through the stages in ways that produce breakthrough innovations and competitive advantage.

Filled with deep insights and fresh perspectives, The Design of Business reveals the true foundation of successful, profitable innovation.

B. Craig Meyers, Patricia Oberndorf The acquisition of open systems and commercial off-the-shelf (COTS) products is an increasingly vital element of corporate and government software development. Properly managed software acquisition offers potential for significant time and cost savings over a system's lifetime. The transition from proprietary, custom-built systems to systems based on standards and commercial products is not easy, however. Managers and their staff must understand the risks and opportunities associated with this acquisition approach. Managing Software Acquisition presents the fundamental principles and best practices for successful acquisition of open, COTS-based systems. It explores the many opportunities and challenges of this approach, defines key terms, anticipates potential problems, and discusses the effect of software acquisition on the manager's job. The information presented addresses critical concerns affecting the entire software industry; it also discusses important issues particular to government acquisition. Managing Software Acquisition moves from a broad overview of the topic to experience-based advice on managing the transition and more detailed information on acquisition.You will find coverage of such topics as: *Promises and pitfalls of open, COTS-based system acquisition *Implications for industry and government—quality, loss of control, and risk *Reference models, architectures, and standards for open systems and COTS products *Implications for cost, schedule, performance, and staff *Engineering practices, including defining requirements, integration, testing, deployment, and support *Contracting strategies and relationships with vendors *Integrated acquisition using standards and COTS products Each major section concludes with realistic, open-ended exercises that illustrate vital issues confronting software acquisition managers. In addition, the book includes an extensive reference section containing a glossary, list of acronyms, sample questions to help organizations evaluate their needs, and more. 0201704544B05222001

Glenn O'Donnell, Carlos Casanova Implement Configuration Management Databases that Deliver Rapid ROI and Sustained Business Value

 

Implementing an enterprise-wide Configuration Management Database (CMDB) is one of the most influential actions an IT organization can take to improve service delivery and bridge the gap between technology and the business. With a well-designed CMDB in place, companies are better positioned to manage and optimize IT infrastructure, applications, and services; automate more IT management tasks; and restrain burgeoning costs. Now, there’s an objective, vendor-independent guide to making a CMDB work in your organization. The CMDB Imperative presents a start-to-finish implementation methodology that works and describes how the CMDB is shifting to the superior Configuration Management System (CMS).

 

Expert CMDB industry analyst Glenn O’Donnell and leading-edge architect and practitioner Carlos Casanova first review the drivers behind a CMDB and the technical, economic, cultural, and political obstacles to success. Drawing on the experiences of hundreds of organizations, they present indispensable guidance on architecting and customizing CMDB solutions to your specific environment. They’ll guide you through planning, implementation, transitioning into production, day-to-day operation and maintenance, and much more. Coverage includes

  Defining the tasks and activities associated with configuration management Understanding the CMDB’s role in ITIL and the relationship between CMDBs and ITIL v3’s CMS Building software models that accurately represent each entity in your IT environment Ensuring information accuracy via change management and automated discovery Understanding the state of the CMDB market and selling the CMDB within your organization Creating federated CMDB architectures that successfully balance autonomy with centralized control Planning a deployment strategy that sets appropriate priorities and reflects a realistic view of your organization’s maturity Integrating systems and leveraging established and emerging standards Previewing the future of the CMDB/CMS and how it will be impacted by key trends such as virtualization, SOA, mobility, convergence, and “flexi-sourcing”

 

Foreword     xi

Prologue     xiii

 

Chapter 1: The Need for Process Discipline     1

Chapter 2: What Is a CMDB?     25

Chapter 3: Planning for the CMS     57

Chapter 4: The Federated CMS Architecture     91

Chapter 5: CMS Deployment Strategy     133

Chapter 6: Integration—There’s No Way Around It!     177

Chapter 7: The Future of the CMS     197

Chapter 8: Continual Improvement for the CMS     241

Chapter 9: Leveraging the CMS     265

Chapter 10: Enjoy the Fruits of Success     297

 

Glossary     313

Debra Paul, Donald Yeates Improving the effectiveness of your IT through better alignment with the business is a precursor to increasing profitability. This practical, introductory guide provides you with the tools to achieve this. It teaches you about strategy analysis and how to model business systems and processes and covers other topics including business case development, change management, and engineering/information resource management. The book also supports the ISEB qualifications in Business Analysis.

Chris Potts Ian is a Chief Information Officer (CIO) who is about to go on a journey of change - whether he likes it or not.  He will be expected to explore, challenge and radically recast the complex, often hostile relationships that can exist between a business and the people in its Information Technology (IT) department.  On the way, Ian, his Chief Executive Officer, Chief Financial Officer and other key stakeholders, experience a transformation in how a business needs to think about the value of its IT people and the work that they do. This results in some truly groundbreaking innovations in the scope and contribution of Ian's role as CIO, the people that work for him and the strategy that he leads.

Watch the characters in this extraordinary business novel as they meet the challenge, struggle and grow. Share in Ian's transformation, and join the author in observing key messages as the adventure unfolds.

Part entertaining novel and part enlightening textbook - FruITion takes the reader through a discovery process revealing indispensable messages about the next generation of strategies for Information Technology.
- Jeremy Hall, Managing Director, IRM UK Strategic IT Training

FruITion brings vividly to life the issues of being a CIO in today's corporate world and how IT, when properly integrated into the objectives of a business can drive massive value creation. His insights into how to win the engagement war and bring technology strategies alive for the non technical are absolutely spot on.
- Steve Adams, COO and Managing Director for Card Services, Euronet Worldwide

The modern CIO is to be seen as part of the business rather than a service provider to the business. Chris Potts is at the forefront of thinking that will put us all there if we act on his inspiration.
- David Brown, CIO of Scottish Water

More from the author, Chris Potts
The debate over the CIO role, and about the extent to which it should be about business or technology, is taking place in an increasing vacuum of strategic context.  Some CIOs have abandoned strategy altogether, while others persevere with a traditional IT Strategy founded in the mindset of the mainframe era.  Meanwhile, business managers and staff continue to develop their knowledge of technology and understanding of how to exploit it.  There seems to be a presumption that the next-generation strategic purpose of the CIO will be an incremental step on from what has gone before - significant, maybe, but still incremental.  What if the CIO's new strategic context is not incremental but disruptive, requiring a very different mindset and skillset?  And, most crucially, what if the corporate strategists - rather than the CIO community - are the ones deciding what context is?   Their offer to the CIO:  you can become one of the corporate strategists like us, but not with your traditional scope and approach to strategy.  What does that offer look like and what does it mean for incumbent CIOs and the people who work for them?

Magnus Ramage, Karen Shipp Systems Thinkers presents a biographical history of the field of systems thinking, by examining the life and work of thirty of its major thinkers. It discusses each thinker’s key contributions, the way this contribution was expressed in practice and the relationship between their life and ideas. This discussion is supported by an extract from the thinker’s own writing, to give a flavour of their work and to give readers a sense of which thinkers are most relevant to their own interests.

Systems thinking is necessarily interdisciplinary, so that the thinkers selected come from a wide range of areas – biology, management, physiology, anthropology, chemistry, public policy, sociology and environmental studies among others. A significant aim of the book is to broaden and deepen the reader’s interest in systems writers, providing an appetising ‘taster’ for each of the 30 thinkers, so that the reader is encouraged to go on to study the published works of the thinkers themselves.

Martin Reynolds, Sue Holwell In a world of increasing complexity, instant information availability and constant flux, systems approaches provide the opportunity of a tangible anchor of purpose and iterate learning. The five approaches outlined in the book offer a range of interchangeable tools with rigorous frameworks of application tried and tested in the ‘real world’. The frameworks of each approach form a powerful toolkit to explore the dynamics of how societies emerge, how organisations create viability, how to facilitate chains of argument through causal mapping, how to embrace a multiplicity of perspectives identifying purposeful activity and how to look for the bigger picture across multiple disciplines.

Systems Approaches offers an excellent first introduction for those seeking to understand what ‘systems thinking’ is all about as well as why the tools discussed herein should be applied to management and professional practice. This book provides a practical guide, and the chapters stand alone in explaining and developing each approach.

Suzanne Robertson, James C. Robertson "If the purpose is to create one of the best books on requirements yet written, the authors have succeeded." —Capers Jones It is widely recognized that incorrect requirements account for up to 60 percent of errors in software products, and yet the majority of software development organizations do not have a formal requirements process. Many organizations appear willing to spend huge amounts on fixing and altering poorly specified software, but seem unwilling to invest a much smaller amount to get the requirements right in the first place. Mastering the Requirements Process, Second Edition, sets out an industry-proven process for gathering and verifying requirements with an eye toward today's agile development environments. In this total update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs while doing the minimum requirements work according to the project's level of agility. Features include *The Volere requirements process—completely specified, and revised for compatibility with agile environments*A specification template that can be used as the basis for your own requirements specifications *New agility ratings that help you funnel your efforts into only the requirements work needed for your particular development environment and project*How to make requirements testable using fit criteria*Iterative requirements gathering leading to faster delivery to the client*Checklists to help identify stakeholders, users, nonfunctional requirements, and more *Details on gathering and implementing requirements for iterative releases*An expanded project sociology section for help with identifying and communicating with stakeholders*Strategies for exploiting use cases to determine the best product to build *Methods for reusing requirements and requirements patterns *Examples showing how the techniques and templates are applied in real-world situations

Jeanne W. Ross, Peter Weill, David Robertson Does it seem you’ve formulated a rock-solid strategy, yet your firm still can’t get ahead? If so, construct a solid foundation for business execution—an IT infrastructure and digitized business processes to automate your company’s core capabilities. In Enterprise Architecture as Strategy: Creating a Foundation for Business Execution, authors Jeanne W. Ross, Peter Weill, and David C. Robertson show you how.

The key? Make tough decisions about which processes you must execute well, then implement the IT systems needed to digitize those processes. Citing numerous companies worldwide, the authors show how constructing the right enterprise architecture enhances profitability and time to market, improves strategy execution, and even lowers IT costs. Though clear, engaging explanation, they demonstrate how to define your operating model—your vision of how your firm will survive and grow—and implement it through your enterprise architecture. Their counterintuitive but vital message: when it comes to executing your strategy, your enterprise architecture may matter far more than your strategy itself.

Nick Rozanski, Eóin Woods Software Systems Architecture is a practitioner-oriented guide to designing and implementing effective architectures for information systems. It is both a readily accessible introduction to software architecture and an invaluable handbook of well-established best practices. It shows why the role of the architect is central to any successful information-systems development project, and, by presenting a set of architectural viewpoints and perspectives, provides specific direction for improving your own and your organization's approach to software systems architecture.With this book you will learn how to *Design an architecture that reflects and balances the different needs of its stakeholders *Communicate the architecture to stakeholders and demonstrate that it has met their requirements *Focus on architecturally significant aspects of design, including frequently overlooked areas such as performance, resilience, and location *Use scenarios and patterns to drive the creation and validation of your architecture *Document your architecture as a set of related views *Use perspectives to ensure that your architecture exhibits important qualities such as performance, scalability, and security The architectural viewpoints and perspectives presented in the book also provide a valuable long-term reference source for new and experienced architects alike. Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects. A supporting Web site containing further information can be found at www.viewpoints-and-perspectives.info

Geary A. Rummler, Alan P. Brache Streamline the processes vital to optimum performance

With over 100,000 copies sold worldwide, Improving Performance is recognized as the book that launched the Process Improvement revolution. It was the first such approach to bridge the gap between organization strategy and the individual. Now, in this revised and expanded new edition, Rummler and Brache reflect on the key needs of organizations faced with today's challenge of managing change. With multiple charts, checklists, hands-on tools and case studies, the authors show how they implemented their Performance Improvement methodology in over 250 successful projects with clients such as Hewlett-Packard, 3M, Shell Oil, and Citibank.

Douglas Schmidt, Michael Stal, Hans Rohnert, Frank Buschmann Designing application and middleware software to run in concurrent and networked environments is a significant challenge to software developers. The patterns catalogued in this second volume of Pattern-Oriented Software Architecture (POSA) form the basis of a pattern language that addresses issues associated with concurrency and networking. The book presents 17 interrelated patterns ranging from idioms through architectural designs. They cover core elements of building concurrent and network systems: service access and configuration, event handling, synchronization, and concurrency. All patterns present extensive examples and known uses in multiple programming languages, including C++, C, and Java. The book can be used to tackle specific software development problems or read from cover to cover to provide a fundamental understanding of the best practices for constructing concurrent and networked applications and middleware.

Roger Sessions Dismantle the overwhelming complexity in your IT projects with strategies and real-world examples from a leading expert on enterprise architecture. This guide describes best practices for creating an efficient IT organization that consistently delivers on time, on budget, and in line with business needs.

IT systems have become too complex and too expensive. Complexity can create delays, cost overruns, and outcomes that do not meet business requirements. The resulting losses can impact your entire company. This guide demonstrates that, contrary to popular belief, complex problems demand simple solutions. The author believes that 50 percent of the complexity of a typical IT project can and should be eliminated and he shows you how to do it.

You ll learn a model for understanding complexity, the three tenets of complexity control, and how to apply specific techniques such as checking architectures for validity. Find out how the author s methodology could have saved a real-world IT project that went off track, and ways to implement his solutions in a variety of situations.

Key Book Benefits:

 Presents a model for understanding IT and enterprise complexity  Provides practical solutions for controlling complexity, and shows how they can be applied in a variety of situations  Features a methodology for checking architectures for validity  Explains how to apply simplification algorithms to software systems  Includes a real-world case study that demonstrates how the author s solutions could have saved an actual IT project that went wrong

Roel Wagter, Martin van den Berg, Joost Luijpers, Marlies van Steenbergen This book presents an approach to enterprise architecture, which enables corporations to achieve their business objectives faster. Focusing on the governance of IT in the organization, it provides tangible tools, advice and strategies for implementing and designing the architectural process within a corporation that will make a major contribution in driving the business forward and achieve its goals.

Kurt Wallnau, Scott Hissam, Robert C. Seacord (Pearson Education) A three-part text on the theory and practice of building systems from commercial components. Part 1 identifies building challenges and presents engineering techniques, part 2 presents an extensive case study, and part 3 provides advice on how to begin a building project. DLC: System design.

R. F. C. Walters Category Theory has, in recent years, become increasingly important and popular in computer science, and many universities now introduce Category Theory as part of the curriculum for undergraduate computer science students. Here, the theory is developed in a straightforward way, and is enriched with many examples from computer science.