Student group programming project - Revision history

Vimala at 12:42, 12 September 2019

2019-09-12T12:42:10Z

← Older revision		Revision as of 12:42, 12 September 2019
Line 1:		Line 1:
	The project shall develop an emergency management application using big data technologies and social media data. Development and run-time		The project shall develop an emergency management application using big data technologies and social media data. Development and run-time platform is a free choice, as is a programming language. The project should be carried out in groups of three. Working individually is allowed only if you come up with your own proposal.
	~~the~~ platform is a free choice, as is a programming language. The project should be carried out in groups of
	> three. Working individually ~~or in pairs~~ is ~~not recommended~~.

	This autumn, we specifically invite projects that are related to emergency management.		This autumn, we specifically invite projects that are related to emergency management.

	== Finding a project idea ==		== Finding a project idea ==
	'''Optional deadline:''' Friday September ~~21st~~		'''Optional deadline:''' Friday September 27th.

	I invite informal, non-mandatory suggestions for programming project ideas by ~~Thursday,~~ September ~~21st~~, by email to [mailto:vimala.nunavath@uia.no vimala.nunavath@uia.no]. Your ideas do not have to be elaborate, but it would be great if you have a (non-binding) group on its feet by then! There will be a mandatory deadline for project proposals later.		I invite informal, non-mandatory suggestions for programming project ideas by Friday September 27th, by email to [mailto:vimala.nunavath@uia.no vimala.nunavath@uia.no]. Your ideas do not have to be elaborate, but it would be great if you have a (non-binding) group on its feet by then! There will be a mandatory deadline for project proposals later.

	== Programming-project proposals ==		== Programming-project proposals ==
	'''Deadline:''' ~~Wednesday~~ October ~~10th~~ 1400		'''Deadline:''' Friday October 4rth 1400

	The deadline for written project proposals is ~~Thursday~~, October ~~5th~~ 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Friday, October 4rth 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

	Student project has to be in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.		Student project has to be in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.
Line 28:		Line 26:

	== Project presentations ==		== Project presentations ==
	The final project presentations: Friday, ~~November 23rd~~.		The final project presentations: Friday, December 6th.

	Depending a little on the number of project groups, each presentation will be brief: 20 minutes for each group.		Depending a little on the number of project groups, each presentation will be brief: 20 minutes for each group.
Line 42:		Line 40:

	== Final project submission ==		== Final project submission ==
	'''Hard deadline:''' ~~November 27th~~ 1400		'''Hard deadline:''' December 13th 1400.

	The end result of the project should be submitted as a ZIP archive through Inspera:		The end result of the project should be submitted as a ZIP archive through Inspera:

Vimala at 16:19, 25 October 2018

2018-10-25T16:19:16Z

Vimala at 16:18, 25 October 2018

2018-10-25T16:18:33Z

← Older revision		Revision as of 16:18, 25 October 2018
Line 30:		Line 30:
	The final project presentations: Friday November 23rd.		The final project presentations: Friday November 23rd.

	Depending a little on the number of project groups, each presentation will be brief~~: perhaps~~ 20 minutes for 3-person ~~groups, 15 minutes for pairs, and 10 minutes if your are working alone~~.		Depending a little on the number of project groups, each presentation will be brief 20 minutes for 4-person group.

	You may demonstrate your project live (most convincing), or you may replay a recorded demonstration (which is good to have as a backup in any case). In addition, I expect each presentation to address/answer at least these points:		You may demonstrate your project live (most convincing), or you may replay a recorded demonstration (which is good to have as a backup in any case). In addition, I expect each presentation to address/answer at least these points:

Vimala at 08:27, 17 October 2018

2018-10-17T08:27:43Z

← Older revision		Revision as of 08:27, 17 October 2018
Line 15:		Line 15:
	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

	Student project has to be done in a group consist of not more than 4 members. Send me an single email from each group, with Cc to all group members.		Student project has to be done in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.

	The proposal does not have to be long, but the following points must be made clear:		The proposal does not have to be long, but the following points must be made clear:

Vimala at 08:27, 17 October 2018

2018-10-17T08:27:14Z

← Older revision		Revision as of 08:27, 17 October 2018
Line 15:		Line 15:
	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

	Student project has to be done in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.		Student project has to be done in a group consist of not more than 4 members. Send me an single email from each group, with Cc to all group members.

	The proposal does not have to be long, but the following points must be made clear:		The proposal does not have to be long, but the following points must be made clear:

Vimala at 08:26, 17 October 2018

2018-10-17T08:26:30Z

← Older revision		Revision as of 08:26, 17 October 2018
Line 15:		Line 15:
	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

	Student project has to be done in a group consist of not more than 4 members. ~~I only need~~ a single email from each group, with Cc to all group members.		Student project has to be done in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.

	The proposal does not have to be long, but the following points must be made clear:		The proposal does not have to be long, but the following points must be made clear:

