Lec7 & 8_System Planning

7/23/2019 Lec7 & 8_System Planning

http://slidepdf.com/reader/full/lec7-8system-planning 1/31

System Planning &

Requirements Gathering



L e Cyc e - PHAS !"PLA##$#G

Planning phase – involves establishinga high-level plan of the intended projectand determining project goals

Primary planning activities include

1. Identify and select the system fordevelopment & Requirement gathering

. !ssess project feasibility

". #evelop the project plan



an Se ect t e Systemfor Development

$rgani%ations use dierent forms of evaluationcriteria and 'echniques to determine (hichsystems to develop

Critical success factor (CSF) – a factor that is

critical to an organi%ation)s success



(easi)ility

Feasibility study – determines if the proposed solution isfeasible and achievable from a *nancial+ technical+ and

organi%ational standpoint #ierent types of feasibility studies conomic feasi)ility stu%y" ,cost-bene*t analysis –

identi*es the *nancial bene*ts and costs associated (iththe systems development project

*perational feasi)ility stu%y" eamines the li/elihoodthat the project (ill attain its desired objectives

+echnical feasi)ility stu%y" determines theorgani%ation)s ability to build and integrate the proposedsystem

Sche%ule feasi)ility stu%y" assesses the li/elihoodthat all potential time frames and completion dates (illbe met

Legal an% contractual feasi)ility stu%y" eamines allpotential legal and contractual rami*cations of theproposed system



0-

PLA##$#G ," Developthe Pro'ect Plan

#eveloping the project plan is adi2cult and important activity

'he project plan is the guiding forcebehind on-time delivery of a completeand successful system

3ontinuous updating of the projectplan must be performed during everysubsequent phase during the 4#53



requirementsgathering

6hat techniques are available forgathering information about

requirements7

6hich technique is best7 6hen iseach appropriate to use7

