Strategies For Software Engineering

An immensely practical resource for professionals in the software industry, this text offers a simple but effective decision-making approach to planning and managing all types of software engineering projects. The book establishes a constructive framework for selecting a development strategy, development methods, and support tools with the ultimate goal of minimizing technical risk and increasing product quality. Specific topics include the range of quality attributes (fitness for purpose, fitness for use, and timely delivery), standards for quality management systems, the work breakdown structure, and the use of metrics and indicators. The book closes with a discussion of the 14 dilemmas of software engineering--and how to break them.

The pervasiveness of software in business makes it crucial that software engineers and developers understand how software development impacts an entire organization. Strategic Software Engineering: An Interdisciplinary Approach presents software engineering as a strategic, business-oriented, interdisciplinary endeavor, rather than simply a technica

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions

- Helps managers combat the manufacturing mindset that dominates business thinking, and shows why this mindset is harmful to software development - Introduces predictability to the historically unpredictable world of software development - Allows organizations to improve job satisfaction by fostering an environment of creativity among developers

This book constitutes the proceedings of the 5th European Software Engineering Conference, ESEC '95, held in Sitges near Barcelona, Spain, in September 1995. The ESEC conferences are the premier European platform for the discussion of academic research and industrial use of software engineering technology. The 29 revised full papers were carefully selected from more than 150 submissions and address all current aspects of relevance. Among the topics covered are business process (re-)engineering, real-time, software metrics, concurrency, version and configuration management, formal methods, design process, program analysis, software quality, and object-oriented software development.