USTM: A New Approach to Requirements Specification

Abstract The problem of inadequate requirements specification is well known. It is argued here that many of the problems stem from an insufficient user orientation on the part of the specifiers. A number of current approaches to requirements specification are reviewed and the need for a methodological approach to requirements capture and specification is discussed. The criteria for the design of a good methodology are deduced from the literature and a novel approach to requirements specification is described: this is the User Skills and Task Match (USTM) methodology. USTM is assessed against other current approaches and the specified criteria. The aim of the USTM methodology is to provide a user-centred approach to requirements specification. Attention is focused on users and their environment at the earliest stage of development in order to facilitate production of software that provides appropriate functionality and that clearly supports users in carrying out their roles at work, i.e. supports the users' cognitive, social and organisational needs. USTM involves generating data about users and their environment and then following a structured procedure in order to derive functional and nonfunctional requirements. The methodology is designed for use by groups of people, typically from marketing, product design, document design and user organisations, who are concerned with the specification of requirements for ‘generic’ systems. A ‘generic’ system is one that is designed to satisfy the needs of many different customers/markets (e.g. a point-of-sale system or personnel system).

[1]  Kathryn L. Heninger Specifying Software Requirements for Complex Systems: New Techniques and Their Application , 2001, IEEE Transactions on Software Engineering.

[2]  Paul A. Booth An Introduction To Human-Computer Interaction , 1989 .

[3]  Pericles Loucopoulos,et al.  Information systems development: a rule-based approach , 1988, Knowl. Based Syst..

[4]  S. Harker,et al.  TASK ANALYSIS AND THE DEFINITION OF USER NEEDS , 1985 .

[5]  Philip J. Barnard,et al.  Rapid prototyping of dialogue for human factors research: the EASIE approach , 1986 .

[6]  George Rzevski On the Comparison of Design Methodologies , 1983, CRIS.

[7]  P. Zave,et al.  Specifying software requirements , 1980, Proceedings of the IEEE.

[8]  Ray Waddington,et al.  Task-Related Knowledge Structures: Analysis, Modelling and Application , 1988, BCS HCI.

[9]  Bruce Christie,et al.  Human Factors of Information Technology in the Office , 1985 .

[10]  Ken Eason,et al.  A USER CENTRED APPROACH TO THE DESIGN OF A KNOWLEDGE BASED SYSTEM , 1987 .

[11]  Brian Wilson,et al.  Systems: Concepts, Methodologies, and Applications , 1990 .

[12]  Dzenan Ridjanovic,et al.  On a Framework for Information Systems Design Methodologies , 1983, CRIS.

[13]  Linda A. Macaulay,et al.  Overcoming Obstacles to the Validation of User Requirement Specifications , 1988, BCS HCI.

[14]  Pericles Loucopoulos,et al.  Knowledge-based approach to requirements engineering using method and domain knowledge , 1988, Knowl. Based Syst..

[15]  Trevor Wood-Harper,et al.  A Taxonomy of Current Approaches to Systems Analysis , 1982, Comput. J..

[16]  D. Benyon,et al.  Towards a Tool Kit for the Systems Analyst , 1987, Comput. J..

[17]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[18]  Paul J. Layzell,et al.  Assisting the Analyst - The aims and objectives of the Analyst Assist project , 1986 .

[19]  Bernard H. Boar Application prototyping: a requirements definition strategy for the 80s , 1984 .

[20]  Robert W. Bailey,et al.  Human Error in Computer Systems , 1983 .

[21]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[22]  John F. Sowa,et al.  Conceptual Structures: Information Processing in Mind and Machine , 1983 .

[23]  Nick Donnelly,et al.  Describing a Product Opportunity: A Method of Understanding the User's Environment , 1987, BCS HCI.

[24]  I. Brandt,et al.  A Comparative Study of Information Systems Design Methodologies , 1983, CRIS.

[25]  Linda A. Macaulay,et al.  Human factors in the IT specification process , 1986 .

[26]  Ken Eason,et al.  Information technology and organisational change , 1988 .

[27]  Robert W. Bailey,et al.  Human performance engineering: A guide for system designers , 1982 .

[28]  Thomas E. Cheatham,et al.  Software Technology in the 1990's: Using a New Paradigm , 1983, Computer.