134,362 research outputs found
UML-SOA-Sec and Saleem's MDS Services Composition Framework for Secure Business Process Modelling of Services Oriented Applications
In Service Oriented Architecture (SOA) environment, a software application is a
composition of services, which are scattered across enterprises and architectures.
Security plays a vital role during the design, development and operation of SOA
applications. However, analysis of today's software development approaches reveals
that the engineering of security into the system design is often neglected. Security is
incorporated in an ad-hoc manner or integrated during the applications development
phase or administration phase or out sourced. SOA security is cross-domain and all of
the required information is not available at downstream phases. The post-hoc, low-level
integration of security has a negative impact on the resulting SOA applications. General
purpose modeling languages like Unified Modeling Language (UML) are used for
designing the software system; however, these languages lack the knowledge of the
specific domain and "security" is one of the essential domains. A Domain Specific
Language (DSL), named the "UML-SOA-Sec" is proposed to facilitate the modeling of
security objectives along the business process modeling of SOA applications.
Furthermore, Saleem's MDS (Model Driven Security) services composition framework
is proposed for the development of a secure web service composition
UML-SOA-Sec and Saleemâs MDS Services Composition Framework for Secure Business Process Modelling of Services Oriented Applications
In Service Oriented Architecture (SOA) environment, a software application is a
composition of services, which are scattered across enterprises and architectures.
Security plays a vital role during the design, development and operation of SOA
applications. However, analysis of todayâs software development approaches reveals
that the engineering of security into the system design is often neglected. Security is
incorporated in an ad-hoc manner or integrated during the applications development
phase or administration phase or out sourced. SOA security is cross-domain and all of
the required information is not available at downstream phases. The post-hoc, low-level
integration of security has a negative impact on the resulting SOA applications. General
purpose modeling languages like Unified Modeling Language (UML) are used for
designing the software system; however, these languages lack the knowledge of the
specific domain and âsecurityâ is one of the essential domains. A Domain Specific
Language (DSL), named the âUML-SOA-Secâ is proposed to facilitate the modeling of
security objectives along the business process modeling of SOA applications.
Furthermore, Saleemâs MDS (Model Driven Security) services composition framework
is proposed for the development of a secure web service composition
Non-functional properties in the model-driven development of service-oriented systems
Systems based on the service-oriented architecture (SOA) principles have become an important cornerstone of the development of enterprise-scale software applications. They are characterized by separating functions into distinct software units, called services, which can be published, requested and dynamically combined in the production of business applications. Service-oriented systems (SOSs) promise high flexibility, improved maintainability, and simple re-use of functionality. Achieving these properties requires an understanding not only of the individual artifacts of the system but also their integration. In this context, non-functional aspects play an important role and should be analyzed and modeled as early as possible in the development cycle. In this paper, we discuss modeling of non-functional aspects of service-oriented systems, and the use of these models for analysis and deployment. Our contribution in this paper is threefold. First, we show how services and service compositions may be modeled in UML by using a profile for SOA (UML4SOA) and how non-functional properties of service-oriented systems can be represented using the non-functional extension of UML4SOA (UML4SOA-NFP) and the MARTE profile. This enables modeling of performance, security and reliable messaging. Second, we discuss formal analysis of models which respect this design, in particular we consider performance estimates and reliability analysis using the stochastically timed process algebra PEPA as the underlying analytical engine. Last but not least, our models are the source for the application of deployment mechanisms which comprise model-to-model and model-to-text transformations implemented in the framework VIATRA. All techniques presented in this work are illustrated by a running example from an eUniversity case study
Planning and Design Soa Architecture Blueprint
Service Oriented Architecture (SOA) is a framework for integrating business processes and supporting IT infrastructure as secure, standardized components-services-that can be reused and combined to address changing business priorities. Services are the building blocks of SOA and new applications can be constructed through consuming these services and orchestrating services within a business process. In SOA, services map to the business functions that are identified during business process analysis. Upon a successful implementation of SOA, the enterprise gain benefit by reducing development time, utilizing flexible and responsive application structure, and following dynamic connectivity of application logics between business partners. This paper presents SOA reference architecture blueprint as the building blocks of SOA which is services, service components and flows that together support enterprise business processes and the business goals
Model Based Development of Quality-Aware Software Services
Modelling languages and development frameworks give support for functional and structural description of software architectures. But quality-aware applications require languages which allow expressing QoS as a first-class concept during architecture design and service composition, and to extend existing tools and infrastructures adding support for modelling, evaluating, managing and monitoring QoS aspects. In addition to its functional behaviour and internal structure, the developer of each service must consider the fulfilment of its quality requirements. If the service is flexible, the output quality depends both on input quality and available resources (e.g., amounts of CPU execution time and memory). From the software engineering point of view, modelling of quality-aware requirements and architectures require modelling support for the description of quality concepts, support for the analysis of quality properties (e.g. model checking and consistencies of quality constraints, assembly of quality), tool support for the transition from quality requirements to quality-aware architectures, and from quality-aware architecture to service run-time infrastructures. Quality management in run-time service infrastructures must give support for handling quality concepts dynamically. QoS-aware modeling frameworks and QoS-aware runtime management infrastructures require a common evolution to get their integration
- âŠ