Vimala at 08:25, 17 October 2018

2018-10-17T08:25:58Z

← Older revision		Revision as of 08:25, 17 October 2018
Line 15:		Line 15:
	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

	~~At this time, you must have decided whether~~ to ~~work alone or~~ in a group. I only need a single email from each group, with Cc to all group members.		Student project has to be done in a group consist of not more than 4 members. I only need a single email from each group, with Cc to all group members.

	The proposal does not have to be long, but the following points must be made clear:		The proposal does not have to be long, but the following points must be made clear:

Vimala at 12:53, 26 September 2018

2018-09-26T12:53:42Z

← Older revision		Revision as of 12:53, 26 September 2018
Line 6:		Line 6:

	== Finding a project idea ==		== Finding a project idea ==
	'''Optional deadline:''' ~~Thursday~~ September 21st		'''Optional deadline:''' Friday September 21st

	I invite informal, non-mandatory suggestions for programming project ideas by Thursday September 21st, by email to [mailto:vimala.nunavath@uia.no vimala.nunavath@uia.no]. Your ideas do not have to be elaborate, but it would be great if you have a (non-binding) group on its feet by then! There will be a mandatory deadline for project proposals later.		I invite informal, non-mandatory suggestions for programming project ideas by Thursday September 21st, by email to [mailto:vimala.nunavath@uia.no vimala.nunavath@uia.no]. Your ideas do not have to be elaborate, but it would be great if you have a (non-binding) group on its feet by then! There will be a mandatory deadline for project proposals later.

	== Programming-project proposals ==		== Programming-project proposals ==
	'''Deadline:''' ~~Thursday~~ October 10th 1400		'''Deadline:''' Wednesday October 10th 1400

	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].
Line 28:		Line 28:

	== Project presentations ==		== Project presentations ==
	The final ~~course session on~~ Friday November 23rd ~~will focus on project presentations~~.		The final project presentations: Friday November 23rd.

	Depending a little on the number of project groups, each presentation will be brief: perhaps 20 minutes for 3-person groups, 15 minutes for pairs, and 10 minutes if your are working alone.		Depending a little on the number of project groups, each presentation will be brief: perhaps 20 minutes for 3-person groups, 15 minutes for pairs, and 10 minutes if your are working alone.

Vimala at 12:35, 26 September 2018

2018-09-26T12:35:45Z

← Older revision		Revision as of 12:35, 26 September 2018
Line 11:		Line 11:

	== Programming-project proposals ==		== Programming-project proposals ==
	'''Deadline:''' Thursday October ~~5th~~ 1400		'''Deadline:''' Thursday October 10th 1400

	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

Vimala at 12:35, 26 September 2018

2018-09-26T12:35:11Z

← Older revision		Revision as of 12:35, 26 September 2018
Line 43:		Line 43:

	== Final project submission ==		== Final project submission ==
	'''Hard deadline:''' ~~December 02nd 0000~~		'''Hard deadline:''' November 27th, kl.14.00

	The end result of the project should be submitted as a ZIP archive through Inspera:		The end result of the project should be submitted as a ZIP archive through Inspera:
	* Just one person in the group shall deliver the group assignment (ZIP file) in Inspera.		* Just one person in the group shall deliver the group assignment (ZIP file) in Inspera.
	* The groups must be created by the candidates. To do that you must create an ID for your group. The ID must be four digits and all the members must know it, and use it.		* The groups must be created by the candidates. To do that you must create an ID for your group. The ID must be four digits and all the members must know it, and use it.
	* When you log in to Inspera you get two options: "Join existing group" or "Create new group".		* When you log in to Inspera you get two options: "Join existing group" or "Create new group".
	* The first member in a group logging in to Inspera must choose: "Create new group".		* The first member in a group logging in to Inspera must choose: "Create new group".
	* All the other members in the same group must choose: "Join existing group".		* All the other members in the same group must choose: "Join existing group".
	* All members in the group must log in to Inspera Assessment (and join the Group), BEFORE one person delivers the group assignment. (Each group can only deliver once)		* All members in the group must log in to Inspera Assessment (and join the Group), BEFORE one person delivers the group assignment. (Each group can only deliver once)

	The submitted ZIP archive should contain your complete project in a single directory, but DO NOT INCLUDE large semantic data sets like DBpedia or other. You do not need to include standard libraries like Jena either. Instead, include a file README.TXT in the root of the project directory to let us know if you have used a particular development environment (like Eclipse), what is needed before your code can be run, and how to run it, and if there are other things to do.		The submitted ZIP archive should contain your complete project in a single directory, but DO NOT INCLUDE large semantic data sets like DBpedia or other. You do not need to include standard libraries like Jena either. Instead, include a file README.TXT in the root of the project directory to let us know if you have used a particular development environment (like Eclipse), what is needed before your code can be run, and how to run it, and if there are other things to do.

