In his CM: the Next Generation series, Joe Farah gives us a glimpse into the trends that CM experts will need to tackle and master based upon industry trends and future technology challenges.
You identify the revision of your tools/processes that are being used for the build. So you might create a baseline twice a month, but do builds on that baseline, adding in all other ready changes, a couple times a day, or multiple times for different variants. Developer builds are (typically) not tracked so rigorously by the CMDB. A build  record, is often referred to simply as a build . A future build  is sometimes referred to as a build notice (similar to change notice in the hardware world) or in the past as a build record.
Finally, BOM is used in the hardware world to describe the set of part revisions required to build something. There are a few differences though and so it might be wise to avoid this term.
My vote: Build, build notice, build record
Context, views, context views. There are a lot of products, a few development/support streams for those products, loads of changes, etc. in a CMDB. Navigating all of that data can be overwhelming. However, any decent CM tool will understand that you're interested in working in a particular context. And the context can be used to simplify the view of the data. Normally it's the context of a particular build record, or the latest checked in source code of a particular product for a particular development stream. Sometimes it is a combination of a baseline or build plus a set of changes. Whatever it is, and however it is specified, the goal is to identify the context of your discussion, query, data search, or whatever.
When applied within the context of a tool, the Context is referred to as a context, a view, or a context View. There are other terms used here and there, but these are the most dominant. For the most part, I think any of these three terms suffices, with context view preferred if there is any confusion. In particular, context is a fairly generic term that can sometimes cause confusion, thus the reason that I quoted it in the first sentence of this paragraph. View is a frequent database term as well, which is more specific than a context view, usually applying to form.
My vote: Context view, context, view (in that order)
Service pack, increment, update package, change supplement. Lots of different terms are used to identify an upgrade package for something that's already been delivered. However, as this is really at the tail end of the ALM