08.01.2013 Views

Back Room Front Room 2

Back Room Front Room 2

Back Room Front Room 2

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

these parameters, as well as some ‘extreme’ values<br />

that were less probable but worth investigating<br />

nonetheless. Each scenario was characterised by the<br />

values of all independent variables; the number of<br />

possible scenarios thus depended on the number of<br />

their feasible combinations.<br />

The models were subjected to testing through<br />

simulation sessions, in workshops involving<br />

stakeholders in groups ranging from 5 to as many as<br />

40. In all workshops the models were presented to<br />

project stakeholders together with the corresponding<br />

scenarios and simulated runs.<br />

These features enabled stakeholders to reach a<br />

consensus about the underlying processes and the<br />

implications that each choice would have on overall<br />

system behaviour. The first type of result, i.e. results<br />

concerning specific components of the system,<br />

helped to answer operational questions concerning<br />

the rational allocation of resources and the resulting<br />

service provision capabilities of the system. The<br />

second type of result proved useful for<br />

understanding the overall behaviour of a venue, thus<br />

answering higher-level, management questions<br />

concerning customer presence and distribution,<br />

arrival and departure patterns etc.<br />

3 CONCLUSIONS<br />

In early requirements, when there is a great deal of<br />

vagueness and uncertainty about system goals that<br />

are often set against a background of social,<br />

organizational and political turbulence, the need for<br />

a systematic and systemic way of dealing with all<br />

ENGAGING STAKEHOLDERS IN DEFINING EARLY REQUIREMENTS 41<br />

Figure 3: Simulation results for the ‘Merchandising’ service<br />

co-development aspects seems to be of paramount<br />

importance.<br />

The work presented in this paper is motivated by<br />

the premise that informal and textual descriptions<br />

need to give way to conceptual modelling languages<br />

with clear semantics and intuitive syntax so that an<br />

application can be defined at an appropriate level of<br />

abstraction. This greatly enhance visualisation of<br />

processes that in turn contribute to a more informed<br />

discussion and agreement between stakeholders.<br />

Whilst qualitative-based conceptual modelling<br />

approaches seem to be an improvement on purely<br />

linguistic-based approaches, they fail to bridge the<br />

communication gap between client stakeholders and<br />

analysts. The issue of analyst-client relationship has<br />

been highlighted by many authors (Kennedy, 1994;<br />

Bashein et al., 1997). This type of modelling<br />

paradigm that has evolved from work on Databases,<br />

Software Engineering or Object-oriented Design,<br />

with its analyst orientation paradigms does little to<br />

enhance communication.<br />

The S 3 approach argues that that qualitative<br />

models need to be enhanced with quantitative<br />

capabilities. These capabilities provide opportunities<br />

for the generation and evaluation of alternative<br />

scenarios with respect to stakeholder choices on<br />

their requirements. This way of working supports the<br />

way experts work on ill-structured problem settings<br />

such as planning and design (Carroll, 2002).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!