A Practical Guide to Enterprise Architecture

av James McGovern, Scott W Ambler, Michael E Stevens, James Linn, Vikas Sharan. Häftad, 2003

Pris:  744:-
Skickas inom 2-5 vardagar.
Fri frakt inom Sverige för privatpersoner vid beställning på minst 99 kr!


Har du läst boken? Bli först att betygsätta och recensera boken .

  • Häftad (Paperback)
  • Språk: Engelska
  • Antal sidor: 336
  • Utg.datum: 2003-11-01
  • Upplaga: illustrated ed
  • Medarbetare: Ambler, Scott W. / Stevens, Michael E. / Linn, James / Sharan, Vikas / Jo, Elias K.
  • Illustrationer: illustrations
  • Dimensioner: 240 x 180 x 28 mm
  • Vikt: 640 g
  • Antal komponenter: 1
  • ISBN: 9780131412750

Bloggat om

Ö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...