Requirements Engineering 2009 demos 4

<h1>Requirements Engineering 2009 demos 4</h1>
<p>
Tasks marked X are compulsory. Answers need to be ready on/before the demo session. 
Send the answers to the demo teacher by email.<br>


<h2>Task 1 X</h2>
Last week one of tasks contained creating a list of requirements for a 
ticket selling system. The customers were excited to see the 
possibilities, but now they wish some extra features. These include:
<ul>
<li> No cash acceptance, since the robery attacks against the machines 
have been recently increasing. Cards can still be accepted.
<li> Paying by a mobile phone sms or call, option for extending the 
time by the phone. 
<li> Sending a reminder of nearly expired parking time to the number 
that paid the ticket. If paid by a card, option for extending the time 
automatically will be displayed at the time of paying.
</ul>

Decribe the new features as requirements (max 10). You do not need to aim at 
completeness and perfect coverage. However, at least one requirement 
should be related to the usability of the system.<br>

Document, what changes you did to the document and how the introduction of 
new requirements changed the SRS characteristics. <br><br>
Prioritize the requrements in the following way: estimate 1) the relative 
benefit (1-9), 2) relative penalty if the requirements is missing (1-9), 3) 
relative cost of implementation (1-9). The priority can be calculated as a total value of 
1) + 2) - 3) using weights (e.g. 1, 0.5, 2). Alternatively, you can search 
for other models for priorization. 

</p>

<h2> Task 2 </h2>
<p>
Read the following document and validate the list of requirements from 
Task 1: <a 
href="http://www.stsc.hill.af.mil/crosstalk/2002/04/florence.html">Reducing Risks Through Proper Specification of Software 
Requirements</a> according to the critical attributes introduced in the 
text.<br>

Read the examples and consider your own requirements.

</p>