Practical Course Advanced Networking (Summer 2015) - Revision history

Dkoll: /* Schedule */

2015-06-15T11:11:40Z

Schedule

← Older revision		Revision as of 13:11, 15 June 2015
Line 58:		Line 58:
	* '''13/14 May, 28 May, 11 June, 25 June, 9 Jul''': Further bi-weekly meetings		* '''13/14 May, 28 May, 11 June, 25 June, 9 Jul''': Further bi-weekly meetings
	** status updates		** status updates
	* '''~~TBA May/June~~''': Mid-term presentation:		* '''July''': Mid-term presentation:
	** Milestones to be achieved: API implemented, small test application		** Milestones to be achieved: API implemented, small test application
	* '''TBA September''': Final presentation:		* '''TBA September''': Final presentation:
	** Milestones to be achieved: Protocol implemented, demo application		** Milestones to be achieved: Protocol implemented, demo application
	** Time limit: 20 minutes + 5 minutes discussion		** Time limit: 20 minutes + 5 minutes discussion

Dkoll: /* Topics */

2015-04-16T14:38:46Z

Topics

← Older revision		Revision as of 16:38, 16 April 2015
Line 63:		Line 63:
	** Milestones to be achieved: Protocol implemented, demo application		** Milestones to be achieved: Protocol implemented, demo application
	** Time limit: 20 minutes + 5 minutes discussion		** Time limit: 20 minutes + 5 minutes discussion

	~~== Topics ==~~

	~~In this semester, we limit the topics to the following:~~

	~~{\| align="center" class="wikitable sortable" {{Prettytable}}~~
	\|-
	~~\|{{Hl2}} \|'''Topic'''~~
	~~\|{{Hl2}} \|'''Description'''~~
	~~\|{{Hl2}} \|'''Students'''~~
	\|-
	~~\| Server implementation~~
	~~\| TBD~~
	~~\| TBD~~
	\|-
	~~\| Client implementation~~
	~~\| TBD~~
	~~\| TBD~~
	\|-
	\| Application and GUI Design*
	~~\| TBD~~
	~~\| TBD~~
	\|-
	\|}

	* There can be more topics in this category, depending on the student count.

Dkoll: /* Schedule */

2015-04-16T14:38:08Z

Schedule

← Older revision		Revision as of 16:38, 16 April 2015
Line 51:		Line 51:

	==Schedule==		==Schedule==
			(Current phase is highlighted)
	* '''16 April, 14:00-16:00''': Kick-off meeting		* '''16 April, 14:00-16:00''': Kick-off meeting
	** Introduction to the course, selection of topics, formation of teams, and discussion of open questions		** Introduction to the course, selection of topics, formation of teams, and discussion of open questions
	* '''30 April, 28 May, 11 June, 25 June, 9 Jul''': Bi-weekly meetings		{{Announcement\| '''30 April, 14:00-16:00''': First bi-weekly meeting
	** ~~Each team gives a~~ status ~~update on their subproject~~		* Milestones to be achieved: Decided on which sensors to extract; Having a plan of how the API will look like}}
	** Time limit: 10 minutes per team, including discussion		* '''13/14 May, 28 May, 11 June, 25 June, 9 Jul''': Further bi-weekly meetings
			** status updates
	* '''TBA May/June''': Mid-term presentation:		* '''TBA May/June''': Mid-term presentation:
	** ~~Each team gives a review of work done and work~~ to be ~~done in the second half of the semester~~		** Milestones to be achieved: API implemented, small test application
	** Time limit: ~~10 minutes per team + 5 minutes discussion~~
	** You can re-use material from your earlier status updates here
	* '''TBA September''': Final presentation:		* '''TBA September''': Final presentation:
	** ~~Each team presents the work done~~		** Milestones to be achieved: Protocol implemented, demo application
	** Time limit: 20 minutes ~~per team~~ + 5 minutes discussion		** Time limit: 20 minutes + 5 minutes discussion

	== Topics ==		== Topics ==

Dkoll: /* Course description */

2015-02-17T12:09:10Z

Course description

