Commits

Clark C. Evans committed a699d26

editing the EXAMPLES file to add sales pitch

Comments (0)

Files changed (1)

 Examples
 ========
 
-Let's assume we have a data model, with schools, departments, programs and
-courses.  Here it is::
+HTSQL provides outstanding clarity without sacrificing rigor.  Not only
+is working with HTSQL more productive than SQL, but things are possible
+that would have otherwise exceeded a user's mental capacity.
+
+Let's assume we have a data model, with schools, departments, programs
+and courses.  Here it is::
 
          +-------------+       +--------+
     /---m| DEPARTMENT  |>-----o| SCHOOL |m----\
     ORDER BY 1, 2;
 
 
-Departments that belong to any school with "art" in its name
-------------------------------------------------------------
+Departments in schools having "art" in its name
+-----------------------------------------------
 
 HTSQL::
 
                  WHERE (s.code = p.school));
 
 
-For each school, the number of programs and the number of departments
----------------------------------------------------------------------
+Number of programs and departments per school
+---------------------------------------------
 
 HTSQL::
 
     ORDER BY s.code;
 
 
-For each school, the average number of courses offered by the departments
--------------------------------------------------------------------------
+Average number of courses offered by departments in each school
+---------------------------------------------------------------
 
 HTSQL::
 
     ORDER BY s.code;
 
 
+HTSQL transforms development processes by actively engaging data
+managers and business analysts in software construction.  In traditional
+development models, a requirement document, sample data, and a wireframe
+are given to a developer.  In this model, the data analyst also provides
+a HTSQL query.
+
+By having a query, there is less guesswork.  Less round trips.
+