Even Working Super-Well , Your Software Is Bad

Anas AlnaggarAnas Alnaggar
2 min read

Table of contents

  • This is a very confusing truth, after working on your software regarding gathered requirements and main functionalities if your customer is not completely satisfied I'm sorry to tell you that your software is bad.

  • Gathering requirements from the customer is not an easy task, you must go beyond what he said in requirements gathering, simply because the customer himself may not know properly about what he wants.

  • Catching this idea through reading head first object oriented analysis and design book(Highly Recommended), ch.2 which talks about making a smart dog door for Todd and Gina and making a logical scenario to a remote control so once the dog barks to go away you can press the remote control button to open the door but even of this good logic, there's a huge problem!

  • The problem is all about getting other pets (Dog's friends) inside the home that's because either todd or gina forget to close the door by pressing the remote button again to close it, so in this current case, your software is not working well at all even you did all your picked requirements very well.

  • The simple straightforward solution is to meet with your customers for a second time to pick a refined-requirements, this time you must go beyond the customer's requirements to do this properly.

  • Finally in my opinion, to get requirements in a good way is to read well about the user requirements phase through books, articles etc.. and to listen more and more about real-life use cases to try to avoid all of these situations in your future work, good luck!

11
Subscribe to my newsletter

Read articles from Anas Alnaggar directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Anas Alnaggar
Anas Alnaggar