Manage the software defect process - ocawley/ittsqa04 GitHub Wiki

lab 1 – x00064688 – 16-09-2014

Manage the software defect process

There are few software defect in the market that are made specially to fight against defects. Those software can be expensive, not to say that the cost of finding and correct defects can be most expensive software development activities. As time pass it will get harder to detect software defect so development teams need to implement a defect management process that focus on preventing defect for future use and, also catching defects in early process as possible and to minimize the impact of defect for the future. This defect management model is not used to be a standard, but in fact a starting point for the development of a customized defect management process in an organization. Companies using the model can reduce defects and their impacts during their software development projects. The defect software must be easy and simple for users to be able to use it, but making sure that the information founded should be enough to reproduce the defect and allow development to determine the root that cause the defect. Once the defect has be found the team needs to create a report that actual defect and if the defect has already been reported then team, needs to have a better solution to solve the defect. If is need team need to implement some changes in order to fixed the defect, and also is needed to document the details of the solution that was founded.. This way all the team will know the solution and might also be useful for future. This process can be also time consuming , it can takes few minutes, in some case it can take hours depending on the defect outcome.

References: Website: 1995- 22014PTC Inc. available at: http://www.defectmanagement.com/defectmanagement/index.htm [accessed 16-09-2014] Website: http://www.mks.com/solutions/discipline/dm/defect-management [accessed 16-09-2014]