Once the software starts losing its value and quality in the environment, it is deemed to be shifting into the ageing phase of its lifecycle. The quality of the software can be determined at any point in its lifecycle and therefore this can assist experts and developers to check the deterioration in the value and quality of the software. Data concerning certification and quality from 2007 until 2011 was analysed and has revealed that software measurements can be used to constantly observe quality. Our software certification model pays more attention to the participation of users in the assessment process. Journal of Software and Systems Development This model uses PQF model as its standard of quality certification. Earlier studies conducted by us concerning software product certification applications have proven that SCM-Prod model, which uses the product quality method for software certification, is suitable for maintaining the quality of the product during its lifecycle (Yahaya, Deraman & Hamdan, 2008 2010). The above mentioned studies are mainly aimed at validating software items from the viewpoint of developers, dealers and examiners and pay little attention to the viewpoint and participation of the users. Such models are appropriate for the normal evaluation of software with constant features such as portability, usability, dependability, maintainability, practicality and competence. Some examples of this method are the Good Software mentioned in the IT Times, the Requirement-driven Workbench and the SCM-Prod (IT Times, 2011 Lee, Ghandi & Wagle, 2007 Yahaya, Deraman & Hamdan, 2008). Another method involves measuring quality against the ISO9126 model (Lee, Ghandi, & Wagle, 2007 Welzel & Hausen, 1997 Heck et al., 2010). Most of the software certification methods depend mainly on official validation, professional and developer evaluations, and software measurements to ascertain the quality of an item. The IT Times (2011) referred to Good Software as a quality certification programme designed by the Koreans and which has been in use over the past ten years. This is the latest software engineering theory which is fast gaining recognition in the software industry. Stanfford and Wallnau (2001) also share the same view of certification as a procedure whereby the value given to a particular asset is validated by the issuance of a certificate which can be produced as evidence of its authenticity. A software certification as a fact sheet presenting the proven external behaviours of the software (and possibly proven internal behaviours as well) (Voas, 1999). person or organisation, and this value is validated by the issuance of a certificate, which can be produced as evidence of its authenticity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |