Making use of scenarios for validating analysis and design

Dzida, Wolfgang; Freitag, Regine

doi:10.1109/32.738346

Cited by 47 publications

(9 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Verification and validation have been defined in various ways that do not necessarily comply with standard definitions. For instance, journal articles and textbooks use the terms ''verification'' and ''validation'' interchangeably [7,8], or in some cases there is reference to ''verification, validation, and testing (VV&T)'' as if it were a single concept, with no discernible distinction among the three terms [9]. Table 1 shows definitions of verification and validation as provided by international and national bodies.…”

Section: Definitions Of Verification and Validationmentioning

confidence: 98%

Design verification and validation in product lifecycle

2010

View full text Add to dashboard Cite

Section: Definitions Of Verification and Validationmentioning

confidence: 98%

Design verification and validation in product lifecycle

2010

View full text Add to dashboard Cite

“…In many of these approaches, scenarios are used to structure the interaction between users and the system under development (e.g., [20], [21]). However, in the case of information or automation control software, it must be validated that the behavior of the system satisfies process requirements, regardless if these requirements are imposed by technical processes or business processes.…”

Section: Related Workmentioning

confidence: 99%

Early Validation of Automation Plant Control Software using Simulation Based on Assumption Modeling and Validation Use Cases

Brandstetter

Froese

Tenbergen

et al. 2015

CSIMQ

View full text Add to dashboard Cite

Abstract. In automation plants, technical processes must be conducted in a way that products, substances, or services are produced reliably, with sufficient quality and with minimal strain on resources. A key driver in conducting these processes is the automation plant's control software, which controls the technical plant components and thereby affects the physical, chemical, and mechanical processes that take place in automation plants. To this end, the control software of an automation plant must adhere to strict process requirements arising from the technical processes, and from the physical plant design. Currently, the validation of the control software often starts late in the engineering process in many cases -once the automation plant is almost completely constructed. However, as widely acknowledged, the later the control software of the automation plant is validated, the higher the effort for correcting revealed defects is, which can lead to serious budget overruns and project delays. In this article we propose an approach that allows the early validation of automation control software against the technical plant processes and assumptions about the physical plant design by means of simulation. We demonstrate the application of our approach on the example of an actual plant project from the automation industry and present it's technical implementation.

show abstract

“…Social interaction and the physical limitations of ageing were implicit in all the scenarios. The use of scenarios is an accepted and valuable tool [65][66][67] and is superior to self-report [7]. In Rosson and Carroll's [67] categorisation of scenarios, each of the scenarios of this study could be termed an activity scenario, because each describes and suggests a potential use of the mobile phone artefact.…”

Section: Scenariosmentioning

confidence: 99%

Worth-centred mobile phone design for older users

Renaud

Biljon

2010

Univ Access Inf Soc

View full text Add to dashboard Cite

The twenty-first century society fights against an inherent tendency to over-classify and label people. In the case of the aged, despite all efforts, the perception of the helpless, feeble older person still prevails. The truth of the matter is that people over sixty often do not fit this profile. The aged are a heterogeneous group with varying different skills and abilities in many different areas. This paper challenges prevalent mobile phone design decisions that appear to have been made based on the erroneous pre-conception of the incapable elder. Designers currently produce ''senior'' mobile phones that are, at best, inadequate and, at worst, insulting to a sector of society that deserves respect and consideration. Age does indeed influence mobile phone usage, and people over sixty often have specific and special needs, quite apart from agerelated limitations, that predict their use of mobile phones. Most mobile phones designed for older users simply reduce the number of features: the so-called simplification approach. Apart from reducing the effectiveness of the phone, this approach often incorporates the fatal design flaw of using numbers or letters, on speeddial buttons, which requires the user to remember the button-person mappings. In fact, this design rationale reduces the value of the phone to the user. This paper argues that mobile phone design for older users should be worth-centred (Cockton G in Designing worth is worth designing. In: Proceedings of the 4th Nordic conference on human-computer interaction: changing roles. Oslo, Norway, pp [165][166][167][168][169][170][171][172][173][174] 2006) rather than simplificationdriven. The worth-centred approach maximises worth to the user of the phone. This is achieved by maximising effectiveness while accommodating reduced capabilities. To maximise ease of use, and consequent accessibility, features may have to be reduced in an informed way. To facilitate this, a mapping process is proposed whereby user needs are linked to uses of the phone, and then to the features that facilitate these uses. Needs fall into a number of categories, and each category is characterised by a number of different uses, which form a usage space. Features can be linked to one or more usage spaces, and thus be used to support needs. The first step in the conducted research entailed the identification of the needs of the older mobile phone user. Then, it was determined whether these needs were indeed being met by the uses afforded in existing phones. Having concluded that most users' needs were not being met, the next step was to capture data on the needs, limitations and expectations of people over the age of sixty. This was achieved by conducting a series of one-to-one interviews with a number of older mobile phone users and also supervising a participatory design experiment. Using the findings of the analysis, a usage space model is proposed, which serves to align feature inclusion with user needs. Based on this usage space model (the theoretical contribution), a prototype mobil...

show abstract

Making use of scenarios for validating analysis and design

Cited by 47 publications

References 18 publications

Design verification and validation in product lifecycle

Design verification and validation in product lifecycle

Early Validation of Automation Plant Control Software using Simulation Based on Assumption Modeling and Validation Use Cases

Worth-centred mobile phone design for older users

Contact Info

Product

Resources

About