USER-CENTERED SYSTEMS ENGINEERING: A SUCCESS STORY

Douglas L. Miller, G. Wolfman, A. J. Volanth
{"title":"USER-CENTERED SYSTEMS ENGINEERING: A SUCCESS STORY","authors":"Douglas L. Miller, G. Wolfman, A. J. Volanth","doi":"10.1109/DASC.1995.482912","DOIUrl":null,"url":null,"abstract":"Systems engineering organizations are increasingly concerned with finding ways to be more “customer driven” and to establish “user-centered’ systems engineering practices. However, it is much easier to find recommendations than it is to find examples of successhl user-centered systems engineering. This paper reports the success of one organization in developing user-centered systems engineering practices through four hndamental organizational changes. First, a User Interface (UI) systems engineering team was established with responsibility for systems engineering activities critical to product usability; These activities included development of concepts of use, U1 prototypes, U1 requirements, and managing end-user program involvement. Second, the U1 design was incorporated into the software requirements specifications. Third, effective U1 processes were established for defining requirements, designing and evaluating the UI, and leveraging end-user expertise. Finally, commitment of management and engineering leadership brought about these organizational changes and made their success possible. INTRODUCTION Terms such as “customer driven,” “usercentered design,” and “user-centered systems engineering” can be found echoing through the halls of many systems development organizations today. They reflect a frequently perceived need to find ways to enhance the focus of the systems engineering process and organization on satis@ing customer needs. Customer needs take many forms, but in this case the concern typically has to do with providing systems that do an excellent job of supporting operators in performing their tasks (i.e., system usability); producing these systems within aggressive schedules and tight budgets; and, “getting it right the first time,” rather than through endless expensive system modifications after the system is built. A number of factors bear some responsibility for the growing focus on system usability. One factor is continued “system creep” as computer systems gradually get applied to more workplace tasks. Another related factor is the ever increasing use of computer systems in environments where the operators are experts at their jobs, not experts with computers. Of course, this focus is also partly the effect of past systems that did not adequately meet customer needs.","PeriodicalId":125963,"journal":{"name":"Proceedings of 14th Digital Avionics Systems Conference","volume":"2 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1995-11-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of 14th Digital Avionics Systems Conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/DASC.1995.482912","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 2

Abstract

Systems engineering organizations are increasingly concerned with finding ways to be more “customer driven” and to establish “user-centered’ systems engineering practices. However, it is much easier to find recommendations than it is to find examples of successhl user-centered systems engineering. This paper reports the success of one organization in developing user-centered systems engineering practices through four hndamental organizational changes. First, a User Interface (UI) systems engineering team was established with responsibility for systems engineering activities critical to product usability; These activities included development of concepts of use, U1 prototypes, U1 requirements, and managing end-user program involvement. Second, the U1 design was incorporated into the software requirements specifications. Third, effective U1 processes were established for defining requirements, designing and evaluating the UI, and leveraging end-user expertise. Finally, commitment of management and engineering leadership brought about these organizational changes and made their success possible. INTRODUCTION Terms such as “customer driven,” “usercentered design,” and “user-centered systems engineering” can be found echoing through the halls of many systems development organizations today. They reflect a frequently perceived need to find ways to enhance the focus of the systems engineering process and organization on satis@ing customer needs. Customer needs take many forms, but in this case the concern typically has to do with providing systems that do an excellent job of supporting operators in performing their tasks (i.e., system usability); producing these systems within aggressive schedules and tight budgets; and, “getting it right the first time,” rather than through endless expensive system modifications after the system is built. A number of factors bear some responsibility for the growing focus on system usability. One factor is continued “system creep” as computer systems gradually get applied to more workplace tasks. Another related factor is the ever increasing use of computer systems in environments where the operators are experts at their jobs, not experts with computers. Of course, this focus is also partly the effect of past systems that did not adequately meet customer needs.
以用户为中心的系统工程:一个成功的故事
系统工程组织越来越关注寻找更加“客户驱动”的方法,并建立“以用户为中心”的系统工程实践。然而,找到建议要比找到成功的以用户为中心的系统工程的例子容易得多。本文报告了一个组织通过四个基本的组织变革成功地开发了以用户为中心的系统工程实践。首先,建立了用户界面(UI)系统工程团队,负责对产品可用性至关重要的系统工程活动;这些活动包括开发使用概念、U1原型、U1需求,以及管理终端用户程序参与。其次,U1设计被合并到软件需求规范中。第三,为定义需求、设计和评估UI以及利用最终用户专业知识,建立了有效的U1过程。最后,管理和工程领导的承诺带来了这些组织变革,并使他们的成功成为可能。诸如“客户驱动”、“以用户为中心的设计”和“以用户为中心的系统工程”之类的术语在今天许多系统开发组织的大厅中都可以找到。它们反映了一种经常被感知到的需要,即找到方法来增强系统工程过程和组织对satis@ing客户需求的关注。客户需求有多种形式,但在这种情况下,关注的通常是提供能够出色地支持操作员执行任务的系统(即系统可用性);在激进的时间表和紧张的预算下生产这些系统;而且,“第一次就把它做好”,而不是在系统建成后进行无休止的昂贵的系统修改。许多因素对系统可用性的日益关注负有一定的责任。一个因素是持续的“系统蠕变”,因为计算机系统逐渐应用于更多的工作任务。另一个相关的因素是,在操作员是他们工作的专家,而不是计算机专家的环境中,计算机系统的使用越来越多。当然,这种关注也部分是由于过去的系统没有充分满足客户的需求。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信