Análise de Sistemas de Informação (ASI) - UBIngarcia/aulas/asi1213/UBI ASI 1213 aula 7.pdf ·...

JoãoPauloFernandes,[email protected],[email protected]

AnálisedeSistemasdeInformação(ASI)

AnoLecFvo2012/2013*1ºSemestre

MestradoemEngenhariaInformáFca

UNIVERSIDADEDABEIRAINTERIORFaculdadedeEngenhariaDepartamentodeInformáFca JoãoPauloFernandes,[email protected]

Aula7

1


Previously...

Contentadaptedfrom

SystemsAnalysisandDesignwithUML,4thEdiFonInternaFonalStudentVersion

AlanDennis,BarbaraHaleyWixomandDavidTegarden,

Wiley,2012


2



3

RequirementsDeterminaFon

Purpose:toconverthighlevelbusinessrequirements(fromthesystemrequest)intodetailedrequirementsthatcanbeusedasinputsforcreaFngmodels

Whatisarequirement?AstatementofwhatthesystemmustdooracharacterisFcitmusthaveWilllaterevolveintoatechnicaldescripFonofhowthesystemwillbeimplemented

Types:FuncFonal:relatestoaprocessordataNon‐funcFonal:relatestoperformanceorusability



4

NonfuncFonalRequirements

Requirementtype Example

OperaFonal • Thesystemshouldbeabletofitinapocketorpurse• ThesystemshouldbeabletointegratewiththeexisFnginventorysystem.

Performance • AnyinteracFonbetweentheuserandthesystemshouldnotexceed2seconds.

• ThesystemshouldreceiveupdatedinventoryinformaFonevery15minutes.

Security • Onlydirectmanagerscanseepersonnelrecordsofstaff• Customerscanseetheirorderhistoryonlyduringbusinesshours.

Cultural&PoliFcal • ThesystemshouldbeabletodisFnguishbetweenUnitedStatesandEuropeancurrency

• Thesystemshallcomplywithinsuranceindustrystandards.



5

RequirementsDefiniFonNon‐func8onal,Thesystem: Func8onal,Thesystemmust:

1.Opera8onalRequirements1.1willoperateinMSWindows1.2shouldconnecttoprinterswirelessly1.3shouldautomaFcallybackupattheend

ofeachday2.PerformanceRequirements2.1willstoreanewappointmentin2seconds2.2willretrievetheschedulesin2seconds3.SecurityRequirements3.1onlydoctorscansettheiravailability3.2onlyamanagercanproduceaschedule4.Culturalandpoli8calRequirements4.1NonehasbeenanFcipated

1.ManageAppointments1.1PaFentmakesnewappointment1.2PaFentchangesappointment1.3PaFentcancelsappointment2.ProduceSchedule2.1OfficeManagerchecksdaily

schedule2.2OfficeManagerprintsdailyschedule3.RecordDoctoravailability3.1Doctorupdatesschedule



6

RequirementsDefiniFon

Non‐func8onal,Thesystem: Func8onal:

1. Opera8onal1.1willoperateonWindowsandMac,andallbrowsers.1.2Thewillbeconnectedtovendorstoprovidereal‐FmeproductinformaFon

2. Performance2.1TheproductDBmustbeupdatedinrealFme2.2mustprovideresultstouserqueriesin<5secs

3. Security3.1High‐levelsecuritymustbeavailableforcustomerfinancial

transacFons3.2mustbeprotectedagainstunauthorizedentry

4. Culturalandpoli8cal4.1shouldbeavailableinvariouslanguages4.2shouldtailorproductofferingsandadverFsementstotheregionandcustomer4.3shouldmaintainfeaturestorecognizeandobeyvariouslawsindifferentregionsregardingtaxaFon,shipping,andproductapproval

1. OnlineStore1.1StoreproductinformaFon1.2Allowcustomerstosearchandviewproducts1.3Allowcustomerstoplaceproductsinshoppingcart

2. Ordering2.1Allowcustomerstopurchaseproducts2.2Facilitatecustomerpayment2.3Relaycustomerordertovendors3. CustomerInforma8onManagement3.1ManagecustomerinformaFondatabase3.2TailoradverFsementstocustomerprofile3.3Providecustomerserviceinterface4. VendorManagement4.1Providereal‐Fmeinventorymanagement4.2Trackserviceperformanceofcustomer4.3ManageadverFsements

