Software Engineering Principles and Practices

This book consists of the chapters describing novel approaches to integrating fault tolerance into software development process. They cover a wide range of topics focusing on fault tolerance during the different phases of the software development, software engineering techniques for verification and validation of fault tolerance means, and languages for supporting fault tolerance specification and implementation. Accordingly, the book is structured into the following three parts: Part A: Fault tolerance engineering: from requirements to code; Part B: Verification and validation of fault tolerant systems; Part C: Languages and Tools for engineering fault tolerant systems.

In 1974, Donald Knuth wrote, "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." With computers available now that are millions of times faster than those available then, today's programmers have even less reason to worry about shaving cycles and saving bytes than those a generation ago. But "less" isn't "none": every once in a while, squeezing the last ounce of performance out of the machine really does matter.

Cooperation between the business and IT is governed by two harmful stereotypes: IT claims that in the business they do not know what they want, while the business is convinced that IT does not think with a business mindset. Sometimes, we entrench ourselves in these positions to such an extent that we are unable to find a thread of understanding, which is necessary to develop valuable software.

Software Innovation: eight work-style heuristics for creative system developers.

Addressing general readers as well as software practitioners, this book discusses the fallacies of the mechanistic ideology and the degradation of minds caused by these fallacies. Mechanism holds that every aspect of the world can be represented as a simple hierarchical structure of entities. But, while useful in fields like mathematics and manufacturing, this idea is generally worthless, because most aspects of the world are too complex to be reduced to simple structures.

Software engineering is the art and science of using different methods to efficiently create extensible, sustainable programs that solve problems people care about.

This book contains 46 essays originally published on the Hacknot web site between 2003 and 2006. The version of each essay appearing in the book is substantially the same as the online version, with some minor revisions and editing.

This book provides an introduction to Formal Verification methods. This book was written as a way to dip a toe in formal waters. You may be curious about formal verification, but you’re not yet sure it is right for your needs.

Tap into the wisdom of experts to learn what every programmer should know, no matter what language you use. With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice.

All software design is composition: the act of breaking complex problems down into smaller problems and composing those solutions. Most developers have a limited understanding of compositional techniques. It's time for that to change.

With this practical book, you'll learn 10 easy-to-follow guidelines for delivering Java software that’s easy to maintain and adapt. These guidelines have been derived from analyzing hundreds of real-world systems.

This open access book improves the users' skills needed to implement models for performance evaluation of digital infrastructures with simulation and analytical techniques from the open source Java Modelling Tools (JMT).