Aspects of software development common mistakes

Common mistakes

• Ignoring the intended users

  Stating that requirements are decided only by the programmer or development team.

  Fix itExplain that requirements must be established through interaction with the intended users of the system.

• Treating design as only interface appearance

  Assuming that design means only planning the visual human user interface.

  Fix itRemember that design can also include the data model, algorithms, modular structure and clear documented interfaces.

• Treating test results as complete proof

  Claiming that a program is correct simply because it passes a small number of tests.

  Fix itUse test data as evidence, but also explain logically why the code follows the intended algorithm and acknowledge the role of debugging and feedback.

• Confusing boundary and erroneous data

  Describing a value at the permitted limit as erroneous simply because it is unusual.

  Fix itA value at an included limit is boundary data and should be valid. Erroneous data is outside the permitted conditions or otherwise invalid.

• Naming criteria without evidence

  Writing that a system is usable or reliable without explaining how this would be tested.

  Fix itLink each criterion to a test and state the evidence that would show success, such as user errors, response times or repeated correct results.