User Requirements DocumentVersion: 1.5

Project Team Sander Alewijnse 0649613Alex ten Brink 0655178Quirijn Bouts 0653010Xixi Lu 0654181Martin Rooijackers 0651077Rob Segers 0616788Janot Sijen 0652478Robin Wolffensperger 0612853

Project Manager Nicky Gerritsen

Quality Assurance Manager Edin Dudojevic

Senior Management Mark van den BrandLou Somers

Advisor Erik Luit

Customer Henny van Alphen

February 24, 2011

1

Abstract

This is the User Requirements Document (URD) for the inSEPtion project group.These user requirements were established according to requests formulated by inSEPtiontaking into account the wishes of our customer, Henny van Alphen, functional manager ofthe “Communicatie en Expertise Centrum” at Eindhoven University of Technology.It is written according to the Software Engineering Standard as set by the European SpaceAgency [2].

Contents

1 Introduction 51.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 List of definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 List of references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 General description 82.1 Product perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2 General capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2.1 Main application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2.2 Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2.3 Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.4 News . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.5 Encyclopedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.6 Handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.7 Facebook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.8 Twitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.9 Employee finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.10 Additional social media requirements . . . . . . . . . . . . . . . . . . . 92.2.11 Extendability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2.12 Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.3 General constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.4 User characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.4.1 Students . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.4.2 Application maintainers . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.5 Environment description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5.1 Other systems in the environment . . . . . . . . . . . . . . . . . . . . 112.5.2 Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.6 Assumptions and dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Specific requirements 133.1 Capability requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1.2 Main app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1.3 Map-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1

3.1.4 News-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.5 Agenda-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.6 Employee-finder-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1.7 Encyclopedia-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1.8 Student handbook-app . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1.9 Facebook-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1.10 Twitter-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3.2 Constraint requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.2 Map-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.3 News-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.4 Agenda-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.5 Person-finder-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.6 Encyclopedia-app . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.7 Studenthandbook-app . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2

Document Status Sheet

Document status overview

General

Document title: User Requirements DocumentIdentification: URDAuthor: Sander Alewijnse, Rob Segers, Robin WolffenspergerVersion: 1.5Document status: Approved

Document history

Version Date Reason for change

1.0 10-02-2011 Initial version

1.1 13-02-2011 Requirements edited and added

1.2 14-02-2011 Internal review

1.3 15-02-2011 Group comments

1.4 15-02-2011 Customer review 1

1.5 16-02-2011 Customer review 2

3

Document Change Records since previous issue

General

Document title: User Requirements DocumentIdentification: URD

Changes

Page(s) Paragraph(s) Action

All All Created

12-19 Chapter 3 Requirements edited and added

5-24 Title page, 1.3, 1.4, Chapter 2-3 Process remarks

5, 6, 12-23 1.3, 1.4, Chapter 3 Process group comments

5, 6, 12-23 1.3, 1.4, Chapter 3 Process customer comments

6, 9, 10,13, 16-23 1.3, 2.2, 3.1, 3.2 Process customer comments

4

Chapter 1

Introduction

1.1 Purpose

The user requirements document (URD) contains the requirements for insApption. Theserequirements are a negotiated agreement between the CEC at Eindhoven University of Tech-nology and inSEPtion. Listed requirements, and only these, will be implemented in in-sApption, according to their priorities. Any changes to these requirements require the fullconsent of both parties.

1.2 Scope

insApption is an application designed and developed by the inSEPtion project group forthe CEC at the Eindhoven University of Technology. The purpose of the application isto familiarize new students with the campus and facilities of the Eindhoven University ofTechnology. The application is made for a smart phone running Android version 2.3 andcontains several apps within it, such as a navigation device, news feed and student guide.The app is designed in such a way that it is easy to add new apps to the application.

1.3 List of definitions

Administrator Special user that maintains the application.Android Android is a mobile operating system.API An application programming interface (API) is a particular set of rules

and specifications that a software program can follow to access and makeuse of the services and resources provided by another particular softwareprogram that implements that API.

App(lication) A program or group of programs designed for end users.Calendar view A display in which all days of the selected month are shown chronologically.CEC “Communicatie en Expertise Centrum”.Edge A connection between two vertices (See vertex).ESA European Space Agency.Event Item in one of the feeds regarding the agenda of the TU/e.External resource Information maintained by third parties.

5

