The quality of the software product is a crucial factor that contributes to its success. Therefore, it\nis important to specify the right software quality requirements that will establish the basis for\ndesired quality of the final system/software product. There are several known methodologies/\nprocesses that support the specification of the system/software functional requirements starting\nfrom the user needs to finally obtain the system requirements that the developers can implement\nthrough their development process. System/software quality requirements are interdependent\nwith functional requirements, which means that the system/software quality requirements are\nmeant to be specified in parallel with the latter. The ISO/IEC 25000 [1] SQuaRE series of standards\ninclude the standard ISO/IEC 25030ââ?¬â?Software engineeringââ?¬â?Software Quality Requirements and\nEvaluationââ?¬â?Quality requirements [2], which has as main goal to help specify software quality\nrequirements. As to date, this standard does not offer clear and concise steps that a software\nquality engineer could follow in order to specify them. This article presents modifications recommended\nfor ISO/IEC 25030 standard, with, among the others, a new requirements definition process\nthat allows for specifying the system/software quality requirements taking into account the\nexisting published system and software quality model ISO/IEC 25010 [3] as well as all the stakeholders\nof the project.
Loading....