Pattern-Based context establishment for service-oriented architectures

Authors:
Kristian Beckers;Stephan Faßbender;Maritta Heisel;Rene Meis
Affiliations:
paluno - The Ruhr Institute for Software Technology, University of Duisburg-Essen, Germany;paluno - The Ruhr Institute for Software Technology, University of Duisburg-Essen, Germany;paluno - The Ruhr Institute for Software Technology, University of Duisburg-Essen, Germany;paluno - The Ruhr Institute for Software Technology, University of Duisburg-Essen, Germany
Venue:
Software Service and Application Engineering
Year:
2012

Citing 7
Cited 0

GRAIL/KAOS: an environment for goal-driven requirements engineering

ICSE '97 Proceedings of the 19th international conference on Software engineering
Problem frames: analyzing and structuring software development problems

Problem frames: analyzing and structuring software development problems
The Security Development Lifecycle

The Security Development Lifecycle
A BPMN Extension for the Modeling of Security Requirements in Business Processes

IEICE - Transactions on Information and Systems
On the Secure Software Development Process: CLASP and SDL Compared

SESS '07 Proceedings of the Third International Workshop on Software Engineering for Secure Systems
SOMA: a method for developing service-oriented solutions

IBM Systems Journal
A pattern-based method for identifying and analyzing laws

REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality

Quantified Score

Hi-index	0.00

Visualization

Abstract

A context description of a software system and its environment is essential for any given software engineering process. Requirements define statements about the environment (according to Jackson's terminology). The context description of a Service-Oriented Architecture is difficult to provide, because of the variety of technical systems and stakeholders involved. We present two patterns for SOA systems and support their instantiation with a structured method. In addition, we show how the pattern can be used in a secure service development life-cycle.