Requirements Specification Project

<p>
<h1> Requirements Specification Project</h1>

 Many new technologies are becoming available, such as multi-touch surfaces or augmented reality. 
Your team has 
been selected to conduct analysis, planning, and development of an example application on some of the new and emerging 
technologies. End users will be senior citizens of age >60 living in 
care-houses. <br><br> Your task is to:

<ul>
 <li>Analyze the possibilities and challenges of the new technology, and 
the problems associated with interaction and deployment of the technology. 
 <li>Identify the customers/users, enrironment and collect their needs. The user description will be a part of the 
document. This is an internal project and you need to employ 
brainstorming and/or stroyboarding to elicit requirements. If however you manage to employ a real potential user 
with matching profile, you 
will earn extra point.
 <li>State the problems clearly and specifically.
 <li>Analyze the problems rigorously: Fill the gaps for "The problem of 
xxxxx", "Affects xxxxx", "and results in xxxxx". "Benefits of the 
solution xxxxx".  
 <li>Derive the features of the intended system. Prioritize.
 <li>Publish the initial version of the features, and drop the document and link to the teachers. Deadline: 
9.12.2009 
16:00. Continue on the work immediately. 
 <li>Describe the system as a set of use case models (2-4). 
 <li>Optional (extra point): Write a Vision document as a user story, including a detailed description of three most 
important use cases. Publish.
 <li>Collect requirements specification. You can use any template (give reference), or some of the following:<br>
    <ul>
     <li> http://cs.joensuu.fi/pages/intra/tSoft/suojattu/vm.htm, in Finnish
     <li> IEEE Software Requirements Specification, use google to find it out.
     <li> Requirements Templates at http://www.construx.com/Page.aspx?hid=1626
   </ul>
 <li> Based on the requirements and use cases, create test cases with expected outcomes. 
 <li> The deadlines for the complete document will be 15.12.2009.
</ul>

<h2>Target applications</h2>
 
1) <b>A multitouch newspaper reader interface </b>that 
allows users to interact with newspaper in a traditional fashion, e.g. 
using gestures, but also benefits from the computerized environment 
(video news, comments on the news, scrapping of the news, to name few). In addition, the realtime connection allows to 
update the news, provide more information, browse older issues, interact with the editors 
and other users. 
<br>
2) <b>Other multitouch application for senior users</b> of your choice. 
Negotiate the topic with teachers.

<h2>Guidelines - continuously updated!</h2> 
 <ul>
  <li> Use simple language (English), avoid convoluted language. It is cost-effective to write requirements that are easy to read and understand.
  <li> Use diagrams when appropriate.
  <li> Aim at quantitative description of requirements.
  <li> Consider the diverse backgrounds of the users of the document. 
  <li> Review the document continuously, aim at consistency.
  <li> It is very likely that during the development changes will occur 
that will affect the requirements. prepare the document so that changes 
can be maintained. 
 </ul> 
 
<br>
Assessment: The requirements specification should be (according to IEEE standard): Correct, Unambiguous, Complete, Consistent, Ranked for importance and stability, Verifiable, Modifiable, Traceable. 
</p>