To make it easy for you to get started with GitLab, here's a list of recommended next steps.
### Groupe jour
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
- Systèmes de base de données / ISC_431 /
- Horaires: 11h15-12h00 - 13h00-14h30
## Add your files
### Groupe soir
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
- Vous pouvez me contacter par email pour prendre rendez-vous ou pour des questions administratives ou d'ordre général
- Vos questions **techniques et théoriques seront ignorées** -> venez au cours,
- Je réponds toutefois à vos questions à mon bureau en **B506** le **jeudi de 14h à 15h**
- Quentin Leblanc répond à vos questions à son bureau **A403** les:
- lundi, jeudi et vendredi toute la journée
- Joël von der Weid répond à vos questions à son bureau **A403** les:
- lundi matin, mardi après-midi et mercredi
## Programme
### Semaine 1 - 19 et 21 février
- chapitre 0
- chapitre 1 - Intro Base de données
- chapitre 2 - Modélisation EA
### Semaine 2 - 26 et 28 février
- chapitre 2 - modélisation EA - FIN
- exercices
### Semaine 3 - 04 et 06 mars
- corrections des exercices
- exercices
### Semaine 4 - 11 et 13 mars
- chapitre 3 - intro BD rel.
- exercices
### Semaine 5 - 18 et 20 mars
- chapitre 4 - modélisation relationnelle
- Exercices serie 4
### Semaine 6 - 25 et 27 mars
- chapitre 5 - algèbre relationnelle
- exercices serie 4
### Semaine 7
## Integrate with your tools
-**Vacances**
-[ ] [Set up project integrations](https://gitedu.hesge.ch/stephane.malandai/sbd2024/-/settings/integrations)
### Semaine 08 et 10 avril
## Collaborate with your team
- corrigé d'exercices serie 4
- exercices serie 5
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
Use the built-in continuous integration in GitLab.
### Semaine 9 - 25 avril et 27 avril
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
- chapitre 6 - modélisation mod. rel. -> FIN
- exercices serie 6
***
### Semaine 10 - 2 mai et 4 mai
# Editing this README
- Corrigé série 6
- Test 1 : modèle EA et modèle relationnel
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
### Semaine 11 - 9 mai et 11 mai
## Suggestions for a good README
- chapitre 7 : Le SQL
- TP : mise en place de Sqlite
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
### Semaine 12 - 16 mai et 18 mai (ascension)
## Name
Choose a self-explaining name for your project.
– Chapitre 7 - SQL (fin)
- TP 1 : bdd eleves/profs
- lien pour télécharger la bdd : http://gofile.me/6Zy9q/vHomOD4YT
- exercices serie 7 (requêtes)
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
### Semaine 13 - 21 mai et 23 mai
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
– correction test
- correction serie 7
- correction TP1
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
### Semaine 14 - 30 mai et 1 juin
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
- Corrections d'exercices
- TP
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
### Semaine 15 - 6 juin et 8 juin
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
- Chapitre 8
- Corrections - révisions
- TP
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
### Semaine 16 - 13 juin et 15 juin
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
- Test final
- Vos droits: deux feuilles de notes manuscrites individuelles recto-verso écrites à la main
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
### Semaine 17 - 21 juin et 23 juin
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
- Rendu TP : 21 Juin
A rendre:
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
- un rapport (max. 4 pages) comprenant
- Votre modèle EA avec notes et limitations
- Votre modèle relationnel avec notes et limitations
- Si vos modèles sont trop élaborés, vous pouvez prendre un périmètre restreint de votre modèle rel. précédent
- un index => https://www.sqlite.org/lang_createindex.html
- 10-12 requêtes SQL testées à l'aide de votre BD
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.