A Practical Guide to Enterprise Architecture |
By James McGovern, Scott W. Ambler, Michael E. Stevens, James Linn, Vikas Sharan, Elias K. Jo |
| |
Publisher | : Prentice Hall PTR |
Pub Date | : October 28, 2003 |
ISBN | : 0-13-141275-2 |
Pages | : 336 |
| | Copyright |
| | The Coad Series |
| | | About the Series |
| | | About the Series Editor |
|
| | WWW.WWISA.ORG |
| | About Prentice Hall Professional Technical Reference |
| | Acknowledgments |
| | | James McGovern |
| | | Scott W. Ambler |
| | | Michael E. Stevens |
| | | James Linn |
| | | Vikas Sharan |
| | | Elias K. Jo |
|
| | Foreword |
| | | The Burning Need for Architecture |
| | | The Urgent Need for Tools |
| | | The Pressing Need for Appropriate Organization |
| | | Why This Book Is Important |
|
| | Preface |
| | | Why Enterprise Architecture? |
| | | Building an Enterprise Architecture |
| | | About This Book |
| | | Content of This Book |
| | | Disclaimer |
| | | In Summary |
|
| | Chapter 1. Systems Architecture |
| | | Canaxia Brings an Architect on Board |
| | | Network Protocols |
| | | Conclusion |
|
| | Chapter 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 |
|
| | Chapter 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 |
|
| | Chapter 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 |
|
| | Chapter 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 |
|
| | Chapter 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 |
|
| | Chapter 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 |
|
| | Chapter 8. Agile Modeling |
| | | The Goals of Agile Modeling |
| | | Agile Models |
| | | Agile Documents |
| | | Conclusion |
|
| | Chapter 9. Presentation Tier Architecture |
| | | Business Needs and Presentation Requirements |
| | | Key Presentation Tier Components |
| | | General Design Recommendations |
| | | Design Guidelines for Interface Components |
| | | Conclusion |
|
| | Chapter 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 |
|
| | Chapter 11. Data Architecture |
| | | The Business Problem |
| | | Baseline Data Architecture |
| | | Frameworks |
| | | Metadata |
| | | Advanced Metadata Architecture |
| | | Data Security |
| | | Agile Database Techniques |
| | | Establish an Infrastructure That Allows for Rapid Changes in Business Requirements and Database Technologies |
| | | Data That Need to Be Shared and Current Should Be Centralized |
| | | Avoid Monolithic Database Designs |
| | | Use Access Rules to Protect Data |
| | | Data Validation Should Occur at Multiple Tiers within an N-Tier Architecture |
| | | Data Should Be Replicated Based on Business Requirements and Only When Necessary |
| | | Replicated Data Should Be Read-only |
| | | The Replication Topology Implementation Should Meet Existing Business Needs |
| | | Transparency of Location of Data by Accessing Applications Should Be Encouraged |
| | | Implement Tools, Processes, and Policies to Ensure Data Integrity |
| | | When Designing a Database for Performance, It Should Include the Total Performance and Not Just Local Performance |
| | | Prefer Open Standards to Proprietary Extensions |
| | | Protect Credit Card Information Using Encryption |
| | | Conclusion |
|
| | Chapter 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 I Should Be a CIO |
| | | The Next Minute |
| | | Conclusion |
|
| | Appendix A. Business Case |
| | Appendix B. Practical Considerations |
| | Appendix C. The Seven Habits of an Agile Enterprise Architecture |
| | Appendix D. Models |
| | Appendix E. References |
| | Appendix F. Additional Reading |
| | Appendix G. Future Books |
| | About the Authors |