air - User contributions [en]

File:Proj-2014-2015-SmartClassroom-transparents.pdf

2015-04-08T08:29:50Z

Marie.Darrigol:

File:Proj-2014-2015-SmartClassroom-flyer.pdf

2015-04-08T07:18:31Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Proj-2014-2015-SmartClassroom-flyer.pdf"

File:Proj-2014-2015-SmartClassroom-flyer.pdf

2015-04-07T08:56:16Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Proj-2014-2015-SmartClassroom-flyer.pdf": Reverted to version as of 08:50, 7 April 2015

File:Proj-2014-2015-SmartClassroom-flyer.pdf

2015-04-07T08:51:11Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Proj-2014-2015-SmartClassroom-flyer.pdf": Reverted to version as of 08:49, 7 April 2015

File:Proj-2014-2015-SmartClassroom-flyer.pdf

2015-04-07T08:50:02Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Proj-2014-2015-SmartClassroom-flyer.pdf"

File:Proj-2014-2015-SmartClassroom-flyer.pdf

2015-04-07T08:49:14Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Proj-2014-2015-SmartClassroom-flyer.pdf"

File:Proj-2014-2015-SmartClassroom-flyer.pdf

2015-04-07T06:27:01Z

Marie.Darrigol:

Proj-2014-2015-SmartClassroom/SRS

2015-03-31T11:34:12Z

Marie.Darrigol: /* 2. General description */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| Janvier 2015
| Romain Barthelemy, Alan Damotte, Marie Darrigol, Anthony Leonard
| Présentation des exigences du projet Smart Classroom
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==
This document presents the aim of the project Smart Classroom as well as the functionnal and non-functionnal requirements, risks and quality standards.

==1.2 Scope of the product==
This project is integrated at the RICM4 engineering training (Computing Networks and Multimedia Communication) in Polytech'Grenoble school. It will be led by 4 students (2 in the Multimedia option and 2 in the Network option) and will last 7 weeks.

==1.3 Definitions, acronyms ans abbrevations==
* '''NFC''' : Near Field Communication. A NFC tag can be linked to information such as web page, social networks and all sorts of other information in general.
* '''MCQ''' : Multiple-choice Questionnaire
* '''ID''' : Identifier

