er系统中的可用性问题英文3

上传人:3**** 文档编号:252412096 上传时间:2024-11-15 格式:PPTX 页数:28 大小:348.85KB
收藏 版权申诉 举报 下载
er系统中的可用性问题英文3_第1页
第1页 / 共28页
er系统中的可用性问题英文3_第2页
第2页 / 共28页
er系统中的可用性问题英文3_第3页
第3页 / 共28页
资源描述:

《er系统中的可用性问题英文3》由会员分享,可在线阅读,更多相关《er系统中的可用性问题英文3(28页珍藏版)》请在装配图网上搜索。

1、,*,Body Text,Second Level,Third Level,Fourth Level,Fifth Level,Slide Title,Identifying ERP Usability Issues,ERP Research Workshop,Bentley College,October 15,2004,Wendy Lucas,Tamara Babaian,Heikki Topi,Identifying Usability Issues,Anecdotal evidence,Hard to get data into ERP system,Mismatch between E

2、RP terminology and business practices,Even harder to get information out!,Export data to Excel,Access to perform analysis,Forrester Research evaluation*,Tasks require inordinate patience and expertise to complete,Users should demand better usability,*Chew,Orlov,&Herbert,2003,Research Questions,Which

3、 characteristics of large-scale enterprise systems have a negative impact on their usability?,How should these characteristics be categorized?,Can collaboration theory be used as a framework for identifying ERP usability problems and designing systems with improved usability?,Multi-Method Study,Fiel

4、d study to identify usability problems,Development of a theoretical model to provide a strong foundation for enterprise system usability design and evaluation,Development of a prototype,Experimental analysis,Organizational Context for Field Study,Division of a very large diversified Fortune 500 corp

5、oration,Business:maintenance of complex engineering artifacts,All data collected from a single facility,Method and Informants,Data collection through semi-structured interviews,At this stage,10 interviews lasting on average an hour each,A large variety of organizational roles representing shop floor

6、 technicians up through upper middle management,All informants(except one)users of the same large-scale integrated ERP system,Identified Problem Categories,Identification of and access to the correct functionality,Transaction execution support,System output limitations,Support in error situations,Te

7、rminology problems,Overall system complexity,Identifying and Finding Correct Functionality,Navigation problems,“Or maybe we have some menus,but presently it may take us four,five or six routes to get us to basically one screen.I dont always see the links.”,Difficulties in understanding the dependenc

8、ies between the modules,“Theyre warehouse,inventory two separate modules that dont talk to one another.So,that creates that very situation,where somebody can go on the warehousing side,and cancel a transfer order,but they dont know to go look on the materials side of the module,to see what that resu

9、lted in.”,Lacking Transaction Execution Support,Unduly complex transactions,Need to enter data repetitively,“why do I have to keep entering the same data over and over?”,Inconsistent behavior,“Well,I mean,were so used to copying and pasting.In some cases,it remembers and will carry over to some of t

10、he screens,but not in all cases.”,Lacking Transaction Execution Support,Poor support for exception situations leads to system,avoidance,“Like a specific task,nobody wants to do it in the system.You know,theyre used to just going and getting the part and manually doing the paperwork and just taking t

11、he part and just telling the buyer-planner later about it.,“,SystemOutput Limitations,Inabilitytoget required output,“IttheERP doesntgiveyouthe information youneed,anditjustmakesyourworkmore difficult,Ifounditnot easytouse,notthe right information,didntupdate correctly,didnt havealotofflexibility.”,

12、Need to useexternaltoolstoprocess thedata further,“And unlessI exportthat downintoan Excel fileorsomething,thesystem isnot capableofcompressingthatdata,to minimize it,reduceit.”,Cognitivecomplexityofquerytools,Its justthatyouneedtobea brain surgeontoactuallygoout and,produce yourown queries.,Support

13、 in Error Situations,Incorrectorinsufficient error messages,“Youve gottogoseesomebodyabouthow comeit,sred.Butthatsafteryourtransactioniscompleted.Itjustsays transaction failedorsomethinglikethat.”,Lack of specificity,“Wehavea screenwherewetryand returnpartstothewarehouse andifthatsalreadybeen done,t

14、hetransactionhasalreadybeen done,it says,1045error,on thebottomofthe screen.Whatexpletivedoes thatmeantoanybody?”,Missing error messages,“Wehad thecustomized front-endandwehad to hittwobuttonstoexecute atransaction.Butthesystem willallowyou justtohit one.Sothe guyswouldhit oneandeverythingwouldbegre

15、en,hey,I mustbeokay,but theynevercreatedtheotherrequirements thatwerenecessarytocomplete thetransaction.”,TerminologyProblems,Unfamiliar systemlanguage,“The Helpisworthlessbecauseits definitelyprogrammers language based.Sohavingthe Helpcustomized forbusinessprocesseswouldbeanimportantpiece.“,“Well,i

16、twaslikethespaceshiphadlanded,andtheseouterspacecreaturestrainersgotoff,andstartedtalkingtousabouthowweweregoingtodoourjob,becausenobodyunderstoodwhattheyweresaying.,”,”,Needforaglossary,“Iputtogetheraglossaryofhowthevocabularychangedfrompre-ERPtopost,becausepeopledidntunderstandtheterms.,”,”,OverallSystemComplexity,Generalfeelingofoverwhelmingcomplexityleadingtofeelingsoffear,“Itsaveryintimidatingsystem.,“,“,“,hewaslikeadeer;itwaslikehegotsoupsetbecauseitwassooutofhiskingdom,sooutofhisnormal-he

展开阅读全文
温馨提示:
1: 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 装配图网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

相关资源

更多
正为您匹配相似的精品文档
关于我们 - 网站声明 - 网站地图 - 资源地图 - 友情链接 - 网站客服 - 联系我们

copyright@ 2023-2025  zhuangpeitu.com 装配图网版权所有   联系电话:18123376007

备案号:ICP2024067431-1 川公网安备51140202000466号


本站为文档C2C交易模式,即用户上传的文档直接被用户下载,本站只是中间服务平台,本站所有文档下载所得的收益归上传人(含作者)所有。装配图网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对上载内容本身不做任何修改或编辑。若文档所含内容侵犯了您的版权或隐私,请立即通知装配图网,我们立即给予删除!