Dynamic Prioritization of Software Requirements for Incremental Software Development

2021 ◽  
pp. 111-131
Author(s):  
Mandira Roy ◽  
Novarun Deb ◽  
Agostino Cortesi ◽  
Rituparna Chaki ◽  
Nabendu Chaki
Complexity ◽  
2019 ◽  
Vol 2019 ◽  
pp. 1-20
Author(s):  
Paulo A. M. Barbosa ◽  
Plácido R. Pinheiro ◽  
Francisca R. V. Silveira ◽  
Marum Simão Filho

During the software development process, the decision maker (DM) must master many variables inherent in this process. Software releases represent the order in which a set of requirements is implemented and delivered to the customer. Structuring and enumerating a set of releases with prioritized requirements represents a challenging task because the requirements contain their characteristics, such as technical precedence, the cost required for implementation, the importance that one or more customers add to the requirement, among other factors. To facilitate this work of selection and prioritization of releases, the decision maker may adopt some support tools. One field of study already known to solve this type of problem is the Search-Based Software Engineering (SBSE) that uses metaheuristics as a means to find reasonable solutions taking into account a set of well-defined objectives and constraints. In this paper, we seek to increase the possibilities of solving the Next Release Problem using the methods available in Verbal Decision Analysis (VDA). We generate a problem and submit it so that the VDA and SBSE methods try to resolve it. To validate this research, we compared the results obtained through VDA and compared with the SBSE results. We present and discuss the results in the respective sections.


The software development procedure begins with identifying the requirement analysis. The process levels of the requirements start from analysing the requirements to sketch the design of the program, which is very critical work for programmers and software engineers. Moreover, many errors will happen during the requirement analysis cycle transferring to other stages, which leads to the high cost of the process more than the initial specified process. The reason behind this is because of the specifications of software requirements created in the natural language. To minimize these errors, we can transfer the software requirements to the computerized form by the UML diagram. To overcome this, a device has been designed, which plans can provide semi-automatized aid for designers to provide UML class version from software program specifications using natural Language Processing techniques. The proposed technique outlines the class diagram in a well-known configuration and additionally facts out the relationship between instructions. In this research, we propose to enhance the procedure of producing the UML diagrams by utilizing the Natural Language, which will help the software development to analyze the software requirements with fewer errors and efficient way. The proposed approach will use the parser analyze and Part of Speech (POS) tagger to analyze the user requirements entered by the user in the English language. Then, extract the verbs and phrases, etc. in the user text. The obtained results showed that the proposed method got better results in comparison with other methods published in the literature. The proposed method gave a better analysis of the given requirements and better diagrams presentation, which can help the software engineers. Key words: Part of Speech,UM


Author(s):  
Linda Westfall

If software requirements are not right, companies will not end up with the software they need. This chapter discusses the various levels and types of requirements that need to be defined, the benefits of having the right software requirements, the stakeholders of the software requirements and getting them involved in the process, requirements activities throughout the software development life cycle, and techniques for eliciting, analyzing, specifying, and validating software requirements.


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.


10.12737/2554 ◽  
2014 ◽  
Vol 8 (1) ◽  
pp. 104-112
Author(s):  
Ирина Писаренко ◽  
Irina Pisarenko ◽  
Александр Ермаков ◽  
Aleksandr Ermakov

The article dwells on the garment-making-machine control, diagnostics and service software requirements as imposed by the peculiarities of the garment manufacturing technological processes. The authors consider the stages of software development and software quality indicators.


Author(s):  
Osman, M.H. Et.al

Software Requirements Specification (SRS) is considered a highly critical artifact in the software development. All phases in software development are influenced by this artifact. Defects in software requirements may higher the risk of project overschedule that contributes to cost overrun of the project.Researchers have shown that finding defects in the initial software development phase is important becausethe cost of the bug is cheaper if it is fixed early. Hence, our main goal is to provide a platform for requirement engineers to produce better requirement specifications. We propose AmbiDetect, a (prototype) tool toautomatically classify ambiguous software requirements. AmbiDetect combines text mining and machine learning for ambiguous requirement specification detection. The text mining technique is used to extract classification features as well as generating the training set.AmbiDetect usesa machine learning technique to perform the ambiguous requirement specification detection. From an initial user study to validate the tool, the result indicates that the accuracy of detection is reasonably acceptable.Although AmbiDetect is an early experimental tool, we optimist that this tool can be a platform to improve SRS quality.


2020 ◽  
Author(s):  
João Vitor Demaria Venâncio ◽  
Fabiane Barreto Vavassori Benitti

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.


Sign in / Sign up

Export Citation Format

Share Document