TFH Berlin Fachbereich Informatik Medieninformatik SA31: Systemanalyse / SWT1: Softwaretechnik 1 Wintersemester 2000/2001

Lab 5: Requirements Elicitation

1. Consider the scenario you wrote in Lab 4/Exercise 5. Identify the actor of the scenario. Next, write the corresponding use case SetTime. Include all cases, and include setting the time forward, backward, setting hours, minutes, and seconds.
2. Assume the watch system you described also supports an alarm feature. Describe setting the alarm time as a self-contained use case named SetAlarmTime.
3. Examine the SetTime and SetAlarmTime use cases you wrote in Exercises 2 and 3. Eliminate any redundancy by using an include relationship. Justify why an include relationship is preferable to an extend relationship in this case.
4. Explain why multiple-choice questionnaires, as a primary means of extracting information from the user, is not effective for eliciting requirements.
5. From your point of view, describe the strengths and weaknesses of users during the requirements elicitation activity. Describe also the strengths and weaknesses of developers during the requirements elicitation activity.
6. (To be done after the break at 10.00) Define the term "menu". Write your answer on a piece of paper and put it upside down on the table toghether with the definitions of the rest of your row. Compare all the definitions and discuss any substantial difference.
   

The URL pointing to your report is due in my mailbox by 8:00 am the morning of your next exercise.