-
Notifications
You must be signed in to change notification settings - Fork 0
Report 5
Each team member successfully completed their individual parts of the stub application. Every member created their own branch from feature/stub-app, implemented a button that redirects to a new page displaying a public API response, and merged their personal branch back into feature/stub-app. A Dockerfile was already included in the stub application base.
We have begun planning our term project by defining Git conventions, choosing a team structure, and assigning roles. The MVP and Final Milestone plans are still in progress and will be finalized soon.
We follow Conventional Commits, inspired by the AngularJS Commit Guidelines.
Format: <type>(<scope>): <subject> (max 100 chars per line)
Types: feat, fix, docs, style, refactor, perf, test, chore
Rules:
- Imperative, present tense ("add" not "added")
- No capital first letter, no period at the end
- Optional body for motivation/context, optional footer for issue references (
Closes #12) orBREAKING CHANGE:
We follow Conventional Branching. Format: <type>/<description> — lowercase, hyphens only, no special characters.
Prefixes: feature/, bugfix/, hotfix/, release/, chore/
Example: feature/add-login-page, bugfix/fix-header-bug
- Minimum 1 reviewer approval required
- No self-merge
- PR description mandatory (what changed & why)
- PR author resolves conflicts
- Squash merge to keep history clean
- Branch must be up to date with target before merging
We chose Option A: Specialized Sub-Teams.
| Sub-Team | Members |
|---|---|
| Backend | Ali, Ulaş |
| Frontend | Ekin, Bora |
| Mobile & DevOps | Ömer, Baran, Arif |
As per Option A, members assigned to DevOps are also part of either the Frontend or Backend sub-teams, ensuring cross-functional knowledge for infrastructure tasks.
Bora Aydemir
- Created my personal branch (
feature/stub-app-BoraAydemir-button) and updatedconfig.jsandhandlers.jsto add a personalized button to the homepage. - Designed a new UI page (
boraaydemir.html) formatted as a football player card and integrated TheSportsDB API to dynamically fetch and display live athletic data. - Opened a Pull Request to merge my individual implementation into the team's shared branch. #72
- Contributed to determining the team conventions (commit naming, branching, and merge policies). #64
Ekin Kılıç:
- Created personal branch
feature/stub-app-ekin-buttonfromfeature/stub-app - Implemented Button 3 ("Ekin's API") that redirects to a page calling the Random User API and displays user data (name, email, location, phone)
- Created
ekin.htmlwith API integration and styled output - Modified
handlers.jsandconfig.jsaccordingly - Pushed changes and opened a pull request to merge into
feature/stub-app - Wrote the Lab 5 report
Ömer Belemir Delier:
- Created personal branch
feature/stub-app-omerbelemir-buttonfromfeature/stub-app - Implemented a button that navigates to a new page displaying real-time data from a public API
- Developed a simple
Dockerfileto containerize the application and ensure consistent build and runtime environment - Created the results page with API integration and added a brief explanation of the returned API values for users
- Followed team commit conventions (e.g.,
feat:/fix:) during development - Merged the personal branch back into
feature/stub-appafter verifying it met the team’s merge policies - Pulled and synchronized the
feature/stub-appbranch to ensure development started from the correct team baseline
Ulaş Sertan Kemeç
- Created personal branch 'feature/stub-app-UlasSertan-button' from 'feature/stub-app'
- Implemented Button 5
- Modified
handlers.jsandconfig.jsaccordingly - Pushed changes and opened a pull request to merge into
feature/stub-app
Arif Evren
- Added a new page (
arif-evren.html) linked to the "Arif Evren" button (Button 7) on the stub app. - The page fetches live data from the Open-Meteo API (free, no API key required),
displaying current weather conditions in Istanbul, Turkey. - Implemented the
onButton7Clickhandler inhandlers.jsto navigate to the new page. - Committed and pushed the changes to the remote branch
feature/stub-app-ArifEvren-button.
Baran Önder
- Created sub-issues for Lab 5 Report
- Created separate issue for Implementation Plan (MVP + Final Milestone)
- Added Pull Request template (
.github/PULL_REQUEST_TEMPLATE.md) to standardize PR descriptions across the repository - Implemented "Baran - Joke" button in
config.jsandhandlers.js - Created
baran.html— fetches and displays a random programming joke from JokeAPI - Added
Dockerfileusing nginx:alpine to serve the static app - Opened PR from
feature/stub-app-Baran-buttonintofeature/stub-appwith proper description following team conventions
Ali Akkaya
- Created personal branch feature/stub-app-AliAkkaya-button from feature/stub-app
- Implemented a button in config.js and handlers.js that redirects to a new page fetching data from a public API
- Created ali-akkaya.html with API integration and styled the displayed response for readability
- Pushed changes and opened a pull request to merge into feature/stub-app
- Contributed to team discussions on Git conventions and branch naming policies
- Elicitation Questions
- Requirements
- Implementation Plan
- Test Plan & Coverage
- MVP Demo Plan
- Communication Plan
- Responsibility Assignment Matrix
- Use of Standards
- Project Retrospective
- Final Demo Plan
- Final Milestone Deliverables
- Report 1 - Requirements Elicitation & Repository Setup
- Report 2 - SRS Through Scenarios & Mock-ups
- Report 3 - From Scenarios to Use Case Diagrams
- Report 4 - Class Diagrams & Use-case Diagrams
- Report 5 - Git Workflow, Stub Application, and Planning
- Report 6 - Planning for Implementations & Tests
- Report 7 - Finalizing Plan for MVP Milestone Demo
- Report 8 - Standards & Plan Revision
- Report 9 - Requirements Review & Acceptance Testing
- Report 10 - Finalizing Plan for Final Milestone Demo
- 2026-02-18: Weekly Meeting #1
- 2026-02-18: Customer Meeting #1
- 2026-02-25: Stakeholder Meeting
- 2026-02-25: Weekly Meeting #2
- 2026-03-04: Weekly Meeting #3
- 2026-03-11: Weekly Meeting #4
- 2026-04-01: Weekly Meeting #5
- 2026-04-15: Weekly Meeting #6
- 2026-04-22: Weekly Meeting #7
- 2026-04-29: Weekly Meeting #8
- 2026-05-06: Weekly Meeting #9