scholarly journals Ontology and Enterprise Modelling Driven Software Requirements Development Approach

2019 ◽  
Vol 7 (2) ◽  
Author(s):  
Neringa Makrickienė ◽  
Audrius Lopata ◽  
Saulius Gudas
Keyword(s):  
Software Requirements ◽  
Enterprise Modelling ◽  
Development Approach ◽  
Requirements Development

Requirements Engineering

2011 ◽  
pp. 1-20 ◽  
Author(s):  
Päivi Parviainen ◽  
Maarit Tihinen ◽  
Marco Lormanms ◽  
Rini van Solingen
Keyword(s):  
Requirements Engineering ◽  
Sociotechnical Systems ◽  
Software Requirements ◽  
Main Process ◽  
Vast Number ◽  
Complex Process ◽  
System Requirements ◽  
Systems Requirements ◽  
Continuous Activities ◽  
Requirements Development

This chapter introduces requirements engineering for sociotechnical systems. Requirements engineering for sociotechnical systems is a complex process that considers product demands from a vast number of viewpoints, roles, responsibilities, and objectives. This chapter explains the requirements engineering terminology and describes the requirements engineering process in detail, with examples of available methods for the main process activities. The main activities described include system requirements development, requirements allocation and flow-down, software requirements development, and continuous activities, including requirements documentation, requirements validation and verification, and requirements management. As requirements engineering is the process with the largest impact on the end product, it is recommended to invest more effort in both industrial application as well as research to increase understanding and deployment of the concepts presented in this chapter.

scholarly journals Designing eHealth that Matters via a Multidisciplinary Requirements Development Approach

2013 ◽  
Vol 2 (1) ◽  
pp. e21 ◽  
Author(s):  
Lex Van Velsen ◽  
Jobke Wentzel ◽  
Julia EWC Van Gemert-Pijnen
Keyword(s):  
Development Approach ◽  
Requirements Development

scholarly journals REACT-M: uma Abordagem Ágil para o Gerenciamento de Requisitos de Software

2020 ◽  
Author(s):  
Bleno Wilson Frankiin Vale da Silva ◽  
Aline Franciele dos Anjos Lima ◽  
Sandro Ronaldo Bezerra Oliveira ◽  
André Luiz Coelho Pinheiro
Keyword(s):  
Software Requirements ◽  
Agile Methods ◽  
Requirements Management ◽  
Quality Models ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Literature Mapping ◽  
Agile Approach ◽  
Requirements Development

Agile methods provide support to software engineeringactivities, aiming to reduce some of problems of the traditionalapproaches. Quality products can be developed by agilemethodology in less time and budget. Requirements engineeringis a building block of software development. Therefore, thesearch for agile practices for the evolution of requirementsbecomes relevant. Although several researches have been carriedout on the role of requirements engineering in agilemethodologies, there is still a need for studies that seek to alignagile approaches to requirements development and managementprocesses that satisfy highly accepted quality models in themarket. This paper aims to establish an agile approach tosupport software requirements management, based on asystematic literature mapping that draws on existing approachesin agile methodologies that support requirements managementactivities.

Disciplined or Agile?

2022 ◽  
pp. 1980-2000
Author(s):  
Danyllo Wagner Albuquerque ◽  
Everton Tavares Guimarães ◽  
Felipe Barbosa Araújo Ramos ◽  
Antonio Alexandre Moura Costa ◽  
Alexandre Gomes ◽  
...  
Keyword(s):  
Software Process ◽  
Software Requirements ◽  
Customer Requirements ◽  
Main Contributor ◽  
Current State ◽  
Operating Environments ◽  
Requirements Change ◽  
The Subject ◽  
Requirements Development ◽  
Software Practitioners

Software requirements changes become necessary due to changes in customer requirements and changes in business rules and operating environments; hence, requirements development, which includes requirements changes, is a part of a software process. Previous studies have shown that failing to manage software requirements changes well is a main contributor to project failure. Given the importance of the subject, there is a plethora of efforts in academia and industry that discuss the management of requirements change in various directions, ways, and means. This chapter provided information about the current state-of-the-art approaches (i.e., Disciplined or Agile) for RCM and the research gaps in existing work. Benefits, risks, and difficulties associated with RCM are also made available to software practitioners who will be in a position of making better decisions on activities related to RCM. Better decisions can lead to better planning, which will increase the chance of project success.

scholarly journals Improving the System Software Requirements Development Process

1994 ◽  
Vol 4 (1) ◽  
pp. 642-649 ◽  
Author(s):  
Phillip J. Brown ◽  
Alexander E. Iwach ◽  
Donald R. Williams
Keyword(s):  
Development Process ◽  
Software Requirements ◽  
System Software ◽  
Requirements Development

Disciplined or Agile?

2021 ◽  
pp. 130-150
Author(s):  
Danyllo Wagner Albuquerque ◽  
Everton Tavares Guimarães ◽  
Felipe Barbosa Araújo Ramos ◽  
Antonio Alexandre Moura Costa ◽  
Alexandre Gomes ◽  
...  
Keyword(s):  
Software Process ◽  
Software Requirements ◽  
Customer Requirements ◽  
Main Contributor ◽  
Current State ◽  
Operating Environments ◽  
Requirements Change ◽  
The Subject ◽  
Requirements Development ◽  
Software Practitioners

Software requirements changes become necessary due to changes in customer requirements and changes in business rules and operating environments; hence, requirements development, which includes requirements changes, is a part of a software process. Previous studies have shown that failing to manage software requirements changes well is a main contributor to project failure. Given the importance of the subject, there is a plethora of efforts in academia and industry that discuss the management of requirements change in various directions, ways, and means. This chapter provided information about the current state-of-the-art approaches (i.e., Disciplined or Agile) for RCM and the research gaps in existing work. Benefits, risks, and difficulties associated with RCM are also made available to software practitioners who will be in a position of making better decisions on activities related to RCM. Better decisions can lead to better planning, which will increase the chance of project success.

Sign in / Sign up

Export Citation Format

Share Document