Content Caching
- Content Caching
- the
content management
task during which public
content is cached
As illustrated in the preceding figure, Content Caching is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Task
- Subclasses:
The typical responsibilities of Content Caching are to:
- Decrease the access time of popular or recently requested content.
Content caching typically can begin when the following
preconditions hold:
- The
construction phase has started.
- The initial conventions for content caching (e.g.,
guidelines, standards) have been produced during the
process engineering activity.
- The following documents are largely complete and are
relatively stable:
- The
content management team has been adequately staffed and
trained in content caching.
- A server or accellerator is available to store the cached
content.
Content caching is typically complete when the following
postconditions hold:
Content caching typically involves the following teams
performing the following steps in an iterative, incremental,
parallel, and time-boxed manner:
-
Content Management Team:
- Determine the need for content transformation by
reading and understanding the associated:
- Informational (data) requirements in the:
- Information architecture:
- Content design:
- TBD
Content caching typically can be performed using the
following techniques:
Content caching typically results in the production of the
following work products:
-
data components:
- Cached Content:
- Textual content.
- Numerical content.
- Audio content.
- Graphical content.
- Video content.
- Content Metadata
- Content caching should be performed iteratively,
incrementally, and in parallel with other content management
tasks.
- Content caching occurs on an as needed basis.
- Content caching is automated, typically by means of COTS
products.
- The transformed content may be cached for future
use.
- Content transformation may not be necessary content is
only intended for a single client type.