Skip to main content
Log in

Scenario advisor tool for requirements engineering

  • Original Article
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

This study investigates the usefulness of a scenario advisor tool which was built to help requirements engineers to generate sufficient sets of scenarios in the domain of socio-technical systems. The tool provides traceability between scenario models and requirements and helps to generate new scenarios and scenario variations. Through two series of evaluation sessions, we found that the scenario advisor tool helped users to write more sound scenarios without any domain knowledge, and to generate more variations on existing scenarios by providing specific scenario-generation hints for each scenario component. The tool should improve the reliability of requirements elicitation and validation.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8

Similar content being viewed by others

References

  1. Achour CB, Rolland C, Maiden NAM, Souveyet C (1999) Guiding use case authoring: results of an empirical study. In: Proceedings of IEEE symposium on requirements engineering, IEEE Computer Society Press, pp 36–43

  2. Carroll JM (2000) Making use: scenario-based design of human–computer interactions. MIT Press, Cambridge

    Google Scholar 

  3. Carroll JM (1997) Scenario-based design. In: Helander M, Landauer TK, Prabhu P (eds) Handbook of human–computer interaction, 2nd edn (completely revised). Elsevier, Amsterdam, pp 383–406

    Google Scholar 

  4. Carroll JM (1995) Scenario-based design: envisioning work and technology in system development. Wiley, New York

    Google Scholar 

  5. Carroll JM, Mack RL, Robertson SP, Rosson MB (1994) Binding objects to scenarios of use. Int J Hum Comput Stud 41:243–276

    Article  Google Scholar 

  6. Chance BD, Melhart BE (1999) A taxonomy for scenario use in requirements elicitation and analysis of software systems. In: Proceedings of the IEEE conference and workshop on engineering of computer-based systems, Nashville, pp 232–238

  7. Cowie J, Lehnert W (1996) Information extraction, communications of the ACM, ACM Press, New York, 3(1):80–91

  8. Cunning SJ, Rozenblit JW (1999) Test scenario generation from a structured requirements specification. In: Proceedings of IEEE conference and workshop on engineering of computer-based systems. Nashville, pp 166–172

  9. Dearden A, Harrison M, Wright R (2000) Allocation of function: scenarios, context and the economics of effort. Int J Hum Comput Stud 52:289–318

    Article  Google Scholar 

  10. Egyed A (2001) A scenario-driven approach to traceability. In: Proceedings of the 23rd international conference on software engineering (ICSE), Toronto, pp 123–132

  11. Haumer P, Pohl K, Weidenhaupt K (1998) Requirements elicitation and validation with real world scenes. IEEE Trans Software Eng 24(12):1036–1054

    Article  Google Scholar 

  12. Hertzum M (2003) Making use of scenarios: a field study of conceptual design. Int J Hum Comput Stud 58:215–239

    Article  Google Scholar 

  13. Hollnagel E (1993) Human Reliability Analysis Context and Control. Academic, London

    Google Scholar 

  14. Kaindl H (1997) A practical approach to combining requirements definition and object-oriented analysis. Ann Software Eng 3:319–343

    Article  Google Scholar 

  15. Leite JCSP, Hadad G, Doorn J, Kaplan G (2000) A scenario construction process. Requirements Eng 5:38–61

    Google Scholar 

  16. Mylopoulos J (1998) Information modelling in the time of the revolution. Inf Syst 23:127–155

    Article  Google Scholar 

  17. Potts C (1999) ScenIC: a strategy for inquiry-driven requirements determination. In: IEEE international symposium on requirement engineering, Limerick, pp 58–65

  18. Reason J (2000) Managing the risks of organizational accidents. Aldershot, Ashgate

    Google Scholar 

  19. Reason J (1990) Human Error. Cambridge University Press, London

    Google Scholar 

  20. Rolland C, Arhur CB, Cauvel C, Ralyte J, Sutcliffe AG, Maiden N, Jarke M, Haumer P, Pohl K, Dubois E, Heymans P (1998) A proposal for a scenario classification framework. Requirements Eng 3:23–47

    Google Scholar 

  21. Rolland C, Souveyet C, Achour CB (1998) Guiding goal modeling using scenarios. IEEE Trans Software Eng 24(12):1055–1071

    Article  Google Scholar 

  22. Sutcliffe AG, Shin JE, Gregoriades G (2002) Tool support for scenario-based functional allocation. In: Proceedings of the 21st European annual conference on human decision making and control, University of Glasgow, Scotland

  23. Sutcliffe AG, Maiden NAM, Minocha S, Manuel D (1998) Supporting scenario-based requirements engineering. IEEE Trans Software Eng 24(12):1072–1088

    Article  Google Scholar 

  24. Sutcliffe AG, Ryan M (1998) Experience with SCRAM, a Scenario Requirements Analysis Method. In: International conference on requirement engineering, pp 164–171

  25. Weidenhaupt K, Pohl K, Jarke M, Haumer P (1998) Scenarios in system development: current practice. IEEE Software March/April:34–45

    Article  Google Scholar 

  26. Yu E (1997) Towards modelling and reasoning support for early-phase requirements engineering. In: Proceedings of the 3rd IEEE International symposium on requirements engineering. IEEE Computer Society Press, Los Alamitos, pp 226–235

  27. Zhu H, Jin L (1994) Automating scenario-driven structured requirements engineering. In: Proceedings of the 24th annual international computer software and applications conference (COMPSAC’00). Taipei, pp 311–316

  28. Zhu X, Mainden N, Pavan P (2003) Scenarios: bringing requirements and archetectures together. In: Proceedings of the 2nd international workshop on scenarios and state machines: models, algorithms, and tools (SCESM ’03). ICSE ’03, Portland

