The Significance of Requirement Engineering in Software Development - Requirement Engineering Approaches and Challenges

Sep 11, 2026

Uploaded by Mack Lee

Software development advances through feasibility study, requirement gathering and analysis, design, coding, testing, and maintenance, where requirement engineering is pivotal for aligning outcomes with customer needs. The process collects and thoroughly analyzes end-user requirements to ensure completeness and consistency, while addressing anomalies or inconsistencies that emerge in collected inputs. The paper surveys requirement engineering approaches used by organizations to gather, comprehend, and manage requirements change. It also highlights challenges such as communication diversity, ontology-based semantics, iterative change support, and gaps in quantification, scalability, and prioritization.

LanguageEnglish

CategoryForms

FormatPDF

Pages6

Reading Time2 min

AccessFree to download

Introduction

Software Development Life Cycle Phases

Focus on Requirement Gathering and Analysis

Survey

Ontology and Requirement Classification

Challenges in Requirement Elicitation

The Significance of Requirement Engineering in Software Development 1Rani Singh, 2Manish Kumar Assistant Professor Information Technology Ganpat University, Mehsana, Gujarat Abstract- At present, the process of software development comprises a series of steps, commencing with the feasibility study phase, followed by requirement gathering and analysis, design, coding, testing, and maintenance phases. Each of these phases is integral to the success of the software under development. Among these stages, requirement gathering and analysis, also known as requirement engineering, plays a pivotal role. This phase is critical because it ensures that the software aligns precisely with the customer's needs and requirements. It is during the requirement engineering process that customer needs are collected and thoroughly analysed. This phase holds great significance as the end user of the software is the customer. Therefore, it is imperative that the software caters to all of the customer's needs. This paper provides an overview of various requirement engineering approaches adopted by software development companies and organizations for gathering, comprehending, and addressing all sort of anomalies or inconsistencies in the collected requirements. Index Terms-Requirement Engineering, Ontology, Requirements collection, Requirement change management. I. INTRODUCTION Different Software Development Organization follows many different ways for Software development. Initially when the software where developed at early times without any strategies software always leads to software crisis, It was believed that Software Development Life Cycle (SDLC) model can be the solution for the software Crisis. Software development life cycle models follows series of activities initially from feasibility study i.e. studying the economical, technical, operational and legalfeasibilities of the software that will be developed. After the phase exit criteria of feasibility study , the software development goes to requirement gathering phase where the software requirement is gathered from the ultimate user and then the gathered requirement is analysed and on the basis of it SRS documentation is done that has function requirement, non-functional requirement and goals of implementation , then design phase where design document is maintained which includes low- level design and high level design, it also includes function oriented design and object oriented design, the next phase is the coding phase where the programmer adhere some common guide lines for writing the codes, the coding guidelines adhered is in such away that if any teams members change, the code should be clearly understandable. After coding is done and all syntax error is removed the code goes into code review technique which includes code walk through and code inspection. The next phase is testing phase which includes unit testing (testing individual models using drivers and stubs) then integration testing (integrating modules one by one and testing it individually) then is the system testing (testing software overall), the entire testing scenario includes two types of testing , black box testing where the internal structure of the module is not known testing is done to check in outer structure using equivalence class partitioning, boundary value analysis and clean room testing. The next type is the white box testing technique where the internal structure of the module is tested based on statement coverage, path coverage, branch coverage, condition coverage and many more. Finally when all validation and verification testing is done, then comes the maintenance phase which includes all the changes which the software company or organisation has to adhere if the organisation wants that software to be used for longer period of time, or software being developed doesn’t become the legacy product. So maintenance phase includes corrective, perfective and adaptive maintenance. Fig 1. Diagramm

FAQs

Why is requirement engineering critical in software development?

Requirement engineering ensures the developed software aligns precisely with customer needs. It collects and analyzes customer requirements and helps prevent inconsistencies in what the software must deliver.

What steps in SDLC are discussed before requirement engineering is addressed?

The paper describes feasibility study, requirement gathering and analysis (including SRS documentation), design, coding, code review, testing (unit, integration, system, black-box and white-box), and maintenance.

What challenges does requirement elicitation face according to the paper?

Key challenges include rich communication due to geographic and socio-cultural differences, semantic technologies leading to ontology concepts, managing dynamic requirement changes for iterative development, and lack of quantification, scalability, prioritization, and interdependency in collected requirements.

Sep 11, 2026

Uploaded by Mack Lee