Skip to content
This repository was archived by the owner on Nov 3, 2025. It is now read-only.

Bad Practices & Good Practices in Software Development

gozdeberk edited this page Feb 23, 2016 · 2 revisions

Success or Failure

Most software projects fail but there are also successes. To be successful rather than fail, software developers should place importance on practices. Bad practices stem from the incomplete good practices. In other words, best practices address the root causes of poor software development.
Here is an outline of bad practices & good practices.

Bad Practices (Root Causes)

  • Ambiguous communication
  • Overwhelming complexity
  • Insufficient testing
  • Insufficient requirements management
  • Undetected inconsistencies among requirements, designs and implementations
  • Brittle architecture

Good Practices (Best Practices)

  • Develop iteratively
  • Manage requirements
  • Use component architecture
  • Model software visually
  • Verify quality
  • Control change

Resources:
[Resource - The University of Texas at Austin] (https://www.cs.utexas.edu/~mitra/csSummer2014/cs312/lectures/bestPractices.html)
Resource - IBM
Resource - University of North Florida

Clone this wiki locally