Tracing the Scenarios in Scenario-Based Product Design: a study to support scenario generation

Scenario-based design originates from the human-computer interaction and\ud software engineering disciplines, and continues to be adapted for product development. Product development differs from software development in the former’s more varied context of use, broader characteristics of users and more tangible solutions. The possible use of scenarios in product design is therefore broader and more challenging. Existing design methods that involve scenarios can be employed in many different stages of the product design process. However, there is no proficient overview that discusses a\ud scenario-based product design process in its full extent. The purposes of creating scenarios and the evolution of scenarios from their original design data are often not obvious, although the results from using scenarios are clearly visible. Therefore, this paper proposes to classify possible scenario uses with their purpose, characteristics and supporting design methods. The classification makes explicit different types of scenarios and their relation to one another. Furthermore, novel scenario uses can be referred or added to the classification to develop it in parallel with the scenario-based design\ud practice. Eventually, a scenario-based product design process could take inspiration for creating scenarios from the classification because it provides detailed characteristics of the scenario

Translating Business Process Models to Class Diagrams

Choreography of business processes can track messages between different services. At the time of writing, there are no guidelines t o d raw a U ML C lass D iagram f rom t he Business Process Choreography. This paper reports an experiment using a set of guidelines. Objective: Evaluate the subjects’ performance and perceptions when applying the BPc2Class-guidelines and BPc2Class-discovery process. Method: To measure the performance and user perception of both ways of mapping the processes, a comparative experiment was conducted with 38 subjects. The subjects, being master students, solved a process case in the first session and a guidelines case in the second session. A survey was filled in by the subjects to measure the user perception variables. Results: The results indicated that the guidelines showed significantly better results in five out of the six measured variables. Conclusion: Based on the findings and limitations of this research the use of guidelines looks promising, but future research is necessary to further generalize the conclusion

A Contigency Model for Requirements Development

Drawing upon the requirements and software development literature, the present study proposes an integrative contingency model for requirements development. Based on 116 quality journal articles, we analyze requirements development risks, requirements development techniques, and heuristics for how they are effectively related. Subsequently, we synthesize the insights from the identified literature into a model for requirements development that relates patterns of risk resolution to archetypical risk profiles. The model integrates the literature on requirements and software development; sets the scene for future research; and, finally, proposes how practitioners can manage risks in requirements development projects

The Influence of Analyst Communication in IS Projects

Information system (IS) researchers have long noted that IS analysts need to understand users’ needs if they are to design better systems and improve project outcomes. While researchers agree that analyst communication activities are an important prerequisite for such an understanding, little is known about the nature of different communication behaviors IS analysts can undertake to learn about users’ system needs and the impact of such behaviors on IS projects. To address this gap, this paper draws from the learning literature to articulate the information transmission activities IS analysts can undertake and the content of the information they can transmit when learning about users’ organizational tasks and information needs. The influence of analyst communication activities on the generation of valid information regarding user needs, analyst learning, and IS project outcomes are then investigated via a case study of two IS projects. The analysis of the two cases suggests that analysts who encourage the use of concrete examples, testing, and validation, and who solicit feedback about users’ business processes are likely to better understand users’ tasks, and in turn design systems that better meet users’ task needs than analysts who do not

Scenario advisor tool for requirements engineering

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