A Review on Advanced Techniques of Requirement Elicitation and Specification in Software Development Stages

2020 ◽  
Author(s):  
G.C. Sampada ◽  
Tende Ivo Sake ◽  
Megha Chhabra
Keyword(s):  
Software Development ◽  
Requirement Elicitation ◽  
Development Stages

A Requirement Elicitation Methodology for Global Software Development Teams

2011 ◽  
pp. 3273-3282
Author(s):  
Gabriela N. Aranda ◽  
Aurora Vizcaíno ◽  
Alejandra Cechich ◽  
Mario Piattini
Keyword(s):  
Software Development ◽  
Real Life ◽  
Global Software Development ◽  
Requirement Elicitation ◽  
Development Team ◽  
Cognitive Characteristics ◽  
Development Teams ◽  
Geographically Distributed ◽  
Elicitation Process ◽  
Software Development Teams

Failures during the elicitation process have been usually attributed to the difficulty of the development team in working on a cooperative basis (Togneri, Falbo, & de Menezes, 2002), but today there are other points that have to be considered. In order to save costs, modern software organizations tend to have their software development team geographically distributed, so distance between members becomes one of the most important issues added to the traditional problems of the requirement elicitation process (Brooks, 1987; Loucopoulos & Karakostas, 1995). So far, literature has widely analysed real life Global Software Development (GSD) projects and pointed out the main problems that affect such environments, especially related to communication. As a complementary view, we have focused our research on analysing how cognitive characteristics can affect people interaction in GSD projects, especially during the requirement elicitation process, where communication becomes crucial. In this article, we present the main characteristics of requirements elicitation in GSD projects and introduce a cognitive-based requirement elicitation methodology for such environments.

scholarly journals EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS

2017 ◽  
Vol 10 (13) ◽  
pp. 122
Author(s):  
B Sathis Kumar
Keyword(s):  
Software Development ◽  
Architectural Design ◽  
Quality Attributes ◽  
Clear Understanding ◽  
Design Decision ◽  
Functional Requirements ◽  
Requirement Elicitation ◽  
Development Organization ◽  
Prime Design ◽  
Reliability Performance

Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and non-functional requirements from the customer. Security, usability, reliability, performance, scalability and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality attributes requirement help to identify and shape the software architecture. A software system’s architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as Architecturally Significant Requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage.In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase 

Requirement Elicitation for Bespoke Software Development: A Review Paper

2019 ◽  
pp. 805-821
Author(s):  
Rabiya Jalil ◽  
Javaria Khalid ◽  
Maliha Maryam ◽  
Myda Khalid ◽  
Sadaf Nawaz Cheema ◽  
...  
Keyword(s):  
Software Development ◽  
Review Paper ◽  
Requirement Elicitation

A Model for Selecting Techniques in Distributed Requirement Elicitation Processes

2011 ◽  
pp. 351-363 ◽  
Author(s):  
Gabriela Aranda ◽  
Aurora Vizcaíno ◽  
Alejandra Cechich ◽  
Mario Piattini
Keyword(s):  
Cognitive Psychology ◽  
Software Development ◽  
Cognitive Styles ◽  
Requirements Elicitation ◽  
Global Software Development ◽  
Development Projects ◽  
Requirement Elicitation ◽  
Distributed Development ◽  
Development Processes ◽  
And Control

This chapter introduces a model based on techniques from cognitive psychology as a means to improve the requirement elicitation in global software development projects. Since distance negatively affects communication and control, distributed development processes that are crucially based on communication, such as requirements elicitation, have to be specially rethought in order to minimize critical situations. This chapter proposes reducing problems in communication by selecting a suite of appropriate elicitation techniques and groupware tools according to stakeholders’ cognitive styles. It also shows how information about stakeholders’ personalities can be used to make them feel comfortable and to improve their performances when working in a group.

scholarly journals An Approach for Selecting the Suitable Requirement Elicitation Technique

2021 ◽  
Vol 12 (3) ◽  
pp. 2083-2087
Author(s):  
Ibrahim Hassan Hussein Et.al
Keyword(s):  
Software Development ◽  
Initial Phase ◽  
Requirements Elicitation ◽  
Requirement Elicitation ◽  
Requirements Gathering

Requirements elicitation is an initial phase in software development. In this phase, requirements engineers gather the requirements of the software under development from users, stakeholders and customers. The techniques used for gathering requirements have a big influence on the quality of requirements and the success of project. Many requirements elicitation techniques (RET) such as: interview, prototype and observation can be used for requirements gathering process. However, one technique is not suitable for all different projects. Usually requirement engineers select the RET based on personal preferences and assumptions such as; this is the only technique which they know. However, this subjective decision can result in using inappropriate RET. Using unsuitable RET may decrease the quality of elicited requirements. Even though researchers have proposed many techniques for elicitation, one of the challenging issues is to choose the suitable RET for specific situations. The purpose of this paper is to help requirement engineers to choose suitable RET. To do that firstly, we identify factors that affect in selecting RET. Secondly, an approach to select suitable RET is proposed. Thirdly, a prototype is developed to help requirements engineers and to ease the process of selectingelicitation technique. Lastly, experts evaluate the proposed approach and the prototype.

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

2019 ◽  
Vol 8 (2S2) ◽  
pp. 230-233 ◽  
Keyword(s):  
Software Development ◽  
Collaborative Filtering ◽  
Development Process ◽  
Requirement Engineering ◽  
Vital Role ◽  
Software Development Process ◽  
Requirement Elicitation ◽  
Requirement Specification ◽  
Human Effort ◽  
Software Requirement Specification

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).

scholarly journals Desarrollo de un sistema de información para la eficiente gestión de sustancias químicas con base en la Norma Oficial Mexicana NOM-018-STPS-2015

2019 ◽  
pp. 10-17
Author(s):  
Raquel Arciga-Pedraza ◽  
Elmer Colin-Alcantar ◽  
Brenda Juarez-Santiago ◽  
Edson Jair Lizardi-Miranda
Keyword(s):  
Software Development ◽  
Programming Languages ◽  
Daily Life ◽  
Chemical Substances ◽  
Development Stages ◽  
Agile Methodology ◽  
Del Rio ◽  
Technological University ◽  
Html 5 ◽  
Web Platform

The technologies of the information nowadays are essential in the development of our daily life. They have been reflected in various activities and serve the purpose of integrating various branches of science. Having this in mind, the development team achieved to identify that in the division of chemistry at the technological university of San Juan del Rio, there was the necessity to have a web platform to consult the substances that are in storage. And also provide a tool for the implementation of the official Mexican norm NOM-018-STPS-2015 which has the purpose of identifying the dangers and risks of dangerous chemical substances through the use of pictograms. The software development stages were implemented using XP (Xtreme Programming) being that it’s an agile methodology and it allows to prioritize tasks according to the client’s requirements, using the programming languages PHP 7, MySQL and HTML 5. The acquired result was a web system with the modules of queries, substances information, which was used by students of chemistry engineering who evaluated the platform via a survey, and accomplished a 75% of satisfaction.

Sign in / Sign up

Export Citation Format

Share Document