Requirements analysis and modelling

The rapid change in the software engineering field, in particular the emerging of software development methodologies has relaxed the need for well definedness of the requirements. A primary characteristic of the process in developing a system with ill defined requirements is the iteration through one or more development phases before the requirements are clarified. By exposing end users to the problem of revising and iterating on a larger scale system design through several levels of the software life cycle, we are able to be more responsive to their evolving requirements as they gain experience in formulating critical system requirements. Iterative requirements elicitation and requirements elicitation have been tied closely to two techniques: object oriented modeling (analysis) and rapid prototyping. In the context of these observations the discussion focuses on the following two questions: Should object oriented modeling and design be the focus or should greater emphasis be placed on traditional structured analysis techniques that are more widely used in practice? How should prototyping be treated?.<
>