scholarly journals Non-Functional Requirements Elicitation

2019 ◽  
Vol 8 (2S11) ◽  
pp. 2129-2132
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Quality Attributes ◽  
Requirements Analysis ◽  
Requirements Elicitation ◽  
Software System ◽  
Functional Requirements ◽  
Important Activity

Non-Functional requirements elicitation is one of the most important activity in requirements engineering. Non-functional requirements define the quality attributes of software system. If this analysis is not done properly, it may cause for problems in further phases that in turn may lead to failure of the software. Hence the non-functional requirements analysis has to be given at most priority in software development. This paper presents survey on different approaches proposed for Non-Functional requirements analysis

scholarly journals Empirical and Statistical Study of Elicitation Complications

2016 ◽  
Vol 15 (7) ◽  
pp. 6940-6946
Author(s):  
Sidra Arshad ◽  
Hafiza Tahira Fazal ◽  
Tahir Nawaz
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Development Process ◽  
Statistical Study ◽  
Requirement Engineering ◽  
Requirements Elicitation ◽  
Software Requirements ◽  
Software Development Process ◽  
Functional Requirements ◽  
Statistical Software

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.

scholarly journals Requirements Elicitation and Access: A Research

2019 ◽  
Vol 8 (11S) ◽  
pp. 903-905
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Requirements Elicitation ◽  
Functional Requirements ◽  
Customer Needs ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Important Activity

Requirements Elicitation and Analysis is one of the most important activity in software development life cycle. Requirements Elicitation and Analysis is about gathering and analyzing the requirements as per customer needs. If this analysis is not done properly, it may cause for problems in further phases that in turn may lead to failure of the software. Hence the requirements Elicitation and Analysis has to be given at most priority in SDLC. This paper presents a survey on requirements elicitation and analysis, particularly on functional Requirements.

scholarly journals Requirements Prioritization using Risk Assessment for Analyzing Requirements

2019 ◽  
Vol 8 (2S11) ◽  
pp. 785-791
Keyword(s):  
Risk Assessment ◽  
Literature Review ◽  
Requirements Engineering ◽  
Early Stage ◽  
Requirements Analysis ◽  
Requirements Elicitation ◽  
Requirements Prioritization ◽  
Analysis Process

Requirements elicited from requirements elicitation session with stakeholders are usually comes in bulk and it is impossible to execute them simultaneously. In addition, the requirements elicited are unfiltered and usually low quality including ambiguous, incomplete and unclear. The low quality of requirements are then refined in the next activity which is requirements analysis in requirements engineering. This paper aims to integrate requirements prioritization techniques focused on the factor of risk in requirements analysis since the early stage of requirements engineering. It is seems to have a little evidence on that requirements prioritization focus on the factor of risk in requirements based on our conducted literature review. This paper begins with elaboration on requirements prioritization, further to the aspects of requirements prioritization, criteria for best suited technique, a literature review on requirements prioritization techniques. We then proposed a framework for requirements analysis with the integration of requirements prioritization. A case study is elaborated for a better vision on the process of the proposed approach. Finally, this study is believed to produce a better quality of requirements from the requirements analysis process.

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 

Best Practices Guidelines for Agile Requirements Engineering Practices

2010 ◽  
pp. 1-14
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Careful Analysis ◽  
Requirement Engineering ◽  
Functional Requirements ◽  
Knowledge Based ◽  
Development Methodology ◽  
Requirement Change ◽  
Engineering Practices ◽  
Agile Requirements

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

Best Practices Guidelines for Agile Requirements Engineering Practices

2012 ◽  
pp. 1403-1416
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Careful Analysis ◽  
Requirement Engineering ◽  
Functional Requirements ◽  
Knowledge Based ◽  
Development Methodology ◽  
Requirement Change ◽  
Engineering Practices ◽  
Agile Requirements

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

scholarly journals Safety Requirements Analysis using Misuse Cases Method

2021 ◽  
Vol 7 (1) ◽  
pp. 1-9
Author(s):  
Ryo Alif Ramadhan ◽  
Dana Sulistyo Kusumo ◽  
Jati Hiliamsyah Husen
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Security Analysis ◽  
Safety Analysis ◽  
Requirements Analysis ◽  
Software Requirements ◽  
Analysis Approach ◽  
Analysis Method ◽  
Safety Requirements ◽  
Software Product

Safety requirements analysis is an activity inside software requirements engineering that focuses on finding and solving safety gaps inside a software product. One method to do safety requirements analysis is misuse cases, a technique adopted from the security analysis method. Misuse cases provide a safety analysis approach which allows detailed steps from different stakeholders' perspective. In this research, we evaluate the misuse cases method's understandability by implementing it to analyze safety requirements for an electric car's autopilot system. We assessed the developed models using the walkthrough method. We found differences between how the model understood from someone with experience in software development and those who don't.

scholarly journals Requirements Engineering of Village Innovation Application Using Goal-Oriented Requirements Engineering (GORE)

