Hi! What you heard from your instructor about seperating different BizTalk \”pieces\” into seperate projects is good practice. What I usually do is I have 1 solution, lets call it SampleSolution. Underneath this solution, I have 1 project for each piece in the solution…so orchestrations get a project, transforms get a project, pipelines get a project and etc. I usually name my projects with the solution name followed by a period and whatever component happens to be. So for my SampleSolution, my orchestrations project would be called SampleSolutions.Orchestrations, my maps would be called SampleSolution.Transforms and so on.
This tends to help keep things organized and a bit less chaotic. It also is handy if you use custom deployment tools such as the Deployment Framework from Scott Colestock. Hope this helps!