Chair for Applied Software Engineering Prof. B. Brügge, Ph. D.
Software Engineering Exercise, SoSe 2009 Exercise 3 - (due May 13th)
1/1
Requirements Change and Object Design Exercise
1) Requirements Change
In any realistic project, requirements are subject to change. Reasons can be incompleteness of requirements, misinterpretations in the elicitation, better
understanding of the application domain or simply a change of mind by the client.
We are your clients and we have changed our minds. We have changed the
requirements you are currently implementing just before the 3rd exercise session. Try to find out, which requirements have changed. Write down the names of the changed requirements, indicate how you found out which requirements were changed and hand them in as paper homework. Change your implementation to cover the changed
requirements.
Hint: You can use the document exporter to export single requirements, just right-click the requirement in question and select “Export”.
2) Your Object Design
Create a UML Class diagram of the object design of your requirements validator and the test cases in your Unicase project. Also hand in a printed version of the diagram with your paper homework.
Hint: The document export can also create a pdf from a diagram.
3) Help Us Improving Unicase
Please give a separate answer for every team member for each question.
Question 1: How difficult was it to find the specification, i.e. the functional requirement for every action item?
1: very hard to find 2: quite hard to find
3: adequately findable / I don’t know 4: quite easy to find
5: very easy to find
Question 2: How did you find the functional requirement that was changed?
1: History Browser 2: Dashboard
3: Browsing all requirements
4: Other: please note down how you found out!
