Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!ads.com!potomac.ads.com!wbrooks
From: wbrooks@potomac.ads.com (Bill Brooks)
Newsgroups: comp.human-factors
Subject: Re: rules of thumb
Message-ID: <1991Jun26.132555.18427@potomac.ads.com>
Date: 26 Jun 91 13:25:55 GMT
References: <1991Jun26.092540@axion.bt.co.uk>
Distribution: na
Organization: Advanced Decision Systems, Arlington, VA
Lines: 33

In article <1991Jun26.092540@axion.bt.co.uk> jpope@axion.bt.co.uk (john pope) writes:
>
>I'd also be interested in people's views on systems analysis
>methods. To me, many seem to ignore human factors aspects:

I have found that starting at a VERY macro view and considering where the
system-to-be-developed fits in has been quite helpful.  By very macro, I mean
looking at it from your client's boss' customer's perspective.  Asking
questions like: Does it impact rush hour traffic?  Does it impact the
environment?  Sure, this sounds pretty pointless, but even if you only take
a few minutes at these most macro perspectives and progress downward, it
really helps a lot in requirements analysis and understanding the problem.

I think any experienced system developer will agree (or maybe not :^) that
a client almost never states the problem well enough to be solved.  He usually
has hidden agendas or there are other factors he either hasn't taken into
account (like upcoming relocation or an impending telecommuting policy) or
isn't aware of (recent technology innovations).  So it is important for
the system engineer and the system analyst to understand the whole problem.

As far as commercial tools/analytical techniques, I don't really have a
favored approach.  I use what appears to be most effective for each situation
or client.  That usually means using a variety of redundant tools at first and
continuing with those that are best understood or received.  I will say though
that storyboards have been the most effective (yeah, I know.  They take a long
time and aren't as useful as other tools for the developers, but they do give
the customer a good view of the proposed system).



-- 
William Brooks			UUCP: sun!sundc!potomac!wbrooks
Advanced Decision Systems	Internet:  wbrooks@potomac.ads.com