← Older revision		Revision as of 14:09, 17 February 2015
Line 31:		Line 31:
	Possible applications are, for instance, smart cities, in which the use of mobile phones as sensors can increase the sustainability of rural areas.		Possible applications are, for instance, smart cities, in which the use of mobile phones as sensors can increase the sustainability of rural areas.

	In this course, students will - under supervision - implement such a crowd sensing system. We will have different tasks to complete, ranging from client/server infrastructure implementation to sensor analysis and the design of user applications and their GUIs.		In this course, students will - under supervision - implement such a crowd sensing system. We will have different tasks to complete, ranging from client/server infrastructure implementation to sensor analysis and the design of user applications and their GUIs. Each team will work on a different task and grades will not be influenced by the performance of the other groups.

	Outcomes of the course may result in publications at well-known research venues, which the students are then invited to attend.		Outcomes of the course may result in publications at well-known research venues, which the students are then invited to attend.

	An example of a crowd sensing system in action can be found on [https://www.youtube.com/watch?v=vrKLOGSOVYk on Youtube]		An example of a crowd sensing system in action can be found on [https://www.youtube.com/watch?v=vrKLOGSOVYk on Youtube]


	==Organization==		==Organization==

Dkoll: /* Passing requirements */

2015-02-17T12:04:59Z

Passing requirements

← Older revision		Revision as of 14:04, 17 February 2015
Line 47:		Line 47:

	==Passing requirements==		==Passing requirements==
	* Present your topic and '''demonstrate your project''' at the end of this course (70%)		* Actively participate in the project communication (20%)
			* Present your topic and '''demonstrate your project''' at the end of this course (50%)
	* Prepare a '''written report''' on the selected topic (12-15 pages, Template:[ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip]) (30%)		* Prepare a '''written report''' on the selected topic (12-15 pages, Template:[ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip]) (30%)
	* It is mandatory for all students to '''stick to the deadlines''' mentioned in [[#Schedule]]'''.

	==Schedule==		==Schedule==

Dkoll: Created page with "== Details == {{CourseDetails |credits=180h, 6 ECTS |module=M.Inf.805.6C: Fortgeschrittenenpraktikum Computernetzwerke (6C), M.Inf.1800.Mp: Fortgeschrittenen Praktikum Computerne..."

2015-02-17T12:03:43Z

Created page with "== Details == {{CourseDetails |credits=180h, 6 ECTS |module=M.Inf.805.6C: Fortgeschrittenenpraktikum Computernetzwerke (6C), M.Inf.1800.Mp: Fortgeschrittenen Praktikum Computerne..."

New page

== Details ==
{{CourseDetails
|credits=180h, 6 ECTS
|module=M.Inf.805.6C: Fortgeschrittenenpraktikum Computernetzwerke (6C), M.Inf.1800.Mp: Fortgeschrittenen Praktikum Computernetzwerke
|lecturer=[http://user.informatik.uni-goettingen.de/~dkoll Dr. David Koll],[http://www.net.informatik.uni-goettingen.de/people/stephan_sigg Dr. Stephan Sigg]
|ta=[http://www.net.informatik.uni-goettingen.de/people/lingjun_pu Lingjun Pu, MSc]
|time=start:April 16, 2015, 14:00-16:00
|place=IfI 3.101
|univz=[https://univz.uni-goettingen.de/qisserver/rds?state=verpublish&status=init&vmfile=no&publishid=156366&moduleCall=webInfo&publishConfFile=webInfo&publishSubDir=veranstaltung]
|
}}

==Prerequisites==
Solid knowledge in computer networks (e.g., obtained by attending the course "Computer Networks")
Solid object-oriented programming knowledge including networking techniques like sockets (preferably in JAVA)
Ideally, you have experience in Android Programming (however, not necessary for all projects)

==Course description==
The course is designed to provide students with the opportunity to enhance their programming skills in the network context.
For that, participating students can form teams of two to three students to tackle a particular problem.
Here, the problem can be chosen from a list of available topics.
In the past, students have created mobile phone apps to share rides on a train,
have investigated the propagation of wireless signals or have
implemented research simulators.

This semester, the Practical Course Advanced Networking will take a different approach than in previous editions.
Instead of working on disjoint topics, student teams will cooperate within a larger project in the area of ''crowd sensing''.

Crowd sensing is an emerging research area that deals with using mobile phones as sensors.
The advantages of using smartphones over classical sensors range from more computational and communication resources to multi-modal sensing capabilities.
Possible applications are, for instance, smart cities, in which the use of mobile phones as sensors can increase the sustainability of rural areas.

In this course, students will - under supervision - implement such a crowd sensing system. We will have different tasks to complete, ranging from client/server infrastructure implementation to sensor analysis and the design of user applications and their GUIs.

Outcomes of the course may result in publications at well-known research venues, which the students are then invited to attend.

An example of a crowd sensing system in action can be found on [https://www.youtube.com/watch?v=vrKLOGSOVYk on Youtube]

==Organization==
===Informational meeting===
We will have bi-weekly status update meetings.
These meetings are usually short if everything goes well ;)

===Course teams===
Students conduct this course in small teams. A team consists of at most three students.

==Passing requirements==
* Present your topic and '''demonstrate your project''' at the end of this course (70%)
* Prepare a '''written report''' on the selected topic (12-15 pages, Template:[ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip]) (30%)
* It is mandatory for all students to '''stick to the deadlines''' mentioned in [[#Schedule]]'''.

==Schedule==
* '''16 April, 14:00-16:00''': Kick-off meeting
** Introduction to the course, selection of topics, formation of teams, and discussion of open questions
* '''30 April, 28 May, 11 June, 25 June, 9 Jul''': Bi-weekly meetings
** Each team gives a status update on their subproject
** Time limit: 10 minutes per team, including discussion
* '''TBA May/June''': Mid-term presentation:
** Each team gives a review of work done and work to be done in the second half of the semester
** Time limit: 10 minutes per team + 5 minutes discussion
** You can re-use material from your earlier status updates here
* '''TBA September''': Final presentation:
** Each team presents the work done
** Time limit: 20 minutes per team + 5 minutes discussion

== Topics ==

In this semester, we limit the topics to the following:

{| align="center" class="wikitable sortable" {{Prettytable}}
|-
|{{Hl2}} |'''Topic'''
|{{Hl2}} |'''Description'''
|{{Hl2}} |'''Students'''
|-
| Server implementation
| TBD
| TBD
|-
| Client implementation
| TBD
| TBD
|-
| Application and GUI Design*
| TBD
| TBD
|-
|}

* There can be more topics in this category, depending on the student count.