{'fraction_non_alphanumeric': 0.008285004142502071, 'fraction_numerical': 0.0, 'mean_word_length': 5.259067357512953, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
An Experimental Study on Effort Measurement for Evaluating Core Requirement in Product Release

The numerous number of requirements requires large amount of effort to arrange the core requirements for a particular product release properly. Therefore we need a potential method to sequence a list of requirements those are going to be included in the next software product. In order to select a right method that can tackle a problem of high consumed effort for core requirements evaluation, we need a precise approach to assess the effort consumed by available prioritizing models. This paper presents an experimental study which focuses on the procedure for effort measurement to compare the prioritizing methods. The experiment is executed and validated using data collected from two real software development projects. By drawing a comparison between two prioritizing models: a simple ranking method and an assembly prioritizing method, the experimental result shows that the percent of consumed effort for the assembly method was reduced dramatically compare with the percent of effort for a simple ranking one. The results indicate that the proposed scheme can be used to measure the effort explicitly.