1 / 5100%
Traditionalb techniquesb forb determiningb systemb requirementsb duringb analysisb typicallyb
involveb ab sequential,b top-downb approach.b Thisb involvesb identifyingb keyb requirements,b
creatingb ab requirementsb document,b andb refiningb itb basedb onb feedback.b Anb exampleb wouldb beb
interviewingb andb listening.b Contemporaryb techniquesb tendb tob beb moreb iterativeb andb flexible.b
Thisb approachb allowsb forb moreb frequentb feedbackb andb enablesb teamsb tob adaptb tob changes.b
Anb exampleb wouldb beb prototypingb andb Focusb groups.b Radicalb techniquesb challengeb
traditionalb assumptionsb aboutb requirementb gatheringb andb management.b Thisb approachb
prioritizesb learningb andb experimentationb andb aimsb tob validateb assumptionsb aboutb theb
product'sb market.b Anb exampleb wouldb beb questionnaires.b Eachb techniqueb hasb itsb strengthsb andb
weaknesses,b andb itsb usefulnessb willb dependb onb theb project'sb context.b Eachb techniqueb hasb
potentialb drawbacks.b Traditional,b suchb asb theb Waterfallb method,b canb beb inflexibleb andb mayb
notb allowb forb changesb inb requirements.b Contemporary,b suchb asb Agile,b canb beb challengingb tob
implementb ifb theb teamb isb notb experienced.b Thisb canb alsob resultb inb scopeb creep.b Radical,b suchb
asb Leanb Startup,b canb beb riskyb becauseb itb involvesb testingb assumptionsb beforeb investingb
heavilyb inb development.b Thisb canb resultb inb delaysb ifb theb teamb needsb tob pivotb orb changeb
direction.b Choosingb theb appropriateb techniqueb dependsb onb severalb factors,b includingb theb
requirements.b Evaluateb theb project'sb requirementsb andb considerb ifb theyb areb well-understoodb
andb stable.b Ifb theyb are,b theb Waterfallb modelb mayb beb appropriate.b Ifb theyb areb likelyb tob change,b
thenb ab contemporaryb techniqueb mayb beb moreb suitable.b Assessb theb potentialb risksb andb benefitsb
ofb eachb techniqueb andb compareb them.b Identifyb theb potentialb needsb andb priorities.b
Traditional-b thisb isb tob beb doneb whereb thereb isb ampleb sampleb spaceb andb theb timeb isb alsob notb ab
constraint,b theb geographyb isb alsob defined.b Theb drawbackb isb itb isb timeb consumingb andb tob beb
usedb whenb sampleb sizeb isb goodb &b ampleb timeb isb present.b
Contemporaryb isb usedb whenb theb timeb isb limitedb andb moreb analysisb isb required,b theb sampleb
sizeb isb less,b andb web areb requiredb tob getb ab birdb eyeb viewb ofb theb situation.b Theb drawbackb isb theb
resultsb giveb theb bird'sb viewb asb basedb moreb onb analysisb andb estimate.b Itb isb tob beb usedb whenb
web haveb lessb time,b andb web needb anb overallb trend.b
Radical-b Itb isb theb mostb advancedb techniqueb available,b whenb theb timeb isb less,b andb theb sampleb
sizeb isb toob less.b Prototypingb helpsb whenb web haveb almostb nilb sampleb sizeb andb web useb similarb
patternsb tob understandb theb trend,b thisb mightb notb beb accurateb inb practicalb senseb asb theb
variablesb mayb change.b Tob beb usedb whenb web dob notb haveb ab sampleb sizeb butb haveb ab similarb
modelb whichb behavesb inb likewiseb fashion.b Whenb itb comesb tob systemsb analysisb differentb
techniquesb areb usedb tob determineb systemsb requirements.b Traditional,b contemporary,b andb
radicalb techniquesb areb threeb suchb methods.b Theb traditionalb techniqueb focusesb onb gatheringb
informationb aboutb theb systems'b requirementsb fromb stakeholdersb throughb interviews,b surveys,b
andb questionnaires.b Theb contemporaryb techniqueb reliesb onb prototypingb andb iterativeb design,b
whichb involvesb developingb ab workingb modelb ofb theb systemb andb refiningb itb throughb feedbackb
fromb users.b Theb radicalb techniqueb involvesb brainstormingb andb creativeb thinkingb tob generateb
innovativeb solutionsb thatb challengeb traditionalb assumptions.Eachb ofb theseb techniquesb hasb itsb
strengthsb andb weaknesses.b Theb traditionalb techniqueb isb usefulb whenb dealingb withb well-
understoodb problemsb andb stakeholdersb withb clearb expectations.b However,b itsb drawbacksb
includeb theb potentialb forb biasb andb limitedb creativity.b Theb contemporaryb techniqueb isb mostb
effectiveb whenb dealingb withb complexb orb unfamiliarb problems,b asb itb allowsb forb rapidb
prototypingb andb anb iterativeb designb processb thatb canb quicklyb generateb solutions.b However,b itb
canb beb time-consumingb andb costly,b andb feedbackb fromb usersb mayb notb alwaysb beb reliable.b
Theb radicalb techniqueb isb idealb whenb dealingb withb uncertainb orb ill-definedb problems,b asb itb
encouragesb innovativeb thinkingb andb promotesb out-of-the-boxb solutions.b However,b itb canb beb
difficultb tob implementb andb mayb requireb ab significantb investmentb ofb timeb andb resources.b
Ultimately,b theb decisionb ofb whichb techniqueb tob useb shouldb beb basedb onb ab carefulb assessmentb
ofb theb project'sb goals,b requirements,b andb constraints.b Ifb youb lookb atb ab listb ofb reasonsb forb
failedb projects,b you'db probablyb seeb reasonsb like:b scopeb creep,b unclearb requirements,b
insufficientb planning,b andb insufficientb resources.b Mostb ofb theseb centerb aroundb planning.b
Analysisb isb anotherb planningb phaseb forb usb inb theb SDLC.b Forb thisb reason,b web callb itb BUFDb --b
bigb up-frontb design.b Web tryb tob getb tob ab perfectb stateb inb requirementsb andb theb designb thatb
follows,b thenb web implementb themb withoutb anyb issues.b Orb atb leastb web tryb tob inb waterfallb
methods.b Agileb takesb ab differentb approach.b Web takeb ab bigb ideab (anb epicb orb feature)b atb theb
startb ofb ab project,b thenb web breakb itb downb intob smallerb piecesb (ab userb story).b Whenb we'reb
readyb tob implementb theb storyb inb ourb sprint,b web breakb itb downb againb intob ab seriesb ofb tasks.b
Theb resultb isb thatb web actuallyb dob moreb planningb inb agileb thanb inb waterfall.b But,b web dob itb
incrementallyb andb web dob itb justb inb timeb beforeb web buildb it.b Inb agile,b ourb requirementsb shouldb
beb clear,b butb thisb isn'tb alwaysb theb case.b Ib workedb forb ab companyb thatb developedb softwareb forb
customers,b andb web wereb wroughtb withb issues.b Thisb mightb haveb beenb theb faultb ofb theb
customer,b theb productb owner,b orb theb developers.b Maybeb allb ofb theb above.b Ib sayb thisb becauseb
thereb isb nob silverb bulletb whenb itb comesb tob buildingb systems.b Duringb theb analysisb phaseb isb
whereb theb as-is-systemb isb understoodb andb theb gatheringb ofb requirementsb ofb theb to-be-systemb
happens.b Thereb areb traditional,b contemporary,b andb radicalb techniquesb thatb canb beb usedb tob
determineb theb requirements.b Traditionalb b Typicallyb usesb anb interviewb approach,b whereb theb
systemb analysistb willb dob someb researchb upb frontb thenb conductb interviewsb withb appropriateb
subjectb matterb expertsb tob understandb theb issueb andb gatherb theb requirementsb forb theb newb
system.b Thisb usuallyb isb doneb usingb ab top-downb approachb withb closed,b open,b orb probingb
questions.b Theb benefitb ofb thisb techniqueb isb thatb youb areb speakingb withb allb levelsb andb canb trulyb
digb downb intob theb system.b Theb drawbackb isb itb isb timeb consumingb andb ifb notb doneb correctlyb
canb leadb tob scopeb creep.b Contemporaryb b Thisb techniqueb typicallyb worksb withb groups,b theb
readingb thisb weekb givesb anb exampleb ofb Jointb Developmentb Assessmentb (JAD).b Doneb withb ab
facilitator,b usuallyb atb anb offsiteb location,b yourb moreb seniorb levelb subjectb matterb expertsb
attendb whob understandb mission,b issuesb andb requirements.b Inb myb experienceb thisb isb howb web
haveb dealtb withb requirementsb gathering.b Theb benefitb isb thatb itb canb beb doneb quickerb withb lessb
ofb ab scopeb creep.b Theb drawbackb isb thatb youb haveb severalb seniorb levelb individualsb outb ofb theb
labb forb ab weekb orb two.b Radicalb b Ib lookb atb thisb asb ab greenfieldb approach,b ab completeb redesignb
andb thinkingb ofb theb system.b Theb advantageb isb youb canb designb theb wayb youb need,b butb theb
disadvantageb isb theb cost.b
Interviewingb andb Listening-
Interviewingb isb oneb ofb theb traditionalb waysb analystsb gatherb informationb aboutb anb informationb
systemsb project.b Earlyb inb ab project,b anb analystb mayb spendb ab largeb amountb ofb timeb
interviewingb peopleb aboutb theirb work,b theb informationb theyb useb to.
Advantages:
b Interviewb isb ab flexibleb tool.
b Itb offersb ab betterb opportunityb ratherb thanb theb questionnaireb tob evaluateb theb validityb ofb theb
informationb gathered.
b Itb isb anb effectiveb techniqueb forb elicitingb informationb aboutb complexb subject.
Disadvantages:
b Longb preparationb time.
b Takeb ab lotb ofb timeb andb moneyb tob conduct.
b Interviewsb areb alsob usefulb whenb theb topicb youb areb studyingb isb ratherb complex,b whenb
whateverb youb planb tob askb requiresb lengthyb explanation,b orb whenb yourb topicb orb answersb tob
yourb questionsb mayb notb beb immediatelyb clearb tob participantsb whob mayb needb someb timeb orb
dialogueb withb othersb tob workb throughb theirb responsesb tob yourb questions
Students also viewed