Abstract
Usability is part of product risk management and quality management. It should also be part of product creation process. However, usability engineering models do not fit into concurrent product development practices. In this paper we describe what incompatibilities there are between usability engineering lifecycle and concurrent product development process and describe an example how this problem is handled at Nokia Mobile Phones. Current descriptions for usability engineering lifecycle describe how the work is done during one engineering lifecycle or in one product development project (project organisation) from the very beginning of design to the product launch and to the collection of field feedback. However, in mature development organizations usability engineering is continuous and parallel work from one product to another (line organisation) and the engineering practice should take this continuity into account. In addition to this, product development is naturally divided into three different phases that set different requirements for the engineering work. These phases are concept work, actual product development and evaluation of the product on the market.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
