SAFE SOFTWARE: THE BOOK!

HOW TO DEVELOP SAFE AND STABLE SOFTWARE IN A EFFICIENT , REPEATABLE AND ECONOMIC WAY

TRANSFORM SOFTWARE DEVELOPMENT FROM RISK AND COST, TO STRATEGIC COMPETITIVE ADVANTAGE . EVEN IF YOU DO NOT HAVE SPECIFIC EXPERIENCE .

Learn how to apply scientific and engineered methods typical of large aerospace companies and adapted to medium-small companies where the programming team is limited to groups even from just 1 person or more, reducing costs and risks and helping to arrive first on the market with a more stable product

To get a copy, please send an email to:

book@safer-software.com

or fill this form:

HAVE YOU EVER DELIVERED A THEME, AN ARTICLE, A BOOK WITHOUT REREADING IT?

OR YOU HAVE EVER PRINTED IT AS IT WAS, HOPING THAT THE READER OR THE PROFESSOR WILL FIND YOUR ERRORS FOR YOU?

IF YOU REREAD IT: HOW OFTEN DO YOU DO IT?

Normally when you write something important, what you do: you wait to have written 300 pages to give a rereading? Or 50? Obviously the answer is the same for everyone: NO.

This is an example that I often give my clients about the theoretical and practical importance of software testing.

Writing software is like writing a book: especially when it comes to rereading it

Let’s take a student, a professional from another field, a journalist, a writer. We can take ourselves as an example, because in life, starting from school desks, we wrote something: when we reread what we wrote?

Well, depending on what we do when we write, without knowing it and even without ever writing a line of code in our life, we have already done a “test”:

Read More

“We are late because of the software”

“We should adopt a new development process but we do not have the time”

“A very interesting tool but there is no budget, I’m sorry”

“Our software development method is very artisanal”

“We do not have time to test because we have to sell the product”

“The test is boring and expensive, we have to cut the times”

“We want to stay focused on our core business”

“We have to recall 10,000 units from the market for a problem”

“Some people are hurting themselves using our device”

“The relatives of our customers who were victims of accidents with our vehicles got organized into a class-action”

If any of these phrases is known to you because happened your company or in that of your competitor, or if just hearing it makes you feel a cold shiver: then this article is for you.

I have been working in the software development sector for over 25 years and I have covered a long series of responsibilities, roles and tasks related to the software life cycle, in various fields: from developer to manager, from modelling to testing, from employee to freelance, from management software to aerospace software, from the safety-critical to the business-critical software.

For years I was forced to fight against all the problems related to software development: delays, misunderstandings, bugs, complaints from customers, managers.

Well, do you know what impressed me in all these years of international experience?

The feeling of powerlessness in seeing how software, although omnipresent in every aspect of our lives, is actually a completely underestimated, underestimated and mistreated discipline but of absolute and ever-increasing importance and above all danger.

Read More