Essay regarding User Requirement Analysis

User Requirement Analysis

Proceedings of IFIP seventeenth World Computer system Congress, Montreal, Canada, 25-30 August 2002, p133-148. Kluwer Academic Marketers.

User requirements analysis

An assessment supporting methods

Martin Maguire

Research Institution in Ergonomics and Individual Factors Loughborough University, UK m. c. [email protected] alternating current. uk

Nigel Bevan

Serco Usability Services, UK [email protected] serco. com

Abstract:

Understanding user requirements is a fundamental element of information systems design and it is critical to the success of interactive systems. However indicating these requirements is less than simple to obtain. This newspaper describes basic methods to support user requirements analysis which can be adapted to a range of conditions. Some quick case studies are defined to illustrate how these kinds of methods had been applied used. user requirements, user-centred design and style, usability strategies

Key words:

1 )

INTRODUCTION

Understanding user requirements is an important part of information devices design and it is critical for the success of interactive devices. It is now extensively understood that successful systems and goods begin with a comprehension of the needs and requirements of the users. As specified in the ISO 13407 normal (ISO, 1999), user-centred style begins which has a thorough comprehension of the needs and requirements of the users. The benefits range from increased production, enhanced top quality of work, reductions in support and schooling costs, and improved user satisfaction. Requirements analysis is not a basic process. Particular problems confronted by the expert are: • addressing sophisticated organisational scenarios with many stakeholders • users and designers thinking along traditional lines, reflecting the existing system and processes, instead of being impressive • users not knowing beforehand what they want through the future system (Olphert & Damodaran, 2002)

2 •

M. Maguire and N. Bevan

rapid development periods, reducing enough time available for end user needs research • symbolizing user requirements in an suitable form. This kind of paper thinks how these types of problems could be addressed by selecting appropriate techniques to support the user requirements generation and validation. That describes each method quickly and displays how it contributes to the needs process. The foundation for the use of different end user requirements strategies is a simple procedure as shown in Physique 1 under encompassing some elements:

Information gathering

User needs identification

Envisioning and evaluation

Requirements specification

Physique 1: General process to get user requirements analysis

The four phases, and methods used to support the periods, are referred to in the next areas, followed by a summary table featuring the advantages and drawbacks of each technique.

2 .

DATA GATHERING

The first step in user requirements analysis should be to gather background information about the users and stakeholders and the processes that presently take place. This methods might be adopted: Stakeholder analysis recognizes all the users and stakeholders who may influence or perhaps be impacted by the system. This helps ensure that the needs of all those involved are considered. If required, the system is usually tested by simply them. Customer groups can include end users, supervisors, installers, and maintainers. Different stakeholders include recipients of output in the system, marketing staff, purchasers and support staff (Taylor, 1990). Stakeholder analysis identifies, for each end user and stakeholder group, their particular main functions, responsibilities and task desired goals in relation to the program. One of the main concerns is tips on how to trade-off the competing requires of different stakeholder groups inside the new system (see some. 5 Allowance of function and consumer cost-benefit analysis).

User requirements analysis

3

Secondary researching the market involves exploring published resources such as study reports, census data, market information, that throw light upon the...

