Elicitation：.docVIP

Elicitation the gathering of information about the PD and the requirements Closely interwoven with analysis and specification but has problems and technology of its own Not always easy - requires considerable expertise (and some natural talent !) Have to deal with users and clients. Not always a simple matter of transferring knowledge from one place to another - some is in a very tenuous form and must be rationalised and fleshed out Remember, the three main considerations are :- what information should be gathered from what sources can it be gleaned and by what mechanisms or techniques it may be gathered Before looking at these points in more detail, a word about - Elicitation output (elicitation notes) Largely unprocessed, unstructured and may contain many irrelevancies and, initially, omissions Often regarded as temporary - but may be useful for tracing or audit Example :- Client - skyhi elevator co. Contact (technical) Jason Hukins 01202 489345, X 4783. I/v 15/6. Previous s/w contractor unsatisfactory (Late and buggy!) Full h/w details available. Looking for full spec by 1/10. Will pay installment for spec and negotiate for the rest (Andy can cover this - needs to contact Geoff Shepperd (finance director). H/w all to hand- full specs available (got copies). Interface blocks all operate at 0 - 5V (20mA) - direct port connection no prob. Max 4 lifts per controller, max 20 floors. One lift per shaft (next generation won’t be !). All lifts, same # of floors. Requirements :- All lifts (if 1) to be used approximately equally. Lift only reverses direction if no outstanding lift calls in current direction (lift call - button inside lift, floor call - button outside lift !) Must not change motor polarity whilst moving ! (It’ll blow.) In emergency, stop all motors (if poss.) Floor calls should be serviced by the lift that will get there soonest (approx.) Tricksy to predict - could pick up more calls on the way. Services calls in the order it gets there - not the order th