What Is A Use Case in eXie?

Using eXie to catalog important content makes sense because there is a purpose to be served when the content gets re-used. Being able to identify the nature of the content’s importance makes it both more likely and more logical that the content will be visibly relevant to each case of use. Every frame or template in eXie is assigned to a Use Case, and optionally to additional contextual information as well. Some use cases are already offered by eXie, and an eXie user can create new ones as needed.



A Use Case generally indicates HOW the framed content is intended to be useful.

The content in the chosen frame may either be used for a particular purpose, or used as a particular type of instrument.

Examples of Used For will be things like this: Examples of Used As will be things like this:
  • Training
  • Guidance
  • Marketing
  • Planning
  • Coaching
  • Designing
  • Auditing
  • Research


  • Knowledge base
  • Curriculum
  • Portfolio
  • Agenda
  • Catalog
  • Specification
  • Project Plan
  • Evidence



In eXie, the difference between one Use Case and another is typified in the labels of the columns and rows of an eXie frame. People who have great familiarity about a case of usage can provide their expertise in deciding what labels are strong ways for everyone to think about the related content.

In that way, Use Cases help us to define Templates and to keep content collections strongly linked to what actually makes them most valuable – their active usage.

A related idea in eXie is Context.  In eXie we want to identify WHERE and WHY the content is being used. So, we offer a separate Context descriptor to allow you to include that with your frame.

A  Use Case associates with contexts like these: Examples of contexts will be things like this:
  • Certain events or timing
  • Specific roles or groups
  • Certain types of activity or processes


  • Season, meeting, product, publication or exhibition
  • Teacher or Owner or Customer
  • Education or Sports or Strategy or Customer Support



Summary – There can be a frame of content for which things like the following are true:

  • the Use Case is Training, and the Context is Students
  • the Use Case is Knowledge base, and the Context is Support
  • the Use Case is Designing, and the Context is a Product