A Practical Guide to Enterprise Architecture (häftad)
Häftad (Paperback)
Antal sidor
illustrated ed
Ambler, Scott W. / Stevens, Michael E. / Linn, James / Sharan, Vikas / Jo, Elias K.
240 x 180 x 28 mm
640 g
Antal komponenter

A Practical Guide to Enterprise Architecture

Häftad, Engelska, 2003-11-01
553 kr
Specialorder (osäker tillgång). Skickas inom 11-20 vardagar.
Fri frakt inom Sverige för privatpersoner.
  • Comprehensive explanation of enterprise architecture concepts and methods
  • Extend the Rational Unified Process to include Enterprise Architecture
  • Unified view of the various architectural disciplines to create strategic blueprints
  • Perspectives on Enterprise Development and Technology
Indispensable technical, process, and business insight from leading enterprise architects

Many organizations today face the challenge of designing, building, and maintaining large-scale distributed enterprise systems that are able to adapt to changing business needs. Many repeat the mistakes of others, resulting in cost overruns, blown deadlines, and lost opportunity. Today's business climate places additional burden on IT to deliver. Ever-adapting business drivers can diverge from the capabilities of the enterprise IT systems today, especially if the systems are complex, fragile, and intolerant of change. Enterprise architecture can help future-proof IT investments made today.

A Practical Guide to Enterprise Architecture helps readers create adaptive architecture strategies for successfully implementing enterprise architectures. This classic handbook goes beyond theory and presents strategies that are based on experiences within organizations across multiple industry verticals. Behind each opinion, technique, and principle is a wealth of knowledge provided by some of the best-known industry thought leaders today.

This book's authors have architected industrial-strength software and infrastructure for many of the world's leading firms-in financial services, telecommunications, media, and e-business. They present practical guidance, candid assessments of existing practice, and detailed examples from their own experience. Coverage includes:

  • Strategies for enterprise architecture-which ones work and why
  • Proven "product line" practices for streamlining the design of enterprise software
  • Understanding how to translate key business drivers into enterprise architecture output
  • Agile architectural and modeling techniques-presented by their creator, Scott Ambler
  • Architecting presentation tiers, user experience, and usability methods to create a reusable base of core assets
  • Overcoming the challenges of transitioning to agile methods
  • Identifying architecture enabling human resource practices
Whether you're a working architect or plan to become one, A Practical Guide to Enterprise Architecture will be your timely, trusted advisor-today and for years to come.

Visa hela texten

Passar bra ihop

  1. A Practical Guide to Enterprise Architecture
  2. +
  3. Introduction to Disciplined Agile Delivery: A Small Agile Team's Journey from Scrum to Continuous Delivery

De som köpt den här boken har ofta också köpt Introduction to Disciplined Agile Delivery: A S... av Mark Lines, Scott W Ambler (häftad).

Köp båda 2 för 686 kr


Har du läst boken? Sätt ditt betyg »

Bloggat om A Practical Guide to Enterprise Architecture

Övrig information

JAMES McGOVERN, Enterprise Architect for Hartford Financial Services, is a co-author of the bestselling books Java Web Services Architecture and Agile Enterprise Architecture. SCOTT W. AMBLER, senior consultant with Ronin International, specializes in O-O analysis/design, agile modeling, and architectural audits of mission-critical systems. His best sellers include Agile Modeling and The Elements of Java Style. MICHAEL E. STEVENS, Software Architect for Hartford Financial Services, is a columnist for Developer.com. He co-authored Java Web Services Architecture. JAMES LINN, consultant at Hartford Technology Services, co-authored XQuery Kick Start. VIKAS SHARAN is managing partner of Lozoic and architecture team member at Baypackets. ELIAS JO, Systems Architect for The New York Times Digital, has architected and/or led development at DeutscheBank, Citibank, Standard & Poor, and ADP.





1. Systems Architecture.

Canaxia Brings an Architect on Board. Network Protocols. Conclusion.

2. Software Architecture.

What Is Software Architecture? The Role of a Software Architect. Why We Need Software Architecture. The System Stakeholders. Creating a Software Architecture: An Example. Architecture Description Languages and UML. Quality Attributes. Architectural Viewpoints. Architectural Styles, Patterns, and Metaphors. Conclusion.

3. Service-Oriented Architecture.

Benefits of an SOA. Characteristics of an SOA. Web Services. Services at Canaxia. SOA Issues. SOA Management. SOA Best Practices. SOA Antipatterns. Conclusion.

4. Software Product Lines.

Product Lines at Canaxia. History of Product Lines. What Is a Software Product Line? Product Line Benefits. Product Line Aspects. Conclusion.

5. Methodology Overview.

The Software Development Life Cycle. Extreme Programming. SEI/CMM. The Zachman Framework. Model-Driven Architecture. Rational Unified Process. Using These Methodologies. Conclusion.

6. Enterprise Unified Process.

The Enterprise-Unified Process. The Production Phase. The Retirement Phase. The Operations and Support Discipline. The Enterprise Management Discipline. Why Adopt the EUP? Conclusion.

7. Agile Architecture.

Agility in a Nutshell. Potential Problems with Traditional Approaches to Enterprise Architecture. An Agile Approach to Architecture. What Should Agile Architecture Efforts Produce? Agile Architecture at Canaxia. Introducing an Agile Approach into Your Organization. Are Other Architecture Approaches Agile? Potential Problems with an Agile Approach. Conclusion.

8. Agile Modeling.

The Goals of Agile Modeling. Agile Models. Agile Documents. Conclusion.

9. Presentation Tier Architecture.

Key Presentation Tier Components. General Design Recommendations. Design Guidelines for Interface Components. Conclusion.

10. Usability and User Experience.

Understanding Usability. User Experience Components. Usability and User Experience Design Process. Usability Techniques. Sharing the Usability Test Reports. Out-of-the-Box Experience. Conclusion.

11. Data Architecture.

The Business Problem. Baseline Data Architecture. Frameworks. Metadata. Advanced Metadata Architecture. Data Security. Agile Database Techniques. Conclusion.

12. Thought Leadership.

Organizational Matrix. Outsourcing and Core Competencies. Strong Technical Leadership. Architects Stand the Test of Time. The Savage Pursuit of Best Practices. The Agile CIO. The Mysteries of Open Source. Consultant 101. Why...