- “My Way.” I often get into a situation where I am going to create a new document by editing a copy of an existing document. When in this situation, the first thing I do is open the existing document in my editor and perform a “save as” to a new name for the new document. The need here is to not overwrite the existing document with the edits. Knowing that along with all of my wonderful strengths, I am also absent-minded, I save the file under a new name first, so that I won’t absent-mindedly save my edits to the existing file. People who are not absent-minded like me don’t need a procedure that guards against this problem. They know they will rename before they save (I don’t really know how they accomplish this, but I’ve seen them—they do!).
- “The Way.” The general rule of defect reporting is one defect per defect record. The purpose is clear resolution of defects. Each defect is typically prioritized, fixed, and re-tested. Some are resubmitted because they fail re-test. Some have even more states they go through. If there are multiple defects in a record, tracking and determining the prioritizations and states of the defects becomes time consuming and confusing. It is much easier to have priority and status fields which apply to the defect record. Thus, the best practice is one defect per defect record.
Learn how to tie software requirements together with visual models and other artifacts created during the analysis process.