Software Design Defects Detection and Classification Literature review

Software Design Defects Detection and Classification - Literature review Example This essentially refers to â€Å"fitness for use†. On a detailed elucidation of quality, software design defects come into the picture. Quality software not only meets the full user requirements, but is also usable for the purpose it was designed( Du Bois, Verelst and Demeyer 2004). Given the software process as earlier mentioned morphs the information from one form to another, errors are likely to occur in any of the forms (user needs, design, code etc.) of the product. This paper focuses on the design of software and the relation to the overall product. Generally, it ties software quality management to the success of the software process. In a more specific perspective, realised by careful examination of the models and frameworks of the software process, the paper reviews the software design defects are detected. The models reviewed are an indispensable part of software development and as such, it is important to examine how they help â€Å"clean up† the software proc ess(Leszak, Perry and Stoll 2002). In addition, the paper classifies the software design defects â€Å"shortcomings† that stem from poor design of software. In software development, the writing of a defect free code is one of the major concerns. This concern is cuts across the e software development and object oriented programming community. ... The shortcoming of this approach was that the same defects would still be realised in another software process(Moha and Gueheneuc 2005). It is important to consider the uniqueness, of each piece of software. They are designed as artefacts and meant to serve the user needs adequately. However, the process – individuals, tools, methodology- followed are is the same. This aspect of software development shows that the defects in the process are likely to be repeated. Applying quality management â€Å"control† on the software process is being adopted as a guarantee to achieve software quality. Total quality management of the software design aims at continuously improving the quality of the end product( Kessentini, Sahraoui and Boukadoum 2011 ). Managing the software design by controlling the end product at the design stage is a technique to curve out the causes of defects. This technique adopts a set of practices throughout the software process and is aimed at consistently m eeting the end user needs. While focussing on the software design defects, it is important to note that poor customer requirements elicitation could contribute to poor design of the software (Moha 2007). The focus here is the practices of software management adopted to counter software defects and detect the defects. Most importantly, the main idea is using established processes to catch the software design defects. From this perspective, we are able to examine how total quality management – continuous management of the process – is effected using the design The development of code for software development is a practice that requires skill and experience, producing a design defect free code that does