Download references

Acknowledgements

This work was funded by the EPSRC Systems Integration Programme SIMP project (Systems Integration for Major Projects).

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Alistair G. Sutcliffe.

Appendices

Appendix A

1.1 Scenario taxonomy tables

Actor area

Component

Definition

Synonym

Property

Activity

Manifestations of behaviour; reported history; collections of action; higher order units

Behaviour (ref. task)

Complexity, physical/cognitive activity

Agent

A human or machine that carries out a task; one that acts or has the power or authority to act; has sub-types of human and machine agents

Actor, Artefact

Human agent: capability, expertise, motivation, aptitude, responsibility, authority, trust

   

Machine agent: reliability, task support, usability, utility

Attribute

Information or data that describes an agent or object

Characteristic, feature, quality, property

N/A

Group

An informal or temporary assembly of agents

Cluster, formation

Capability, motivation, authority, trust

Organisation

The persons (or committees or departments, etc.) who make up a governing body and who work together; it has a leader

Constitution, unit, structure, group

Capability, motivation, authority, trust

Physical structure

Something physical which is made up of a number of parts that are held or put together in a particular way.

Authority, compound, object container

Size

Role

The characteristic and expected social behaviour of an agent

Function, occupation, position

N/A

Intention area

Component

Definition

Synonym

Property

Goal

The purpose toward which an endeavour is directed; future intent

Intention, purpose, aim

Importance, quality

Objective

Something worked toward or striven for; higher order goal

Intention, target

Importance

Plan

A descriptive specification of plans

Strategy, approach

Effectiveness, clarity

Policy

A plan or course of action, as of a government, political party, or business, intended to influence and determine decisions, actions, and other matters; a set of statements used to guide, a principle, or procedure considered expedient, prudent, or advantageous

Principle, mission

Effectiveness, clarity

Task area

Component

Definition

Synonym

Property

Action

The process of acting or doing that results in change in the world; a physical change, as in position, mass, or energy, that an object or a system undergoes; actions are either continuous or discrete; actions have a duration.

Behaviour, activity, procedure

Complexity, duration, physical/cognitive

Event

Something that takes place; events can be contained in a message

Occurrence, happening

