Predrag Skoković, Marija Rakić-Skoković FULL TEXT ARTICLE (PDF)
In many organizations, testing, regarded as quality verification, begins only once code has been completed. However, errors found in requirements are the leading cause of project failures, defects and rework. Even though many companies use some method of requirements management and some form of software quality testing, most of them cannot (or do not) link them together. While searching for an application lifecycle management (ALM) methodology that might give us an answer to these problems, Requirements-Based Testing (RBT) emerged as a possible solution. RBT provides a set of quality assurance activities and management tools that enable getting requirements right from the outset. This paper presents lessons learned while introducing requirements-based testing methodology, in order to put the project in control and deliver applications on time.
ARTICLE INFOKey words: open innovation, open evaluation, crowdfunding Article history: Received (10.07.2010); Revised (19.09.2010); Accepted (30.09.2010) Number of downloads (since May 2017):