SUDPLAN Scenario Management System Requirements Specification V2
Creators: name: Dihé, Pascal
Publisher: name: Zenodo
Year: 2011
Subjects: requirements engineering
scenario management
climate change
urban development
FP7
SUDPLAN
decision support system
user-centred design
requirements specification

description: This document has been produced by the consortium of the European Project FP7-247708 Sustainable Urban Development Planner for Climate Change Adaptation (SUDPLAN). It is the second deliverable of Task 3.1 - Requirements Specification, and contains the updated requirements of the second requirements analysis phase and is considered to be the final and stable version of the SUDPLAN requirements. The purpose of this document is to establish the requirements of the Scenario Management System of SUDPLAN, sometimes referred to herein as the SUDPLAN platform. In order to understand the high level requirements of SUDPLAN, one must first understand SUDPLAN as a fundamentally interactive system. The entire purpose of the system is to support human decision makers. While this point might seem obvious and not worth mentioning, it is important to understand that many (if not most) decision support systems fail because they fail to focus on the humans who are part of the system. In SUDPLAN we are determined not to make this mistake. We have focused on the human users of the system as the most important source of information – a perspective described in the literature as user-centred design. The requirements described in the present document derive in great part from a thoughtful and systematic process by which the needs of the users were elicited and transformed into requirements. While some requirements come from other sources, none are more important than those of the users, who are understood to be integral elements of the system. For the system to succeed, the users must succeed. For this reason, SUDPLAN is a user-driven system, and its requirements, as elaborated in the present document, are intimately connected with the anticipated users of its applications.
description: {"references": ["Buschmann, F. and Henney, K., Five Considerations for Software Architecture, Part 1, IEEE Software, 2010.", "Diaper, D., The Handbook of Task Analysis for Human-Computer Interaction, Lawrence Erlbaum Assoc Inc., 2003.", "Frysinger, S. P., Integrative Environmental Modeling. In Keith C. Clarke, Brad E. Parks and Michael P. Crane (Eds), Geographic Information Systems and Environmental Modeling, Prentice Hall, 2002.", "Hackos, J. T. and Redish, J. C. (1998). User and Task Analysis for Interface Design. Wiley, 1998.", "ORCHESTRA, Reference Model for the ORCHESTRA Architecture (including Annex A2: Requirements for the ORCHESTRA Architecture and ORCHESTRA Service Networks). Open Geospatial Consortium Inc., 2007.", "Preece, Rogers, and Sharp, Interaction Design: Beyond Human-Computer Interaction (2nd Edition), Wiley, 2007.", "Schlobinski, S., Denzer, R., Frysinger, S., G\u00fcttler, R., Hell, T., Vision and Requirements of Scenario-driven Environmental Decision Support Systems Supporting Automation for End Users, International Symposium on Environmental Software Systems, 2011.", "Sundar, S. S. and Marathe, S. S., Personalization versus Customization: The Importance of Agency, Privacy, and Power Usage. Human Communication Research, 2010.", "Valsala, Vinu and Shamil Maksyutov, Design and Validation of an Offline Oceanic Tracer Transport Model for a Carbon Cycle Study. Journal of Climate, American Meterological Society, 2008."]}