Clarification of Customers’ “Demand” in Development Process
HCD is a method to give better UX to stakeholders and to provide system and product with high usability for users and stakeholders. When system and product with high usability could be developed, it is easy to verify their usability by usability test. However, it is difficult to check whether these products or system achieve that a user wants to really do it which required in UX white paper. To verify what is thing that users want to do, we discuss what is necessary for development process by analyzing how to take in customer needs to specification from the view point of software engineering and HCD. We propose a phase “acquisition of user demand” before “clarification of user needs” and “specification of user requirements” which are activities of HCD process.
It is important to clarify “demand” and to separate solving by requirements to system and besides that, and both customers’ and developers’ shall be recognize that to satisfy the customer’ needs to the system is not same as to realize customers’ “demand”.
KeywordsHCD SWE Quality Requirements Development process
- 1.ISO9241-210: Human-centred design for interactive systems (2010)Google Scholar
- 2.Tanikawa, Y., Suzuki, H., Kato, H., Fukuzumi, S.: Problems in usability improvement activity by software engineers - consideration through verification experiments for human- centered design process support environment. In: Yamamoto, S. (ed.) HCI 2014, Part I. LNCS, vol. 8521, pp. 641–651. Springer, Heidelberg (2014)Google Scholar
- 3.ISO/IEC 25062: Software engineering.— Software product Quality Requirements and Evaluation (SQuaRE) .— Common Industry Format (CIF) for usability Test Reports (2005)Google Scholar
- 4.Roto, V., Law, E., Vermeeren, A., Hoonhout, J. (ed.): Use Experience White Paper - Bringing clarity to the concept of user experience, Result from Dagstuhl Seminar on Demarcating User Experience, September 15–18, 2010, pp. 1–12 (2010)Google Scholar
- 5.Nonaka, M., Azuma, M.: Systems and Software Quality: 5. Non-Functional Software Requirements Definitions: For Creating Quality Software, Information processing society of Japan, vol. 55, No.1, pp. 31–37, January 2014 (in Japanese)Google Scholar
- 6.ISO/IEC25030: Software engineering -Software product Quality Requirements and Evaluation (SQuaRE) –Quality Requirements (2007)Google Scholar
- 7.IEEE CS, ACM: Software Engineering 2004: Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering (2004). http://sites.computer.org/ccse/
- 8.V-Modell XT (2005). http://www.v-modell-xt.de
- 9.ISO/IEC 25010: Software engineering. -Software product Quality Requirements and Evaluation (SQuaRE) - System and software quality models (2011)Google Scholar
- 10.Okubo, R., Tanikawa, Y., Fukuzumi, S.: Proposal for a method to clarify customer needs using HI (Human Interface) patterns. In: Proceedings of the 5th International Conference on Applied Human Factors and Ergonomics AHFE 2014, pp. 4097–4108 (2014)Google Scholar
- 11.ISO/IEC25022: Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Measurement of quality in use (2016)Google Scholar
- 12.ISO/IEC25063: Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Context of use description (2014)Google Scholar