← Older revision		Revision as of 16:19, 25 October 2018
Line 1:		Line 1:
	The project shall develop a emergency management application using big data. Development and run-time		The project shall develop an emergency management application using big data technologies and social media data. Development and run-time
	platform is free choice, as is programming language. The project should be carried out in groups of		the platform is a free choice, as is a programming language. The project should be carried out in groups of
	three ~~and not more~~. Working individually or in pairs is not recommended.		> three. Working individually or in pairs is not recommended.

	This autumn, we specifically invite projects that are related to emergency management.		This autumn, we specifically invite projects that are related to emergency management.
Line 8:		Line 8:
	'''Optional deadline:''' Friday September 21st		'''Optional deadline:''' Friday September 21st

	I invite informal, non-mandatory suggestions for programming project ideas by Thursday September 21st, by email to [mailto:vimala.nunavath@uia.no vimala.nunavath@uia.no]. Your ideas do not have to be elaborate, but it would be great if you have a (non-binding) group on its feet by then! There will be a mandatory deadline for project proposals later.		I invite informal, non-mandatory suggestions for programming project ideas by Thursday, September 21st, by email to [mailto:vimala.nunavath@uia.no vimala.nunavath@uia.no]. Your ideas do not have to be elaborate, but it would be great if you have a (non-binding) group on its feet by then! There will be a mandatory deadline for project proposals later.

	== Programming-project proposals ==		== Programming-project proposals ==
	'''Deadline:''' Wednesday October 10th 1400		'''Deadline:''' Wednesday October 10th 1400

	The deadline for written project proposals is Thursday October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].		The deadline for written project proposals is Thursday, October 5th 1400. Everyone who intends to take the course must send me a proposal by then, by email to [mailto:vimala.nunavath@uib.no vimala.nunavath@uib.no].

	Student project has to be ~~done~~ in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.		Student project has to be in a group consist of not more than 4 members. Send me a single email from each group, with Cc to all group members.

	The proposal does not have to be long, but the following points must be made clear:		The proposal does not have to be long, but the following points must be made clear:
