*   in our SE terms, 
    process as the framework/approach used to
    perform tasks in a project;

    Jalote argues: that emphasis on process
    distinguishes SE from most other computing
    disciplines;

*   process: sequence of steps performed
    for a given purpose

    you have a process for a particular project --
    there are GENERAL process models that SE
    folks have come up with and described
    (even proposed...)

    *   COULD think of a process model as being
        essentially a compilation of best practices
        that make up a recipe for success in
	an appropriate class of projects;

...jumping ahead to this set of
   mostly-classic software development process
   models:

   *   Waterfall
   *   Prototyping
   *   Iterative development
   *   Rational Unified Process
   *   Timeboxing
   *   XP and Agile Processes

*   prototype -
    *   here, the prototype(s) are NOT final
        deliverables -- the client can
	try them out, make suggestions, etc.
	BASED on them, BUT they are intended
	to clarify the requirements;