Unit 4 Flashcards
Suggest a business rule that constrains overlapping reservations made by the same person.
Overlapping reservations made by the same person are allowed only if the guest names are different, or at least distinguished from one another.
In the Volere template in Section 6, we recorded some non-functional requirements. What further work is needed in order to produce the software requirements?
We need to
remove any ambiguities and
add clear fit criteria.
Additionally, we need to
identify which functional requirements they constrain;
in some instances, they will apply to whole use cases. Often we will need to consult the system stakeholders for further details.
What else needs to be done in terms of non-functional requirements?
We should look at each of the functional software requirements in turn, and consider whether there are any non-functional requirements that apply to them but have been omitted. We should not assume that the stakeholders will supply a complete set of requirements, so cross-checks such as these are essential.
Is it also necessary to check the non-functional software requirements against the original user requirements?
Yes. For example, as well as simply missing explicit non-functional requirements in the template, there might well be non-functional requirements implied under product constraints.
Is it possible that elaborating the functional requirements as above might require us to revise our non-functional requirements? What if we were to add new functional requirements?
Yes, in both cases. There may well be constraints on the added functionality that are not covered by the existing non-functional requirements.
Can elaboration of our software requirements lead to inconsistencies? Give an example.
Yes. For example, if we add sufficient extra functionality, the time taken by the system to carry out the necessary work might mean we are unable to satisfy the time constraint in usability requirement U1.
