|Due at Thursday, November 5th, 11:00 am (before the lecture starts)|
In case there is a problem with your SVN account, we can help you more effectively if you worked through our SVN Troubleshooting guide.
In your group's repository you will find a file named
A01T01_HelloRepository.txt in the folder
A01_TowardsRequirementsElicitation. One after another you should check out this folder, add a friendly greeting to this file and commit it again.
It is not enough that we find each group members name in the file. The additions have to be made from the respective accounts.
Requirements should be correct, clear, consistent, and complete. The following task is meant to practice these four quality attributes, so that you have a better understanding about how these terms are used. Maybe you get as well a first idea about how to look for incorrect, unclear, inconsistent, and incomplete requirements.
Your colleague reviewed a requirements document and listed eleven sentences that are obviously not good. To classify the problems you are now asked to complete the table below that tells the other team members which quality is missing and explains it shortly.
Here are the eleven sentences from the requirements document:
Here is the table that you should complete. Your colleague already started with the work:
|(11)||Correctness||That's for sure not required. Although global warming is a serious issue, the contribution of printing receipts is clearly irrelevant.|
|(08) and ( _ )||Consistency|
|(02) and ( _ )||Clearness|
|(04)||How much do children have to pay when there is no public holiday?|
|( _ ) and (06)|
|( _ )|
|( _ )|
Your colleague collected three scenarios about reserving hotel rooms. She already rearranged them a bit, so that they are already very similar. Abstract (the flow of events of) a Use Case from these scenarios:
Use Case: Reserve Room