SDA SE Wiki
Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering
User Tools
Sidebar
Table of Contents
Assignment 1: Towards Requirement Elicitation
| Due at Thursday, November 5th, 11:00 am (before the lecture starts) |
|---|
If you face technical difficulties or have problems understanding the assignment, ask us for help!
In case there is a problem with your SVN account, we can help you more effectively if you worked through our SVN Troubleshooting guide.
You can mail to one of the tutors, Matthias bartsch@cs.uni-bonn.de or Boris jentsch@cs.uni-bonn.de.
For all tasks you find a template for the solution already in your repository in the folder
A01_TowardsRequirementsElicitation.
Task 1: Hello Repository
| 2 points |
|---|
Since some SVN accounts were not working early enough, you can still get the points for this task. We expect you to do this task!
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.
The text in the file gives you some information as well : (Click to expand)
It is not enough that we find each group members name in the file. The additions have to be made from the respective accounts.
Task 2: Distinguish between Completeness, Consistency, Clearness, Correctness
| 3 points |
|---|
The terms “Completeness”, “Consistency”, “ Clearness”, and “Correctness” are motivated and defined on the slides 24-28 of the last lecture (accessible using your SVN account). If you are interested in more details and explanation you might consult the standard IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements Specifications (accessible from within the university network).
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:
- (01) As it is customary the bill shows the total amount due excluding VAT.
- (02) For parties who plan difficult negotiations, two extra rooms next to the conference room are offered for half the price of the conference room.
- (03) The check out has to be acknowledged.
- (04) During public holidays, children accompanied by their parents pay only a forth of the amount their parents pay.
- (05) The stay can be longer than reserved. In this case the total amount due is the product of the fee for the rooms and the number of nights the guest stayed.
- (06) The deposit for a reservation is exactly a third of the total amount due on the final bill when the customer checks out.
- (07) On the back of each receipt printed there is a recipe printed.
- (08) The total amount due on the bill includes VAT.
- (09) Bunks are not provided.
- (10) The regular fee for parties is $500 per evening. A firework at the end of the party can be booked for $100 extra.
- (11) To raise awareness of current ecological issues the carbon footprint of printing a receipt will be printed on each receipt.
Here is the table that you should complete. Your colleague already started with the work:
| Sentence(s) | Missing Quality | Explanation |
|---|---|---|
| (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 | |
| (03) | Completeness | |
| (04) | How much do children have to pay when there is no public holiday? | |
| ( _ ) and (06) | ||
| ( _ ) | ||
| ( _ ) |
Task 3: Abstract a Use Case from Scenarios
| 2 points |
|---|
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
- The customer selects to reserve a room.
- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
- The system displays the reservation confirmation number and check-in instructions.
- The use case terminates.
teaching/lectures/atsc/2009/assignment_1.txt · Last modified: 2018/05/09 01:59 (external edit)
Page Tools