1.ReviewtheAmazon.comWebsite.DeveloptherequirementsdefiniFonforthesite.CreatealistoffuncFonalbusinessrequirementsthatthesystemmeets.WhatdifferentkindsofnonfuncFonalbusinessrequirementsdoesthesystemmeet?Provideexamplesforeachkind.


TheAnalysisPhase:

Requirements‐GatheringTechniques

Contentadaptedfrom

SystemsAnalysisandDesignwithUML,4thEdiFonInternaFonalStudentVersion

AlanDennis,BarbaraHaleyWixomandDavidTegarden,

Wiley,2012


7



8

RequirementsGatheringTechniques

Purpose‐Uncoverallrequirements(thoseuncoveredlateintheprocessaremoredifficulttoincorporate)‐ Buildsupportandtrustamongusers

TechniquesInterviews

JointApplicaFonDevelopment(JAD)QuesFonnaires

DocumentanalysisObservaFon



9

Interviews

Mostpopulartechnique—ifyouneedtoknowsomething,justask

Ingeneral,theyareconductedone‐on‐one

Steps:1.Selectpeopletointerview&createaschedule2.DesigninterviewquesFons(Open‐ended,closed‐ended,&probingtypesofquesFons)3.Preparefortheinterview(Unstructuredvs.structuredintervieworganizedinalogicalorder)4.Conducttheinterview(Top‐downvs.boqom‐up)5.Follow‐uparertheinterview



10

1.SelectInterviewees

Ge

ne

rate

d b

y C

am

Sc

an

ne

r



11

2.DesignInterviewQuesFons

DonotaskquesFonsaboutinformaFonthatisavailablefromothersources!



12

2.DesignInterviewQuesFons

Howcanorder

processingbeimproved?

HowcanwereducethenumberofFmesthatcustomers

returnordereditems?

Howcanwereducethenumberoferrorsinorderprocessing(e.g.,shipping

thewrongproducts)?

Top‐down

BoRom‐up

High‐level:Verygeneral

Medium‐level:Moderatelyspecific

Low‐level:Veryspecific



13

3.Preparefortheinterview

‐InthesamewayasyouwouldprepareforapresentaFon

‐Defineageneralinterviewplan,lisFngwhattoaskandinwhatorder

‐Antecipatepossibleanswersandprovidefollow‐upwiththem

‐Confirmtheareastheintervieweehasknowledge

‐Preparetheintervieweeaswell

explainthereasonsfortheinterview

presenttheareastobediscussedfarenoughinadvance

JoãoPauloFernandes,[email protected],[email protected]ãoPauloFernandes,[email protected]

14

4.Conducttheinterview‐Buildrapportwiththeinterviewee,sothathe/shewilltrustyou,andtellsyouthewholetruth,notjustanswersthathe/shethinksarewanted

‐Beprofessionalandunbiased

‐Startbyexplainingwhytheintervieweeisthereandwhywaschosen

‐Followyourinterviewplan

‐ Carefullytakedetailednoteswritedowneverythingtheintervieweesays

downbeafraidtoaskhim/hertopauseorslowdown

recordingtheinterviewraisesseveralissues

‐Separatefactsfromopinion

‐ TheintervieweeshouldbegivenFmetoexpressopinionsoutsidetheplan

‐ Explainwhathappensnext



15

5.Post‐InterviewPrepareaninterviewreportandsendtotheintervieweeforverificaFon



16

JointApplicaFonDevelopment(JAD)

ItisorenthemostusefulmethodforcollecFnginformaFonfromusers canreducescopecreep preventssystemrequirementsfrombeingtoospecificortoovague

Jointuser‐analystmeeFnghostedbyafacilitator10to20users1to2scribesasneededtorecordthesessionUsuallyinaspeciallypreparedroom

MeeFngscanbeheldelectronicallyandanonymouslyReducesproblemsingroupsetngsCanbeheldremotely



17

JointApplicaFonDevelopment(JAD)

Ge

ne

rate

d b

y C

am

Sc

