Requirements Traceability

2010 ◽  
pp. 102-120
Author(s):  
Elias Canhadas Genvigir ◽  
Nandamudi Lankalapalli Vijaykumar
Keyword(s):  
Software Development ◽  
Change Management ◽  
Requirements Engineering ◽  
Software Requirements ◽  
Requirements Management ◽  
Requirements Traceability

This chapter presents a research about the Software Requirements Traceability. The main elements of traceability, definitions, problems and prospects are presented. The chapter is organized by topics and its beginning is a review about requirements engineering, its categories (Elicitation, Analysis and Negotiation, Documentation, Validation, and Management) and its role in software development. Afterwards, the requirements management and its elements (Identification, Change Management and Traceability) are described. Traceability is discussed; its aspects and problems are exploited as well as its classifications, techniques, links, metrics and models. Finally the Conclusion presents the main points that can be explored in future researches.

A Novel Approach to Change Management in Requirements Engineering Context

2015 ◽  
Vol 7 (3) ◽  
pp. 18-44 ◽  
Author(s):  
Soumia Bendakir ◽  
Nacereddine Zarour ◽  
Pierre Jean Charrel
Keyword(s):  
Change Management ◽  
Requirements Engineering ◽  
Source Code ◽  
User Requirements ◽  
Requirements Management ◽  
Multi Agent System ◽  
Novel Approach ◽  
Requirements Change ◽  
Multi Agent ◽  
The Cost

Requirements change management (RCM) is actually an inevitable task that might be considered in system development's life cycle, since user requirements are continuously evolving (some are added, others are modified or deleted). A large majority of studies have examined the issue of change, while most of them focused on the design and source code, requirements were often forgotten, even though, the cost of fixing the defect and introduced error due to the requirements is less higher compared to the cost of error in design and implementation. For this purpose, this work focuses on change issues in the requirements engineering (RE) context, which contains the complete initial specification. Properties such as adaptability, perception, and cooperation of the multi-agent system (MAS) allow managing changing requirements in a controlled manner. The main objective of this work is to develop an agent-oriented approach which will be effective in the requirements management to be adapted to changes in their environments.

scholarly journals Jogo para apoio ao ensino-aprendizagem de especificação de requisitos

2020 ◽  
Author(s):  
João Vitor Demaria Venâncio ◽  
Fabiane Barreto Vavassori Benitti
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Software Design ◽  
Development Process ◽  
Process Research ◽  
Requirements Specification ◽  
Software Requirements ◽  
Software Development Process ◽  
Mobile Game ◽  
Specification Techniques

Requirements Engineering is concerned with identifying, analyzing,documenting and managing software requirements, which is an importantphase in the software development process. Research showsthat most software design failures are due to requirements engineeringissues. Thus, we propose a solution for the active learningof requirements specification techniques. Considering that the userstory technique is currently well accepted by IT companies, thispaper proposes a mobile game that supports learning and practicein writing user stories.

Handling Extemporaneous Information in Requirements Engineering

2011 ◽  
pp. 1718-1722 ◽  
Author(s):  
Gladys N. Kaplan ◽  
Jorge H. Doorn
Keyword(s):  
Software Development ◽  
Error Correction ◽  
Requirements Engineering ◽  
Relevant Information ◽  
Software Requirements ◽  
Software Project ◽  
Maintenance Costs ◽  
The Right ◽  
The Universe ◽  
Requirements Completeness

The key of the success or failure of a software project depends on solving the right problem (Rumbaugh, 1994; Sawyer, 2005). Thus, software requirements should be correct, unambiguous, consistent, and as complete as possible (Institute of Electrical and Electronics Engineers [IEEE], 1998). Errors in requirements raise software development and maintenance costs notoriously (Katasonov & Sakkinen, 2006). The later the requirement error is detected, the higher the correction cost turns out to be. Error correction costs have been widely studied by many researchers (Bell & Thayer, 1976; Davis, 1993). Errors in requirements may be due to several reasons such as poor communication among requirements engineers, clients, and users; poor or nonexistent requirements validation; and the level of sternness of the models being used, especially to model relevant information captured from the universe of discourse (UofD). Requirements engineering is the area of software engineering responsible for proposing and developing solutions to elicit, model, and analyze requirements by means of heuristics, guidelines, models, and processes which tend to requirements’ completeness, quality, correctness, and consistency. Many proposals have been put forward by many researchers (Bubenko & Wrangler, 1993; Jacobson, Christerson, Jonsson, & Overgaard, 1992; Leite & Oliveira, 1995; Macaulay, 1993; Reubenstein & Waters, 1991).

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 Effect of Project Management in Requirements Engineering and Requirements Change Management Processes for Global Software Development

IEEE Access ◽  
2018 ◽  
Vol 6 ◽  
pp. 25747-25763 ◽  
Author(s):  
Muhammad Shafiq ◽  
Qinghua Zhang ◽  
Muhammad Azeem Akbar ◽  
Arif Ali Khan ◽  
Shahid Hussain ◽  
...  
Keyword(s):  
Project Management ◽  
Software Development ◽  
Change Management ◽  
Requirements Engineering ◽  
Global Software Development ◽  
Management Processes ◽  
Requirements Change

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.

Sign in / Sign up

Export Citation Format

Share Document