Don't like ads? PRO users don't see any ads ;-)
Public Pastes
Guest

Untitled

By: a guest on May 4th, 2012  |  syntax: None  |  size: 4.44 KB  |  hits: 21  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
This paste has a previous version, view the difference. Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. \title{Requirements Contract}
  2. \author{
  3. Johannes Berdin
  4. \and
  5. Christoph Hirtz
  6. \and
  7. Andreas Mohr
  8. \and
  9. Mark Simkin
  10. \and
  11. Daniel Mohr
  12. \and
  13. Nicolas Mach
  14. }
  15. \date{\today}
  16.  
  17. \documentclass[12pt]{article}
  18.  
  19. \usepackage{enumerate}
  20.  
  21. \begin{document}
  22. \maketitle
  23.  
  24. \section{Must have}
  25.  
  26. \begin{itemize}
  27. \renewcommand{\labelitemi}{$\circ$}
  28. \item The application will have an event calendar, which will aggregate news related to the Saarland University from different local news sites. This calendar will also offer the possibility to filter/categorize the available events by predefined categories. The information stored in the event calendar will be available offline once it was downloaded by the application. In order to receive new information, an Internet connection is required.
  29.  
  30. \item A news feed will be available containing news, like press releases, related to Saarland University and CISPA. These news will be aggregated from existing news sites and it therefore requires an Internet connection to retrieve the information. Afterwards, this information will be available without a connection to the Internet, too.
  31.  
  32. \item A static information screen will show general "Getting Here" information, i.e. the directions to Saarland University. There should be information on how to get to the university by car and by bus. Therefore, the corresponding bus lines should be shown.
  33.  
  34. \item There will be a campus map, which will be available offline. On the map, points of interest, i.\,e.\ Parking, restaurants, bus stops, the user's own current position, ATMs, post boxes and shops will be highlighted.
  35.  
  36. \item It will be possible to see the mensa menu of the current week. This menu will contain the different available meals for each day. After retrieving the current week's menu, it can be viewed offline as well.
  37. \item The application source code will allow easy maintenance and extensibility.
  38.  
  39. \item The application will support all android versions starting from version 2.3 Gingerbread.
  40. \end{itemize}
  41.  
  42.  
  43.  
  44. \section{May have}
  45. \begin{itemize}
  46. \renewcommand{\labelitemi}{$\circ$}
  47. \item It may be possible to let the application calculate routes between the user and different points of interest or specific buildings on the campus in order to guide the users to their destination. This would require an internet connection as well as GPS positioning to get the current location of the user.
  48. \item There might be a searchable register of persons, containing information like office location, phone number and email address. This could be used in connection with the navigation function to direct the user to office of the person searched.
  49.  
  50.  
  51. \item There may be an interface which could be used to manually enter events to be displayed by the event screen on the phone. Event data includes time, location, date, etc.
  52.  
  53. \item It may be possible to categorize the news feed by faculties in order to only see the events that belong to a certain faculty.
  54.  
  55. \item Apart from the current mensa menu it may be possible to retrieve further data like the price of each meal.
  56.  
  57. \item In addition to the existing points of interest, other facilities like public restrooms may be shown on the map.
  58. \end{itemize}
  59.  
  60.  
  61.  
  62. \section{Must not have}
  63. \begin{itemize}
  64. \renewcommand{\labelitemi}{$\circ$}
  65. \item There will be no specific user interface optimization for tablets, i.e. there will be no graphics optimized for large screens of Android tablets.
  66.  
  67. \item It will not be possible to view the mensa food in 3D, nor will there be any information about the calorie content of each meal as this information is not available nor is it possible to acquire.
  68. \item There will be no Near Field Communication (NFC) support. In particular, there will be no possibility to use the NFC sensors of some of the newer mobile phones in order to access the data stored on the students' university card, due to security issues .
  69. \item There will be not routing inside of buildings, i.\,e.\ it will not be possible to be guided to a specific room by the application.
  70. \item The application will not support Android versions that are older than 2.3. Older versions are not used by the majority of android users and the additional effort and code complexity is not justified for such a small user base. Older versions would require specific new code passages because of their partly deprecated API.
  71. \item The static information screen will not show dynamic information like the current bus schedule.
  72. \end{itemize}
  73.  
  74.  
  75.  
  76. \end{document}
create a new version of this paste RAW Paste Data