Abstract
Requirement gathering for software development project is the most crucial stage and thus requirement engineering (RE) occupies the chief position in the software development. Countless techniques concerning the RE processes exist to make sure the requirements are coherent, compact and complete in all respects. In this way different aspects of RE are dissected and detailed upon. A comparison of RE in Agile and RE in Waterfall is expatiated and on the basis of the literature survey the overall Agile RE process is accumulated. Agile being a technique produces high quality software in relatively less time as compared to the conventional waterfall methodology. The paramount objective of this study is to take lessons from RE that Agile method may consider, if quality being the cardinal concern. The study is patterned on the survey of the previous research reported in the coexisting literature and the practices which are being pursued in the area.
Highlights
Software development methodology known as software development life cycle (SDLC) is a sectionalisation of software development work
Comparison of Agile and Waterfall Development Methods Agile and waterfall methods stand apart so far as their activities are concerned, as they are put to use within the development process [6]-[9]
Requirement engineering involves a number of processes for gathering requirements in accordance with the needs and demands of users and stakeholders of the software product
Summary
Software development methodology known as software development life cycle (SDLC) is a sectionalisation of software development work. Common methodologies include Waterfall, Prototyping, Iterative and Incremental development, Spiral development, Rapid application development, Extreme Programming and other different kinds of Agile methodology All these methods comprise of multiple phases and a variety of different activities. Waterfall method is understood for its concrete and complete requirements and these features make this approach more viable and stable It is often said about this method that spending more time early in the cycle can pave way to greater success at later stages. The Agile development method came to limelight as the result of gathering of seventeen representatives from the software development industry in snowbird, Utah in 2001 [3] Their intention was to develop innovative approaches to software development that would make organization react rapidly and adapt to volatile requirements and technologies. The remainder of the paper is organized as follows: Section 2 gives a comparison between traditional and Agile software development methodologies.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
