One of the most important parts of any software development project is creating detailed, accurate requirements. Without a clear understanding of what needs to be built, it's impossible to create a high-quality end product. Unfortunately, writing good requirements is often easier said than done. The primary reason that people write poor requirements is that they have had no training or experience in writing good requirements. If you or your staff have problems with writing good requirements, you may benefit from guidance in how to write good requirements. The college courses you took probably never mentioned the subject of requirements. Even if you have taken classes in system engineering or program management, you may have had only an introduction to the subject of writing requirements. If you are using existing specifications for guidance, you may be using poor examples. By taking the time to learn how to write better requirements, you can improve the overall quality of your software development projects - and save yourself a lot of headaches down the road.