diff --git a/clang/include/clang/Analysis/FlowSensitive/DataflowAnalysis.h b/clang/include/clang/Analysis/FlowSensitive/DataflowAnalysis.h
--- a/clang/include/clang/Analysis/FlowSensitive/DataflowAnalysis.h
+++ b/clang/include/clang/Analysis/FlowSensitive/DataflowAnalysis.h
@@ -136,6 +136,29 @@
   return BlockStates;
 }
 
+/// Abstract base class for dataflow "models": reusable analysis components that
+/// model a particular aspect of program semantics, with respect to a specific
+/// lattice. Models are very similar to analyses, except:
+///
+/// a) Models implement a typed dynamic (that is, virtual) interface (with
+///    respect to the lattice type), while analyses implement an untyped dynamic
+///    interface.
+///
+/// b) Models should focus on a _particular_ aspect of program semantics -- for
+///    example, a type and its related functions. FIXME: determine how models
+///    should relate to each other -- that is, how they should compose. Open
+///    questions include: Do we want to enable composition of models that have
+///    different lattice types? Do we want to support models with no lattices
+///    that only use the Environment?
+///
+/// c) Models do not provide an initial element -- that is the responsibility of
+///    the analysis.
+template <typename LatticeT>
+class DataflowModel : public Environment::ValueModel {
+public:
+  virtual void transfer(const Stmt *Stmt, LatticeT &L, Environment &Env) = 0;
+};
+
 } // namespace dataflow
 } // namespace clang