Welcome, new Bangazonians!

Your job is to build out a .NET Web API that makes each resource in the Bangazon ERD available to application developers throughout the entire company.

1. Products
2. Product types
3. Customers
4. Orders
5. Payment types
6. Employees
7. Computers
8. Training programs
9. Departments

Pro tip: You do not need to make a Controller for the join tables, because those aren't resources.

Your product owner will provide you with a prioritized backlog of features for you to work on over the development sprint. The first version of the API will be completely open since we have not determined which authentication method we want to use yet.

First, you need to plan.

• Your team needs to use the official SQL script (see below) and build a Bangazon ERD using dbdiagram.io. Once your team agrees that the ERD is complete, you must get it approved by your manager before you begin writing code for the API.
• Read all of the tickets. They're in order of priority. This is a week long sprint, and you're in charge of deciding how many tickets you want to take on. When you've decided, Jordan will come around for a commitment ceremony.

Next, you need to author the Models needed for your API. Make sure that each model has the approprate foreign key relationship defined on it, either with a custom type or an List<T> to store many related things.

You will be using the Official Bangazon SQL file to create your database. Create the database using SSMS or the SQL Server Object Explorer in Visual Studio, create a new SQL script for that database, copy the contents of the SQL file into your script, and then execute it. Every team member will need to build the database on their own computer. To avoid merge conflicts in your appsettings.json file, make sure you all name your database the same thing.

Now it's time to build the controllers that handle GET, POST, PUT, and DELETE operations on each resource. Make sure you read and clarify the requirements in the issue tickets to you can use SQL to return the correct data structure to client requests.

Each feature ticket your team will work on for this sprint has testing requirements. This boilerplate solution has a testing project includes with some starter code. You must make sure that all tests pass before you submit a PR.