<span>Itβs a jungle out there.<br>Delivering software solutions with predictable costs, time, scope, and quality has become more complicated than ever. Developers need to account for multiple moving targets, including often avoided but always relevant factors such as culture, people, and leadership.
Metrics-driven enterprise software development : effectively meeting evolving business needs
β Scribed by Datta, Subhajit
- Publisher
- J. Ross Publishing
- Year
- 2007
- Tongue
- English
- Leaves
- 305
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
...a commendable contribution toward advancing the theory and practice of software engineering. Taking a cut across the software engineering life cycle and brilliantly juxtaposing know-how and show-how, Metrics-Driven Enterprise Software Development is a fine source of guidance on the use of metrics in enterprise software development for developers and managers alike.
--Deependra Moitra, Venture Catalyst and Management Consultant; Former Associate Vice President & General Manager, Infosys Technologies Limited
Metrics-Driven Enterprise Software Development is honest, informative and even funny in the right places without diluting the topic. The introduction of this book is beautifully crafted. It made me want to read more a rare accomplishment for a technical book.
--Shovon Mukherjee, Partner, GBS, IBM Global Services
This practical reference discusses why essential processes so often fail to deliver quality industrial software to meet user needs. It describes how to integrate processes and metrics to ensure easier and more effective enterprise software development. Its metrics-driven approach guides practitioners at every step of the life cycle and helps them analyze, design, implement, test and deploy solutions with greater confidence, purpose and sensitivity to evolving business needs.
KEY FEATURES --Presents insights and strategies for formulating metrics in software development activities and clarifies them in the context of iterative and incremental development methodologies
--Introduces techniques for building, applying and interpreting metrics for the workflows across the software development life cycle phases of inception, elaboration, construction and transition
--Highlights rigor vs. expediency trade-offs in the design and use of metrics, and suggests discovery vs. invention strategies for leveraging the correct metric
--Offers a free downloadable metrics-driven software development presentation and a quick reference glossary of important metrics -- available from the Web Added Value Download Resource Center at www.jrosspub.com
β¦ Table of Contents
Content: pt. 1. Context --
pt. 2. Constructs --
pt. 3. Case study.
π SIMILAR VOLUMES
<span>Itβs a jungle out there.<br>Delivering software solutions with predictable costs, time, scope, and quality has become more complicated than ever. Developers need to account for multiple moving targets, including often avoided but always relevant factors such as culture, people, and leadership.
<div><p><b>Summary</b></p> <p><i>Software Development Metrics</i> is a handbook for anyone who needs to track and guide software development and delivery at the team level, such as project managers and team leads. New development practices, including "agile" methodologies like Scrum, have redefined
<div><p><b>Summary</b></p> <p><i>Software Development Metrics</i> is a handbook for anyone who needs to track and guide software development and delivery at the team level, such as project managers and team leads. New development practices, including "agile" methodologies like Scrum, have redefined
<div><p><b>Summary</b></p> <p><i>Software Development Metrics</i> is a handbook for anyone who needs to track and guide software development and delivery at the team level, such as project managers and team leads. New development practices, including "agile" methodologies like Scrum, have redefined
<p><i>Software Engineering: Architecture-driven Software Development</i> is the first comprehensive guide to the underlying skills embodied in the IEEE's Software Engineering Body of Knowledge (SWEBOK) standard. Standards expert Richard Schmidt explains the traditional software engineering practices