Comprehensive Catalogue of Ingredients

Value proposition

As a cooking enthusiast, I want an organized collection of ingredients, so that I can easily access detailed ingredient profiles, flavour characteristics and recommended matches.

Description

Acceptance criteria

A database of ingredients is created?
Each ingredient profile includes name, description, nutritional information, used quantities, possible allergens, flavour characteristics, and recommended matches.?
Ingredients can be categorized and tagged?
Tasks
Design Database Schema: Define the database schema to store ingredient details, including name, description, nutritional information, used quantities, possible allergens, flavour characteristics, and recommended matches.
Implement Backend API: Create an endpoint to fetch all ingredients.

Hi there,

nice start!

I have some suggestions and feedback:

Acceptance Criteria: The AC should not be questions, but statements that describe the flow of your application. They should describe what is visible and only what will be implemented in that user story. -> you should remove the bullet point for the database from the AC; -> you should also remove the third bullet point where you mention tagging and a category. Having only an overview of all ingredients, does not include categories or tags. Therefore, it should not be mentioned in the User Story. If you want to add categories and/or tags, you can do so in a separate User Story. -> your wireframe shows a box that I assume is an image, however, I don't see a mention of an image in the AC. -> Could there be a scenario where no ingredients are fetched and thus displayed? If that is the case, you might want to think about what to display users in case something goes awry with the fetch

Tasks:

They are for you as developers as a guidance to implement the feature, you could think about adding a mention of a list component and potentially a ingredient card component

In general, I think it is a challenge to start a capstone project directly with a database. I usually recommend starting with local data and making use of the dummy data provided to you by us. That will make the start of the project a lot quicker. You can always switch to a database at a later point, in the second sprint for instance. Please talk this through in your team. I won't veto the database approach, but as written above, I recommend the approach with local data and states when starting a capstone project.

I hope my comment is helpful to you. Please update your User Story accordingly and repost it afterwards.

Thanks in advance and cheers ✌️

ndrbn0 / Flavion