Note
As per course requirements, we have ensured that the repository name exactly matches our team name. Please see below for the project overview.
This repository is based on a project template provided by Associate Professor Vlado Sruk, PhD. We have modified this template to suit our needs and would like to acknowledge the professor's effort in providing a solid foundation for our project assignment.
This collaborative effort was undertaken as part of a project assignment for the Software Engineering course at the Faculty of Electrical Engineering and Computing at the University of Zagreb.
The AI Research Lab Management (AIReLM) application simplifies management for academic and private institutions working on AI research, enabling project proposal submission, task assignment, progress tracking, result testing, and expense tracking.
For a more comprehensive description of the project, please refer to the wiki.
-
User Registration
Users can register an account. -
Institution Creation
The system facilitates the establishment of an institution. -
Access Request
You can submit an access request to a specific institution. -
Researcher Project Idea Submission
Each researcher in the institution can submit their project proposal directly to the institution. -
Team Invitation and Management
Team leaders can assemble their teams.
For a complete list and more comprehensive description of the functional requirements, please refer to the wiki.
-
Security
The application should ensure the confidentiality, integrity, and availability of user data. -
Usability
The application should be easy to use for all intended users. -
Scalability
The application should be able to handle a large number of users and projects without compromising performance. -
Performance
The application should respond quickly to user interactions and load times should be minimized. -
Reliability
The application should be reliable, users should be able to use it without expecting crashes and errors and in case they do happen, data should not be lost.
For a more comprehensive description of the non-functional requirements, please refer to the wiki.
To get started, open your terminal, and run the following command:
docker compose up| Name | GitHub account | Role |
|---|---|---|
| Filip Alaber | @GrmiSijeva | |
| Marko Flegar | @mflegar | |
| Josip Koprivnjak | @Josip-Koprivnjak | |
| Vedran Maksić | @VedranMaksic | |
| Antonija Pandžić | @Antonija-Pandzic | |
| Antonio Tolić | @antoniotolic | |
| Niko Žužul | @NikoZuzul |
Read our contributing guide to learn about our development process.
As students, you are likely familiar with the minimum standards of acceptable behavior as defined in the FER Student Code of Conduct, as well as additional guidelines for teamwork on the Software Engineering course. We expect you to respect the IEEE Code of Ethics, which plays an important educational role in establishing the highest standards of integrity, responsible behavior, and ethical conduct in professional activities. By doing so, the community of software engineers defines common principles that define moral character, making important business decisions, and establishing clear moral expectations for all members of the community.
The Code of Conduct is a set of enforceable rules that serve to clearly communicate expectations and requirements for community/team work. It explicitly defines the obligations, rights, unacceptable behavior, and corresponding consequences (in contrast to an ethical code). A widely accepted Code of Conduct for working in an open-source community has been provided within this repository.
This repository contains Open Educational Resources and is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license that allows you to download, share, and modify the work as long as you:
- Attribute the author
- Do not use it for commercial purposes
- Share it under the same terms
- All third-party packages are distributed under their own licenses
- All other resources (images, models, animations, etc.) are distributed under their own licenses
- The repository's wiki is subject to the same licensing terms as the repository itself
@software{fnmjava2025relm,
author = {{fnm.java}},
title = {{AIReLM}},
url = {},
version = {0.1.0},
year = {2025}
}