er系統(tǒng)中的可用性問題英文3_第1頁
er系統(tǒng)中的可用性問題英文3_第2頁
er系統(tǒng)中的可用性問題英文3_第3頁
er系統(tǒng)中的可用性問題英文3_第4頁
er系統(tǒng)中的可用性問題英文3_第5頁
已閱讀5頁,還剩23頁未讀, 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡介

IdentifyingERPUsabilityIssuesERPResearchWorkshopBentleyCollegeOctober15,2004WendyLucasTamaraBabaianHeikkiTopiIdentifyingUsabilityIssuesAnecdotalevidenceHardtogetdataintoERPsystemMismatchbetweenERPterminologyandbusinesspracticesEvenhardertogetinformationout!ExportdatatoExcel,AccesstoperformanalysisForresterResearchevaluation*TasksrequireinordinatepatienceandexpertisetocompleteUsersshoulddemandbetterusability*[Chew,Orlov,&Herbert,2003]ResearchQuestionsWhichcharacteristicsoflarge-scaleenterprisesystemshaveanegativeimpactontheirusability?Howshouldthesecharacteristicsbecategorized?CancollaborationtheorybeusedasaframeworkforidentifyingERPusabilityproblemsanddesigningsystemswithimprovedusability?Multi-MethodStudyFieldstudytoidentifyusabilityproblemsDevelopmentofatheoreticalmodeltoprovideastrongfoundationforenterprisesystemusabilitydesignandevaluationDevelopmentofaprototypeExperimentalanalysisOrganizationalContextforFieldStudyDivisionofaverylargediversifiedFortune500corporationBusiness:maintenanceofcomplexengineeringartifactsAlldatacollectedfromasinglefacilityMethodandInformantsDatacollectionthroughsemi-structuredinterviewsAtthisstage,10interviewslastingonaverageanhoureachAlargevarietyoforganizationalrolesrepresentingshopfloortechniciansupthroughuppermiddlemanagementAllinformants(exceptone)usersofthesamelarge-scaleintegratedERPsystemIdentifiedProblemCategoriesIdentificationofandaccesstothecorrectfunctionalityTransactionexecutionsupportSystemoutputlimitationsSupportinerrorsituationsTerminologyproblemsOverallsystemcomplexityIdentifyingandFinding

CorrectFunctionalityNavigationproblems“Ormaybewehavesomemenus,butpresentlyitmaytakeusfour,fiveorsixroutestogetustobasicallyonescreen.Idon’talwaysseethelinks.”Difficultiesinunderstandingthedependenciesbetweenthemodules“They're[warehouse,inventory]twoseparatemodulesthatdon'ttalktooneanother.So,thatcreatesthatverysituation,wheresomebodycangoonthewarehousingside,andcancelatransferorder,buttheydon'tknowtogolookonthematerialssideofthemodule,toseewhatthatresultedin.”LackingTransaction

ExecutionSupportUndulycomplextransactionsNeedtoenterdatarepetitively“…whydoIhavetokeepenteringthesamedataoverandover?”Inconsistentbehavior“Well,Imean,we'resousedtocopyingandpasting.…Insomecases,itremembersandwillcarryovertosomeofthescreens,butnotinallcases.”LackingTransaction

