Requirements engineering and agile software development

Some Findings Concerning Requirements in Agile Methodologies

“…Although some authors assert that agile methodologies are just oíd wine in new bottles 3 , other studies show that product development in agile environments is very different to that in conventional environments [11,13,14,28]. Several experience reports, such as [29,30,31,32], describe success stories of using agile approaches.…”

“…This study proposes changes in the agüe requirement process, particularly in eXtreme Programming. Other publications, such as [20,13] identify some of the presented aspects in this paper but without going into them and point out the need to explicitly consider nonfunctional requirements management in Agüe. However, none of these studies had the opportunity of compare the result of an agüe and a conventional project referred to the same product as it is the case of this work.…”

“…The problem is not so much how to express these requirements but the impact that may have on the product if they are not introduced at the right development stage. Actually it might be thought that most oí the non-íunctional requirements should be known in the ñrst stages of the development [13]. Although agüe approaches contémplate an extensive use of refactoring techniques, the impact, e.g.…”

“…Other papers, such as [20,13,21,22,23,24] report some problems in this área but do not analyze them in depth. Some of the open issues in agüe methodologies concern elicitation of non-functional requirements and requirements documentation tasks.…”

“…In [13,14] the differences between requirements speciñcation in conventional and agüe approaches are analyzed. Conventional methodologies are focused on antícípatíon abítitíes and can be termed as plan based [15,16] because these process models are deñned in such a way that the later an error is discovered, the more expensive wül be to correct it.…”