Drupal fits all, Survey

In systems engineering the basic elements of an application are
broken down into the core entities or objects. Then the different
functions related to each entity are designed and programmed. An
example is in a HR system, the core entity would be an employee, an
employee then has properties and possible statuses. An example of a
property is an employee may be a manager or an employee may have a
manager. Statuses of an employee may be the employee's standing in
the organisation, typically on an employee's initial employment they
would be a junior employee then later a senior employee. The chart
below defines some typical propertities and statuses for different
entities that come from different systems. From the chart one can
deduct that these different systems for totally different purposes
could possibly be built using one type of software, Drupal in this case.

This survey is being conducted to determine how much code Drupal
implementers actually write. The advent of modules such as CCK, Views,
Organic Groups, Workflow, Ubercart, E-Commerce, Panels and Actions
along with a dozen or so other modules has a empowered web developers
with the ability to create sites writing little or no custom code. Is
this true? If you are Drupal user please take the survey at www.mahalasoft.co.za