Graciela D. S. Hadad

Enhancing a requirements baseline with scenarios

Scenarios are well recognised as an important strategy towards understanding the interface between the environment and the system as well as a means of eliciting and specifying software behaviour. We adopt a broader view of scenarios. For us, a scenario is an evolving description of situations in the environment. Our proposal is framed by Leite’s work on a client-oriented requirements baseline, which aims to model the external requirements of a software system and its evolution. Scenarios start by describing the environment situations, according to the main actions performed outside the software system. Scenarios also help to clarify the interrelation between functional and non-functional requirements. We have validated our strategy and the related representations based on case studies.

Requirements Authorship: A Family Process Pattern

Different contexts determine a different software process. This is especially true for requirements production. Different situations in a given universe of discourse will require different requirements processes. This paper proposes a family pattern that approaches the universe of discourse (context) from the viewpoint of whom are the actors demanding the software. We show five different instantiations of this pattern.