Are you measuring technical debt
Are you suffering from low developer productivity

If you cannot answer these questions, this ebook is written for you! Within 90 pages you will understand the most important software quality concepts.

Learn about controlling and monitoring software quality through an analogy, no matter your background
Consider the job of a general practitioner (GP). That person needs to know quite a bit about the human body. The human body can also be compared to a system with inputs (e.g., eating), processing (e.g., functioning of heart) and outputs (sweat). To assess the health of a human system the GP uses key performance indicators (KPI's), such as: heartbeat and temperature. These KPI's enable the GP to quickly detee whether and what kind of follow up action is necessary. After reading this ebook you'll understand the KPI's to assess a software system. It goes without saying that this example is a gross simplification of reality.

This ebook covers the 8 essential software quality conceptsneeded to excel. Learning the most important concepts does not have to be hard. Learning and thus uncovering your blind spots is the first step. The 8 essential concepts are:

1. lines of code,
2. duplication,
3. unit size,
4. unit complexity,
5. unit interfacing,
6. module coupling,
7. component balance,
8. component independence.
So, after reading this ebook you'll be able to challenge or assess the 'software health' of a application on a fine-grained level based on these 8 essential concepts.

Can you explain these concepts without showing code
Yes. The concepts are technology independent and are explained by making use of analogies. The software metrics are technology independent. This means that it does not matter whether you write Python, C#, C, Ruby, Java, javascript, TypeScript, Visual Basic, R, PHP, Cobol, Prolog, Go, Swift, Kotlin, Scala, Haskell or Ada. The metrics are independent because they are based on the programming language's characteristics. For instance, for almost all technologies you can measure the 'Lines of code' and duplication.

Why should I buy this book
Only buy when you are new to software quality and want a complete bners' perspective. This ebook is specifically developed for
- Software architects that care about the 'health' of the system. Collectively, the 8 KPI's give you a perspective to measure software health;
- Product owners / project managers / software managers / architecture assurance managers that build software systems, but have no clue how software eeers could write high quality code that improves software architecture;
- Anyone interested in the basics of software quality, explained in layman's terms;

BONUS Material
- Additional reading for managers;
- Additional reading for developers;
- Overview of software quality tools for software testing, quality assurance and /or performance testing.

I'm fully convinced of the benefits, but I don't see why I should learn all this from you.
True, let me explain by giving you an overview of my experience
- (Chief) Information Security Officer. Managing a team of Security, Privacy and Architecture professionals. Responsible for implementing and maintaining a well-balanced organisational risk posture;
- Part researcher. I read the science; you'll get the knowledge! What more do you want
- Software quality consultant. I've advised many managers of large / small IT projects on various software related aspects;
- Quality assurance eeer. I have implemented large IT systems for large companies.



DOWNLOAD
1dl.net


https://1dl.net/gn1n66p82fep/FjvVPxQQ_.B0BGSJN54C.rar.html



uploadgig.com


https://uploadgig.com/file/download/83b0014E8bDffB66/FjvVPxQQ_.B0BGSJN54C.rar



rapidgator.net


https://rapidgator.net/file/cb55d27087c8060b5e856832f023d845/FjvVPxQQ_.B0BGSJN54C.rar.html