Requirements analysis is one of the central challenges of software engineering: how do I determine the customer requirements completely, comprehensibly, without contradictions and correctly and also document them in such a way that I can use them as a basis for implementation and subsequent testing? A variety of project management methods exist to standardise the process of software development and formalise the process from requirements definition to acceptance testing. Depending on the process, the project participants are supported by various tools, forms and other aids to ensure orderly project progression.

The aim of this thesis is to evaluate which approaches exist for analysing requirements and how these are supported in practice. To this end, an overview of the topic of "requirements engineering" is first presented. The following concrete project and process models are then used to analyse the role of requirements analysis, how it is supported and what advantages and disadvantages result from it:

• Waterfall model
• Spiral model
• V-model
• V-model XT
• Prototype model
• Unified Software Development Process (USDP)
• Rational Unified Process (RUP)
• Feature Driven Development (FDD)
• Extreme Programming
• Scrum

It should also be shown how the role of requirements analysis changes over time in the various project models. Finally, a recommendation for best practices should be made, in which the advantages and disadvantages of the various approaches are combined and formulated as a recommendation.

If you are interested, please contact or .