Imprecise Software Requirements: A Software Development Risk

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.

Download Full-text

A Framework for the Generation of Class Diagram from Text Requirements using Natural language Processing

International Journal of Advanced Trends in Computer Science and Engineering ◽

10.30534/ijatcse/2021/041012021 ◽

2021 ◽

Vol 10 (1) ◽

pp. 25-31

Keyword(s):

Natural Language Processing ◽

Software Development ◽

Natural Language ◽

Language Processing ◽

English Language ◽

Software Requirements ◽

Class Diagram ◽

Requirement Analysis ◽

Part Of Speech ◽

Software Engineers

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

Download Full-text

What, Why, Who, When, and How of Software Requirements

Advances in Systems Analysis, Software Engineering, and High Performance Computing - Handbook of Research on Emerging Advancements and Technologies in Software Engineering ◽

10.4018/978-1-4666-6026-7.ch001 ◽

2014 ◽

pp. 1-18 ◽

Cited By ~ 1

Author(s):

Linda Westfall

Keyword(s):

Life Cycle ◽

Software Development ◽

Software Requirements ◽

Development Life Cycle ◽

Software Development Life Cycle ◽

The Right

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.

Download Full-text

Requirements Traceability

Handbook of Research on Software Engineering and Productivity Technologies ◽

10.4018/978-1-60566-731-7.ch008 ◽

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.

Download Full-text

Dynamic Prioritization of Software Requirements for Incremental Software Development

10.1007/978-981-16-4294-4_8 ◽

2021 ◽

pp. 111-131

Author(s):

Mandira Roy ◽

Novarun Deb ◽

Agostino Cortesi ◽

Rituparna Chaki ◽

Nabendu Chaki

Keyword(s):

Software Development ◽

Software Requirements

Download Full-text

A Systematic Literature Review on Risk Factors in Software Development Outsourcing

International Journal of Engineering & Technology ◽

10.14419/ijet.v7i3.20.18984 ◽

2018 ◽

Vol 7 (3.20) ◽

pp. 76

Author(s):

Alawiyah Abd Wahab ◽

Teh Piak San

Keyword(s):

Risk Factors ◽

Literature Review ◽

Software Development ◽

Systematic Literature Review ◽

Lower Cost ◽

Technical Skills ◽

Project Managers ◽

Public And Private ◽

Software Development Outsourcing ◽

Development Risk

Software development outsourcing has become a prevalent practice in the software industry. Organizations in both public and private sectors are adopting software development outsourcing in order to achieve lower cost and to access to skilled labour. However, it is widely recognized that outsourced software development projects involve risks and sometimes leads to undesirable consequences. Existing research in the software engineering and related areas have identified several risks in the software development outsourcing projects such as lack of communication and technical skills. The aim of this paper is to examine the literature on outsourced software development in order to identify some risks that could occur during the pre-contract, contract and post-contract phases of the outsourcing life cycle. It is anticipated that by understanding these risks, project managers could better manage them and subsequently increase the possibility of the success of outsourcing project. A systematic literature review of studies on software development outsourcing published in year 2005 to year 2015 was conducted. Of 41 studies consulted, 18 were concerned with outsourcing software development risk factors. The top three risk factors identified are lack of required technical skills and competencies (61%), lack of communication (44%) and poorly articulated requirements (44%).

Download Full-text