A Path for the Implementation of Best Practices for Software Requirements Management Process Using a Multimodel Environment

Author(s):  
Gloria Piedad Gasca-Hurtado ◽  
Mirna Muñoz
2018 ◽  
Vol 7 (2.14) ◽  
pp. 62
Author(s):  
Azlin Nordin ◽  
Amirul Ikhwan Omar ◽  
Megat Usamah Megat Mohamed Amin ◽  
Norsaremah Salleh

Scenario-based methodology has been applied in analyzing real world experience into representation in software environment. Nonetheless, capturing, documenting and managing scenarios are extremely labor-intensive. Hence, the generic aims of this project are to investigate, explore and analyze requirements management process towards supporting scenario-based requirements approach. Based on our analysis of the existing RE or Requirements Management (RM) tools, most of the tools had less focus or missing some significant RE features to facilitate scenario-based   methodology. We analyzed all the relevant features and developed a prototype i.e.  Scenario-based Requirements Tool (SMaRT) to demonstrate how scenario-based approach can be implemented to further supports scenario-based RE  methodology and  covers most of the RE process  i.e. elicitation,  analysis  and  negotiation, documentation, validation,   and  management. SMaRT improves the RE tool features i.e. project and requirements management, document generation and validation function to further supports scenario-based RE methodology and covers most of the RE process i.e. elicitation, analysis, negotiation, documentation, validation, and management.   


Author(s):  
Elias Canhadas Genvigir ◽  
Nandamudi Lankalapalli Vijaykumar

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.


IEEE Software ◽  
2000 ◽  
Vol 17 (2) ◽  
pp. 101-102 ◽  
Author(s):  
Wm.P. Rogers

1999 ◽  
Vol 9 (1) ◽  
pp. 1437-1441 ◽  
Author(s):  
Gisela John ◽  
Matthias Hoffmann ◽  
Matthias Weber ◽  
Martin Nagel ◽  
Carsten Thomas

2019 ◽  
Vol 26 (88) ◽  
pp. 128-150
Author(s):  
Jeremy Kramer ◽  
Torrey Wagner

This article provides insights into the current state of developmental testing (DT) and requirements management in Department of Defense information systems employing Agile development. The authors describe the study methodology and provide an overview of Agile development and testing. Insights are described for requirements, detailed planning, test execution, and reporting. This work articulates best practices related to DT and requirements management strategies for programs employing modernized Software Development Life Cycle practices.


2020 ◽  
Author(s):  
Bleno Wilson Frankiin Vale da Silva ◽  
Aline Franciele dos Anjos Lima ◽  
Sandro Ronaldo Bezerra Oliveira ◽  
André Luiz Coelho Pinheiro

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.


2016 ◽  
pp. 2146-2170
Author(s):  
Jack S. Cook ◽  
Pamela A. Neely

Using an interpretive case study approach, this chapter describes the data quality problems in two companies: (1) a Multi-Facility Healthcare Medical Group (MHMG), and (2) a Regional Health Insurance Company (RHIS). These two interpretive cases examine two different processes of the healthcare supply chain and their integration with a business intelligence system. Specifically, the issues examined are MHMG's revenue cycle management and RHIS's provider enrollment and credentialing process. A Data and Information Quality (DIQ) assessment of the revenue cycle management process demonstrates how a framework, referred to as PGOT, can identify improvement opportunities within any information-intensive environment. Based on the assessment of the revenue cycle management process, data quality problems associated with the key processes and their implications for the healthcare organization are described. This chapter provides recommendations for DIQ best practices and illustrates these best practices within this real world context of healthcare.


Sign in / Sign up

Export Citation Format

Share Document