Deliverable 4 - sidarragac/JobJourney GitHub Wiki
- 1. Project requirements
- 2. Infographic
- 3. System design
- 4. Usability analysis
- 5. Future work
- 6. Repository
- 7. Video
| Requirement identifier | Requirement | Developed |
|---|---|---|
| FR01 | If there's a new user, The JobJourney web application shall provide the user with the ability to register using a form. | Yes |
| FR02 | The JobJourney web application should provide the user with the ability to login in their account to access their process in roadmaps. | Yes |
| FR03 | The roadmap system shall provide the user with the ability to register their specific interests and objectives. | Yes |
| FR04 | The roadmap system shall use LLM models to create a roadmap based on the given objectives and interest of the user. | Yes |
| FR05 (OLD) | The roadmap system should add to the roadmap job suggestions the user can take on each step. | No |
| FR05 (NEW) | The roadmap system shall ensure complete visualization of the provided information of LLM model | Yes |
| FR06 | The roadmap system should provide the user with the ability to mark a step as a completed. | Yes |
| FR07 (OLD) | The roadmap system could provide the user with the ability to request updates on some steps of the roadmaps. | No |
| FR07 (NEW) | The roadmap system could provide the user with the ability to delete a roadmap. | Yes |
| FR08 (OLD) | The data-analisys system should display by areas of interest, the roadmap completion of other users if and only if they are similar to the user's interest. | No |
| FR08 (NEW) | The data-analisys system should display the roadmaps of other users priorized by same interests and city. | Yes |
| FR09 | The roadmap system could bring recommendations based on every specific goal. | No |
| FR10 | The data-analisys system should allow to visualize other users roadmaps and progress by filtering some pre-established categories. | Yes |
| FR11 (OLD) | The roadmap system could provide the user with the ability to build different roadmaps that shows different ways to reach the same goal. | No |
| FR11 (NEW) | The roadmap system could provide the user with the ability to build different roadmaps. | Yes |
| FR12 | The JobJourney web application should bring the user categories to distinguish the the different roadmaps the users request. | Yes |
| FR13 | The JobJourney web application could be able to use the Google OAuth tool to register and log in. | Yes |
| FR14 | The roadmap system could use webscrapping tecniques to bring information regarding the user's proposed goal. | No |
| FR15 | The roadmap system could allow the user to clone other users roadmap in order to complete it themselves. | Yes |
| FR16 (NEW) | The JobJourney web application should allow users to like a roadmap. | Yes |
| FR17 (NEW) | The web application should allow the user to select the language of the information displayed. | Yes |
| FR18 (NEW) | The JobJourney web application could allow users to provide links to their social networks, update their profile picture and change their interests. | Yes |
| NFR1 | The JobJourney web application should be user-friendly, creating a simple UI that explicitly shows where is the user standing at and implementing well labeled buttons. | Yes |
| NFR2 (OLD) | The JobJourney web application should be fast preventing the usage of large animations or heavy files. | No |
| NFR2 (NEW) | The JobJourney web application should have an intuitive navigation system and navigation bar allowing users to access any page within 3 clicks or less. | Yes |
| NFR3 | The JobJourney web application should guarantee that the password created by the user is secure by verifying that it has at least one capital letter, one symbol, one number and more than 8 characters. | Yes |
| NFR4 | The roadmap system should allow the user to visualize the progress of a roadmap. | Yes |
| Comment/Observation | Possible improvement action | Improvement implementation |
|---|---|---|
| Too much text in screen when showing the roadmap. | Using modals may help not stacking a bunch of text in the screen at the same time. A modal for each step containing the checkpoints, study material and job suggestion. | Yes |
| Brief explanation could be added in the interest selection form, to inform the user the purpose of selecting the interests. | Add a description in the interest selection form mentioning the purpose of the selected interests. | Yes |
| Register form camps delete after making a mistake, it’s tedious to fill it in all over again. | Send back the data that the user already entered back to the template so it´s pre filled when the user retries to fill the form. Adding a visual indicator showing that the password and password confirmation match may also be helpful. | Yes |
| The whole web app looks monochrome, black and white. | Add blue titles and headers according to the selected color palette. Adding some unique color to each interest and display it (in a tag) when showing a list of roadmaps can make the explore section, analytics and user profile look more colorful. | Yes |
Although the roadmaps provide recommended studying material, there is no way to validate that the person is actually using it and fulfilling what the checkpoints say. A way to validate that the person is actually completing what the checkpoint suggests could be implemented. Either by connecting JobJourney to educational applications that provide certification or allowing users to upload certificates to their profile to validate roadmaps.
The job suggestions provided in each step of the roadmap aren´t very specific. Taking into account that the product owner already works with real vacancies of multiple companies, every step of a roadmap could have a real job that the person could apply to. Even better, implementing a way to give people access to a list of real vacancies after completinmg each step.