RE: Task-based vs. System-Based Procedures

["Anthony Markatos" <tonymar -at- hotmail -dot- com>]

Bill Burns said:

..it's one thing to debate whether the task-based and system-based
perspectives should be the same. It's another thing entirely to claim that 
there's no distinction between how a user approaches an application and how 
a developer designs it.

Tony Markatos responds:

Properly utilizing Structured Systems Analysis and Design (SSAD) - the most 
prevalent of the formal analysis/design techniques - requires that the 
developer "approach" the application the same way that the end-user does.  
When a developer does not do such, the whole formal analysis/design effort 
falls apart - often very quickly and very completely.  This happens 
frequently - like real frequently.  The result is the poor designs that we 
(TW's) so often have to document.

Bill Burns said:

I find it rather reductionist in terms of practice (as opposed to the ideal 
world that academics keep fathoming) to claim that the legitimate software 
development world follows this strict set of
principals

Tony Markatos responds:

Most do not follow "this strict set of principles".  This is no surprise to 
anyone with any experience in the software industry.  But, taking a rigorous 
user-centered approach to analysis the foundation of good design.  And many 
have had great success with end-user focused development tools like SSAD - 
including myself.

Tony Markatos
(tonymar -at- hotmail -dot- com)

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com