Line 25:		Line 25:
	* What technologies (programming language, libraries, development and collaboration tools) you are planning to use.		* What technologies (programming language, libraries, development and collaboration tools) you are planning to use.

	(These points are particularly important if you want to do a project based on your own ideas. If you chose one of the suggests project themes, some of the points may of course be given.)		(These points are particularly important if you want to do a project based on your own ideas. If you chose one of the suggests project themes, some of the points may, of course, be given.)

	== Project presentations ==		== Project presentations ==
	The final project presentations: Friday November 23rd.		The final project presentations: Friday, November 23rd.

	Depending a little on the number of project groups, each presentation will be brief 20 minutes for ~~4-person~~ group.		Depending a little on the number of project groups, each presentation will be brief: 20 minutes for each group.

	You may demonstrate your project live (most convincing), or you may replay a recorded demonstration (which is good to have as a backup in any case). In addition, I expect each presentation to address/answer at least these points:		You may demonstrate your project live (most convincing), or you may replay a recorded demonstration (which is good to have as a backup in any case). In addition, I expect each presentation to address/answer at least these points:
	* what have you made? - or: what is your application doing?		* what have you made? - or: what is your application doing?
	* which technologies have you used (languages, libraries, IDEs etc.)		* which technologies have you used (languages, libraries, IDEs etc.)
	* which datasets have you used? - or: where did you get your data from~~? are you using (only) semantic data, or are you lifting (some of) them?~~		* which datasets have you used? - or: where did you get your data from?
	* which vocabularies are you using? have you created a new vocabulary/ontology, or extend existing ones?
	* why is it a good idea to do this using big data and big data technologies? - or: what does your app do that was not possible (or at least not easy) to do before?		* why is it a good idea to do this using big data and big data technologies? - or: what does your app do that was not possible (or at least not easy) to do before?
	* exactly what have you done and programmed so far?		* exactly what have you done and programmed so far?
	* what are you planning to do in ~~the last weeks~~?		* what are you planning to do in future?
	* have you got particular problems you need to address?		* have you got any particular problems you need to address?

	== Final project submission ==		== Final project submission ==
	'''Hard deadline:''' November 27th~~, kl.14.00~~		'''Hard deadline:''' November 27th 1400

	The end result of the project should be submitted as a ZIP archive through Inspera:		The end result of the project should be submitted as a ZIP archive through Inspera:
	* Just one person in the group shall deliver the group assignment (ZIP file) in Inspera.		* Just one person in the group shall deliver the group assignment (ZIP file) in Inspera.
	* The groups must be created by the candidates. To do that you must create an ID for your group. The ID must be four digits and all the members must know it, and use it.		* The groups must be created by the candidates. To do that you must create an ID for your group. The ID must be four digits and all the members must know it, and use it.
	* When you log in to Inspera you get two options: "Join existing group" or "Create new group".		* When you log in to Inspera you get two options: "Join existing group" or "Create new group".
	* The first member in a group logging in to Inspera must choose: "Create new group".		* The first member in a group logging in to Inspera must choose: "Create new group".
	* All the other members in the same group must choose: "Join existing group".		* All the other members in the same group must choose: "Join existing group".
	* All members in the group must log in to Inspera Assessment (and join the Group), BEFORE one person delivers the group assignment. (Each group can only deliver once)		* All members in the group must log in to Inspera Assessment (and join the Group), BEFORE one person delivers the group assignment. (Each group can only deliver once)

	The submitted ZIP archive should contain your complete project in a single directory~~, but DO NOT INCLUDE large semantic data sets like DBpedia or other~~. ~~You do not need to include standard libraries like Jena either. Instead, include~~ a file README.TXT in the root of the project directory to let us know if you have used a particular development environment (like Eclipse), what is needed before your code can be run, and how to run it, and if there are other things to do.		The submitted ZIP archive should contain your complete project in a single directory. Include a file README.TXT in the root of the project directory to let us know if you have used a particular development environment (like Eclipse), what is needed before your code can be run, and how to run it, and if there are other things to do.

	The file name of your archive should contain the student numbers of everyone in the group. (Not that your student number is different from your student card number...). In addition to your code, the ZIP archive should contain a ~~two-~~page description of your project (see below). You can also include ~~small example~~ data sets to run the code on~~, if you want to~~.		The file name of your archive should contain the student numbers of everyone in the group. (Not that your student number is different from your student card number...). In addition to your code, the ZIP archive should contain a 2 page description of your project (see below). You can also include the data sets to run the code on.

	== Submitted code ==		== Submitted code ==
	You should comment the code lightly in-line. This does not mean one comment line for each code line but, e.g., one brief comment for each logical group of code lines. In particular, we do not require full Javadoc.		You should comment the code lightly in-line. This does not mean one comment line for each code line but, e.g., one brief comment for each logical group of code lines. In particular, we do not require full Javadoc or similar.

	== Project description ==		== Project description ==
	Your ZIP archive should contain a ~~short~~ project description. Put this description in the root folder of your project directory before you ZIP it. The project description file should be anonymous, and contain the exam numbers of all group members, BOTH on the first page and in the file name (e.g., ProjectDescription_102_113.pdf .)		Your ZIP archive should contain a 2-page project description. Put this description in the root folder of your project directory before you ZIP it. The project description file should be anonymous, and contain the exam numbers of all group members, BOTH on the first page and in the file name (e.g., ProjectDescription_102_113.pdf .)

	The length of the project description is ~~max~~ 2 A4 pages with 11pt font and 2.5 cm margins. This is a HARD limit. You can have appendices, though, and any figures or tables come in addition to the two pages. The quality of your code is more important than the quality of the 2-page description. You receive a grade on the project, not on the report.		The length of the project description is maximum 2 A4 pages with 11pt font and 2.5 cm margins. This is a HARD limit. You can have appendices, though, and any figures or tables come in addition to the two pages. The quality of your code is more important than the quality of the 2 page description. You receive a grade on the project, not on the report.

	* You should briefly explain the purpose of your system. Why have you made this? Why is it a good idea to do this using ~~semantic~~ technologies? What can you do now that wasn't possible before?		* You should briefly explain the purpose of your system. Why have you made this? Why is it a good idea to do this using big data technologies? What can you do now that wasn't possible before?
	* You should probably list the technologies/tools/standards/~~vocabularies~~ you have used and explain briefly why you chose each of them. Did you consider alternatives? Why were the ones you chose better?		* You should probably list the technologies/tools/standards/ datasets you have used and explain briefly why you chose each of them. Did you consider alternatives? Why were the ones you chose better?
	* If you are reading/converting/lifting data from multiple sources and/or using existing tools in addition to your own program, you should probably include a flow chart or architecture sketch (which is different from a class diagram).		* If you are reading/converting/lifting data from multiple sources and/or using existing tools in addition to your own program, you should probably include a flow chart or architecture sketch (which is different from a class diagram).
	* You should probably include a class diagram and/or data flow diagram of your system.		* You should probably include a class diagram and/or data flow diagram of your system.
	* You should mention any particular problems you have had and/or things you want to do differently next time.		* You should mention any particular problems you have had and/or things you want to do differently next time.
	* If you want to briefly describe how to run the code you have submitted, you can do that separately in a README.TXT file.		* If you want to briefly describe how to run the code you have submitted, you can do that separately in a README.TXT file.