Skip to content

Instantly share code, notes, and snippets.

@AntonyMRuiz

AntonyMRuiz/crudactivity-ProjectSync.md

Created October 22, 2025 05:22
Show Gist options
  • Save AntonyMRuiz/8621f03a1a5828a8605c789af28ffd5b to your computer and use it in GitHub Desktop.
Save AntonyMRuiz/8621f03a1a5828a8605c789af28ffd5b to your computer and use it in GitHub Desktop.
Download ZIP
Raw
crudactivity-ProjectSync.md

CRUDACTIVITY — ProjectSync

Database Integration, ORM, Git Flow, and Azure DevOps Traceability

Context

Crudzaso aims to develop ProjectSync, an internal tool designed to register and track the active projects within the organization. The goal is for each team to build a system that manages essential project information such as name, status, description, and responsible person, while ensuring complete traceability of the development process and collaboration across the team.

This activity focuses on applying both technical and professional skills: connecting to a real database, implementing an ORM, maintaining version control with Git Flow, and documenting the process through Azure DevOps.

Technical Requirements

  • Language: Java 21
  • Framework: Spring Boot (Web, Data JPA, Validation)
  • Database: MySQL 8
  • ORM: JPA/Hibernate with Spring Data JPA
  • Testing: JUnit 5 (unit and integration)
  • Frontend: HTML + JavaScript (Bootstrap or Tailwind)
  • Version Control: Git (following Git Flow principles)
  • Work Management: Azure DevOps Boards + Repos
  • Naming convention: English for code, endpoints, and structures

Functional Requirements

  • Connect the backend to a MySQL database with a table for project records.
  • Implement the complete CRUD flow (create, read, update, delete).
  • Validate all required fields and handle HTTP errors appropriately.
  • Add auditing fields for creation and update timestamps.
  • Build a frontend that interacts with the backend to manage projects visually.
  • Maintain and document progress through Azure DevOps and Git.

Azure DevOps Traceability

  • Create and manage Epics, Features, and User Stories.
  • Link commits, branches, and Pull Requests to the corresponding Work Items.
  • Follow the standard progress workflow: New → Active → Resolved → Closed.
  • Provide written evidence of progress, decisions, and agreements made by the team.
  • Document the implementation and outcomes of each User Story.

Testing and Quality

  • Unit tests to validate core business logic.
  • Integration tests to verify database connectivity and CRUD operations.
  • Validation of error handling and data consistency.
  • Functional tests of the frontend interacting with the backend API.

Deliverables

  1. Source code connected to a working MySQL database.

  2. REST API implementing all CRUD operations for project management.

  3. Frontend correctly integrated with the backend.

  4. Executable unit and integration tests.

  5. Git repository with documented commits and branches.

  6. Work traceability through Azure DevOps (Work Items, PRs, linked commits).

  7. A README document that clearly explains:

    • Project setup and execution steps.
    • Database connection configuration.
    • Team roles and responsibilities.
    • Lessons learned and final conclusions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment