This repository contains the Requirement Engineering, Design, Implementation & Testing (R&DD + I&T) project developed for the course Software Engineering 2 (A.Y. 2025–2026).
The project focuses on the analysis, design, and implementation of Best Bike Paths (BBP), a software system that supports cyclists in recording trips, sharing information about bike paths, and visualizing optimal routes between locations.
 |
 |
 |
 |
The goal of this project is to apply software engineering principles and methodologies to:
- Analyze system requirements
- Model the problem domain
- Define a robust system design
- Implement and test the system
The project is composed of three main deliverables:
- Requirement Analysis and Specification Document (RASD)
- Design Document (DD)
- Implementation and Testing Document (ITD)
- Acceptance Testing Document (ATD)
All documents are developed according to the structure and guidelines provided by the course instructors.
The repository is organized as follows:
.
├── RASD/ # Sources and artifacts for the RASD
├── DD/ # Sources and artifacts for the Design Document
├── ITD/ # Implementation and Testing deliverable
├── ATD/ # Acceptance Testing Document and automated tests
├── DeliveryFolder/ # Final PDF submissions (versioned)
└── README.md # Project overview
Best Bike Paths (BBP) is a system that allows:
- Users to record and analyze cycling trips
- Manual and automated insertion of bike path information
- Sharing and merging of path data across users
- Visualization of ranked bike paths between an origin and a destination
For collaborative writing, the team used Google Docs to draft the RASD document, allowing individual contributions and revisions to be tracked. For the DD, a Pro Overleaf account was purchased, enabling the team to view and utilize the full history of contributions. Because of this functionality, Google Docs was not used for the DD.
The following links allow to inspect the revision history of each document:
For the ITD and ATD deliverables, while the number of commits may not be equally distributed among team members, participation and contribution were equal across all parts of the implementation and testing phases. The commit distribution reflects workflow organization rather than individual contribution levels.
Final versions of the documents are exported as PDF files and committed to the DeliveryFolder in accordance with the project rules. The folder also includes a
CHANGELOG.md document, tracking all the notable changes (if any) applied to the final
deliverables, along with links to the corresponding pdf versions.
- Sebastiano Pietrasanta
- Pietro Saveri
- Ashley Andrea Squarcio
- Course: Software Engineering 2
- Academic Year: 2025–2026
- Project Type: R&DD + I&T