an

ne

r



18

JADSteps1.SelectparFcipants

FollowsthesameprinciplesusedforinterviewsThefacilitatorshouldbeexperienced

2.DesignaJADsession

Sessionsrequirecarefulplanningtobesuccessful

Closed‐endedquesFonarerarelyused3.PrepareforaJADsession PreparetheanalystsandparFcipantsforwhatisexpectedofthem:ifthepurposeofthesessionistodevelopanunderstandingofthecurrentsystem,usersmayneedtobringdocumentsorusermanuals4.ConductaJADsession Groundrulesshouldbeestablished:followtheschedule,respectother’sopinion,accepFngdisagreement,onepersontalkingattheFme Facilitator:ensuresagendaisrespected;establishescommonvocabularyforthesession;recordsinputs5.Post‐JADfollow‐up AJADpost‐sessionreportispreparedandcirculatedamongaqendees.



19

QuesFonnaires

AsetofwriqenquesFonsusedtoobtaininformaFonfromindividuals

Maybepaperbasedorelectronic(e.g.,webbased)

Commonuses:LargenumbersofpeopleNeedbothinformaFonandopinionsWhendesigningforuseoutsidetheorganizaFon(customers,vendors,etc.)

Typicalresponserates:<50%(paper);<30%(Web)



20

QuesFonnairesSteps1.SelecttheparFcipants IdenFfythepopulaFon UserepresentaFvesamplesforlargepopulaFons

2.DesigningthequesFonnaire CarefulquesFonselecFon

RemoveambiguiFes

3.AdministeringthequesFonnaire Workingtogetgoodresponserate

OfferanincenFve(e.g.,afreepen)

4.QuesFonnairefollow‐up SendresultstoparFcipants

Sendathank‐you



21

GoodQuesFonnaireDesign

Beginwithnon‐threateningandinteresFngquesFons

GroupitemsintologicallycoherentsecFons

Noimportantitemsattheveryend

Donotcrowdapagewithtoomanyitems

AvoidabbreviaFons

AvoidbiasedorsuggesFveitemsorterms

NumberquesFonstoavoidconfusion

PretesttoidenFfyconfusingquesFons

Provideanonymitytorespondents



22

DocumentAnalysis

ProvidesinformaFonaboutthe“as‐is”system

Reviewtechnicaldocumentswhenavailable

Reviewtypicaluserdocuments:

Forms

Reports

Policymanuals

LookforuseraddiFonstoforms

Lookforunusedformelements



23

ObservaFon

Users/managersorendon’tremembereverythingtheydo

ChecksvalidityofinformaFongatheredinotherways

Behaviorsmaychangewhenpeoplearewatched

Workerstendtobeverycarefulwhenwatched

Keepalowprofile

Trynottointerruptorinfluenceworkers

BecarefulnottoignoreperiodicacFviFes

Weekly…Monthly…Annually



24

ObservaFon

Generated by CamScanner



25

Requirements‐GatheringTechniquesCompared

AcombinaFonoftechniquesmaybeused

Documentanalysis&observaFonrequireliqletraining;JADsessionscanbeverychallenging


TheSystemProposal

• Combinesallmaterialcreatedinplanning&analysis• IncludedsecFons:– ExecuFvesummary

• ProvidesallcriFcalinformaFonissummaryform• HelpsbusyexecuFvesdeterminewhichsecFonstheyneedtoreadinmoredetail

– Thesystemrequest– Theworkplan– Thefeasibilityanalysis– TherequirementsdefiniFon– Currentmodelsofthesystem(expectedtoevolve)


SystemProposalTemplate


Summary

• Presentedinthischapter:– DiscussionoffuncFonalandnon‐funcFonalrequirementsdeterminaFon

– Requirementsanalysisstrategies

– Requirementsgatheringtechniques– AlternaFverequirementsdocumentaFontechniques

– Thesystemproposal

Análise de Sistemas de Informação (ASI) - UBIngarcia/aulas/asi1213/UBI ASI 1213 aula 7.pdf ·...

Documents

Transcript of Análise de Sistemas de Informação (ASI) - UBIngarcia/aulas/asi1213/UBI ASI 1213 aula 7.pdf ·...