You may have to Search all our reviewed books and magazines, click the sign up button below to create a free account.
“Don’s book is a very good addition both to the testing literature and to the literature on quality assurance and software engineering... . [It] is likely to become a standard for test training as well as a good reference for professional testers and developers. I would also recommend this book as background material for negotiating outsourced software contracts. I often work as an expert witness in litigation for software with very poor quality, and this book might well reduce or eliminate these lawsuits....” –Capers Jones, VP and CTO, Namcook Analytics LLC Software and system testers repeatedly fall victim to the same pitfalls. Think of them as “anti-patterns”: mistakes that ma...
Offering a practical way to generate effective and efficient project-specific system architecture engineering methods, this volume addresses the entire range of systems architecture including hardware, software, subsystems, and systems of systems. It defines a set of architectural roles and teams and provides a repository of reusable architectural engineering process components to develop high-quality system architectures. It examines a cohesive set of tailorable tasks and components steps for producing associated architectural work products and establishes a recommended set of industry best practices for engineering the architecture of software-intensive systems.
"[The authors] have done an excellent job of bringing forth the power and the flexibility of this most useful framework in an easy to read and understand introduction. Although it has been written to be an introductory text in OPF, I found [it] also readily useable as a handbook for initial process definition, an accessible treatment of important issues in software process design, and a textbook in OPF." Houman Younessi Associate Professor of Computer Science, Rensselaer Polytechnic Institute The OPEN Process Framework provides a template for generating flexible, yet disciplined, processes for developing high-quality software and system applications within a predictable schedule and budget. Using this framework as a starting point, you can create and tailor a process to meet the specific needs of the project.
Using a rigorous, technical approach, it is written by a leader in the field who has developed his own object-oriented design techniques. Covers object-oriented design of software from requirements analysis to design, principles that can be applied for all types of software ranging from large to extremely complex to real time systems. The methods discussed can be used with either object-oriented or object-based language. Contains a copious amount of practical examples.
The Elements of Java Style, written by renowned author Scott Ambler, Rogue Wave Software Vice President Alan Vermeulen, and a team of programmers from Rogue Wave, is for anyone who writes Java code. While there are many books that explain the syntax and basic use of Java, this book, first published in 2000, explains not just what you can do with the syntax, but what you ought to do. Just as Strunk and White's The Elements of Style provides rules of usage for the English language, this book provides a set of rules for Java practitioners to follow. While illustrating these rules with parallel examples of correct and incorrect usage, the book provides a collection of standards, conventions, and guidelines for writing solid Java code which will be easy to understand, maintain, and enhance. Anyone who writes Java code or plans to should have this book next to their computer.
Martin Fowler is a consultant specializing in object-oriented analysis and design. This book presents and discusses a number of object models derived from various problem domains. All patterns and models presented have been derived from the author's own consulting work and are based on real business cases.
It was only an old book that the professor found while traveling by train through Scotland. A scholar of medieval history, Professor George Smith was on sabbatical studying Scottish legends and myths when he chanced to meet an aged Scotsman and his granddaughter on their way to her new boarding school in the Isles of Skye. The young girl had accidentally left her book behind, and the professor picked it up meaning to send it on to her. But then he looked inside and discovered it was no ordinary book. It was a school textbook on magic. Could it be real? Could it have actually been left by accident and found by chance? Or was it all an elaborate hoax played on the unsuspecting professor? Did h...
With over 3,000 main entries and over 600 pages, this book is the only reference of its kind dedicated to the terminology used in the object technology field.
Software Project Secrets: Why Software Projects Fail offers a new path to success in the software industry. This book reaches out to managers, developers, and customers who use industry-standard methodologies, but whose projects still struggle to succeed. Author George Stepanek analyzes the project management methodology itself, a critical factor that has thus far been overlooked. He explains why it creates problems for software development projects and begins by describing 12 ways in which software projects are different from other kinds of projects. He also analyzes the project management body of knowledge to discover 10 hidden assumptions that are invalid in the context of software projects.
This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes ca...