RE: In Search of a Class

[Jim Shaeffer <jims -at- spsi -dot- com>]

<snip>
he's assigned several of us to locate and attend a seminar on
"effectively capturing software application functionality content..."
</snip> 

I have no new ideas about a seminar or class, but I did remember something
that may help. 

In a previous life, IBM taught me the following mantra: 

Feature, Function, Benefit. 

When selling high-tech stuff, mention the feature, describe its function and
anchor the statements with a benefit to the user. 

Here are 2 made up examples: 

1. Feature: Software is built using off-the-shelf object modules. Function:
Code is easy to reuse or replace without rewriting the system. Benefit:
Lower maintenance costs and faster bug fixes so you don't lose money due to
downtime. 

2. Feature: Software implements rapid search algorithm XYX. Function: Finds
data base entries real fast. Benefit: You get to go home earlier. 

Filling in a simple three column table with features, functions and benefits
may give you a technique to enrich the content.  (For every feature you list
try to fill in a table cell with  one or more benefits _to the user_.) 
It can also lead to informative discussions with developers about why some
features are included  in the product. 

Jim Shaeffer
jims -at- spsi -dot- com