References: Andriole, S. L. (1989), Storyboard prototyping: a new approach to end user requirements examination, QED Info Sciences, Incorporation. Bevan N (2001) Foreign Standards to get HCI and Usability. Foreign Journal of Human-Computer Research, 55, four. Bevan, And, Bogomolni, My spouse and i, & Ryan, N (2000) Cost-effective customer centred design and style, www.usability.serco.com/trump Bevan, N. & Macleod, M (1994) User friendliness measurement in context. Behavior and Technology, 13, 132-145 Beyer, L. & Holtzblatt, K. (1998), Contextual design: defining customer-centered systems, Morgan Kaufmann Writers. Bruseberg, A. & McDonagh-Philp, D. (2001), New product development by eliciting user experience and goals, International Log of Human-Computer Studies, 55(4), 435-452. Checkland, P. (1981), Systems pondering, systems practice, Wiley. Cooper, A. (1999), The inmates are running the asylum: for what reason high tech items drive us crazy and how to restore the sanity, Sams publishing. Eason, K. M. (1988), Information technology and efficiency change, Taylor and Francis. Ericsson Infocom Consultants STOMACH and Linköping University (2001), The Delta method. www.deltamethod.net/ Hackos, L. & Redish, J. (1998), User and task analysis for interface design, Wiley. Hall, R. R. (2001), Prototyping intended for usability of recent technology, Foreign Journal of Human-Computer Research, 55, four, 485-502. APPLE (2002), EZSort http://www-3.ibm.com/ibm/easy/eou_ext.nsf/Publish/410 INTERNATIONALE ORGANISATION FUR STANDARDISIERUNG (1997), INTERNATIONALE ORGANISATION FUR STANDARDISIERUNG 9241: Ergonomics requirements pertaining to office work with visual screen terminals (VDTs), 17parts, Foreign Standards Organisation. ISO (1999), ISO 13407: Human-centred design and style processes to get interactive devices, International Criteria Organisation.

of sixteen

M. Maguire and D. Bevan

INTERNATIONALE ORGANISATION FUR STANDARDISIERUNG (2002), ISO/IEC 9126-4: Software engineering – software merchandise quality – Part 5: Quality being used Metrics, Intercontinental Standards Enterprise. Kirwan, W. & Ainsworth, L. T. (eds. ) (1992), Strategies for task examination, Taylor and Francis. Macaulay, L. A. (1996), Requirements engineering, Springer Verlag Series on Utilized Computing. Maguire, M. C. (1998), User-centred requirements guide. EC Telematics Applications Program, Project TE 2010 RESPECT (Requirements Architectural and Requirements in Telematics), WP4 Deliverable D4. 2, version a few. 3, May possibly. http:www.lboro.ac.uk/research/husat/respect/rp2.html Maguire, M. C. (1999), NCR Knowledge Laboratory. Report in study with the management of domestic funds by family, 7 May, RSEHF (formerly HUSAT), Loughborough University, Loughborough, UK. Maguire, M. C. & Hirst, S. J. (2001a), User friendliness evaluation in the LINK project TIGS website and feedback on OVC specification. HUSAT Consultancy Limited, 2 03 2001. RSEHF (formerly HUSAT), Loughborough University, Loughborough, UK. Maguire, Meters. C. & Hirst, S i9000. J. (2001b), Metropolitan Authorities Service upgrade of corporate intranet internet pages. HUSAT Agency Limited, dua puluh enam March 2001. RSEHF (formerly HUSAT), Loughborough University, Loughborough, UK. Maguire, M. C. (2001c), Circumstance of use within usability actions, International Record of Human-Computer Studies, 55(4), 453-484. Arranger, R. & Smith, M. (2002), Web usability for dummies, New York: Famished Minds. Nielsen, J. (2000), Designing world wide web usability: The practice of simplicity, New Riders Submitting. Nicolle, C. & Abascal, J. (eds. ) (2001), Inclusive style guidelines for HCI, Taylor swift & Francis. Olphert, C. W. & Damodaran, D. (2002), Having what you want, or perhaps wanting everything you get? - beyond customer centred design and style, Proceedings in the Third Worldwide Conference on Design and Emotion, Loughborough, UK, 1-3 July 2002. Preece, T., Rogers, Sumado a., Sharp, They would., Benyon, D., Holland, H. & Carey, T. (1994), Human-computer connection. Addison-Wesley. Robertson, S. & Roberston, T. (1999), Learning the requirements process, AddisonWesley and ACM Press. Taylor, N. (1990), The HUFIT preparing, analysis and specification toolset, In D. Diaper, G. Cockton, G. Gilmore & B. Shackel, (eds. ), Human-Computer Connection - COMMUNICATE '90, 371-376. Amsterdam: North-Holland.