On Jun 28, 2006, at 10:21 AM, Robert Patterson wrote:
Owain Sutton:
"Authorization Improvements" are NOT a feature.
Just to be clear about terminology. All behavior that is according to
the design spec is a feature, including authorization. What
authorization is not (from the user perspective) is a "benefit". It is
most important to distinguish between benefits and features, because
it becomes much easier to distinguish which stakeholder(s) a feature
benefits.
Well-put. So I would view a single authorisation as an improvement over
multiple ones, since I don't have to mess around with two different
apps and companies. I have two computers, plus school machines, and
that got to be a real hassle, let me tell you.
Christopher
_______________________________________________
Finale mailing list
Finale@shsu.edu
http://lists.shsu.edu/mailman/listinfo/finale
