Computer Module Essay Example | Topics and Well Written Essays - 750 words

Computer Module - Essay Example The question being asked is what constitutes the defining paradigms of quality in the phase of conflicting perceptions in the IT industry. It is against this background that the central focus of this paper is tailored towards highlighting the most classical principles that are in tune with best practices in the industry. For obvious reasons, it spares the paper the drudgery of professing speculative theories. The conventional structure of software language has always being targeted at making available a system of unambiguous programming pattern based on logical processes that are explicit in their usage.1 In a related study, Jagdish et la (2002) allude to the fact that the continuous dependence on computer software for the execution of virtually all industrial, commercial and social activities makes it imperative for the question of quality to be ranked very highly in the process of developing software-a fact that has gained unanimous support from all concerned stakeholders. Notwithstanding the consensus held about the latter, the point of division however, lies in the inability to establish a similar consensus in establishing a standardized definition of what the term "quality" really means when it comes to software technology. Its definition is always crafted to suit a specific purpose, in other words, depending on what the software in question will be used for, then an appropriation o f quality is assigned to it (Boehm 1978, Vincent et la 1998, Sefikla et la 1998). To ease this complication, Jagdish et la (2002) recommends the usage of the object-oriented paradigm to replace the conventional systems of conducting any meaningful software quality assessment (also see Li & Henry 1993). Object-oriented metrics approach is a representation of an entirely innovative system of that is able to handle a comparatively larger aggregate array of tasks than was hitherto possible. Notwithstanding, it is woefully saddled in a limitation of the magnitude and scope of the tasks it can be used to assess. Primarily, the obvious reasons are that all that is known about it and application is still in its infancy. For instance, it is known to lack the capacity to fully integrate a small quantity of discrete data, which may be terribly below the high expectations placed on quality assessment in a large scale context (Schmidt et la 2000, Brian et la 1996, Sefikla et la 1996). In another interesting study, Schmidt (2000) is not particularly enthused about the fact that prior to the implementation of the object-oriented metrics, there is no mechanism that enables any credible quality assessment check to be conducted on it during the development process. Essentially, any quality alterations that the software might stand in need of, would certainly have to be deferred until such a time that user feedback is generated. A significant amount of effort is required to get the object-oriented metrics running effectively during the early stages of the development process. Granted all the working dynamics are systemically synchronized then, much of the testing process will ensure a smooth performance of the software. Quality Appraisal In view of the limitations inherently