Skip to content

2026.1

Class 2026.1

Meetings

Aula Qua. 12h00 14h00
Aula Sex. 12h00 14h00
Atendimento Ter. 12h00 13h30

Instructors

[ Instructor : Humberto Sandmann]

[ Student Assistant : Lucas Abatepietro]

Students

Grade

\[ \text{Final Grade} = \left\{\begin{array}{lll} \text{Individual} \geq 5 \bigwedge \text{Team} \geq 5 & \implies & \displaystyle \frac{ \text{Individual} + \text{Team} } {2} \\ \\ \text{Otherwise} & \implies & \min\left(\text{Individual}, \text{Team}\right) \end{array}\right. \]
2026-02-25T21:31:14.060832 image/svg+xml Matplotlib v3.10.8, https://matplotlib.org/
  1. Quizzes: the course will have 3 quizzes, the quiz with the lowest grade will be dropped. And, the final quiz grade will be the uniform average of the two best grade quizzes:

    \[ \text{Quizzes} = \frac{\text{Q1} + \text{Q2} + \text{Q3} - \min(\text{Q1}, \text{Q2}, \text{Q3})}{2} \]
  2. Microservice: the students will have to implement a microservice. The grade is a concept grade, based on Notas da Engenharia:

    Concept Grade
    A (+) 9 (10)
    B (+) 7 (8)
    C (+) 5 (6)
    D 4
    I 0
  3. Team: the team have to be composed by 2 up to 3 members. The team grade will be the same for all members of the team. The team grade will be based on the project delivery and documentation.

    Group Registration

    Deadline to register: March 6th, 2026.

    Teams from 2 up to 3 members.

    Create a repository on GitHub to share the project code and documentation.

    Form to register student groups: https://forms.gle/DoRxGcnx5vb5ggkYA.

    This is MANDATORY to organize the teams and the AWS accounts.

    Repository name

    The repository name should be something profissional, for example: platform, microservices, etc.

    Also, the repository should linked to GitHub authors.

  4. Documentation: the project documentation will be evaluated based on the quality of the documentation and the completeness of the documentation. The documentation should be complete and should cover all the aspects of the project, including the architecture, the design decisions, the implementation details, and the testing strategy. The documentation should be clear and concise, and should be easy to understand. The documentation should be well-structured and should follow the best practices of software documentation. The purpose of the documentation is to provide a portfolio about the subject to potential employers or collaborators.

    Documentation Requirements

    Deadline to deliver: May 22th, 2026.

    The project documentation HAVE TO be hosted on GitHub Pages and should be public;

    The format to publish the documentation is mkdocs, the documentation should be published in the GitHub Pages;

    A template based on material is available to assist with the documentation: delivery template.

    Template

    A template based on material is available to assist with the documentation: delivery template.

    1. Fork the template repository;
    2. Clone the forked repository;
    3. Edit the documentation;
    4. Push the changes to the forked repository;
    5. Publish the documentation on GitHub Pages.

    There is instructions more accurate on Using this template.

Planning

Repositories

Principal: https://github.com/repo-classes/pma.261

Microservice Interface Implementation
Account account account-service
Auth auth auth-service
Gateway gateway-service