Facebook page A page on facebook.com. The information on such apage is maintained by a specific user such as the TU/e(http://www.facebook.com/TU.Eindhoven). It may also includemessages from other Facebook users.

Facebook status The status of a Facebook user, as presented to other users of Facebook onhis Facebook page.

GUI Graphical User Interface.Launcher An interface element to start an application or sub-application.Like ”Like” is a way to give positive feedback or to connect with things on

Facebook.Main-app(lication) The application that functions as a portal to the other sub-applications.Main menu Part of the main-app in which the launchers are shown.MediaWiki MediaWiki is a popular free web-based wiki software application. A wiki is

a website that allows the creation and editing of any number of interlinkedweb pages via a web browser.

MoSCoW model A prioritization technique used in software development to reach a com-mon understanding with the client on the importance they place on thedelivery of each requirement.

News item Item in one of the feeds regarding the TU/e news.Path A pair of geographical points, which are connected by a straight road.POI Point-of-Interest.RSS feed An RSS feed is a data format used for providing users with frequently

updated content (such as news and agenda information).Satellite (map) view A display of a map that consists of aerial photos.Sub-app(lication) An application, which can only be started by using a launcher in the

main-app.Stylistic (map) view A display of a map that does not consist of photos, but of lines, boxes,

etc.TU/e Eindhoven University of Technology.Tweet To post an update to a Twitter page.Twitter page A page on the social network site twitter.com. Information on such a page

consists of a list of so-called tweets. An example is the Twitter page ofthe TU/e (http://twitter.com/TUeindhoven).

Topic Item regarding a subject inside the Encyclopedia or Student Handbook.UCAR User Capability Requirement.UCOR User Constraint Requirement.URD User Requirements Document.User Student who uses the system and has no rights to modify the app.Vertex Geographical point that is important in the navigation process.

1.4 List of references

[1] CEC. TU/e corporate identity. http://www.tue.nl/nl/diensten/cec/huisstijl.Guidelines regarding layout and design.

[2] ESA Board for Software Standardization and Control (BSSC). European Space AgencySoftware Engineering Standards. February 1991.

6

[3] Android UI team. Android guidelines. http://developer.android.com/guide/practices/ui_guidelines/index.html.Guidelines regarding the User Interface.

[4] Twitter Development team. Twitter guidelines. http://developer.twitter.com/pages/display_guidelines.Guidelines regarding the layout of a “tweet”.

1.5 Overview

The remainder of this document discusses user requirements in general in chapter 2 and infull detail in chapter 3.

7

Chapter 2

General description

2.1 Product perspective

Within the TU/e there are many information systems. For students that have just arrivedhere, especially foreign students, it is not clear where they can find information about certainfacilities. Group inSEPtion will develop an application that will help guide students onthe campus. The application will use various information systems already available and addnew functionality. Another requirement is that the application should be adaptable and easymaintainable.

2.2 General capabilities

insApption will have the capabilities described below in order to provide students an easyoverview of the campus and its facilities.

2.2.1 Main application

The main application is a portal to all the other separate sub-application (sub-apps) whichwill provide the specific functionality, described in the following paragraphs. So calledsub-applications will have no interaction, not counting some minor exceptions. The sub-applications that are present in this main application should be maintainable, meaning newones can be added and existing ones can be modified or deleted easily by a qualified soft-ware maintainer. Furthermore the main language of the application will be English, (only)in the main application the language can be changed to Dutch and the other way around.Sub-applications will be shown depending on availability in the selected language.

2.2.2 Map

This sub-application provides a navigational assistance on the TU/e campus (+ the trainstation). Users should be able to search for a certain point of interest and navigate from aspecific location to another location. Locations can be entered in a text field and resolved to acertain building plus (if applicable) the floor and room number. Locations can also be selectedon the map. The map sub-application should provide a map view containing a map of thecampus on which the current position, buildings(and information about them),the plannedroute and the searched locations are shown.

8

2.2.3 Agenda

The agenda shows all upcoming events regarding the TU/e, as provided in various RSS-feeds.The events should be presented in a calendar form and should be searchable.

2.2.4 News

The news application shows all news items regarding the TU/e, as provided in a RSS-feed.

2.2.5 Encyclopedia

This sub-application provides an Android specific front-end for the encyclopedia of the TU/ethat is available as a MediaWiki. This includes a search functionality and a main-screen. Theencyclopedia sub-application is only available in the Dutch language.

2.2.6 Handbook

This sub-application enables students to read the student handbook. Users can also openlinks mentioned in the handbook. The handbook application is only available in the Dutchlanguage.

2.2.7 Facebook

The Facebook application directs students to the Facebook page of the TU/e. The Facebookpages are not necessarily written in one language. The TU/e page contains information bothin English and Dutch, hence we will present the same page for both selectable languages.Furthermore the users are able to view other Facebook pages related to the university.

2.2.8 Twitter

The Twitter application directs the students to the Twitter page of the TU/e. The Twitterpage is shown in the selected language. Furthermore the users are able to view other Twitterpages related to the university.

2.2.9 Employee finder

In this application it is possible to search personnel on the university. Information availablefrom the university servers about the searched person will be shown.

2.2.10 Additional social media requirements

It is possible to tweet about a certain subject inside the application. Furthermore it is possibleto use Facebook functionality meaning “like” and “share”.

2.2.11 Extendability

insApption will be extendable. This means that a skilled Java Android programmer shouldbe able to easily add a new sub-application to insApption, and add a launcher to it in themain-application.

9

2.2.12 Maintainability

insApption will be “easy” to maintain. Application maintainers should be able to maintainthe application, without having knowledge about Java Android programming. They shouldbe able to modify the approximate appearance of the application. This means the colors,and GUI figures in the applications, but not the addition/deletion of GUI elements. This canonly be done achieved by adding a complete new sub-application to insApption (See 2.2.11).The application maintainer should also be able to change the (lists of) information sourcesof the sub-applications: agenda, news, Facebook and Twitter (more on this in the section 3).The application maintainer should also be able to add/delete/modify the data used in themap-application.

2.3 General constraints

Some sub-applications rely heavily on specific services provided by third parties (employeedatabase, RSS-feeds, MediaWiki of encyclopedia), hence our means to search data are lim-ited and the external data cannot be modified. Furthermore group inSEPtion is bound byseveral guidelines (Twitter, Facebook, Android, corporate identity [1], etc.). First-time usersshould not have any difficulty getting familiar with insApption and further use should notcause any difficulties either.

2.4 User characteristics

There are two types of users that interact with the final product.

2.4.1 Students

This is the main target group of our application. They should be able to use the applicationwithout any problems and without any knowledge about the program. Students should onlybe able to (anonymously) retrieve information from the application, except for the social net-work functionalities (Twittering and using Facebook). For these social network functionalitiesthe user must have an already created Twitter and Facebook account. The application willhave the option to store the username and password for these accounts in order to preventthe user from entering them every time they tweet or use Facebook.

2.4.2 Application maintainers

The application maintainers (administrators) will maintain the application, but are assumedto have no knowledge about Java Android programming. These users might have to interactwith insApption in a different way from the students. The interaction may consist of editingfiles on a server, running a different special designed (by insApption) edit application to editremote files.

10

2.5 Environment description

2.5.1 Other systems in the environment

insApption must interface with several other systems. RSS-feeds, the web-version of theTU/e Encyclopedia, Facebook, Twitter, Google and the employee-pages database of the uni-versity are existing systems insApption is planned to interact with or make use of. Agraphical representation of the environment of insApption is shown in figure ??.

RSS-feedsThe primary goal of this system is to provide the news application and the agenda applicationwith information. The interaction with the RSS-feeds is one-way. The application will retrieveinformation via the internet and process it locally in order to display it in the two sub-apps.The most important RSS-feeds are the news feed and the agenda feed of the new TU/e site.

TU/e EncyclopediaThis system will provide the information shown in the encyclopedia application. The inter-action with this system will consist for sending queries to the MediaWiki of this encyclopediaand receiving the resulting information via the internet.

FacebookThis system has its own API and for performing “like” and other actions. Besides that theapplication can show the mobile site of Facebook.

TwitterThis system has its own API and for performing “tweet” and other actions. Besides that theapplication can show the mobile site of Twitter.

Employee-pages databaseThis system will provide the information shown in the employee finder application. Theinteraction with this system will consist of sending queries to the employee pages server andreceiving the resulting information via the internet.

GoogleThis system will provide insApption with their satellite images of the campus.

2.5.2 Platform

The application that students use will run on smart phones (with the operating system An-droid 2.3). The application maintainer will use a computer.

2.6 Assumptions and dependencies

• The application needs internet access.

• A webserver is available for insApption to store data on (done by application main-tainer) and retrieve data from (done by the students).

11

• The agenda RSS-feed has a certain fixed format from which the date of an event canbe parsed.

• The student handbook will be available in a format that is searchable and that is splitinto hierarchical sections, however the links may be outdated.

• The MediaWiki will not change.

• The API of Facebook will not change.

• The API of Twitter will not change.

• The access methods of the employee-pages database will not change.

• The TU/e Encyclopedia is available in the MediaWiki format.

• The design guidelines of Twitter, Facebook, Google and Android overrule the guidelinesof the corporate identity [1] in conflicting situations.

12

Chapter 3

Specific requirements

The specific requirements discussed in this section are divided into logical subsections. Forprioritizing the specific requirements for insApption, we will adhere to the MoSCoW model.The capital letters in MoSCoW stand for:M Must have; these requirements are essential for the product.S Should have; these requirements are not critical for the product to work, but are

nearly as important as the must haves, meaning they must be implemented if at allpossible.

C Could have; requirements which are not critical to the product’s success. If they canbe implemented with little development costs, they can increase customer satisfaction.

W Would have; these requirements will not be implemented in this project. However,they would be nice to have in future versions of the product.

The priority for each requirement is mentioned with the respective requirement.

3.1 Capability requirements

3.1.1 General

LanguageUCAR001 MAll text elements in the user interfaces are presented in the selected language (forlanguage selection see requirement UCAR101. The available languages are mentionedin UCAR002 and UCAR003).

UCAR002 MEnglish is an available language.

UCAR003 MDutch is an available language.

Program adaptabilityUCAR004 MSub-apps and their launchers can be added to the main app by a qualified programmer.

UCAR005 MSub-apps and their launchers in the main app can be deleted by a qualified program-mer.

13

Maintenance of user interfaceUCAR006 MThe administrator can change the colors used in the user interfaces of the sub-appsand main-app (this does not include the external resources).

UCAR007 MThe administrator can change the fonts used in the user interfaces of the sub-appsand main-app (this does not include the external resources).

UCAR008 MThe administrator can change icons used in the user interfaces of the sub-apps andmain-app (this does not include the external resources).

UCAR009 MThe administrator can change buttons used in the user interfaces of the sub-apps andmain-app (this does not include the external resources).

UCAR010 MThe administrator can change the background used in the user interfaces of the sub-apps and main-app (this does not include the external resources).

UCAR011 MThe administrator can change text elements used in the user interfaces of the sub-appsand main-app (this does not include the external resources).

3.1.2 Main app

UCAR101 MThe language can only be selected in the main app.

UCAR102 MThe default language of insApption is English

UCAR103 MThe main menu contains a launcher to the Map-app.3.1.3

UCAR104 MThe main menu contains a launcher to the News-app.3.1.4

UCAR105 MThe main menu contains a launcher to the Agenda-app.3.1.5

UCAR106 MThe main menu contains a launcher to the Facebook-app.3.1.9

UCAR107 MThe main menu contains a launcher to the Twitter-app.3.1.10

UCAR108 MThe main menu contains a launcher to the Employee-finder-app.3.1.6

UCAR109 MThe main menu contains a launcher to the Encyclopedia-app, only if the Dutch lan-guage is selected.3.1.7

UCAR110 MThe main menu contains a launcher to the Student handbook-app, only if the Dutchlanguage is selected.3.1.8

UCAR111 SIt is possible to “like” insApption from within the main menu.

14

UCAR112 SIt is possible to “tweet” insApption from within the main menu.

UCAR113 CThere is a link to a Twitter settings menu.

UCAR114 CThere is a link to a Facebook settings menu.

UCAR115 CIn the settings menu for Twitter the user can save username in combination withpassword, regarding Twitter.

UCAR116 CIn the settings menu for Facebook the user can save username in combination withpassword, regarding Facebook.

UCAR117 CIn the settings menu for Twitter there is an option to delete the saved username incombination with the password, regarding Twitter.

UCAR118 CIn the settings menu for Facebook there is an option to delete the saved username incombination with the password, regarding Facebook.

UCAR119 MThe application maintainer can modify the appearance of the separate launchers.

3.1.3 Map-app

UCAR201 MIt is possible to search for a certain building on the campus of the TU/e by name.

UCAR202 MIt is possible to search for a certain building on the campus of the TU/e by address.

UCAR203 SIt is possible to search for a certain POI on the campus of the TU/e by name.

UCAR204 MA search described in requirements UCAR201 and UCAR202 results in a displayedset of buildings that match the search input.

UCAR205 SA search described in requirements UCAR203 results in a displayed set of POI’s thatmatch the search input.

UCAR206 SIt is possible to view an element from the search result described in UCAR201,UCAR202 and UCAR203 in the map view.

UCAR207 MIt is possible to navigate from a building on the campus to another building on thecampus.

UCAR208 SIt is possible to navigate from a building on the campus to a POI on the campus.

UCAR209 SIt is possible to navigate from a POI on the campus to a building on the campus.

UCAR210 SIt is possible to navigate from a POI on the campus to a POI on the campus.

15

UCAR211 SIt is possible to navigate from an POI on the campus to another location on thecampus.

UCAR212 MIt is possible to navigate from a street on the campus to another location on thecampus.

UCAR213 WIt is possible to switch between different means of transportation in the navigator.

UCAR214 MThe from-location can be searched by the name of a building.

UCAR215 MThe from-location can be searched by the address of a building.

UCAR216 SThe from-location can be searched by the name of a POI.

UCAR217 MThe from-location is selected from the search result described in UCAR211 andUCAR212.

UCAR218 MThe from-location can be selected on the map.

UCAR219 MThe to-location can be searched by the name of a building.

UCAR220 MThe to-location can be searched by the address of a building.

UCAR221 SThe to-location can be searched by the name of a POI.

UCAR222 MThe to-location is selected from the search result described in UCAR215 andUCAR216.

UCAR223 MThe to-location can be selected on the map.

UCAR224 MThe route planned by the navigator is shown in the map view.

UCAR225 MThe application has a map view in stylistic style.

UCAR226 MThe application has a map view in satellite style.

UCAR227 MIt is possible to switch between stylistic map view and satellite map view.

UCAR228 MIt is possible to zoom when in the map view.

UCAR229 MIt is possible to pan when in the map view.

UCAR230 MCurrent location is shown in the map view.

UCAR231 SPOI’s of a building are indicated.

16

UCAR232 CIt is possible to “tweet” the user’s current location.

UCAR233 CIt is possible to change the status on Facebook. The new status will indicate theuser’s current location.

UCAR234 MThe administrator can change the stylistic map.

UCAR235 MThe administrator can add buildings.

UCAR236 MThe administrator can remove buildings.

UCAR237 MThe administrator can add vertices of a path which is used in the route planner.

UCAR238 MThe administrator can remove vertices of a path which is used in the route planner.

UCAR239 MThe administrator can remove edges of a path which is used in the route planner.

UCAR240 MThe administrator can add edges of a path which is used in the route planner.

UCAR241 SThe administrator can add POI’s. A POI should belong to a certain building, floorand room number.

UCAR242 SThe administrator can remove POI’s. A POI should belong to a certain building,floor and room number.

UCAR243 SThe administrator can link a POI to a certain building, floor and room.

UCAR244 SThe administrator can unlink a POI from a certain building, floor and room.

3.1.4 News-app

UCAR301 MTitles of all news items available through the news RSS-feeds are shown on the titlescreen.

UCAR302 MFrom the first titles of the news articles, the first lines are shown.

UCAR303 MFull news report is shown after choosing the corresponding news title.

UCAR304 CIt is possible to “like” a certain news item.

UCAR305 CIt is possible to “tweet” a certain news item.

UCAR306 MThe administrator can modify the list of news RSS-feeds that are available in English.

UCAR307 MThe administrator can modify the list of news RSS-feeds that are available in Dutch.

17

3.1.5 Agenda-app

UCAR401 MWhen the agenda-app is started, upcoming events are shown on the title screen.

UCAR402 SThere is a calender view.

UCAR403 SIt is possible to open calendar view.

UCAR404 SIt is possible to close calendar view.

UCAR405 SThe user can change the calender to a different month.

UCAR406 SThe user is able to see on which days events take place in calendar view.

UCAR407 SThe current day is indicated on the calendar.

UCAR408 SBy selecting a certain day in the calendar the events for that day are shown.

UCAR409 MIt is possible to search for events by date.

UCAR410 MIt is possible to search for events by subject.

UCAR411 MA search described in requirements UCAR406 and UCAR407 results in a displayedset of events that match the search input.

UCAR412 CIt is possible to “like” a certain event.

UCAR413 CIt is possible to “tweet” a certain event.

UCAR414 MThe only events that are available in the agenda-app are extracted from the agendaRSS-feeds in the selected language.

UCAR415 MThe administrator can modify the list of agenda RSS-feeds that are available in En-glish.

UCAR416 MThe administrator can modify the list of agenda RSS-feeds that are available in Dutch.

18

3.1.6 Employee-finder-app

UCAR501 MIt is possible to search a person by name.

UCAR502 CIt is possible to search a person by department.

UCAR503 MA search described in requirements UCAR501 and UCAR502 results in a displayedset of employees that match the search input.

UCAR504 MIt is possible to view all personal info available through the employee pages of a personin the search result set of requirement UCAR503.

UCAR505 CIt is possible to show the location of the employee’s office in the map view (see 3.1.3).

UCAR506 CIt is possible to plan a route to the location of the employee’s office (see 3.1.3).

3.1.7 Encyclopedia-app

UCAR601 MWhen the Encyclopedia-app is started the most searched items are shown on the titlescreen.

UCAR602 MWhen the Encyclopedia-app is started the most recent items are shown on the titlescreen.

UCAR603 MIt is possible to search the book by a certain word or phrase.

UCAR604 MA search described in requirement UCAR602 results in a displayed set of topics.

UCAR605 MThe user can select a topic from the search result list.

UCAR606 MBy clicking on a topic the full text regarding that topic is shown.

UCAR607 CIt is possible to “like” a certain topic.

UCAR608 CIt is possible to “tweet” a certain topic.

19

3.1.8 Student handbook-app

UCAR701 MWhen the student handbook-app is started the most searched items are shown on thetitle screen.

UCAR702 MIt is possible to search the book by a certain word or phrase.

UCAR703 MA search described in requirement UCAR702 results in a displayed set of topics.

UCAR704 MThe user can select a topic from the search result described in requirement UCAR703.

UCAR705 MBy clicking on a topic the full text regarding that topic is shown.

UCAR706 CIt is possible to “like” a certain topic.

UCAR707 CIt is possible to “tweet” a certain topic.

3.1.9 Facebook-app

UCAR801 MWhen the Facebook-app is started the page of TU/e on Facebook is shown on thetitle screen.

UCAR802 MOther TU/e related Facebook-sites can be selected from a list (see for contents of listrequirement UCAR803).

UCAR803 MThe administrator can modify the list of TU/e related Facebook-sites.

3.1.10 Twitter-app

UCAR901 MWhen the Twitter-app is started the page of TU/e on Twitter is shown on the titlescreen.

UCAR902 MOther TU/e related Twitter-sites can be selected from a list (see for contents of listrequirement UCAR903).

UCAR903 MThe administrator can modify the list of TU/e related Twitter-sites.

20

3.2 Constraint requirements

3.2.1 General

UCOR001 MThe app runs on a smart phone with operating system Android version 2.3.

UCOR002 MAll layout shall be according to the TU/e corporate identity [1], unless in conflictwith the guidelines of requirements UCOR003-UCOR006.

UCOR003 MIcons are according to the Android Icon Guidelines.[3]

UCOR004 MThe user interfaces should be according to the Android User Interface Guidelines.[3]

UCOR005 MThe Twitter ”tweet” interface should be according to the Twitter Guidelines.[4]

UCOR006 MThe Facebook ”like” interface should be according to the Facebook Guidelines.

3.2.2 Map-app

UCOR201 MThe campus map covers the campus of the TU/e.

UCOR201 MThe campus map covers the central train station of Eindhoven.

UCOR202 MA new stylistic map has the right dimensions.

UCOR202 MA new stylistic map is geographically correct.

3.2.3 News-app

UCOR301 MNews is restricted to what is available in the feeds on the list of news RSS-feeds.

3.2.4 Agenda-app

UCOR401 MAgenda is restricted to what is available in the feeds on the list of agenda RSS-feeds.

3.2.5 Person-finder-app

UCOR501 MInformation about a certain person is restricted to what is available on the employeepages of the TU/e.

3.2.6 Encyclopedia-app

UCOR601 MThe information and the search methods of the Encyclopedia-app are restricted tothe services provided by the MediaWiki of the TU/e Encyclopedia.

21

3.2.7 Studenthandbook-app

UCOR701 MThe information and the search methods of the Studenthandbook-app are restricteddepending on file format of the handbook-information.

22