A Practical Guide to Enterprise Architecture; James McGovern, Scott W Ambler, Michael E Stevens, James Linn, Vikas Sharan; 2003

A Practical Guide to Enterprise Architecture Upplaga 1

av James McGovern, Scott W Ambler, Michael E Stevens, James Linn, Vikas Sharan
Acknowledgments.

Foreword.

Preface.

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 I Should Be a CIO. The Next Minute. Conclusion.

Appendix A.

Appendix B.

Appendix C.

Appendix D.

Appendix E.

Appendix F.

Appendix G.

About the Authors.

Index.
Acknowledgments.

Foreword.

Preface.

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 I Should Be a CIO. The Next Minute. Conclusion.

Appendix A.

Appendix B.

Appendix C.

Appendix D.

Appendix E.

Appendix F.

Appendix G.

About the Authors.

Index.
Upplaga: 1a upplagan
Utgiven: 2003
ISBN: 9780131412750
Förlag: PRENTICE-HALL
Format: Häftad
Språk: Engelska
Sidor: 336 st
Acknowledgments.

Foreword.

Preface.

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 I Should Be a CIO. The Next Minute. Conclusion.

Appendix A.

Appendix B.

Appendix C.

Appendix D.

Appendix E.

Appendix F.

Appendix G.

About the Authors.

Index.
Acknowledgments.

Foreword.

Preface.

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 I Should Be a CIO. The Next Minute. Conclusion.

Appendix A.

Appendix B.

Appendix C.

Appendix D.

Appendix E.

Appendix F.

Appendix G.

About the Authors.

Index.
Begagnad bok (0 st)

Om A Practical Guide to Enterprise Architecture (2003)

I november 2003 släpptes boken A Practical Guide to Enterprise Architecture skriven av James McGovern, Scott W Ambler, Michael E Stevens, James Linn, Vikas Sharan. Det är den 1a upplagan av kursboken. Den är skriven på engelska och består av 336 sidor djupgående information om övrigt. Förlaget bakom boken är PRENTICE-HALL.

Köp boken A Practical Guide to Enterprise Architecture direkt från en annan student på Studentapan och spara pengar.

KurslitteraturÖvrigtÖvrigtA Practical Guide to Enterprise Architecture
Bokens omdömen
Ingen har recenserat den här boken ännu.

Sälj vidare boken när du är klar

När du är klar med boken säljer du enkelt vidare och tjänar pengar på nolltid med Studentapan. Vi tar hand om allt det krångliga så att du får mer tid över till annat. På det sättet kan du tjäna tillbaka det mesta av kostnaden för boken.
Värdera & sälj böcker

Klimatsmart kurslitteratur

Bli en miljöhjälte under din studietid och ge dina gamla kursböcker ett nytt liv. Genom att återanvända dina kursböcker minskar du utsläppen av koldioxid (CO2) med hela 59%. För en psykologstudent skulle det innebära minskade CO2-utsläpp med cirka 240 kg under studietiden. En stor vinst för din plånbok och miljön. Det kallar vi klimatsmart kurslitteratur.

Liknande kurslitteratur

Begagnad bok (0 st)