




版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)
文檔簡(jiǎn)介
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. 本站所有資源如無(wú)特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。
最新文檔
- 【正版授權(quán)】 ISO 13943:2008 RU Fire safety - Vocabulary
- 【正版授權(quán)】 IEC 61058-1:2000+AMD1:2001 CSV FR-D Switches for appliances - Part 1: General requirements
- 【正版授權(quán)】 IEC 60669-1:1998+AMD1:1999 CSV EN-D Switches for household and similar fixed-electrical installations - Part 1: General requirements
- 【正版授權(quán)】 IEC 60335-2-73:2002+AMD1:2006 CSV EN-D Household and similar electrical appliances - Safety - Part 2-73: Particular requirements for fixed immersion heaters
- 【正版授權(quán)】 IEC 60245-8:1998+AMD1:2003 CSV FR-D Rubber insulated cables - Rated voltages up to and including 450/750 V - Part 8: Cords for applications requiring high flexibility
- 少先隊(duì)輔導(dǎo)員培訓(xùn)方案
- 小班小球快跑課件
- 護(hù)理上門服務(wù)方案
- 2025年銷售公司年度工作方案演講稿
- 2025年學(xué)校一班級(jí)班務(wù)工作方案
- 鐵路轉(zhuǎn)轍機(jī) ZDJ9型電動(dòng)轉(zhuǎn)轍機(jī)認(rèn)知
- 第四章礦井通風(fēng)動(dòng)力
- 2021年4月四川省自考06093人力資源開發(fā)與管理試題及答案含解析
- 聯(lián)社監(jiān)事長(zhǎng)整改措施
- 產(chǎn)房醫(yī)院感染控制風(fēng)險(xiǎn)評(píng)估表
- 冠心病健康教育完整版
- 2021年新高考英語(yǔ)讀后續(xù)寫母親節(jié)課件高考英語(yǔ)一輪復(fù)習(xí)
- 《關(guān)于“人工智能”》非連續(xù)文本閱讀練習(xí)及答案
- 鋼平臺(tái)鋪板計(jì)算excel(可當(dāng)計(jì)算書)
- 《強(qiáng)化學(xué)習(xí)理論與應(yīng)用》環(huán)境
- 國(guó)開經(jīng)濟(jì)法律基礎(chǔ)形考任務(wù)國(guó)開電大《經(jīng)濟(jì)法律基礎(chǔ)》形考任務(wù)4答案
評(píng)論
0/150
提交評(píng)論