Business application design and enterprise service design: a comparison

Schelp, Joachim; Winter, Robert

doi:10.1504/ijssci.2008.021763

Cited by 12 publications

(8 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…SCHELP and WINTER show that the conceptual design of enterprise services does not differ considerably from traditional application design. However they point out that a well-founded and differentiated design method for enterprise services is still missing [28].…”

Section: Related Workmentioning

confidence: 99%

“…Company C indirectly aims at process flexibility by concentrating on products as a result of business processes. SCHELP and WINTER [28] mention the connection of business-oriented artifacts and IT artifacts as the main objective of service orientation on the integration layer. Thus, enterprise services aim at supporting IT/Business Alignment.…”

Section: Service Oriented Integration Architecturementioning

confidence: 99%

“…Enterprise services can be defined as abstract logical representations of IT functionalities on the integration layer [28]. To enable flexibilisation of functionalities within business processes, enterprise services should encapsulate coarse-grained functionalities [2].…”

Section: Service Oriented Integration Architecturementioning

confidence: 99%

“…Company B also models activity oriented and business object oriented services. According to the traditional application design SCHELP and WINTER [28] distinguish product centered, information centered and function centered enterprise services. In practice the differentiation along contextual factors seems sensible: In company A enterprise services are assigned to application domains so the services are grouped by explicit business contexts.…”

Section: Service Oriented Integration Architecturementioning

confidence: 99%

See 3 more Smart Citations

Towards a Sophisticated Understanding of Service Design for Enterprise Architecture

Aier

Gleichauf

2009

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

Abstract. The service orientation approach emerged form the software engineering community and has now become a widely discussed design paradigm for almost every aspect of an enterprise architecture (EA). However, experience from cases studies has shown that it is necessary to explicitly differentiate service categories in EA, its goals and its resulting design guidelines. This paper derives a sophisticated understanding of different services categories, their respective goals and design guidelines based on empirical research.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Service Oriented Integration Architecturementioning

confidence: 99%

Section: Service Oriented Integration Architecturementioning

confidence: 99%

Section: Service Oriented Integration Architecturementioning

confidence: 99%

See 2 more Smart Citations

Towards a Sophisticated Understanding of Service Design for Enterprise Architecture

Aier

Gleichauf

2009

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

show abstract

“…[27] considers service orientation as an architecture style of its own. The SOA concept aims at providing a stronger alignment of the business process architecture with the underlying IS architecture [67].…”

Section: Service Oriented Architecture and Web Servicesmentioning

confidence: 99%

Service and Document Based Interoperability for European eCustoms Solutions

Vogel

Schmidt

Lemm

et al. 2008

J. theor. appl. electron. commer. res.

View full text Add to dashboard Cite

Innovative eCustoms solutions play an important role in the pan-European eGovernment strategy. The underlying premise is interoperability postulating a common understanding of processes, services and the documents that are exchanged between business and government organizations as well as between governmental authorities of different EU member states. This article provides a stringent approach for deriving documents and services from current eCustoms procedures based on the UN/CEFACT standards framework and for embedding these in a service oriented architecture for Collaborative eGovernment. In doing so, we put a special focus on document engineering by applying the UN/CEFACT Core Component Technical Specification (CCTS), a conceptual framework for modeling document components in a syntax neutral and technology independent manner. By relying on CCTS, we want to tackle the challenge of handling different document configurations imposed by divergent national legislations, different customs procedures (export, import, transit, and excise) and different industries. The resulting conceptual model is transferred to XML schema serving as a basis for Web Services design and implementation. These Web Services are designed for seamless interoperable exchange of electronic customs documents between heterogeneous IS landscapes both on business and government side. Beyond the theoretical deduction practical insights are gained from a European research project implementing the artifacts proposed in a real-world setting.

show abstract

Activity Control in Application Landscapes A Further Approach to Improving Maintainability of Distributed Application Landscapes

Daute

Conrad

2010

Cloud Computing

View full text Add to dashboard Cite

Business application design and enterprise service design: a comparison

Cited by 12 publications

References 0 publications

Towards a Sophisticated Understanding of Service Design for Enterprise Architecture

Towards a Sophisticated Understanding of Service Design for Enterprise Architecture

Service and Document Based Interoperability for European eCustoms Solutions

Activity Control in Application Landscapes A Further Approach to Improving Maintainability of Distributed Application Landscapes

Contact Info

Product

Resources

About