Member-only story

Get It Right Then Keep It Right: Building Better Software, Better

Alfred Ross

·2.6k Followers· Follow

Published in Software Quality Assurance: Get It Right Then Keep It Right (Building Better Software Better 2)

4 min read · 1 month before

45 View Claps

7 Respond

Save

Listen

In today's fast-paced and ever-changing world, software systems are more important than ever before. They are essential for businesses of all sizes, and they play a vital role in our personal lives. However, developing and maintaining high-quality software systems is a complex and challenging task.

Software Quality Assurance: Get it right then Keep it right (Building Better Software Better 2)

Software Quality Assurance: Get it right then Keep it right (Building Better Software Better Book 2)

by David B. Black

4.1 out of 5

Language	:	English
File size	:	657 KB
Text-to-Speech	:	Enabled
Enhanced typesetting	:	Enabled
Print length	:	114 pages
Lending	:	Enabled
Screen Reader	:	Supported

In their book 'Get It Right Then Keep It Right: Building Better Software, Better', Tom DeMarco and Tim Lister provide a comprehensive guide to developing and maintaining software systems that are both effective and efficient. This book is a must-read for anyone who is serious about building better software.

Getting the Requirements Right

The first step in developing any software system is to get the requirements right. This means understanding what the system is supposed to do and how it is supposed to work. It is essential to involve the users in this process, as they are the ones who will ultimately be using the system.

DeMarco and Lister recommend using a variety of techniques to gather and document requirements, such as interviews, workshops, and prototyping. It is also important to prioritize the requirements, so that the most important ones are addressed first.

Designing the System Correctly

Once the requirements have been gathered and documented, the next step is to design the system. This involves creating a blueprint for the system, which specifies how it will be structured and how it will function.

DeMarco and Lister emphasize the importance of using sound design principles, such as modularity, cohesion, and coupling. They also recommend using a variety of design tools, such as UML diagrams and object-oriented analysis and design techniques.

Implementing the Software Effectively

Once the system has been designed, the next step is to implement the software. This involves coding the system and testing it to ensure that it meets the requirements.

DeMarco and Lister recommend using a variety of implementation techniques, such as test-driven development, agile development, and continuous integration. They also emphasize the importance of using a version control system to track changes to the code.

Maintaining the Software

Once the software has been implemented, it is important to maintain it over time. This involves fixing bugs, adding new features, and upgrading the software to new versions.

DeMarco and Lister recommend using a variety of maintenance techniques, such as preventive maintenance, corrective maintenance, and perfective maintenance. They also emphasize the importance of having a well-defined maintenance plan.

'Get It Right Then Keep It Right: Building Better Software, Better' is a comprehensive guide to developing and maintaining high-quality software systems. This book is a must-read for anyone who is serious about building better software.

By following the principles outlined in this book, you can improve the quality of your software systems and ensure that they continue to meet the needs of your users.

Software Quality Assurance: Get it right then Keep it right (Building Better Software Better Book 2)

by David B. Black

4.1 out of 5