The Software Dilemma: Balancing Creativity and Control on the Path to Sustainable Software
Springer Science & Business Media, Mar 14, 2012 - Business & Economics - 282 pages
The complexity of software is continuously growing as a result of today’s interconnected business processes. Governance of architecture and technology strategy helps to ensure coherence of software and avoid excessive complexity. At the same time software development needs room for creativity and empowerment to provide solutions to business problems of increasing complexity. The book looks at this software dilemma from the perspectives of CIOs/CTOs, software architects, and auditors. Each of these groups has different interests which need to be considered, reconciled, and balanced. CIOs/CTOs are provided with the boundary conditions they have to establish assuring the achievement of strategic objectives. Architects and auditors find proven concepts for effectively assessing software projects and architectures, as well as for effectively communicating identified issues to responsible persons. The book is based on the author’s long experience in software engineering, governance, and auditing.
What people are saying - Write a review
We haven't found any reviews in the usual places.
2 The World Has Changed
3 Are You Connected CIO Architect and Auditor?
4 Building the Foundation
5 Orienteering Race Position Direction Go
6 The Software Sustainability Audit
7 Put a Frame Around Your Work
8 The Process Audit Not Just for the Auditor
Other editions - View all
achieve alignment approach architecture assessment architecture governance architecture review asked aspects audit framework audit objectives audit plan audit report audit team audited areas auditors Basel II business impact business objectives checklist CobIT communication company’s components concept conﬂict context of software core corporate govemance corresponding CSA process customer engagement deﬁned development teams Development View difﬁcult discussion effective efﬁcient ensure example execution expectations explain ﬁnal ﬁnancial ﬁnd ﬁrst ﬁt focus formal fulﬁll goals Greg guidelines Gutbrod identiﬁed implementation important inﬂuencing intemal audit interviews issues look non-functional requirements open source phase potential process audits processes and products product audits product owner product quality questions raw ﬁndings recommendations reﬂect relevant reuse risk exposure roles scope Sect situation software architect software audits software development processes software product Software Sustainability Audits speciﬁc stakeholders strategy sufﬁcient sustainable software topic transparency understand users