N/A

Object

Physical or conceptual thing that exists over time and is either changed by a task or changes other objects. In object-oriented programming, objects include data and the procedures necessary to operate on that data

Entity

Physical/conceptual

Procedure

A set of instructions that performs a specific task; a subroutine or function

Method, course of action, process

N/A

Resource

Something that can be used for support or help; an available supply that can be drawn on when needed; the ability to deal with a difficult or troublesome situation effectively

Means, tools, capability, materials

N/A

State

A type of attribute of an object, an agent, or a task.

Condition

N/A

Task

A piece of work assigned or done as part of one’s duties; a function to be performed; an objective.

Duty, procedure, method

Predictability, complexity, reliability

Environment area

Component

Definition

Synonym

Property

Social environment

Social circumstances surrounding an agent or group of agents

Community, public factors

Management culture, time pressure, stress

Economic environment

Economic circumstances surrounding an agent or group of agents

Cost, financial factors

N/A

Physical environment

Physical circumstances surrounding an agent or group of agents

Tangible context

Weather state (wind, cloud, etc.), climate, noise, interruptions, fatigue, stress

Location

Identifying the position of a plan, an act, or a site, etc.

Place, situation, locality

N/A

Situation

Complex state description of context for activity and background circumstances

Circumstance, state, condition

Logical/physical state, temporary, critical

Time

A non-spatial continuum in which events occur in apparently irreversible succession from the past through the present to the future; an interval of time characterised by properties and the occurrences of certain conditions, events, or phenomena

Period, duration

Time period, time point, scale

Environment

Social, economic, and physical environment

N/A

N/A

Communication area

Component

Definition

Synonym

Property

Argument

A discussion about a topic or design problem, often with positions for and against; a controversial communication.

Opinion, assertion, claim, dispute

N/A

Assumption

Something taken for granted or accepted as true without proof; a hypothesis that is taken for granted.

Hypothesis, supposition

N/A

Attitude

An opinion, a state of mind or a feeling; disposition

Approach, mind-set, posture, belief

N/A

Causation

The act or agency or process of causing, by which an effect is produced

Causality, cause, reason, source

N/A

Consequence

A logical or natural conclusion or a result which follows from an action or condition

Effect, outcome, result

N/A

Constraint

Something that controls decisions, prevents or restricts actions of others

Restriction, limitation, check

N/A

Context

The circumstances and events surrounding or leading up to an event or occurrence

Circumstance, setting

N/A

Decision

A judgment or conclusion on an issue, or making up one’s mind

Conclusion, judgment, assessment, evaluation

N/A

Evidence

A proof or an example helpful in forming a conclusion or judgment

Proof, data, verification

N/A

Interpretation

Explaining the meaning of; making sense of

Decoding, understanding, explanation

N/A

Issue

An important question that is in dispute and must be settled

Subject, topic

N/A

Justification

The act of justifying; a fact or circumstance that shows an action to be reasonable or necessary

Validation, good reason, explanation

N/A

Position

A point of view or attitude on a certain question; social standing or status; a situation as it relates to the surrounding circumstances; it separates viewpoints from alternative arguments

Situation, standpoint, status, purpose

N/A

Solution

The method of answering questions; solves a problem; achieves a goal

Result, explanation

N/A

Viewpoint

A position from which something is observed or considered

Perspective, opinion

N/A

Appendix B

2.1 Scenario schema diagrams

Scheme 1
scheme 1

Actor area

Scheme 2
scheme 2

Intention area

Scheme 3
scheme 3

Task area

Scheme 4
scheme 4

Environment area

Scheme 5
scheme 5

Communication area

Rights and permissions

Reprints and permissions

About this article

Cite this article

Shin, J.E., Sutcliffe, A.G. & Gregoriades, A. Scenario advisor tool for requirements engineering. Requirements Eng 10, 132–145 (2005). https://doi.org/10.1007/s00766-004-0207-3

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-004-0207-3

Keywords

Navigation