2021 ◽  
Vol 13 (2) ◽  
pp. 38-46
Author(s):  
Condro Kartiko ◽  
Ariq Cahya Wardhana ◽  
Wahyu Andi Saputra
Keyword(s):  
Requirements Engineering ◽  
Business Processes ◽  
Model Building ◽  
Central Government ◽  
Innovation System ◽  
Requirements Elicitation ◽  
Functional Requirements ◽  
Tree Model ◽  
Replication Studies ◽  
The Village

The delay in the absorption of village funds from the central government to the village government is due to the village government's difficulty preparing village development innovation programs. The innovation tradition will grow if the cycle of transformation of knowledge and acceptable practices from one village to another, especially villages with similar conditions and problems, can run smoothly.  For the process of exchanging knowledge and experiences between villages to run smoothly, it is necessary to codify best practices in a structured, documented, and disseminated manner. This research aims to design an application that functions as a medium for sharing knowledge about the use of village funds through government innovation narratives. The application is expected to become a reference for villages to carry out innovative practices by conducting replication studies and replicating acceptable practices that other villages have done. Therefore, it is necessary to have a system requirements elicitation method that can explore the village's requirements in sharing knowledge so that the resulting system is of high quality and by the objectives of being developed. There are several Goal-Oriented Requirements Engineering (GORE) methods used, such as Knowledge Acquisition in Automated Specification (KAOS) and requirements engineering based on business processes. In this research, the KAOS method was demonstrated as the elicitation activity of a village innovation system. Then the results were stated in the Goal Tree Model (GTM). Model building begins with discussions with the manager of the village innovation program to produce goals. The goals are then broken down into several sub-goals using the KAOS method. The KAOS method is used for the requirements elicitation process resulting in functional and non-functional requirements. This research is the elicitation of the requirement for the village innovation system so that it can demonstrate the initial steps in determining the requirements of the village innovation system before carrying out the design process and the system creation process. The results of this requirement elicitation can be used further in the software engineering process to produce quality and appropriate village innovation applications.

scholarly journals Quality Extended Use Case Point (QUCP): An Improved Cost Estimation Method

2021 ◽  
Vol 10 (6) ◽  
pp. 1-9
Author(s):  
Ibrahim Mohammad Ba’abbad ◽  
M. Rizwan Jameel Qureshi
Keyword(s):  
Software Development ◽  
Cost Estimation ◽  
Cost Model ◽  
Estimation Method ◽  
Quality Attributes ◽  
Estimation Methods ◽  
Use Case ◽  
Functional Requirements ◽  
High Quality ◽  
Use Case Diagram

The quality of a product is one of the major interests of the manufacturing process in all industries. The software industry imposes to construct a project with several phases to ensure producing high-quality software. A software development company estimates time, effort and cost of the project during planning phase. It is important to have accurate estimations to reduce the risks of project failure. Several cost estimation methods are practiced in the software development companies such as Function Point (FP), Use Case Points (UCP), Constructive Cost Model I and II and Story Points (SP). UCP cost estimation method is taken in this research to improve the accuracy of its estimation. UCP estimation depends on the use case diagram of the proposed system. A use case diagram describes the main functional requirements of the proposed system. UCP partially considers non-functional requirements through the technical and environmental factors. There is a lacking in the UCP method to consider the importance of quality attributes in the estimating process. This paper proposes an extended version of the existing UCP method named Quality Extended Use Case Point (QUCP) method in which quality attributes are included to improve the accuracy of cost estimation. A questionnaire is used to validate the proposed QUCP method. It is found after data analysis that seventy five percentages of the participants are agreed that the proposed method will not only help to improve the accuracy of cost estimation but it will also enable a software development company to deliver high-quality products.

NATURAL LANGUAGE SPECIFICATION IMPROVEMENT WITH ONTOLOGIES

2009 ◽  
Vol 03 (04) ◽  
pp. 445-470 ◽  
Author(s):  
SVEN J. KÖRNER ◽  
TORBEN BRUMM
Keyword(s):  
Software Development ◽  
Natural Language ◽  
Requirements Engineering ◽  
Semantic Information ◽  
Software System ◽  
Dialog System ◽  
Development Cycle ◽  
Language Specification ◽  
Correct Implementation

Requirements engineering can solve and cause many problems in a software development cycle. The difficulties in understanding and eliciting the desired functionality from the customer and then delivering the correct implementation of a software system lead to delays, mistakes, and high costs. Working with requirements means handling incomplete or faulty textual specifications. It is vital for a project to fully understand the purpose and the functionality of a software. The earlier specifications are corrected and improved, the better. We created a tool called RESI to support requirement analysts working with textual specifications. RESI checks for linguistic defects [1, 2] in specifications and offers a dialog-system which makes suggestions to improve the text. It points out to the user which parts of the specification are ambiguous, faulty or inaccurate and therefore need to be changed. For this task, RESI needs additional semantic information which is inherent to natural language specifications. It receives this information by utilizing ontologies.

Sign in / Sign up

Export Citation Format

Share Document