( G



(act Gat er ng+echniques

Intervie(s

8uestionnaires

$bservation#ocument 9 Procedure !nalysis

:!#

Prototyping



(act-Gathering +echniques

!. ;act <athering 'hrough Intervie(s

=. ;act <athering 'hrough

8uestionnaires



(act Gathering +hrough $ntervie/s

!0 Depth $ntervie/s - 3onversationis guided largely by feelings andinterest of the person beingintervie(ed.0Structure% $ntervie/s - >seful after a

depth intervie( for obtaining ans(ers to



$ntervie/s

$ntervie/ - a fact-*nding technique (hereby thesystems analysts collect information fromindividuals through face-to-face interaction.

;ind facts

?erify facts

3larify facts

<enerate enthusiasm<et the end-user involved

Identify requirements

4olicit ideas and opinions 1@



+ypes of $ntervie/s an% .uestions

1nstructure% intervie/ –conducted (ith onlya general goal or subject in mind and (ithfe(+ if any+ speci*c questions. 'he intervie(ercounts on the intervie(ee to provide aframe(or/ and direct the conversation.

Structure% intervie/ –intervie(er has aspeci*c set of questions to as/ of the

intervie(ee.

*pen-en%e% question – question that allo(sthe intervie(ee to respond in any (ay.

11



$ntervie/s+ypes of samples

3onvenientA 4ample those people that are convenient i.e.you have easy access.

Random sampleA Bvery nth person on a list+ or randomnumber generator.

Purposeful sampleA those users that meet certain criteria.

4trati*ed sampleA 4ample obtained by the process ofdividing a population into categories representing distinctcharacteristics and then selecting a random sample fromeach category.



$ntervie/

+ypes of .uestions to Avoi%

5oaded questionsA 8uestion (hich contains acontroversial assumption.

5eading questionsA 8uestion that suggests the ans(eror contains the information the eaminer is loo/ing for.

=iased questionsA 8uestions prepared in such a (aythat a particular ans(er is favored over others.

$ntervie/ .uestion Gui%elines

>se clear and concise language.

#on)t include your opinion as part of the question.

!void long or comple questions.

!void threatening questions.

#on)t use CyouD (hen you mean a group of people. 1"



$ntervie/s

Con%ucting the $ntervie/--practicaltips

#on)t (orry+ be happyPay attention4ummari%e /ey points=e succinct and honest

<ive intervie(ee time to as/ questions=e sure to than/ the intervie(eeBnd on time

!nd+ don)t as/ unnecessary questionsE



$ntervie/s

Post $ntervie/

3onsider as/ing for more time if

necessary3on*rm major points identi*ed (ithintervie(ee

5oo/ for <aps and Fe( 8uestions 'ype up notes (ithin G hours,preferably immediately after theintervie( is over



.uestionnaires

.uestionnaire – a special-purpose documentthat allo(s the analyst to collect information andopinions from respondents.

(ree-format questionnaire – a questionnairedesigned to oer the respondent greater latitudein the ans(er. ! question is as/ed+ and therespondent records the ans(er in the spaceprovided after the question.

(i2e%-format questionnaire – a questionnairecontaining questions that require selecting anans(er from prede*ned available responses.

1H



.uestionnaires

1. *pen-n%e% .uestionnaires - Persons

provi%e /ritten ans/ers to generalrather than speci3c questions00 Close%-n% .uestionnaires - 1se forroutine situations or /hen a large

num)er of similar in%ivi%uals /oul% )e

4hat types of

information%o you use to ma5e%ecisions6



.uestionnaires

! questionnaire is similar to a verystructured intervie(any of the same guidelines apply

Choosing respon%ents4hould be representative of all users4ame types of samples

3onvenientRandom samplePurposeful sample

4trati*ed sample



.uestionnaires

Response rates to questionnaires are commonly lo(J over 1K issometimes considered very good.



Analysis

Great starting point

<ets analyst quic/ly up to speed (ith user jargon3an create preliminary models+ e.g. #;#s

+ypes of information to )e %iscovere%"Problems (ith eisting system$pportunity to meet ne( need$rgani%ational directionFames of /ey individuals?alues of organi%ation4pecial information processing circumstancesReasons for current system designRules for processing data



ocumen roce ureAnalysis

(our types of useful %ocuments4ritten /or5 proce%ures#escribes ho( a job is performedIncludes data and information used and created in

the process of performing the job or tas/usiness formBplicitly indicate %ata 8o/ in or out of a system

ReportBnables the analyst to (or/ bac/(ards from the

report to the data that generated it

Description of current information system



Design

9oint Application Design :9AD;

=rings together /ey users+managers and systems analysts

PurposeA collect system

requirements simultaneouslyfrom /ey people

3onducted o-site



9AD session



Design

Participants

4ession 5eader

>sersanagers

4ponsor

4ystems !nalysts

4cribe

I4 4ta



Design

Supporting 9AD /ith GSS

<roup support systems ,<44 can be usedto enable more participation by group

members in :!#

embers type their ans(ers into the

computer

!ll members of the group see (hat othermembers have been typing



Planning

9oint requirements planning :9RP; – a process (hereby highlystructured group meetings are conducted for the purpose of analy%ingproblems and de*ning requirements.

:RP is a subset of a more comprehensive joint application developmentor :!# technique that encompasses the entire systems developmentprocess.

:oint Requirements Planning ,:RP is a technique for dra(ing out userrequirements through joint planning sessions of soft(are users andinformation technology personnel.

'hese informal sessions are (or/shops that provide an openenvironment for people to discuss (hat they do+ ho( they do it+ and(hat critical information they need to support their job responsibilities.6ritten documentation de*ning these requirements results from a :RPsession.

H



Session

!0 Selecting a location !(ay from (or/place (hen possible

Requires several rooms

Bquipped (ith tables+ chairs+ (hiteboard+

overhead projectors Feeded computer equipment

0 Selecting the participants

4ponsors identify the participants for each :RP

(or/shop. Bach needs release from regular duties,0 Preparing the agen%a

=rie*ng documentation

!genda distributed before each session

M



+ypical Room Layout for 9RP session

N



Discovery Prototyping

Discovery prototyping – the act ofbuilding a small-scale+ representative or(or/ing model of the users) requirements inorder to discover or verify those

requirements.

Rudimentary ,primitive or undeveloped

version of system is built

<oalA to develop concrete speci*cations for

ultimate system 0



Prototyping8uic/ly converts requirements to (or/ing version of

system

$nce the user sees requirements converted to system+(ill as/ for modi*cations or (ill generate additionalrequests

Is prototyping useful in any of these cases7

>ser requests are not clear;e( users are involved in the system#esigns are comple and require concrete formOistory of communication problems bet(een analysts

and users

'ools are readily available to build prototype

i



PrototypingDra/)ac5s

'endency to avoid formal documentation

#i2cult to adapt to more general user audience

4haring data (ith other systems is often notconsidered

4ystems #evelopment 5ife 3ycle ,4#53 chec/sare often bypassed

Lec7 & 8_System Planning

Documents

Transcript of Lec7 & 8_System Planning