How to Analyse User Requirements for Service-Oriented Environmental Information Systems

Abstract

Environmental Information Systems (EIS) allow the user to store, query and process environmental information and visualize it in thematic maps, diagrams and reports. Although service-orientation is the predominant architectural style of EIS there is no design methodology that brings together the requirements and the expert knowledge of EIS users with the services and information offerings of existing EIS, and, in addition, explicitly obeys the guidelines and constraints of geospatial standards of the Open Geospatial Consortium (OGC) as side-conditions. This paper focuses on the analysis phase as a prelude to service-oriented design. It proposes a way of gathering, describing and documenting user requirements in terms of extended use cases which may then be used to perform the abstract design step following SERVUS which denotes a Design Methodology for Information Systems based upon Geospatial Service-oriented Architectures and the Modelling of Use Cases and Capabilities as Resources.

Agile Service Engineering in the Industrial Internet of Things

“…The SERVUS methodology was successfully used in numerous cooperative and inter-disciplinary software projects related to various application domains of the IIoT such as environmental information systems [4], environmental risk management, and early warning systems [15] as well as industrial production/Industrie 4.0 [12]. As a result of the domain-independent character of the IIoT and its emerging IIoT platforms, it may also be applied to interrelated application domains such as smart cities or smart regions.…”

“…Originally, the SERVUS methodology and the accompanying PEIS were designed for environmental and risk management projects where the IIoT platform comprises the set of available standards and technologies of the geospatial communities [4,15]. With the ongoing digitization of the industrial production due to initiatives such as Industrie 4.0, SERVUS was applied in IIoT platform development projects with industrial partners.…”

Early Warning for Geological Disasters

“…The Enterprise Viewpoint is being described in the requirements analysis step, mostly in terms of semi-structured use case descriptions (Cockburn 2001;Usländer and Batz 2011), whereas the information and service viewpoint specifications result from the abstract design step. The Enterprise Viewpoint is being described in the requirements analysis step, mostly in terms of semi-structured use case descriptions (Cockburn 2001;Usländer and Batz 2011), whereas the information and service viewpoint specifications result from the abstract design step.…”

The Future Internet Enablement of the Environment Information Space

“…The identification of the specific building blocks and enablers for the environment has been guided by an agile service-oriented analysis and design methodology [1,3] of the EIS requirements inherited from existing European initiatives such as Copernicus 2 and INSPIRE 3 , and the more specific requirements of the following pilot applications.…”