2018-2019 / PROJ0010-1

Software project engineering and management

Durée

20h Th, 290h Proj.

Nombre de crédits

 Master : ingénieur civil en informatique, à finalité10 crédits 
 Master en sciences informatiques, à finalité10 crédits 

Enseignant

Jean-Louis Binot, Benoît Donnet, Guy Leduc, Laurent Mathy

Langue(s) de l'unité d'enseignement

Langue anglaise

Organisation et évaluation

Enseignement durant l'année complète, avec partiel en janvier

Horaire

Horaire en ligne

Unités d'enseignement prérequises et corequises

Les unités prérequises ou corequises sont présentées au sein de chaque programme

Contenus de l'unité d'enseignement

In this course, teams of ± 5 students will carry out a substantial integrated software project, which mainly builds on the knowledge, know-how and skills achieved during their bachelor studies (i.e., programming, software engineering, data bases, operating systems and networks), with the goal of consolidating and integrating them, while achieving a realistic project for real users. The project will include several sprints during which a usable and potentially releasable product increment will be created. Seminars and continuous project reviews will also be organized to teach fundamentals in project management, group coordination, and communication.

Acquis d'apprentissage (objectifs d'apprentissage) de l'unité d'enseignement

The project aims at developing the students' ability to carry out a realistic, complex and incompletely defined software project from the conceptual to the operational phase.
The students will also learn and practice actively project management, including project and team leadership, reporting, oral presentations and defence, thereby improving their autonomy, their abilities to work efficiently in teams, and their communication and writing skills.

Savoirs et compétences prérequis

A bachelor degree in computer science or in engineering with a major in computer science.

Activités d'apprentissage prévues et méthodes d'enseignement

  • Seminars on fundamentals in project management;
  • Seminars on communication skills (oral and written);
  • Seminars on software engineering (static/dynamic diagrams, testing);
  • Sessions on team working;
  • Monthly project reviews, including oral presentations;
  • Feedback on technical progress and project management;
  • Writing of a final report;
  • Defence and demonstration of the project.

Mode d'enseignement (présentiel ; enseignement à distance)

  • Face-to-face seminars;
  • Monthly review meetings;
  • The project is mainly carried out remotely.

Lectures recommandées ou obligatoires et notes de cours

Slides used during the seminars.

Modalités d'évaluation et critères

The evaluation will be based on:

  • the intermediate review meetings (progress achieved, quality of project management) (45% overall, i.e., 10% per review meeting, except the Sprint 0 review that accounts for 5%),
  • the project completion report (10%),
  • the delivered software (30%),
  • the final project defence and demonstration (15%).
Templates are available for the various reports (product vision, product backlog, sprint backlog, project budget, timesheets).  Those reports are used by students to describe the project and their proposed solution with appropriate justifications about design choices. Those reports should also tackle the solution evaluation, some outstanding items, and the lessons learned.
The project defence consists of an oral presentation and a live demonstration of the system, followed by a question/answer session.
The final grade takes account of the amount and quality of the achieved work, the quality of the written report and of the oral presentation, as well as the relevance of the provided answers.
Typically, grades are assigned to the whole group.  However, in some particular cases (e.g., when there are evidences that a member of a group has not participated enough in the project), the grade may be assigned more individually, reflecting the personal involvement of each member of a group. Finally, as the course is essentially a single team project, no resit will be provided. This means that, no second chance to improve the grade will be given to students in case of failure in June.

Stage(s)

Remarques organisationnelles

  • Teams of +/- 5 students, built based on project subject preference, while ensuring a diversity of student profiles in each group (e.g., computer scientists and engineers).
  • Presence at the seminars and intermediate reviews is mandatory.
  • The project will start early during the 1st semester.
  • The final report must be submitted by mid-May.
  • The defences and demonstrations will be scheduled mid-May.
  • Detailed guidelines can be found on the course web site.

Contacts

Coordinators:

  • Jean-Louis Binot (jean-louis.binot@uliege.be)
  • Benoit Donnet (Benoit.Donnet@uliege.be)
  • Guy Leduc (Guy.Leduc@uliege.be)
  • Laurent Mathy (laurent.mathy@uliege.be)
Teaching assistant:
  • Benoît Mattheus (benoit.mattheus@uliege.be) 
  • Benjamin Laugraud (blaugraud@uliege.be)

Notes en ligne

Web page
The course web page contains PDF of the seminar slides, projects subjects, Sprints/Reviews details, the Course agenda.  In addition, students can interact with the Pedagogical Team through the Discusson Forum.