Re: Functionality vs Function

[rjben <rjben -at- NETVISION -dot- NET -dot- IL>]

Please permit me a technologist's perspective. Functionality typically
refers to the way an application (software or other) will work for your
business, meaning it is business process RELATED.  Function typically
indicates a RELATIONAL DEPENDENCY.  Application features typically refer
to the methods the APPLICATION uses to get the job done.

Examples
An application is said to be functional, when it satisfies the business
process requirements, and a whole lot of other criteria.  Mainly it will
do for the business what the business wants it to do, and not vice
versa, which is a typical case scenario.

In a corporate where Sales is a function of Marketing it means that if
there's no Marketing department, the company loses its Sales
functionality.

In software applications the same applies, hence we have a relational
data and funtion model.  Although the relational methodology isn't fully
employed by many object oriented software developers, the function
aspect is still specified in the methods part of the object, i.e.
function cannot be ommitted if one wants eventual functionality.

To complete the confusion, Process and procedure are sub-classes of
Function. Linked to Data, the result would be Functionality, and if
designed accurately the Functionality would be Functional to the
business.  This, in short, is how applications should enable business,
by becoming mutually dependent (Funtion) of a Business Area.

Technical Writing should reflect and explain Function (internal and
business dependencies), Functionality (what it will do for the user),
Features (via which means it will do it) and Operating logic (how it
will do it).

Robert Benjamin
rjben -at- netvision -dot- net -dot- il