Show last authors
1 * {{tucson/}} {{stringEngIta eng="as it is" ita ="come è"/}}
2 ** [[Asynchronous Agents Behaviour in TuCSoN: pro-active notifications>>SdLm1314ProjectAgentsNotifications]] //(Fabio Consalici, Riccardo Drudi)//
3 ** [[Implementazione della persistenza in TuCSoN>>SdLm1314ProjectPersistency]] //(Lorenzo Pontellini, Vincenzo Scafuto)//
4 ** [[Esercizio di profiling sulla classe TucsonNodeService.java>>SdLm1314ProjectMemoryProfiling]] //(Beatrice Mezzapesa)//
5 ** [[Interazione tra l'Inspector e il ciclo di vita della macchina virtuale ReSpecT>>SdLm1314ProjectRespectVMInspector]] //(Roberto D'Elia)//
6 ** [[TuCSoN on Cloud: "Elastic" deployment of TuCSoN nodes in the Cloud>>SdLm1314ProjectElasticTucsonOnCloud]] //(Richiard Casadei)//
7 ** [[TuCSoN on Cloud (Web Service)>>SdLm1314ProjectUIAccountingTucsonOnCloud]] //(Luca Guerra)//
8 ** [[Exception Handling in Middlewares: The case of TuCSoN>>SdLm1314ProjectTucsonExceptions]] //(Alessia Papini, Mattia Balducci)//
9 * {{tucson/}} {{stringEngIta eng="as it will be" ita ="come sarà"/}}
10 ** [[TuCSoN communication language: abstract tuples>>SdLm1314ProjectsTucsonCommunicationLanguage]] //(Richiard Casadei)//
11
12 >{{stringEngIta ita="Risorse" eng="Resources"/}}
13
14 * {{stringEngIta eng="Distributed Systems" ita="i"/}} [[{{stringEngIta eng="projects" ita="progetti"/}}>>SdProjects]] {{stringEngIta eng="through the years" ita="di Sistemi distribuiti attraverso gli anni"/}}
15
16 >{{stringEngIta eng="Project Guidelines" ita ="Linee guida per i progetti"/}}
17
18 Here follows the list of **ongoing** student projects in the context of the class of **Distributed Systems** held by Prof. Omicini **(2013/2014)**.
19 Each entry on the list leads to a separate Wiki page students are encouraged to use at their advantage (write down ideas, track documents, attach code, etc.)
20
21 Projects have been divided into two different "categories", although they share a common goal (for you): **learn what it means to model/design/implement/test a middleware**.
22 Why middlewares? Basically 3 reasons:
23 * being projects proposed in the context of the Distributed System class, it seems reasonable (and profitable, for your career) to start "play" with something //distributed//: middlewares are perfect for the purpose
24 * middlewares pose some non-trivial challenge both at the model, architectural and implementation level, mostly due to their typical distributed nature forcing programmers to //drop many implicit assumptions// made when programming a non-distributed setting
25 * a distributed middleware is already available, which is [[TuCSoN>>TuCSoN.WebHome]], so it seems reasonable not to start "from scratch". Furthermore, TuCSoN is a tuple-based coordination model and infrastructure, that is, a //[[coordination artefact>>Publications.ArtifactsPromas07]]// gaining increasing attention both from the academic world and from the industry
26
27 The two categories have been named "TuCSoN as it is" and "TuCSoN as it will be", which basically means the following:
28
29 * in **"TuCSoN as it is"** you will work on the ready-to-use TuCSoN distribution, improving/adding/fixing some details left behind during time
30 * in **"TuCSoN as it will be"** you will start redesigning ("from scratch") specific, well-delimited TuCSoN pieces based on its formal model as it is described in TuCSoN papers
31
32 What is the difference?
33 The crucial point is that in the first case you deal with already existing code, thus will eventually deal with refactorings, dependency analysis, conflicts resolution; whereas in the latter case, you should face the issues of translating a model or, at best, an abstract architecture and an operational semantics, into code, carefully choosing which assumptions to make.
34 Trust us: neither of the two is easier than the other.
35
36 * TuCSoN “as it is”
37 ** **~!!! UPDATE ~!!!**
38 Although GoogleCode still hosts TuCSoN source code, a __new repository__ has been set up on [[Bitbucket>>https://bitbucket.org/smariani/tucson/wiki/Home||target="_blank"]]: please clone TuCSoN code from this repository (default branch, which is 'master' branch, is fine) and work on a local branch named as follows '//$surname1//-//$surname2//-...' (if you don't know what I'm talking about, __email me asap__)
39 ** **NB:** For the projects here, usage of [[Eclipse>>http://www.eclipse.org/downloads/||target="_blank"]], [[Checkstyle>>http://eclipse-cs.sourceforge.net]] and [[FindBugs>>http://findbugs.sourceforge.net||target="_blank"]] is __strongly suggested__
40
41 * TuCSoN "as it will be"
42 ** **NB:** For the projects here, usage of [[Eclipse>>http://www.eclipse.org/downloads/]], [[Maven>>https://maven.apache.org/eclipse-plugin.html]], [[Checkstyle>>http://eclipse-cs.sourceforge.net]] and [[FindBugs>>http://findbugs.sourceforge.net]] is __mandatory__
43
44 {{velocity}}
45 #set( $currentCourseDoc = "SdLm1314" )
46 {{/velocity}}
47
48
49

Course

— a.y.

2013/2014

— credits

9

— cycle

2nd cycle

— language

wit.gif

Teachers

— professor

Andrea Omicini

— other professors

Marco Fabbri

Context

— university

Alma Mater Studiorum-Università di Bologna

— campus

Cesena

— department / faculty / school

DISI

— 2nd cycle

8614 Ingegneria e scienze informatiche 

URLs & IDs

AMS page
course timetable

— course ID

58260

Partita IVA: 01131710376 - Copyright © 2008-2021 APICe@DISI Research Group - PRIVACY