ExecutionSupportPoorsupportforexceptionsituationsleadstosystemavoidance“Like[aspecifictask],nobodywantstodo[it]inthesystem.…Youknow,they’reusedtojustgoingandget[ting]thepartandmanuallydoingthepaperworkandjusttakingthepartandjusttellingthebuyer-plannerlateraboutit.“SystemOutputLimitationsInabilitytogetrequiredoutput“It[theERP]doesn'tgiveyoutheinformationyouneed,anditjustmakesyou[r]workmoredifficult––Ifounditnoteasytouse,nottherightinformation,didn'tupdatecorrectly,didn'thavealotofflexibility.”Needtouseexternaltoolstoprocessthedatafurther“AndunlessIexportthatdowninto[an]Excelfileorsomething,thesystem[isnot]capableofcompressingthat[data],tominimizeit,reduceit.”CognitivecomplexityofquerytoolsIt'sjustthatyouneedtobeabrainsurgeontoactuallygooutand………produceyourown[queries].SupportinErrorSituationsIncorrectorinsufficienterrormessages“You’vegottogoseesomebodyabouthowcomeit’’sred.Butthat’safteryourtransactioniscompleted.…Itjustsaystransactionfailedorsomethinglikethat.”Lackofspecificity“Wehaveascreenwherewetryandreturnpartstothewarehouseandifthat'salreadybeendone,thetransactionhasalreadybeendone,itsays‘‘1045error’’onthebottomofthescreen.What[expletive]doesthatmeantoanybody?”Missingerrormessages“Wehadthecustomizedfront-endandwehadtohittwobuttonstoexecuteatransaction.Butthesystemwillallowyoujusttohitone.Sotheguyswouldhitoneandeverythingwouldbegreen,hey,Imustbeokay,buttheynevercreatedtheotherrequirementsthatwerenecessaryto[completethetransaction].”TerminologyProblemsUnfamiliarsystemlanguage“The‘Help’isworthlessbecauseit'sdefinitelyprogrammer’slanguagebased.Sohavingthe‘Help’customizedforbusinessprocesseswouldbe[an]importantpiece.““Well,itwaslikethespaceshiphadlanded,andtheseouterspacecreatures[trainers]gotoff,andstartedtalkingtousabouthowweweregoingtodoourjob,becausenobodyunderstoodwhattheyweresaying.””Needforaglossary“Iputtogetheraglossaryofhowthevocabularychangedfrompre-[ERP]topost,becausepeopledidn'tunderstandtheterms.””O(jiān)verallSystemComplexityGeneralfeelingofoverwhelmingcomplexityleadingtofeelingsoffear“It'saveryintimidatingsystem.“““……h(huán)ewaslikeadeer;itwaslikehegotsoupsetbecauseitwassooutofhiskingdom,sooutofhisnormal--heshutdownonme.““[reactionwhenexplaininghowtoenterawell-understoodprocesstotheERPsystem]OtherObservationsHavingresourcestocustomizeisvitallyimportantSignificantamountoftimeandeffortspentonthedevelopmentofinformaldocumentationFormaldocumentationisseldomusedPowerusersplayaverysignificantroleNon-powerusersaremuchlesslikelytoexplorethesystem’’spotentialLearningtoperformanewtaskisadifficultprocessbasedontrialanderror,evenforexperiencedandmotivatedusersDespitethesedifficulties,givenenoughtimeandeffort,usersdolearnhowtocompletetheirrequiredtasksMajorbenefitscomefromintegrated,consistentdataOtherObservationsApproachBasedonCollaborationTheoryAllusabilityproblemsdiscussedareexamplesofnon-collaborativebehaviorbythesystemRecognizesthejointnatureoftheactivityViewssystemasapartnerincollaborationViewingtheSystemAsaPartnerIneedthosesuppliesbyJanuary23,2005Idon’tunderstandwhatyoumeanbyJanuary23,2005Dateperiodisnotvalid.Tryagain…CollaborationTheory*CommitmenttomutualsupportrequiresRecognitionofthecontextinwhichtheactivityoccursCommunicationtocreatecoordinated,althoughindependent,subplansfortheactivityMutualresponsivenessrequiresbothpartiestosharerelevantknowledgeandadapttheirbehaviorformutualsupportIfyou’’rehavingaproblemwithasubtask,andIcanhelpbyprovidinginformationorperforminganaction,Imustofferhelp.*[Bratman,1992;Grosz&Kraus,1996]Example:PurchaseRequisitionTask:CreateaPurchaseRequisition(PR)foranewpart.ProblemsencounteredbyPat,theuser:StartnewPR-partnotinMaterialMaster––scrapthePR,addpartMenupathforaddinganewpartishardtolocateifusedonlyoccasionallyStartnewPR–entertheplant,butforgotthepartnumberLookupthepartnumber––screenchangescompletely-about12differentlookupoptionsdisplayed–whichtochoose?Finallyenteredalldatashehas––butmanyPRformfieldsarestillempty––isshedone?CollaborativeCritiqueInsteadofhavingtoscrappurchaseorderduetomissingpartLinktotheAddNewPartoptionisreadilyavailablefromthesamescreenProblems1and2arepreventedInsteadofrequiringPattorememberthepartnumberSystemremembersthenumberofthenewlyaddedpartProvidesanoptionofenteringitautomaticallyAlsoprovidesaccesstoallpartsforthatplantToletPatknowwhentheprocessiscompleteOptionalfieldsareclearlydistinguishablefromtherequiredonesUsingCollaborationTheoryFrameworkfordesignandevaluationforusabilityRealignsresponsibilitiesbetweentheuserandthesystemaccordingtotheirrolesandnaturalstrengths,e.g.Userrequiredtoknowwhat’sthenextstepversusSystemguidingtheuserthroughthestepsofthebusinessprocessCollaborativeapproachtoERPdesignAdjustable/business-basedsystemvocabularyGuidancethroughstepsofbusinessprocessVisibleaccesstorelatedtasksCommunicationofprogressmadeafterperforminganactionInformationonimportantramificationsofuseractionsbeyondtheobviousSupportforuserinerrorsituation:offeradiagnosis/fixand/oranalternativecourseofactionintermsfamiliartotheuserUsingPrinciplesofCollaborationinInterfaceDesign:aProtot

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲(chǔ)空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

最新文檔

評(píng)論

0/150

提交評(píng)論