The Software Dilemma : Balancing Creativity and Control on the Path to Sustainable Software

Online-Ressource (XXI, 281p. 24 illus, digital)

Description based upon print version of record

The Software Dilemma; Balancing Creativity and Control on the Path to Sustainable Software; Foreword; Preface; Prolog; Contents; 1 Introduction; Software Development Everywhere; Creativity: The Driver Behind Software; Complexity: The Challenge in Software Development; Looking at Other Industries; Sustainable Software: Meeting Today´s Requirements; The Software Dilemma: Balance Governance and Empowerment; How This Book Can Help; Making Things Tangible: The Stories; References; 2 The World Has Changed; 2.1 The Need for Orientation; 2.2 Crisis: And the World Cries for Governance

2.2.1 A First Example from the Stock MarketRisk Awareness Becomes Emphasized When the Stock Price Crashes; 2.2.2 SOX as Result from Corporate and Accounting Scandals; A Pattern as Governance Evolves; 2.2.3 Insolvency of Lehman Brothers; Governance Is as Good as at Its Weakest Implementation; A Pattern of Governance for Weak Points; 2.2.4 Risk of Greece´s Insolvency; 2.3 Crises in Software Development; 2.3.1 Security as a Global Responsibility; 2.3.2 Manage Software Complexity; 2.3.3 The Software´s Patch Curse; 2.4 The Evolving Role of Software Architects

2.4.1 Role Enrichment #1: From Techie to Business Man2.4.2 Role Enrichment #2: Processes Are a New Area of Responsibility; 2.4.3 Role Enrichment #3: To Convince Management Is Key!; 2.4.4 Role Enrichment #4: Don´t Get Caught Up in Technology, Make Unbiased Judgments; 2.5 Governance to the Extreme: Proper and Effective Measures; 2.5.1 Govern What Is Essential; 2.5.2 Keep It Simple but Adequate; 2.5.3 Tackle the Risks; 2.5.4 Do You Know Your Weakest Points?; 2.5.5 Plan Process Improvements; 2.5.6 Correlation Between Efficiency and Effectiveness

2.5.7 Architecture Governance: Is There Still Room for Innovation?2.6 Summary; References; 3 Are You Connected: CIO, Architect, and Auditor?; 3.1 When Common Interests Collide; 3.2 Software Development: On the Radar Screen of Corporate Governance?; 3.2.1 Corporate Governance: A Closer Look; 3.2.1.1 Corporate Governance Principles; 3.2.2 Corporate Governance Meets Software Development; 3.3 From Corporate Governance to Effective Control; 3.4 Roles in Your Company; 3.5 Summary; References; 4 Building the Foundation; 4.1 The Usual Suspects: Lessons Learned from Reviews

4.1.1 Have You Selected the Right Experts?4.1.2 Can You Explain Your Mandate?; 4.1.3 Are You Aligned with Your Stakeholders?; 4.1.4 Stick to Your Topic: Just Look at the Architecture!; 4.1.5 Are You Supported by Management?; 4.1.6 Look Outside the Box, But Stay Focused!; 4.1.7 And He Turns and Was Forgotten; 4.1.8 And the CIO Had the Final Say; 4.2 The Basics: Never Start a Voyage Without a Plan; 4.2.1 Different Flavors of Architecture Reviews; 4.2.2 Some Definitions; 4.3 The Architecture Review Toolbox; 4.3.1 Set Objective; 4.3.2 Define Scope; 4.3.3 Identify Stakeholders

4.3.4 Align with Stakeholders

10.1007/978-3-642-27236-3 [DOI]

ECONIS - Online Catalogue of the ZBW