Since I build an internal glossary at pretty much every organization I join, I figure it's about time to start writing down the most common definitions here that I reference globally:
Framework: A structure which provides a hierarchy, charter and reasoning for policies, standards, and procedures.
Policy: A guideline or statement of position with respect to a given topic.
Process: The highest level description of a large task or series of related tasks. It provides the BIG picture. You are usually dealing with a process when the job involves 3 or more medium to large tasks, more than 1 person, job title or department is involved, there are time delays of hours, days or longer between steps, and multiple procedures and work instructions are necessary to fully describe it.
Procedure: A task which is more detailed than a process, but less detailed than a work instruction. It tells how a series of sequential tasks should be performed to achieve a specific outcome. You are probably dealing with a procedure when the task has 10 separate actions or 3 or more small tasks, the steps get 2 or more levels deep (steps and sub steps), the job involves more than 1 person or department, the task is completed from start to finish in one continuous time frame (no significant delays between steps).
Work Instruction: The most detailed description of a task. It’s sole purpose is to explain step by step how to do a specific task. You are probably dealing with a Work Instruction when the job has fewer than 10 separate actions, the job is performed by 1 person from start to finish, the task is completed in a short amount of time from start to finish.
BYOD framework: Bring Your Own Device. This is a framework for securely allowing employees to attach their personal devices to enterprise networks and services.
DLP framework: Data Loss Prevention. This is a framework to detect potential data breaches / data ex-filtration transmissions and prevent them by monitoring, detecting and blocking sensitive data while in-use (endpoint actions), in-motion (network traffic), and at-rest (data storage).
CASB: Cloud Access Security Broker. This is a security policy enforcement point placed between service consumers and service providers to monitor and enforce enterprise security policies.
Boilerplate: A boilerplate consists of a combination of runtime and predefined services. Because a boilerplate contains a runtime and set of services for a particular solution type, it can be used to quickly start and run an application.
IBM Service Broker: The service broker advertises a catalog of service offerings and service plans to Bluemix and Cloud Foundry and receives calls from Cloud Foundry for four functions: create, delete, bind, and unbind.
Buildpack: A buildpack gathers the run-time and framework dependencies of an application, then packages them with the application into a droplet that the developer deploys into the cloud.
Diego cell: The Diego Cell hosts application instances, reports application status to the Diego Bulletin Board Service (BBS), and provides application logs, errors, and metrics to the Loggregator. Application instances live inside Garden containers. Containerization ensures that application instances run in isolation, get their fair share of resources, and are protected from noisy neighbors.
Cloud Controller: The Cloud Controller directs the deployment of applications. When you push an application to Cloud Foundry, the Cloud Controller uses the CC-Bridge to store the application bits and direct the Diego Brain to coordinate Diego Cells to stage and run applications.
Cloud Foundry Router: The Router routes incoming traffic to the appropriate component in the environment. For example, the Router sends traffic to the Cloud Controller for management of applications in their lifecycle or a hosted application on a Diego Cell. The Router is informed of active application instances through the router-emitter that monitors status in the Diego Bulletin Board Service (BBS). Please see this link, as well as this link.