Towards a Design Method Supporting the Alignment between Business and Software Services

Ramel, Sophie; Grandry, Eric; Dubois, Éric

doi:10.1109/compsac.2009.53

Cited by 8 publications

(5 citation statements)

References 15 publications

(14 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As in this view we do not take technical details into consideration, this leads to a business-driven composition of services ( [32]). For simplicity reasons, because these models should be readable by business experts, we have chosen to use an UML activity diagram to model this choreography, in a way similar to [11]. The activity diagram presents the different roles concerned by the service into swim-lanes: the service consumer, the service provider, and the other actors involved.…”

Section: From the Requirements To The Business Service System Solutionmentioning

confidence: 99%

“…Considering such systems require adaptations of the initial Efficient methodology to move from a message (information exchange) paradigm to a service based paradigm, services being also considered both from technical and business perspectives. Preliminary results regarding the technical perspective have been reported in [11]. In this chapter we focus on the handling of the business perspective.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Capturing and Aligning Assurance Requirements for Business Services Systems

Dubois¹,

Kubicki²,

Ramel³

et al. 2012

Business System Management and Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. In this chapter we introduce and illustrate a systematic and rigorous approach for the elicitation and the modelling of assurance requirements inherent to business services offered by a service system. The approach is based on guidelines provided by the ISO 15504 norm, which is applicable for the assessment of any type of process in order to check its compliance against assurance requirements. We explain how 15504 can be applied in the context of business services with the support provided by goal-oriented requirements engineering techniques like i*. Its use is illustrated through the handling of an excerpt of a real case from the construction sector complemented with expertise developed in IT service level management. While this chapter is focusing on the capture of business requirements and their transformation into a business oriented solution, we also briefly explain how this business view is part of a more complete methodology also encompassing the service value and the service software views associated with a service system.

show abstract

Section: From the Requirements To The Business Service System Solutionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Capturing and Aligning Assurance Requirements for Business Services Systems

Dubois¹,

Kubicki²,

Ramel³

et al. 2012

Business System Management and Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…For this purpose, they map their business motivation model (BMM) to SoaML. (iii) Ramel et al [52] follow an approach based on requirements of business and software services. Indeed, they identify the business requirements using the goal-oriented modeling notation i * and define them by using the UML activity and class diagrams.…”

Section: Research Question 3: Alignment Between Business Requirement Andmentioning

confidence: 99%

Alignment between Business Requirement, Business Process, and Software System: A Systematic Literature Review

Habba

Fredj

Chaouni

2019

Journal of Engineering

View full text Add to dashboard Cite

Alignment is a very wide subject that can be used to support an organization’s information system. Many authors have dealt with this topic according to various dimensions, including the operational alignment dimension. Our work aims to review approaches that discuss the operational alignment by reducing the gap between business requirement, business process, and software system. Therefore, this study was conducted by a systematic literature review (SLR). In the first step, we gather 1846 papers relative to the subject. In the last step, we filter those articles and select only the most pertinent ones, which leave us with 63 studies to focus on. These primary studies were analyzed according to 9 quality assessment criteria.

show abstract

“…In relation to our approach, there are some prominent approaches for defining the cloud value chain reference model [7], like an i * 8 , a goal-oriented social modeling framework for linking business models to their supporting services and process models by Jaap et al [8] and Ramel et al [9]. In their approach, first, the business requirements are modeled with the i * notation and then business services are derived.…”

Section: Related Workmentioning

confidence: 99%

“…CREAM captures the system requirements and their relationships, then builds the cloud application topology in TOSCA. The CREAM is a Javabased web application which is developed in WSO2 Developer Studio 9 . We used Maven to resolve its dependencies and deployed CREAM on WSO2 Application Server.…”

Section: Implementation: Cream Tool Supportmentioning

confidence: 99%

Cloud Resources-Events-Agents Model: Towards TOSCA-Based Applications

Qanbari

Sebto

Dustdar

2014

Advanced Information Systems Engineering

View full text Add to dashboard Cite

International audienceThe dilemma for domain experts and developers during design time of a cloud application is ensuring the sufficient programming abstractions between them in mapping the business requirements to cloud specifications. Thus, a modeling language is needed to capture and express the business requirements. Resources-Events-Agents (REA) is a well-known business requirement modeling language that decomposes the information system into three constituents with the set of compliant binary collaborations called, Duality. This study is a preliminary attempt to employ REA for developing cloud applications. In this study, we define a conceptual mapping between REA model and OASIS Topology and Orchestration Specification for cloud Applications (TOSCA) policies, plans and templates. Based on that, we proceed with the process of building business-driven cloud applications. In support of our model, we implement a cloud REA Modeling tool referred to as CREAM, where business requirements are specified in REA, then corresponding cloud application is composed and built. We describe the underlying mapping strategy as well as the details of our tool in support of the proposed approach

show abstract

Towards a Design Method Supporting the Alignment between Business and Software Services

Cited by 8 publications

References 15 publications

Capturing and Aligning Assurance Requirements for Business Services Systems

Capturing and Aligning Assurance Requirements for Business Services Systems

Alignment between Business Requirement, Business Process, and Software System: A Systematic Literature Review

Cloud Resources-Events-Agents Model: Towards TOSCA-Based Applications

Contact Info

Product

Resources

About