==1.4 References==
Our work follows on from different projects realised by ENSIMAG students :
[http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 

==1.5 Overview of the remainder of the document==

=2. General description=
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module has to fit in well with the others in order to obtain a real innovative infrastructure.
==2.1 Product perspective==
Our product has to meet the following need :
Students come in class, announce their presence and get settled at their work station. The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==2.2 Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==2.3 User characteristics==
There are two types of users for this product and in two different inputs. The first type of user is the teacher who is able to create, modify, pusblish courses and exams. Then there are the students, who, by means of their working space, answer the quizzes and submit their answers.

==2.4 General constraints==
* Application has to work on tablet
* Stable wifi connection is needed inside the smart classroom

==2.5 Assumptions and dependencies==
* No access to extern websites
* Smart Classroom environment allows us to link the tablets to the Moodle server

=3. Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''': Realisation and management of MCQ as part of the SmartClassroom

'''Description''': Our project consists in developing a system wich allows a teacher to prepare his lessons and create MCQ on one hand, and on the other hand allows students to answer at these MCQ. We will also have to manage the identification of each student in order to control their presence during the lessons.

'''Inputs''': Students' and teacher's tablets

'''Source''': NFC tag, touch sreen

'''Outputs''': Identification, answers to each student's question

'''Destination''': This projects is designed to be integrated in the environment of a SmartClassroom and is bound for being used by teachers and students.

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples 

Teacher side : 
* Has to allow the creation of MCQ
* Has to permit the recovery of the results
* Could sort the results per students / questions / answers
* Has to allow the identification by the meaning of a personal ID or a NFC tag
 
Student side :
* Must allow the answer of the MCQ
* Can give an access to the results
* Has to allow modifications before sending the MCQ
* Has to permit the identification by the meaning of a personal ID or a NFC tag

'''Non functional requirements''':
* Easy to use : no user experience needed
* Portability : usage on tablet
* Size : the size of the application won't be more than few bytes
* Usage : Clear interface and elaborate in order to make the user experience efficient
* Resistance : the application have to keep working and watch over during a network failure

'''Pre-condition''':
* Equipment side :
::- a tablet has to be available for each student and for the teacher
::- each student must have his own swipe card in order to be identified
* Application side :
::- a WiFi connection has to be maintened in the classroom

'''Post-condition''':
* the teacher is able to create documents for his lesson and MCQ via the application
* students are identified via their badges

'''Side-effects''':

=4. Product evolution=
The SmartClassroom project is based on several scenarios realised by a number of groups. The part described here is just one of them.
Future enhancements of this environment could be proposed and implemented by future groups in charge of developping this classroom.

=5. Appendices=

=6. Index=

Proj-2014-2015-SmartClassroom

2015-03-31T11:32:06Z

Marie.Darrigol: /* Context */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module has to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his platform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured identification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the NFC tag which contains only his username. The NFC id is sent as the password. The server has just to check if it is either the password associated to the account or the NFC id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using NFC tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

== Week 10 (March, 23rd - March, 30th) ==
*We've got a second NFC tag for our tests
*Some bugs have been corrected, so now our main goal is acheived (log in using a nfc tag)
*Some tests using different nfc tags and different smartphones or tablets need to be done
*Study for the management of students attendance to courses
**[https://docs.moodle.org/28/en/Autoattendance_block#Add_.28one.29 AutoAttendance]
**We found that we could possibly use some existing plugin

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources previously)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom

2015-03-23T15:01:53Z

Marie.Darrigol: /* How to connect to your Moodle local server from the Moodle Mobile app ? (on linux) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the NFC tag which contains only his username. The NFC id is sent as the password. The server has just to check if it is either the password associated to the account or the NFC id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using NFC tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

== Week 10 (March, 23rd - March, 30th) ==
*We've got a second NFC tag for our tests
*Study for the management of students attendance to courses
**[https://docs.moodle.org/28/en/Autoattendance_block#Add_.28one.29 AutoAttendance]

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources previously)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom

2015-03-23T15:01:06Z

Marie.Darrigol: /* Week 10 (March, 23rd - March, 30th) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the NFC tag which contains only his username. The NFC id is sent as the password. The server has just to check if it is either the password associated to the account or the NFC id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using NFC tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

== Week 10 (March, 23rd - March, 30th) ==
*We've got a second NFC tag for our tests
*Study for the management of students attendance to courses
**[https://docs.moodle.org/28/en/Autoattendance_block#Add_.28one.29 AutoAttendance]

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom

2015-03-23T14:56:09Z

Marie.Darrigol: /* Week 10 (March, 23rd - March, 30th) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the NFC tag which contains only his username. The NFC id is sent as the password. The server has just to check if it is either the password associated to the account or the NFC id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using NFC tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

== Week 10 (March, 23rd - March, 30th) ==
*We've got a second NFC tag for our tests
*Study for the management of students attendance to courses

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom

2015-03-23T14:06:30Z

Marie.Darrigol: /* Project schedule */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the NFC tag which contains only his username. The NFC id is sent as the password. The server has just to check if it is either the password associated to the account or the NFC id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using NFC tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

== Week 10 (March, 23rd - March, 30th) ==
*We've got a second NFC tag for our tests

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom/Scrum

2015-03-23T14:01:29Z

Marie.Darrigol: /* Sprints */

= Product backlog =
This is a link to access the Scrum of our project :
*[https://waffle.io/AlanDamotte/SmartClassroom Scrum]
Because our git repository is private, the Scrum has been create on a free repository which doesn't include any code. Please check the main page of our project to access the link of our Github repository. You'll need to have an authorized access. Contact us if you want to access our sources.

==Project description==
Students come in class, announce their presence and get settled at their work station. The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==User Stories==
*'''n°1''' : As a student or a teacher, I want to log in my Moodle account using a NFC tag so that I can directly access my personnal account.
*'''n°2''' : As a teacher, I want to create, modify courses so I can display them on a screen or a wall.
*'''n°3''' : As a teacher, I want to create, modify and share quizzes with my students so they can answer it.
*'''n°4''' : As a student, I want to be able to access the courses.
*'''n°5''' : As a student, I want to be able to answer the quizz.
*'''n°6''' : As a teacher, I wish I could see the results of the quizzes.
*'''n°7''' : As a student or a teacher, I wish I could use classic connection so that I can access to my Moodle account with my username and my password.

==Tasks==
*Study and understanding of the technologies we will use (CAS/LDAP, Cordova,...)
*Connection to Moodle account by means of the NFC tag
**User story n°1
*Courses and exams modifications
**User stories n°2 and 3 (creation and modification)
**User stories n°4 and 5 (use by students)
*Allow classic connection (username and password)
**User story n°7
*Display of results for each student
**User story n°6

A task is finished when :
*it responds to the associated user story
*it has been tested by developpers

==Sprints==
===To do===
*Attendance management (2 weeks)
**We have to think about a solution to manage attendance of the students
*Course management (1 week)
**The application has to provide tools to create, modify, publish courses or exams.
*Results display (1 week)
**The application has to provide tools to display results of quiz that have been answered.

===In progress===
*Connection optimization (1 week)

===Finished===
*CAS and LDAP understanding
**This task was assigned to Anthony Leonard and Romain Barthelemy. They had to understand how LDAP and CAS work in order to begin the connection establishement.
**[http://en.wikipedia.org/wiki/Central_Authentication_Service What is CAS ?]
**[http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol What is LDAP ?]
*Connection establishment (4 weeks)
**The aim is to understand which technologies are already used for Moodle connection.
**The aim is to establish the connection to the student Moodle account while clock-in by means of the NFC tag.

Proj-2014-2015-SmartClassroom

2015-03-17T14:09:30Z

Marie.Darrigol: /* Week 9 (March, 16th - March, 22nd) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the NFC tag which contains only his username. The NFC id is sent as the password. The server has just to check if it is either the password associated to the account or the NFC id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using NFC tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom

2015-03-17T14:08:47Z

Marie.Darrigol: /* Week 9 (March, 16th - March, 22nd) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in understanding actual Moodle architecture before establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

End of sprint 1 which consisted in :
**Code of mobile app and plug-in creation understanding
**CAS/LDAP understanding

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag
**We'll now try to connect using NFC tag. First using data (username and password) stored in the NFC tag, then using the tag id. But to do so, we need the server side to be ready.
*Web side
**Forking the original token distribution system for preparing modifications

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (login and password) are used to open the Moodle account. The url is stored in directly the application because we suppose that the application will only be used for one university and one server. We have a problem though. Indeed, we have to tag twice : the first time to launch this application, the second time to login. But in a way, that allows us to connect to our account even if the application is already opened.
* General :
** Reflections about how to implement a secured system of authentication using the NFC tag (which data to store/read on the tag, etc...)

== Week 9 (March, 16th - March, 22nd) ==
*App side
** We managed to get the NFC tag Id, we will use it later, to connect directly using only this id instead of using username and password. We manage to let the user the possibility to connect to his Moodle account using his username and password (classic connection).
*Web side
**Check where the added fields are located on moodle's database
**Development of a plugin recognizing in the password field if it is the usual password or the nfc tag
*Tests
**The first test using both app side and server side is conclusing. The user can log in his Moodle account using the nfc tag which contains only his username. The nfc id is sent as the password. The server has just to check if it is either the password associated to the account or the nfc id. This way, we also allow classic connection. Nevertheless, at the moment, we have a bug. Log in using nfc tag and the new server plugin changes the user's password with the tag id, which is not supposed to happen.
*End of Sprint 2

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

==How to make tests on your Moodle server ? (on linux)==
* Connect as an admin on your server
* Go on Site administration->Users->Accounts->add a new user
* Set the username (that will be used for the connection), choose the authentication method that you want to test, and every other required field
* If they are needed for the authentication, fill the added fields (Site administration->Users->User profile fields if you have to create them)
* You can try to connect your user with the authentication method to test

=Useful links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

File:Objects diagram.jpg

2015-03-17T14:04:44Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Objects diagram.jpg"

Proj-2014-2015-SmartClassroom/UML

2015-03-17T14:03:28Z

Marie.Darrigol: /* Objects diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

Please note that all these diagrams have been designed at the beginning of the project. Therefore, some of them may not correspond with the final product.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
[[File:objects_diagram.jpg|600px]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg|600px]]
===Scenario 2 : Creation of the MCQ===
[[File:Collaboration_diagram_scenar2.jpg‎|600px]]

===Scenario 3 : Answer to the MCQ===
[[File:Collaboration_diagram_scenar3.jpg‎|600px]]

Proj-2014-2015-SmartClassroom/UML

2015-03-17T14:02:54Z

Marie.Darrigol: /* Collaboration diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

Please note that all these diagrams have been designed at the beginning of the project. Therefore, some of them may not correspond with the final product.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg|600px]]
===Scenario 2 : Creation of the MCQ===
[[File:Collaboration_diagram_scenar2.jpg‎|600px]]

===Scenario 3 : Answer to the MCQ===
[[File:Collaboration_diagram_scenar3.jpg‎|600px]]

File:Collaboration diagram.jpg

2015-03-17T14:02:31Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Collaboration diagram.jpg"

Proj-2014-2015-SmartClassroom/UML

2015-03-17T14:00:42Z

Marie.Darrigol: /* UML Diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

Please note that all these diagrams have been designed at the beginning of the project. Therefore, some of them may not correspond with the final product.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]
===Scenario 2 : Creation of the MCQ===
[[File:Collaboration_diagram_scenar2.jpg‎|600px]]

===Scenario 3 : Answer to the MCQ===
[[File:Collaboration_diagram_scenar3.jpg‎|600px]]

Proj-2014-2015-SmartClassroom/UML

2015-03-17T13:48:59Z

Marie.Darrigol: /* UML Diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.
Please note that all these diagrams have been designed at the beginning of the project. Therefore, some of them may not correspond with the final product.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]
===Scenario 2 : Creation of the MCQ===
[[File:Collaboration_diagram_scenar2.jpg‎|600px]]

===Scenario 3 : Answer to the MCQ===
[[File:Collaboration_diagram_scenar3.jpg‎|600px]]

Proj-2014-2015-SmartClassroom/UML

2015-03-17T13:46:17Z

Marie.Darrigol: /* Scenario 3 : Answer to the MCQ */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]
===Scenario 2 : Creation of the MCQ===
[[File:Collaboration_diagram_scenar2.jpg‎|600px]]

===Scenario 3 : Answer to the MCQ===
[[File:Collaboration_diagram_scenar3.jpg‎|600px]]

File:Collaboration diagram scenar3.jpg

2015-03-17T13:45:49Z

Marie.Darrigol:

Proj-2014-2015-SmartClassroom/Scrum

2015-03-17T13:36:28Z

Marie.Darrigol: /* Sprints */

= Product backlog =
This is a link to access the Scrum of our project :
*[https://waffle.io/AlanDamotte/SmartClassroom Scrum]
Because our git repository is private, the Scrum has been create on a free repository which doesn't include any code. Please check the main page of our project to access the link of our Github repository. You'll need to have an authorized access. Contact us if you want to access our sources.

==Project description==
Students come in class, announce their presence and get settled at their work station. The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==User Stories==
*'''n°1''' : As a student or a teacher, I want to log in my Moodle account using a NFC tag so that I can directly access my personnal account.
*'''n°2''' : As a teacher, I want to create, modify courses so I can display them on a screen or a wall.
*'''n°3''' : As a teacher, I want to create, modify and share quizzes with my students so they can answer it.
*'''n°4''' : As a student, I want to be able to access the courses.
*'''n°5''' : As a student, I want to be able to answer the quizz.
*'''n°6''' : As a teacher, I wish I could see the results of the quizzes.
*'''n°7''' : As a student or a teacher, I wish I could use classic connection so that I can access to my Moodle account with my username and my password.

==Tasks==
*Study and understanding of the technologies we will use (CAS/LDAP, Cordova,...)
*Connection to Moodle account by means of the NFC tag
**User story n°1
*Courses and exams modifications
**User stories n°2 and 3 (creation and modification)
**User stories n°4 and 5 (use by students)
*Allow classic connection (username and password)
**User story n°7
*Display of results for each student
**User story n°6

A task is finished when :
*it responds to the associated user story
*it has been tested by developpers

==Sprints==
===To do===
*Course management (1 week)
**The application has to provide tools to create, modify, publish courses or exams.
*Results display (1 week)
**The application has to provide tools to display results of quiz that have been answered.

===In progress===
*Connection optimization (1 week)

===Finished===
*CAS and LDAP understanding
**This task was assigned to Anthony Leonard and Romain Barthelemy. They had to understand how LDAP and CAS work in order to begin the connection establishement.
**[http://en.wikipedia.org/wiki/Central_Authentication_Service What is CAS ?]
**[http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol What is LDAP ?]
*Connection establishment (4 weeks)
**The aim is to understand which technologies are already used for Moodle connection.
**The aim is to establish the connection to the student Moodle account while clock-in by means of the NFC tag.

Proj-2014-2015-SmartClassroom/UML

2015-03-17T13:30:10Z

Marie.Darrigol: /* Scenario 2 : Creation of the MCQ */

File:Collaboration diagram scenar2.jpg

2015-03-17T13:29:13Z

Marie.Darrigol:

Proj-2014-2015-SmartClassroom/UML

2015-03-17T13:20:35Z

Marie.Darrigol: /* Classes diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]
===Scenario 2 : Creation of the MCQ===
''Soon''
===Scenario 3 : Answer to the MCQ===
''Soon''

File:Classes diagram.jpg

2015-03-17T13:19:55Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Classes diagram.jpg"

Proj-2014-2015-SmartClassroom/UML

2015-03-16T16:25:50Z

Marie.Darrigol: /* Collaboration diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]
===Scenario 2 : Creation of the MCQ===
''Soon''
===Scenario 3 : Answer to the MCQ===
''Soon''

Proj-2014-2015-SmartClassroom/UML

2015-03-16T16:25:25Z

Marie.Darrigol: /* Collaboration diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]
===Scenario 2 : ===
''Soon''
===Scenario 3 : ===
''Soon''

Proj-2014-2015-SmartClassroom/UML

2015-03-16T16:24:34Z

Marie.Darrigol: /* Collaboration diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
===Scenario 1 : Connection to Moodle===
[[File:collaboration_diagram.jpg]]

Proj-2014-2015-SmartClassroom/UML

2015-03-16T16:23:58Z

Marie.Darrigol: /* Collaboration diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
[[File:collaboration_diagram.jpg]]

File:Collaboration diagram.jpg

2015-03-16T16:23:31Z

Marie.Darrigol:

Proj-2014-2015-SmartClassroom/UML

2015-03-16T16:01:42Z

Marie.Darrigol: /* Objects diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
[[File:objects_diagram.jpg]]

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

File:Objects diagram.jpg

2015-03-16T16:01:01Z

Marie.Darrigol:

File:Classes diagram.jpg

2015-03-16T15:45:18Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Classes diagram.jpg"

Proj-2014-2015-SmartClassroom/UML

2015-03-16T15:38:14Z

Marie.Darrigol: /* UML Diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
''Soon''

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

File:Classes diagram.jpg

2015-03-16T15:37:56Z

Marie.Darrigol: Marie.Darrigol uploaded a new version of "File:Classes diagram.jpg"

Proj-2014-2015-SmartClassroom/UML

2015-03-16T15:29:45Z

Marie.Darrigol: /* Classes diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg|600px]]

== Objects diagrams ==
''Soon''

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

File:Classes diagram.jpg

2015-03-16T15:29:09Z

Marie.Darrigol:

Proj-2014-2015-SmartClassroom/UML

2015-03-16T15:21:38Z

Marie.Darrigol: /* UML Diagrams */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
[[File:classes_diagram.jpg]]

== Objects diagrams ==
''Soon''

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

Proj-2014-2015-SmartClassroom/UML

2015-03-16T14:55:03Z

Marie.Darrigol: /* Scenario 1 */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
''Soon''

== Objects diagrams ==
''Soon''

== Sequence diagrams ==

===Scenario 1 : Connection to Moodle===
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

Proj-2014-2015-SmartClassroom/UML

2015-03-16T14:53:36Z

Marie.Darrigol: /* Scenario 1 */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
''Soon''

== Objects diagrams ==
''Soon''

== Sequence diagrams ==

===Scenario 1===
As a student or a teacher, I want to log in my Moodle account using a NFC tag so that I can directly access my personnal account.
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

Proj-2014-2015-SmartClassroom/UML

2015-03-16T14:53:25Z

Marie.Darrigol: /* Scenario 1 : Connection to Moodle */

=UML Diagrams=

The followings are some UML diagrams created for certains aspects of the project.

== Use case ==
[[File:CasUtilisation.jpeg|600px]]

== Classes diagrams ==
''Soon''

== Objects diagrams ==
''Soon''

== Sequence diagrams ==

===Scenario 1===
As a student or a teacher, I want to log in my Moodle account using a NFC tag so that I can directly access my personnal account
''Actors = Teacher or student''
''Tools = Tablet, NFC reader + NFC tag, web server, Moodle''

[[File:UMLMoodle.png]]

===Scenario 2 : Creation of MCQ===
''Actors = Teacher''
''Tools = Tablet, Moodle''

[[File:QCM1.png]]

===Scenario 3 : Answer to the MCQ===
''Actors = Student''
''Tools = Tablet, Moodle''

[[File:QCM2.png]]

== Collaboration diagrams ==
''Soon''

Proj-2014-2015-SmartClassroom/UML

2015-03-16T14:52:12Z

Marie.Darrigol: /* UML Diagrams */

Proj-2014-2015-SmartClassroom/Scrum

2015-03-10T13:04:22Z

Marie.Darrigol: /* Tasks */

= Product backlog =
This is a link to access the Scrum of our project :
*[https://waffle.io/AlanDamotte/SmartClassroom Scrum]
Because our git repository is private, the Scrum has been create on a free repository which doesn't include any code. Please check the main page of our project to access the link of our Github repository. You'll need to have an authorized access. Contact us if you want to access our sources.

==Project description==
Students come in class, announce their presence and get settled at their work station. The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==User Stories==
*'''n°1''' : As a student or a teacher, I want to log in my Moodle account using a NFC tag so that I can directly access my personnal account.
*'''n°2''' : As a teacher, I want to create, modify courses so I can display them on a screen or a wall.
*'''n°3''' : As a teacher, I want to create, modify and share quizzes with my students so they can answer it.
*'''n°4''' : As a student, I want to be able to access the courses.
*'''n°5''' : As a student, I want to be able to answer the quizz.
*'''n°6''' : As a teacher, I wish I could see the results of the quizzes.
*'''n°7''' : As a student or a teacher, I wish I could use classic connection so that I can access to my Moodle account with my username and my password.

==Tasks==
*Study and understanding of the technologies we will use (CAS/LDAP, Cordova,...)
*Connection to Moodle account by means of the NFC tag
**User story n°1
*Courses and exams modifications
**User stories n°2 and 3 (creation and modification)
**User stories n°4 and 5 (use by students)
*Allow classic connection (username and password)
**User story n°7
*Display of results for each student
**User story n°6

A task is finished when :
*it responds to the associated user story
*it has been tested by developpers

==Sprints==
===To do===
*Course management (1 week)
**The application has to provide tools to create, modify, publish courses or exams.
*Results display (1 week)
**The application has to provide tools to display results of quiz that have been answered.

===In progress===
*Connection establishment (4 weeks)
**The aim is to understand which technologies are already used for Moodle connection.
**The aim is to establish the connection to the student Moodle account while clock-in by means of the NFC tag.

===Finished===
*CAS and LDAP understanding
**This task was assigned to Anthony Leonard and Romain Barthelemy. They had to understand how LDAP and CAS work in order to begin the connection establishement.
**[http://en.wikipedia.org/wiki/Central_Authentication_Service What is CAS ?]
**[http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol What is LDAP ?]

Proj-2014-2015-SmartClassroom

2015-03-09T16:16:00Z

Marie.Darrigol: /* Week 8 (March, 9th - March, 15th) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and its data (url, login and password) are used to open the Moodle account

== Week 9 (March, 16th - March, 22nd) ==

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

=Usefull links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom

2015-03-09T16:15:20Z

Marie.Darrigol: /* Week 8 (March, 9th - March, 15th) */

= Project presentation=

== Context ==
The aim of this project is to design a new innovative information system for the future of the classroom, by making easier and especially automating daily tasks. Although there are already four projects linked to the smart classroom and realized by ENSIMAG students, our module have to fit in well with the others in order to obtain a real innovative infrastructure. 
[[File:Classe.jpg]]

== Description ==
Our project follows those realized by students of ENSIMAG : [http://fablab.ensimag.fr/index.php/Projet_%22SmartClassroom%22 Smart Classroom] 
Following this link you can find how the infrastructure of the project has been implemented by them.

Our product has to meet the following need : 
Students come in class, announce their presence and get settled at their work station.
The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==Product functions==
* Individual and secured idendentification
* Creation of courses' constituents
* Reply to the test by the students
* Results display
* Reorganisation of the students in working groups depending on their level

==Product evolution==
SmartClassroom project is based on a couple of storylines realized by different groups, and we are only working on one of these.
Future upgrades of this environment could be put forward and implemented by other groups in charge of developing this project.

= Project team =

Tutors : Didier Donsez, Vivien Quema, Jérome Maisonnasse, Amr Alzouhri-Alyafi

[[Proj-2014-2015-SmartClassroom-Team1|Man Machine Interface]]
*Marie Darrigol
*Alan Damotte

[[Proj-2014-2015-SmartClassroom-Team2|Identification and communication between the students and the teacher]]
*Romain Barthelemy
*Anthony Léonard

=Links=
*[[Proj-2014-2015-SmartClassroom/UML|UML Diagrams]]
*[[Proj-2014-2015-SmartClassroom/SRS|Requirements (SRS)]]
*[[Proj-2014-2015-SmartClassroom/Scrum|Scrum]]
In order to access our git repository, you need to have an authorized access. Please contact us if you want to access our sources.
*[https://github.com/AlanDamotte/auth Git repository]

=Project schedule=

The project has begun in January the 13th.

== Week 1 (January, 13rd - January, 18th) ==
* Meeting with Jérome Maisonnasse and Amr Alzouhri-Alyafi for the presentation of Smart Classroom, current projects and projects that can be done.
* Reflection on the realisation of the project : division into two sub-projects that match our respective courses (NFC and interface).

== Week 2 (January, 19th - Janurary, 25th) ==
* Presentation of our project
* Contact with ENSIMAG students
* Pick up of the equipment and research on the technologies we can use for the realisation of the project
* Pick up of OpenHAB
* Pick up of Moodle API and installation of a Moodle server on our computers
* Pick up NFC connection + writing/reading with NFC tag
* Writing of the SRS file (requirements)

== Week 3 (January, 26th - February, 1st) ==
* Realisation of the first UML diagrams (use case, classes diagrams and sequence diagrams)
* Meeting with ENSIMAG students and project handover
** They explained us what they have done, the difficulties they had to face
** They gave us the source code of the project they have been working on
* First look of the source code
* First look on Cordova

== Week 4 (February, 2nd - February, 8th) ==
* Establishment of the Scrum requirements of our project
* Meeting with our tutors in order to present them our progress and the goals we would like to achieve in a few weeks
* Beginning of the first sprint which consists in establishing the connection to the student Moodle account while clock-in by means of the NFC tag 
**The server has to verify the ID associated to the NFC tag.
**The application has to launch the moodle application and open the student Moodle account associated.
* Installation of Cordova and first compilation of moodle mobile sources

== Week 5 (February, 9th - February, 15th) ==

* Documentation about several aspects of the project and Moodle source code
* Creation of some design patterns and the FAQ
* Meeting with Michael Magi, supervisor of the Moodle server of Joseph Fourier University (UJF)
** We now have a new orientation to explore while developping our app : we will probably use LDAP which is common to every french University
** We don't specially need to develop a new plugin starting from zero, we could use what is already existing and just change some things in order to obtain the right behaviour

Client side :
* Classic connection (using login and password) on our machines working

Server side :
* Beginning of the creation of the plugin (managing NFC connection)

== Week 6 (February, 23rd - March, 1st) ==
* Creation of a private Git repository to develop our plugin
** We asked for an educational account in order to create a private account : [https://education.github.com/ Free student account]
* Updating of Scrum
* Installation of ApacheDS : [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
** This is used to install a LDAP local server

== Week 7 (March, 2nd - March, 8th) ==
*App side
**Now we can launch Android Moodle Application when Scanning the NFC Tag

== Week 8 (March, 9th - March, 15th) ==
* App side :
** The NFC tag is read and url, login and password are used to open the Moodle account

== Week 9 (March, 16th - March, 22nd) ==

=FAQ=
Requirements :
* You need to have a proper installation of Moodle local server on your device : [https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu How to install Apache, MySQL, PHP on Ubuntu] [https://github.com/moodle/moodle Moodle sources]
* You need to have a proper installation of Moodle mobile : [https://github.com/moodlehq/moodlemobile Moodle Mobile sources]
==How to connect to your Moodle local server from the Moodle Mobile app ? (on linux)==
* Go to your Moodle server folder, which is supposed to be there : /var/www/html/moodle (it depends on where you put your moodle sources precedently)
* Open your config.php file
* Open a terminal and type ifconfig, you should see an inet address (wlan0). Replace in the config.php the address 127.0.0.1 with this address.
* You should be able to connect to your server from your app using the following url : http://[youripaddress]/moodle

*'''If you want to be able to connect from your mobile app, you need to connect your phone to your computer by means of usb cable. Then you need to allow connection sharing. Finally, copy the ip adress of the usb0 interface (from the command ifconfig) and paste it in your config.php file. You should be able to connect to your local server from your mobile app.'''

==How to install a LDAP local server ? (on linux)==
* [http://directory.apache.org/apacheds/download/download-archive.html ApacheDS Download]
* Follow the instructions
* To launch the server, open a new terminal, go to your LDAP server directory, then open bin directory, and execute the following command : "./apacheds.sh start"
* If you got the following error : "./apacheds.sh: 105: ./apacheds.sh: Syntax error: "(" unexpected (expecting ")")", change the first line of the script to "#!/bin/bash"

=Usefull links=
*[https://docs.moodle.org/dev/Core_APIs API Moodle]
*[https://github.com/moodlehq/moodlemobile Moodle mobile sources]
*[http://cordova.apache.org/ Apache Cordova]
*[http://air.imag.fr/index.php/SCL3711 NFC Reader SCL3711]
*[https://docs.moodle.org/dev/Authentication_plugins How to create a new authentication module - Official Moodle documentation]

Proj-2014-2015-SmartClassroom/Scrum

2015-03-09T12:40:52Z

Marie.Darrigol: /* Scrum */

= Product backlog =
This is a link to access the Scrum of our project :
*[https://waffle.io/AlanDamotte/SmartClassroom Scrum]
Because our git repository is private, the Scrum has been create on a free repository which doesn't include any code. Please check the main page of our project to access the link of our Github repository. You'll need to have an authorized access. Contact us if you want to access our sources.

==Project description==
Students come in class, announce their presence and get settled at their work station. The teacher does the same and accesses his plateform where he can get courses and exams that he has created before. Then, the teacher can submit multiple-choice questionnaire to students. They answer to it individually before submitting their answer to the teacher. After that, he can refer to the results and publish it by theme. The teacher can start again a lesson if he sees that it hasn't been clear enough for his students. Finally, he can reorganize students by working group.

==User Stories==
*'''n°1''' : As a student or a teacher, I want to log in my Moodle account using a NFC tag so that I can directly access my personnal account.
*'''n°2''' : As a teacher, I want to create, modify courses so I can display them on a screen or a wall.
*'''n°3''' : As a teacher, I want to create, modify and share quizzes with my students so they can answer it.
*'''n°4''' : As a student, I want to be able to access the courses.
*'''n°5''' : As a student, I want to be able to answer the quizz.
*'''n°6''' : As a teacher, I wish I could see the results of the quizzes.
*'''n°7''' : As a student or a teacher, I wish I could use classic connection so that I can access to my Moodle account with my username and my password.

==Tasks==
*Study and understanding of the technologies we will use (CAS/LDAP, Cordova,...)
*Connection to Moodle account by means of the NFC tag
**User story n°1
*Courses and exams modifications
**User stories n°2 and 3 (creation and modification)
**User stories n°4 and 5 (use by students)
*Allow classic connection (username and password)
**User story n°7
*Display of results for each student
**User story n°6

==Sprints==
===To do===
*Course management (1 week)
**The application has to provide tools to create, modify, publish courses or exams.
*Results display (1 week)
**The application has to provide tools to display results of quiz that have been answered.

===In progress===
*Connection establishment (4 weeks)
**The aim is to understand which technologies are already used for Moodle connection.
**The aim is to establish the connection to the student Moodle account while clock-in by means of the NFC tag.

===Finished===
*CAS and LDAP understanding
**This task was assigned to Anthony Leonard and Romain Barthelemy. They had to understand how LDAP and CAS work in order to begin the connection establishement.
**[http://en.wikipedia.org/wiki/Central_Authentication_Service What is CAS ?]
**[http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol What is LDAP ?]