{"title":"Identifying Design Features Using Combination of Requirements Elicitation Techniques","authors":"L. Murugesan, Rashina Hoda, Z. Salcic","doi":"10.1109/DISE.2017.9","DOIUrl":null,"url":null,"abstract":"Requirements elicitation (RE) is the explanatorydevelopment activity of helping users figure out what theywant. However, acquisition of requirements is challenging andinappropriate requirements might lead to unncessary projectdevelopment cost. It is important to validate the requirementswith various possible techniques to design a software solution. It is equally important to choose appropriate techniques for RE. To understand the importance of RE, Energy feedback or visualizationof electricity consumption application had been chosenwhich would help in reducing household electricity consumptionby motivating the residential end-users. To design an effectiveand innovative solution for visualization application, this articleused a combination of three RE techniques, viz., systematicliterature review (SLR), crowdsourcing survey and user-centreddesign (UCD) based design activity. The SLR assessed 22 studies, while the crowdsourcing survey and the design activity had137 and 6 participants respectively. The RE techniques wereinterdependent and the results from each technique was fedto design the subsequent phases. Each of the RE techniques'motivation, procedure and its results were discussed and werestatistically compared with each other forming the top sevenfeatures of the system to be developed. This study also analyzedthe effectiveness of the requirements elicitation by conductingretrospective on the RE techniques. The retrospective analyzedthings that went well, things that did not go well, and things thatcan be improved. It led to the discussion on how effectively canthis process be improved to collect the requirements.","PeriodicalId":387017,"journal":{"name":"2017 IEEE/ACM 1st International Workshop on Design and Innovation in Software Engineering (DISE)","volume":"118 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2017-05-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"7","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2017 IEEE/ACM 1st International Workshop on Design and Innovation in Software Engineering (DISE)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/DISE.2017.9","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 7
Abstract
Requirements elicitation (RE) is the explanatorydevelopment activity of helping users figure out what theywant. However, acquisition of requirements is challenging andinappropriate requirements might lead to unncessary projectdevelopment cost. It is important to validate the requirementswith various possible techniques to design a software solution. It is equally important to choose appropriate techniques for RE. To understand the importance of RE, Energy feedback or visualizationof electricity consumption application had been chosenwhich would help in reducing household electricity consumptionby motivating the residential end-users. To design an effectiveand innovative solution for visualization application, this articleused a combination of three RE techniques, viz., systematicliterature review (SLR), crowdsourcing survey and user-centreddesign (UCD) based design activity. The SLR assessed 22 studies, while the crowdsourcing survey and the design activity had137 and 6 participants respectively. The RE techniques wereinterdependent and the results from each technique was fedto design the subsequent phases. Each of the RE techniques'motivation, procedure and its results were discussed and werestatistically compared with each other forming the top sevenfeatures of the system to be developed. This study also analyzedthe effectiveness of the requirements elicitation by conductingretrospective on the RE techniques. The retrospective analyzedthings that went well, things that did not go well, and things thatcan be improved. It led to the discussion on how effectively canthis process be improved to collect the requirements.