MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for the ‘punchlines’ tag

Punchlines – ECN PAPPL 2013 OptimMarkus – 2013-03-20

without comments

Claire:

Gaëtan:

  • submitted pull request to add unit tests for issue #559
  • worked on issue #230: suggested UI design, dove into code

 

Written by G_Girin

March 20th, 2013 at 8:51 am

Posted in Developer Essentials

Tagged with , ,

Punchlines – ECN PAPPL 2013 OptimMarkus – 2013-03-11

without comments

Claire

Gaëtan

Written by G_Girin

March 11th, 2013 at 4:18 pm

Posted in Developer Essentials

Tagged with , ,

Punchlines – ECN PAPPL 2013 OptimMarkus – 2013-02-18

without comments

Claire

  • was assigned to issue #1007
  • worked on issue #1007: examined existing code in order to find the methods needed for this feature

Gaëtan

  • reproduced issue #559 and added a more detailed description – as a comment
  • got started developing to implement the required feature
  • learned how to use the debugger

 

Written by G_Girin

February 18th, 2013 at 4:40 pm

Posted in Developer Essentials

Tagged with , ,

Punchlines – ECN PAPPL 2013 OptimMarkus – 2013-02-11

without comments

Claire

Gaëtan

 

Written by G_Girin

February 12th, 2013 at 12:25 pm

Posted in Developer Essentials

Tagged with , ,

Punchlines ECN – 12th December 2012

without comments

Here are the punchlines from our group (students from Centrale Nantes):

Amandine:

Status :

  • Order contents of the final reports
  • Reuse the controller results to get the results of an assignment
  • Creation of the code to insert graphs

Next steps :

  • Repartition of the parts of the final report
  • Continue the views and hope they will run!

Road block :

  • None

Alexy & Nora:

Status :

  • Revert a wrong method to define skills and objective
  • Creation of the reusable concept : when created, a criterion can be chosen as “reusable” with a checkbox. Then, when changing a marking scheme, a reusable criterion can be chosen among a list of reusable criteria. He is then added to the marking scheme (so than he can be edited if needed).

Next steps :

  • Finishing the creation and the implementation of reusable criterion

Road block :

  • None

Nicolas and Sebastien:

Status :

  • Revert our wrong changes to the views.
  • Reflexion on how to adapt the results and home controllers to display the new graphs and marks in the right way and at the right place.

Next steps :

  • Validate the final report’s plan and write the report.

Road block :

  • All other changes we need to do are too long and too complex for us to do it in time.

Antoine

Status :

  • Start adding methods to the controller “assignments” so as to get the data used to display results graphs in the assignment view as a student
  • Start writing the html and javascript to display those data

Next steps :

  • Finish it
  • Work on the final report

Written by amandine.lavergne

December 12th, 2012 at 10:36 am

Posted in Status Reports

Tagged with ,

Punchlines ECN – 21st November 2012

without comments

Here are the punchlines from our group (students from Centrale Nantes):

Amandine:

Status

  • Redefinition of objectives and skills with the benefit of insight
  • List files which call rubric and flexible criterion,
  • Understand the association table

Next steps :

  • Identify how the display of the graphs is made
  • Beginning final reports
  • Identify, according to what we can do from our requirement document, which views and controlers will be implemented

Alexy:

Status :

  • First elaboration of the migration for the models about rubric_criterion and flexible_criterion
  • Beginning of the elaboration of the views of a student (graphs page and stats page)

Next steps :

  • Modification of the migration to include a has_many relation between a rubric_criterion and different levels of evaluation (optional)
  • Continue to create the views for the students (so that they can look at their evolution and their marks)

Nicolas:

Status :

  • Participating in the elaboration of the migration for the rubric_criterion and flexible_criterion models
  • Working on reusable criterion
  • Redefinition of objectives and skills

Next steps :

  • Modification of the migration to include a has_many relation between a rubric_criterion and different levels of evaluation
  • Final reports

Nora:

Status :

  • First elaboration of the migration for the models about rubric_criterion and flexible_criterion
  • Working on skill and objective definitions

Next steps :

  • Working on reusable criterion
  • Beginning final reports

Antoine

Status :

  • Start working on the views to be implemented
  • Identify the files to be modified
  • Comprehension of the way graphs are generated

Next steps :

  • Keep on working on the views

Written by amandine.lavergne

November 21st, 2012 at 1:51 pm

Posted in Status Reports

Tagged with ,

Punchlines ECN – 14th November 2012

without comments

Here are the punchlines from our group (students from Centrale Nantes):

Amandine:

Status :

  • I am still in the installation of MarKus with my new computer.

Next steps :

  • Extreme programming while my computer don’t have MarkUs installed
  • List files which call rubric and flexible criterion, create the association tab of skills and objectives (inheriting from rubric and flexible criterion)
  • Understand the association tab
  • Identify, according to what we can do from our requirement document, which views and controlers will be implemented
  • Identify how the display of the graphs is made

Road block :

  • My computer crashed.

Alexy:

Status :

  • Tasks defined and shared within the three groups
  • Elaboration of the new models which will inherit from rubric_criterion and flexible_criterion
  • Possible creation of a new table for the objectives (with a precision of one and a scale of 100) or reuse of the existing table for flexible criteria and change of the precision and/or scale

Next steps :

  • Define new methods to modify the number of levels of a skill (number of levels of a rubric criterion)
  • Discover where the marks of a student relatives to a criterion are stored

Road block :

  • Sick

Nicolas:

