User Stories - chrisdacel/Backend_EcoRisaralda GitHub Wiki
| ID | Name | Summary | Responsible |
|---|---|---|---|
| HU001 | Tourist registration | As a tourist, I want to be able to register on the website to access personalized information. | Cristian Acevedo/Cristian Monsalve |
| HU002 | Ecotourism sites visualization | As a user, I want to view a list of available ecotourism sites in Risaralda with their photos and descriptions to choose the ones that interest me the most. | Cristian Acevedo/Cristian Monsalve |
| HU003 | User preferences | As a user, I want to select my tourism preferences (rivers, mountains, hiking, natural reserves) so the platform can recommend ecotourism sites according to my interests. | Cristian Acevedo/Cristian Monsalve |
| HU004 | Ecotourism site search | As a user, I want to search for an ecotourism site by name or location to find it easily. | Cristian Acevedo/Cristian Monsalve |
| HU005 | Geolocation of ecotourism sites | As a user, I want to visualize ecotourism sites on an interactive map to identify their exact location and plan my visit. | Cristian Acevedo/Cristian Monsalve |
| HU006 | Ecotourism site details | As a user, I want to visualize ecotourism sites on an interactive map to identify their exact location and plan my visit. | Cristian Acevedo/Cristian Monsalve |
| HU007 | Ratings and comments | As a tourist, I want to rate and leave comments about the ecotourism sites I visited to help other users make decisions | Cristian Acevedo/Cristian Monsalve |
| HU008 | Save favorite sites | As a registered tourist, I want to save my favorite ecotourism sites in a list to easily access them later. | Cristian Acevedo/Cristian Monsalve |
| HU009 | Ecotourism site management | As a tour operator, I want to register and manage the ecotourism sites I administer to promote them within the platform. | Cristian Acevedo/Cristian Monsalve |
| HU010 | Ecotourism event publishing | As a tour operator, I want to publish events and special activities related to ecotourism sites to attract more visitors. | Cristian Acevedo/Cristian Monsalve |
| HU011 | Personalized notifications | As a registered user, I want to receive notifications about new sites, events, or promotions to stay informed. | Cristian Acevedo/Cristian Monsalve |
| HU012 | Cross-platform (Web and Mobile) | As a user, I want to access information from both the website and the mobile app for greater convenience and availability. | Cristian Monsalve/Jackeline Giraldo |
| HU013 | Operator statistics dashboard | As a tour operator, I want to view statistics of my sites (visits, favorites, average ratings, and recent comments) to analyze performance and improve management. | Cristian Monsalve/Jackeline Giraldo |
| HU014 | Recommendation section | As a user, I want to view recommendations of ecotourism sites based on my preferences to discover places aligned with my interests. | Cristian Monsalve/Jackeline Giraldo |
| HU015 | User profile | As a user, I want to manage my personal profile (profile picture, name, last name, password change, and account deletion) to keep my information updated and control my account. | Cristian Monsalve/Jackeline Giraldo |
| HU016 | Administrative statistics dashboard | As an administrator, I want to view general system indicators (active tourists, operators, sites, and events) to understand platform status and make decisions. | Cristian Monsalve/Jackeline Giraldo |
HU001
| Element | Description |
|---|---|
| Tourist Registration | As a tourist, I want to be able to register on the website to access personalized information and save my favorite sites |
| - The user can view at least the name, description, image, and location of each ecotourism site. | |
| - The page size must be adaptable to any device. | |
| Acceptance Criteria | - The registration page must be adaptable to any device. |
| - The user must be able to access site information, search bar, and content filtering without needing to register. | |
| - The registered user must be able to save their selected ecotourism sites. | |
| - The registered user must have the option to choose their preferences so the system can recommend ecotourism sites according to their interests. | |
| Detailed Ecotourism Site Information Prototype | Figure 1. High-fidelity prototype of the user registration module. |
| Responsible | Cristian Acevedo / Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | Registration is independent from other system functionalities |
| Negotiable | It is well defined, but there is room for negotiable changes |
| Valuable | Provides value by enabling tourist account registration and access privileges |
| Estimable | Can be completed in one sprint with low effort for both mobile and desktop |
| Small | Does not require large space and registration is optional for general use |
| Testable | Must be tested and is easily testable |
HU002
| Element | Description |
|---|---|
| Ecotourism Sites Visualization | As a user, I want to view a list of available ecotourism sites in Risaralda with their photos and descriptions to choose the ones that interest me the most. |
| - As a user, I want to view sites from any device. | |
| - As a user, I want the information about ecotourism sites to adapt to the screen size. | |
| Acceptance Criteria | - As a user, I want to find information about ecotourism sites across all of Risaralda. |
| - As a user, I want to be able to save my preferred ecotourism sites. | |
| - The registered user must have access to an algorithm that helps decide a destination based on their preferences. | |
| Detailed Ecotourism Site Information Prototype | Figure 2. High-fidelity prototype of the site collection module. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | The visualization of ecotourism sites does not require user registration |
| Negotiable | It is well defined, but allows for negotiable changes |
| Valuable | Provides value by allowing users to view information and the range of ecotourism sites |
| Estimable | Can be completed in one sprint with moderate effort for both mobile and desktop |
| Small | Small enough to fit within a sprint |
| Testable | Must be tested and is easily testable |
HU003
| Element | Description |
|---|---|
| User Preferences | As a user, I want to select my tourism preferences (rivers, mountains, hiking, natural reserves) so that the platform can recommend and display ecotourism sites according to my interests. |
| Acceptance Criteria | - The user must be able to select one or multiple preferences from their profile. |
| - The system must store the preferences selected by the user. | |
| - The system must display recommended sites based on the user’s preferences. | |
| - The preferences section must be accessible only to authenticated users. | |
| - The selection interface must be clear, intuitive, and adaptable to mobile and desktop devices. | |
| Detailed Ecotourism Site Information Prototype | Figure 3. High-fidelity prototype of the user preference selection module. |
| Dependencies | A database with ecotourism site categories to filter content |
| User authentication system | |
| Preference-based recommendation logic | |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | This user story depends on the authentication system and the availability of categories in the database. |
| Negotiable | It is well defined, but allows adjustments in how preferences are selected or presented. |
| Valuable | Enables personalization of the user experience by displaying relevant content based on interests. |
| Estimable | Estimated medium effort due to data persistence and recommendation logic implementation. |
| Small | Can be developed in one or two sprints depending on the complexity of the recommendation system. |
| Testable | Can be validated through preference selection testing and recommendation accuracy. |
HU004
| Element | Description |
|---|---|
| Ecotourism Site Search | As a user, I want to search for an ecotourism site by name or location to find it easily. |
| - As a user, I want to search for any ecotourism site from the search bar without needing to register. | |
| - As a user, I want the search bar size to adapt to the screen size. | |
| Acceptance Criteria | - As a user, I want the search feature to be easy to use from any device. |
| - As a user, I want the search bar to display suggestions of ecotourism sites based on the letters I type. | |
| Detailed Ecotourism Site Information Prototype | Figure 4. High-fidelity prototype of the site collection module with search functionality. |
| Dependencies | A database with ecotourism site information to perform content search |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | This user story depends on a database containing ecotourism site information to filter content |
| Negotiable | It is well defined, but allows minor negotiable adjustments |
| Valuable | Provides value by allowing users to access a site by searching its name or location |
| Estimable | Estimated moderately high effort due to implementing a search system from scratch, both on mobile and desktop |
| Small | Small enough to be completed within a sprint |
| Testable | Must be tested and is easily testable |
HU005
| element | description |
|---|---|
| Geolocalization of sities | As a user, I want to be able to visualize ecotourism sites on an interactive map to locate their exact position and plan my visit. |
| - As a user, I want each ecotourism site to have its own map with details such as coordinates and names | |
| - As a user I want maps to adjust to screen size | |
| Aceptante criteria | - As a user I want maps to be easily viewable from any device |
| - As a user I want maps to be large and interactive with wide navigation space | |
| Detailed information prototype of Ecotourism sites | **Figure 5. High-fidelity prototype of the site collection module with the interactive map section.. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Reviview |
|---|---|
| Independent | Does not depend on other page functionalities to be displayed in the ecotourism site |
| Negotiable | It is well defined, but there is the possibility of specific negotiable adjustments |
| Valuable | It has the value of allowing a tourist to see the location of the places they want to visit |
| Estimable | It has the value of allowing a tourist to see the location of the places they want to visit |
| Small | Small enough to be carried out in one sprint |
| Testable | Must be subject to testing, being easily testable |
HU006
| Element | Description |
|---|---|
| Ecotourism Site Detail | As a user, I want to visualize detailed information of an ecotourism site (location, climate, characteristics, flora and fauna, infrastructure and recommendations) in order to better understand the place and plan my visit. |
| - The user must be able to access a detailed view of each ecotourism site. | |
| Acceptance Criteria | - The system must display information such as location, climate, characteristics, flora and fauna, infrastructure and recommendations. |
| - The information must be organized in a clear and easy-to-understand way. | |
| - The view must include representative images of the site. | |
| - The interface must be adaptable to mobile and desktop devices. | |
| - The user must be able to visualize the site location through an integrated map. | |
| Detailed Ecotourism Site Information Prototype | Figure 6. High-fidelity prototype of the tourist site information module. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | It is independent because it does not depend on other functionalities or modules of the page to function |
| Negotiable | There is a possibility of adjustments regarding the structure of the information. |
| Valuable | It provides value by allowing tourists to better understand the ecotourism site of their interest. |
| Estimable | A moderate effort is estimated in the implementation of the web page. |
| Small | It can be carried out within a sprint |
| Testable | It must be subject to testing, being easily testable |
HU007
| Element | Description |
|---|---|
| Rating and Comments | As a tourist, I want to be able to rate and leave comments about the ecotourism sites I visited in order to help other users make decisions |
| - As a user, I want to be able to rate and comment on ecotourism sites, as long as I am registered in the system. | |
| Acceptance Criteria | - As a user I want to be able to write reviews with a minimum of 50 characters |
| - As a user I want the reviews and ratings to be visible and adaptable to any device | |
| - As a user I want to be able to rate each ecotourism site from 1 to 5 stars | |
| Detailed Ecotourism Site Information Prototype | Figure 7. High-fidelity prototype of the tourist site information module - comments and ratings section. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | It is not independent since it depends on other modules such as authentication and registration. |
| Negotiable | It is well defined, but there is a possibility of adjustments in the rating criteria and how users leave comments |
| Valuable | It provides value by allowing tourists to understand the experiences and quality classification of other users. |
| Estimable | A high effort is estimated due to the implementation of a complex validation system that detects spam and avoids multiple ratings from a user on both platforms (web/app) |
| Small | Small enough to be carried out in 2 sprints |
| Testable | It must be subject to testing, being easily testable |
HU008
| Element | Description |
|---|---|
| Save Favorite Sites | As a registered tourist, I want to be able to save my favorite ecotourism sites in a list to easily access them later. |
| - As a user, I want the selected sites to be saved in a separate space where I can access them whenever I want | |
| Acceptance Criteria | - As a user, I want to be able to save my favorite sites as long as I am registered in the system |
| - As a user I want the saved sites to be displayed responsively according to the screen size | |
| - As a user I want to be able to select the sites I want to save through an interactive button | |
| Detailed Ecotourism Site Information Prototype | Figure 8. High-fidelity prototype of the favorites module of tourist sites. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | It is not independent since it depends on modules such as authentication and registration |
| Negotiable | It is well defined, but there is a possibility of adjustments in how ecotourism sites are stored and organized. |
| Valuable | It provides value by allowing tourists to save sites of interest to view or visit later. |
| Estimable | Moderate effort for web / high effort for mobile due to synchronization processes |
| Small | Small enough to be carried out in one sprint |
| Testable | It must be subject to testing, being easily testable |
HU009
| Element | Description |
|---|---|
| Ecotourism Site Management | As a tour operator, I want to be able to register and manage the ecotourism sites that I administer in order to promote them within the platform. |
| - The operator must be able to create a new ecotourism site. | |
| Acceptance Criteria | - The system must allow entering information such as name, location, contact, description, characteristics and validation documentation. |
| - The operator must be able to upload images of the site. | |
| - The operator must be able to edit the information of their registered sites. | |
| - The operator can only manage the sites that belong to them. | |
| - Access to this functionality must be restricted to users with the operator role. | |
| Detailed Ecotourism Site Information Prototype | Figure 9. High-fidelity prototype of the ecotourism site registration module. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | It does not depend on any other module within the system. |
| Negotiable | It is well defined, but there is a possibility of specific adjustments in its structure |
| Valuable | It provides value by allowing the operator to register and promote the ecotourism site they manage. |
| Estimable | A moderate effort is estimated for both platforms (web and mobile), as the authenticity of the site must be validated to avoid false information. |
| Small | Small enough to be carried out in two sprints |
| Testable | It must be subject to testing, being easily testable |
HU010
| Element | Description |
|---|---|
| Ecotourism Event Publishing | As a tour operator, I want to publish events and special activities related to ecotourism sites in order to attract more visitors. |
| - As an operator, I want to be able to publish events and special activities related to my site only if I am registered in the system. | |
| Acceptance Criteria | - As an operator I want the registration page to be adaptable to any device size |
| - As an operator, I want published events and activities to be visible in the personalized notifications section for users. | |
| - As an operator, I want to publish at least the event name, ecotourism site name, schedule, contact and location where the event will take place. | |
| Detailed Ecotourism Site Information Prototype | Figure 10. High-fidelity prototype of the event creation module. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | It is not independent since it depends on registration, login and notifications modules. |
| Negotiable | It is well defined, but there is a possibility of adjustments in how information is displayed and updated. |
| Valuable | It provides value by allowing operators to publish events and activities of their sites. |
| Estimable | A moderate effort is estimated due to the need to define event timeframes and proper data handling. |
| Small | Small enough to be carried out in two sprints |
| Testable | It must be subject to testing, being easily testable |
HU011
| Element | Description |
|---|---|
| Personalized Notifications | As a registered user, I want to receive notifications about new sites, events or promotions in order to stay informed. |
| - As a user I want to view information in clear and direct notifications. | |
| Acceptance Criteria | - As a user I want notifications to match my preferences, previously evaluated through system functions. |
| - As a user I want personalized notifications to be ordered by priority in the section where they are stored. | |
| - As a user I want the option to mute or stop receiving notifications that are not of my interest. | |
| Detailed Ecotourism Site Information Prototype | Figure 11. High-fidelity prototype of the notifications module. |
| Responsible | Cristian Acevedo/Cristian Monsalve |
| Criteria | Review |
|---|---|
| Independent | It is dependent since it requires user registration. |
| Negotiable | It is well defined, but there is a possibility of negotiable adjustments. |
| Valuable | It allows users to stay informed about events, new sites and promotions in a personalized way. |
| Estimable | A moderate effort is estimated due to preference-based algorithms. |
| Small | Small enough to be carried out in two sprints |
| Testable | It must be subject to testing, being easily testable |
HU012
| Element | Description |
|---|---|
| Multiplatform (Web and Mobile) | As a user, I want to access the information from both the website and the mobile app for greater convenience and availability. |
| - As a user I want to view and access all system functionalities through both the website and the mobile application. | |
| Acceptance Criteria | - As a user I want both the website and the mobile app to be sufficiently optimized so that compatibility matches the device being used. |
| - As a user I want there to be no functionality restrictions between devices. | |
| - As a user I want information and data to be reflected both on the website and the mobile application. | |
| Detailed Ecotourism Site Information Prototype | Figure 12. High-fidelity prototype of the responsive home module. |
| Responsible | Cristian Monsalve / Jackeline Giraldo |
| Criteria | Review |
|---|---|
| Independent | It is independent since both platforms can function correctly without depending on each other. |
| Negotiable | It is well defined, but there is a possibility of negotiable adjustments. |
| Valuable | It allows users to adapt to their preferences and availability without losing functionality or information. |
| Estimable | A high effort is estimated due to development and data synchronization requirements. |
| Small | Small enough to be carried out in several sprints |
| Testable | It must be subject to testing, being easily testable |
HU013
| Element | Description |
|---|---|
| Operator Statistics Panel | As a tour operator, I want to visualize statistics of my sites (visits, favorites, average ratings and recent comments) in order to analyze performance and improve the management of my ecotourism sites. |
| - The operator must be able to visualize the number of visits of their sites. | |
| Acceptance Criteria | - The operator must be able to visualize the number of sites marked as favorites. |
| - The operator must be able to visualize the average rating of their sites. | |
| - The system must display the most recent comments (maximum 6). | |
| - The information must be displayed clearly in the statistics panel. | |
| - The data must correspond only to the authenticated operator’s sites. | |
| - The interface must be adaptable to mobile and desktop devices. | |
| Detailed Ecotourism Site Information Prototype | Figure 13. High-fidelity prototype of the statistics panel module. |
| Dependencies | Database with information about visits, favorites, ratings and comments. |
| Authentication and role control system (operator). | |
| Relationship between operator and their ecotourism sites. | |
| Responsible | Cristian Monsalve / Jackeline Giraldo |
| Criteria | Review |
|---|---|
| Independent | It depends on authentication and existing data associated with operator sites. |
| Negotiable | It can be expanded with new metrics or visualizations. |
| Valuable | It allows operators to analyze performance and make decisions. |
| Estimable | A medium effort is estimated due to data processing. |
| Small | It can be developed in one or two sprints. |
| Testable | It is validated by verifying correct data correspondence. |
HU014
| Element | Description |
|---|---|
| Recommendation Section | As a user, I want to visualize ecotourism site recommendations based on my preferences in order to discover places aligned with my interests. |
| - The authenticated user must visualize a recommendation section. | |
| Acceptance Criteria | - The system must display sites based on user preferences. |
| - Each recommended site must show image, name, brief information and location. | |
| - The section must be visible on the main page or collection. | |
| - The interface must adapt to mobile and desktop devices. | |
| - If the user has no preferences configured, the system must show general recommendations. | |
| Detailed Ecotourism Site Information Prototype | Figure 14. High-fidelity prototype of the recommendations section module. |
| Dependencies | System authentication. |
| User preferences module. | |
| Ecotourism sites database. | |
| Recommendation logic. | |
| Responsible | Cristian Monsalve / Jackeline Giraldo |
| Criteria | Review |
|---|---|
| Independent | It depends on user preferences and site database. |
| Negotiable | It can be improved with advanced recommendation algorithms. |
| Valuable | It helps users discover relevant sites. |
| Estimable | A medium effort is estimated. |
| Small | It can be implemented in one or two sprints. |
| Testable | It is validated by checking preference-based recommendations. |
HU015
| Element | Description |
|---|---|
| User Profile | As a user, I want to manage my personal profile (profile picture, name, last name, email, password change and account deletion) in order to keep my information updated and control my account. |
| - The user must be able to visualize their personal information (name, last name and email). | |
| Acceptance Criteria | - The user must be able to update their profile picture. |
| - The user must be able to edit their personal information. | |
| - The user must be able to change their password securely. | |
| - The user must be able to delete their account. | |
| - Access must be restricted to authenticated users only. | |
| - The interface must adapt to mobile and desktop devices. | |
| Detailed Ecotourism Site Information Prototype | Figure 15. High-fidelity prototype of the user profile module. |
| Dependencies | User authentication system. |
| User database. | |
| Account management module. | |
| Responsible | Cristian Monsalve / Jackeline Giraldo |
| Criterio | Revisión |
|---|---|
| Independent | It depends on authentication to access user data. |
| Negotiable | It can be expanded with more customization options. |
| Valuable | It allows users to manage their account information. |
| Estimable | A medium effort is estimated due to security implementation. |
| Small | It can be developed in one or two sprints. |
| Testable | It is validated through correct data updates and security checks. |
HU016
| Element | Description |
|---|---|
| Administrative Statistics Panel | As an administrator, I want to visualize general system indicators (active tourists, active operators, active sites and active events) in order to understand the platform status and make administrative decisions. |
| - The administrator must be able to visualize the number of active tourists. | |
| Acceptance Criteria | - The administrator must be able to visualize the number of active operators. |
| - The administrator must be able to visualize the number of active sites. | |
| - The administrator must be able to visualize the number of active events. | |
| - Data must be displayed clearly in the administration panel. | |
| - Information must be dynamically updated. | |
| Detailed Ecotourism Site Information Prototype | Figure 16. High-fidelity prototype of the admin dashboard with system indicators. |
| Dependencies | Database with users, sites and events. |
| Authentication and role system (admin). | |
| Data query logic. | |
| Responsible | Cristian Monsalve / Jackeline Giraldo |
| Criteria | Review |
|---|---|
| Independent | It depends on database and authentication system. |
| Negotiable | It can be extended with more indicators. |
| Valuable | It allows administrators to understand system status quickly. |
| Estimable | Low to medium effort. |
| Small | It can be implemented in one sprint. |
| Testable | It is validated by comparing real system data. |