Work Products may take various shapes or forms, such as:

• A model, such as the Use-Case Model or the Design Model, which contains other Artifacts.
• A model element; that is, an element within a model, such as a Design Class, a Use-Case or a Design Subsystem.
• Project data that might be kept in databases or other types of tabular information repositories such as spreadsheets.
• Source code and executable programs that contribute to the product or Solution.
• Various types of documents, for example a specification document, such as Requirements Specification, or a plan document, such as the Software Requirements Plan.

They can therefore be categorized accordingly. An example is "Specification", which categorizes requirements specifications that define a system with a well-defined system boundary, such as use case or functional requirements specification. Unlike in Domains, a single Work Product can be categorized in multiple Work Product Kinds.