scholarly journals Implementing Item-Based Collaborative Filtering System in Requirement Elicitation

In Requirement Engineering, Gathering Requirements plays a vital role in the Software Development Process. There are lot of processes available to gather requirements i.e. Brainstorming, Interview, Observation. This process takes lot of time and effort for the developer to gather and continue the development, and if the requirements which are analyzed are not up to the satisfaction of the user, it will cause issues in end product resulting in loss of human effort, time and cost. To overcome this issue faced by the developers we have developed a tool using item-based collaborative algorithm for users which will recommend users the required set of functional and nonfunctional requirements based upon the questionnaire given tothe user and produce a software requirement specification (SRS).

2020 ◽  
Author(s):  
Sai Lohith Vasireddi ◽  
Mahesh Dhaka ◽  
Jinan Fiaidhi

The research paper focuses on automating software development process by automating the team formation by extracting information from the software requirement specification (SRS) document of the project.


2020 ◽  
Author(s):  
Sai Lohith Vasireddi ◽  
Mahesh Dhaka ◽  
Jinan Fiaidhi

The research paper focuses on automating software development process by automating the team formation by extracting information from the software requirement specification (SRS) document of the project.


Author(s):  
Naveen N Kulkarni Et.al

Software Requirements Engineering (SRE) process define software manuscripts with sustaining Software Requirement Specification (SRS) and its activities. SRE comprises many tasks requirement analysis, elicitation, documentation, conciliation and validation. Natural language is most popular and commonly used to form the SRS document. However, natural language has its own limitations wrt quality approach for SRS. The constraints include  incomplete, incorrect, ambiguous, and inconsistency. In software engineering, most applications are object-oriented. So requirements are unlike problem domain need to be developed. So software  documentation is completed in such a way that, all authorized users like clients, analysts, managers, and developers can understand it. These are the basis for success of any planned project. Most of the work is still dependent on intensive human (domain expert) work. consequences of the project success still depend on timeliness with tending errors. The fundamental quality intended for each activity is specified during the software development process. This paper concludes critically with best practices in writing SRS. This approach helps to mitigate SRS limitation up to some extent. An initial review highlights capable results for the proposed practices


2021 ◽  
Vol 2021 ◽  
pp. 1-18
Author(s):  
Aqsa Rasheed ◽  
Bushra Zafar ◽  
Tehmina Shehryar ◽  
Naila Aiman Aslam ◽  
Muhammad Sajid ◽  
...  

Agile software development has large success rate due to its benefits and promising nature but natively where the size of the project is small. Requirement engineering (RE) is crucial as in each software development life cycle, “Requirements” play a vital role. Though agile provides values to customer’s business needs, changing requirement, and interaction, we also have to face impediments in agile, many of which are related to requirement challenges. This article aims to find out the challenges being faced during requirement engineering of agile projects. Many research studies have been conducted on requirement challenges which are somehow biased, no suggestions are given to improve the agile development process, and the research does not highlight large-scale agile development challenges. Hence, this article covers all the challenges discussed above and presents a comprehensive overview of agile models from requirement engineering perspective. The findings and results can be very helpful for software industry to improve development process as well as for researchers who want to work further in this direction.


2016 ◽  
Vol 15 (7) ◽  
pp. 6940-6946
Author(s):  
Sidra Arshad ◽  
Hafiza Tahira Fazal ◽  
Tahir Nawaz

The performance of Requirement Engineering is like framework for software development process. All-inclusive software has four mainstays of requirement engineering processes i.e. Functional and non-functional requirements, design,implementation and testing build the complete software fortification on top of the mainstays. Requirement engineers have to face numerous challenges to develop successful and impressive software. Requirements Engineering (RE) leads software development process. Different constraints and needs of users are explored as well as hitches in previous system are depicted. The scope of this study is to exemplify the difficulties faced by users in the utmost maiden phase of RE Requirements Elicitation and a framework is presented as well. A survey was conducted in different campuses of Universities in Pakistan for this purpose. Questionnaire was distributed among project development students of various disciplines to gather and highlighted the problems during Requirements Elicitation. Finally the predictive statistical software SPSS was used to input the collected data for more precise calculations, the results of which are discussed in section 3.


Sensors ◽  
2021 ◽  
Vol 21 (10) ◽  
pp. 3480
Author(s):  
Walter Takashi Nakamura ◽  
Iftekhar Ahmed ◽  
David Redmiles ◽  
Edson Oliveira ◽  
David Fernandes ◽  
...  

The success of a software application is related to users’ willingness to keep using it. In this sense, evaluating User eXperience (UX) became an important part of the software development process. Researchers have been carrying out studies by employing various methods to evaluate the UX of software products. Some studies reported varied and even contradictory results when applying different UX evaluation methods, making it difficult for practitioners to identify which results to rely upon. However, these works did not evaluate the developers’ perspectives and their impacts on the decision process. Moreover, such studies focused on one-shot evaluations, which cannot assess whether the methods provide the same big picture of the experience (i.e., deteriorating, improving, or stable). This paper presents a longitudinal study in which 68 students evaluated the UX of an online judge system by employing AttrakDiff, UEQ, and Sentence Completion methods at three moments along a semester. This study reveals contrasting results between the methods, which affected developers’ decisions and interpretations. With this work, we intend to draw the HCI community’s attention to the contrast between different UX evaluation methods and the impact of their outcomes in the software development process.


Sign in / Sign up

Export Citation Format

Share Document