English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Zendy Plus

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Zendy Tools

Zendy Open

It is well known fact that was phrased by famous quality scholar P.B. Crosbythat it is always cheaper to do the job right the first time. However, thisstatement must be reconsidered with respect to software development projects,because the concept of quality and associated costs measurements in softwareengineering discipline is not as matured as in manufacturing and other fieldsof the industry. Post delivery defects (i.e. software bugs) are very common andintegral part of software industry. While the process of measuring andclassifying quality cost components is visible, obvious and institutionalizedin manufacturing industry, it is still evolving in software industry. Inaddition to this, the recommendations of British standard BS-6143-2:1990 forclassifying quality-related costs into prevention costs, appraisal costs, andfailure costs have been successfully adopted by many industries, by identifyingthe activities carried out within each of these categories, and measuring thecosts connected with them, software industry has a long-way to go to have thesame level of adoption and institutionalization of cost of quality measurementsand visibility. Cost of Quality for software isn't the price of creating aquality software product or IT-service. It's actually the cost of NOT creatinga quality software product or IT-service. The chronic affliction of majority ofsoftware development projects that are frequently found bleeding with costoverruns, schedule slippage, scope creep and poor quality of deliverables inthe global IT industry, was the trigger for this research work. Lessons learntfrom this study offer valuable prescriptive guidance for small and mediumsoftware businesses, who can benefit from this study by applying the same fortheir quality improvement initiatives using CoQ-metric, to enhance thecapability and maturity of their SDLC-project performance.

Measuring Cost of Quality (CoQ) on SDLC Projects is Indispensible for Effective Software Quality Assurance