Status :

  • Teams and tasks defined
  • Working with Seb on skills and objectives (and temporarily with alexy and nora)

Next steps :

  • Evaluation of what can and what cannot be done
  • New models for skills and objectives to define and implement
  • Work on the future join table(s)

Road block :

  • None

Sebastien: Sick

 

Nora:

Status :

  • Finished Rails for Zombies tutorial
  • Tasks defined and shared within the three groups
  • Tried to code skills and objectives with no success

Next steps :

  • Understand the association tab
  • Identify, according to what we can do from our requirement document, which views and controlers will be implemented
  • Study the way to use inheritance for skills and objectives

Road block :

  • Problems with git

Antoine

Status :

  • Tasks defined and shared within the three groups
  • Start identifying which files use rubric and flexible criterion

Next steps :

  • List files which call rubric and flexible criterion, create the association tab of skills and objectives (inheriting from rubric and flexible criterion)
  • Understand the association tab
  • Identify, which views and controllers will be implemented

Written by amandine.lavergne

November 14th, 2012 at 11:56 am

Posted in Status Reports

Tagged with ,

Punchlines ECN – 7th November 2012

without comments

Here are the punchlines from our group (students from Centrale Nantes):

Amandine:

Status :

  • Only reviewing code and tutorials Rails For Zombies

Next steps :

  • Organization of the development

Road block :

  • The holidays

Alexy:

Status :

  • Continue studying the code.

Next steps :

  • Identify clearly what can be done according to the time remaining and share it.

Road block :

  • The holidays.

Nicolas:

Status :

  • Learned rubyonrails with rails4zombies
  • Studying Markus’ code

Next steps :

  • Identify work to be done in the code

Road block :

  • holidays

Sebastien:

Status :

  • Began to study the code.

Next steps :

  • Identify what needs to be done and share the work.

Nora:

Status :

  • Learned rubyonrails with rails4zombies : almost finished
  • Studying Markus’ code

Next steps :

  • Finish rails4zombies
  • Understanding Markus’ code’s structure

Road block :

  • Holidays

Antoine

Status :

  • Reviewing MarkUs code and tutorial on Ruby On Rails

Next steps :

  • Identify the work to be done

Road block :

  • Holidays

Written by amandine.lavergne

November 7th, 2012 at 11:17 am

Posted in Status Reports

Tagged with ,

Punchlines ECN – 24th October 2012

without comments

Here are the punchlines from our group (students from Centrale Nantes):

Amandine:

Status :

  • Final validation of the requirement document
  • Study of the code of MarkUs
  • Quick review of Ruby On Rails and of RailRoady (UML diagram for Rails)

Next steps :

  • Development and development
  • Implementing a quality phase

Alexy:

Status :

  • Final modifications of the views to match the requirement document
  • Final version of the requirement document
  • Studying of the existing code about markus

Next steps :

  • Elaborating the different teams and which tasks they are going to work on
  • Finding someone who is familiar with MarkUs

Nicolas:

Status :

  • Worked on the final version of the requirements doc
  • Learning Ruby on Rails (for Zombies)

Next steps :

  • Look at MarkUs’s code

Sebastien:

Status :

  • Final modification of planning
  • Final version of requirements

Next steps :

  • Dig in MarkUs’s code

Nora:

Status :

  • Final validation of the requirement document
  • Study of the code of MarkUs
  • Get familiar with git

Next steps :

  • Trying to implement quality methods for the development
  • Continue studying MarkUs code

Antoine

Status :

  • Final validation of the requirement document
  • Study RoR and Railroad
  • Look at the code of MarkUs

Next steps :

  • Start development

Written by amandine.lavergne

October 24th, 2012 at 9:04 am

Posted in Status Reports

Tagged with ,

Punchlines ECN – 17th October 2012

without comments

Here are the punchlines from our group (students from Centrale Nantes):

Amandine:

Status :

  • Made the planning of the project
  • Reflexion about the views according to the scenarios

Next steps :

  • Validation of the requirement document by Morgan Magnin with the different views
  • Focus on which points to develop
  • Point with all the team for the technical aspects

Road block :

  • Issues with the planning still on the part “development” which won’t be clear until the requirement document is not validated

Alexy:

Status :

  • First elaboration of the development part of our project
  • Creation of some of the views to illustrate our project according to the scenarios
  • Learning of Ruby
  • Precision of the specifications

Next steps :

  • Validation of the specifications
  • Finish the development part of the planning
  • Start the sharing of the tasks (development part)

Nicolas:

Status :

  • Summarized and synthesized the poll’s results
  • Worked on the requirements document (mainly translation)
  • Learning Ruby

Next steps :

  • Finish the development part of the planning
  • Validation of the requirements document by Mr. Magnin
  • Become more familiar with Markus
  • Ruby on Rails

Sebastien:

Status :

  • Reflexion on the planning
  • Analysed and summarized the poll’s results
  • Ruby

Next steps :

  • Finish the development part of the planning
  • Validation of the requirement document by Morgan Magnin

Nora:

Status :

  • Working on the requirement document (adding sequence diagrammes)
  • Correcting the requirement document

Next steps :

  • Learning more about Ruby
  • Finishing the requirement document

Antoine

Status :

  • Creation of views to illustrate our project according to the scenarios
  • Start learning Ruby
  • Correcting the requirement document

Next steps :

  • Validation of the requirement document
  • Keep on learning Ruby

Road block :

  • None

Written by amandine.lavergne

October 17th, 2012 at 8:56 am

Posted in Status Reports

Tagged with ,