Decomposition of SQuaRE – Based Requirements for the Needs of SOA Applications

Abramowicz, Witold; Haniewicz, Konstanty; Hofman, Radosław; Kaczmarek, Monika; Zyskowski, Dominik

doi:10.1007/978-1-4020-9532-0_7

Cited by 4 publications

(8 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Reliability [50], [196], [43], [34], [172], [45], [60], [81], [163], [1], [51], [204], [93], [178]. Usability [8], [179], [1], [51], [93].…”

Section: Dimension Referencesmentioning

confidence: 99%

“…Evolutionary Techniques [74], [110], [29], [100], [39], [54], [207], [31], [56], [87], [30], [211], [1], [191]. Petri Nets [36], [201], [212], [140].…”

Section: Dimension Referencesmentioning

confidence: 99%

“…SOC [198], [105], [47], [36], [131], [39], [145], [38], [197], [58], [142], [183], [91], [10], [4], [215], [120], [19], [21], [31], [45], [189], [212], [158], [1], [174], [164], [188], [191].…”

Section: Dimension Referencesunclassified

See 2 more Smart Citations

Designing service-based applications in the presence of non-functional properties: A mapping study

Neto

Vargas-Solar²,

Costa

et al. 2016

Information and Software Technology

View full text Add to dashboard Cite

“…Reliability [50], [196], [43], [34], [172], [45], [60], [81], [163], [1], [51], [204], [93], [178]. Usability [8], [179], [1], [51], [93].…”

Section: Dimension Referencesmentioning

confidence: 99%

“…Evolutionary Techniques [74], [110], [29], [100], [39], [54], [207], [31], [56], [87], [30], [211], [1], [191]. Petri Nets [36], [201], [212], [140].…”

Section: Dimension Referencesmentioning

confidence: 99%

See 1 more Smart Citation

Designing service-based applications in the presence of non-functional properties: A mapping study

Neto

Vargas-Solar²,

Costa

et al. 2016

Information and Software Technology

View full text Add to dashboard Cite

“…The differences between BLA and SLA are illustrated by Salles et al [28] who exemplify a BLA goal with "the business subprocess starting in the activity [1] and ending in the activity [4] must be concluded within 24 h" whereas the corresponding SLAs goals are exemplified with "the web service invoked to execute the activity [1] must be completed within 2 h" and "the web service invoked to execute the activity [4] must have 95% of availability".…”

Section: Non-functional Requirementsmentioning

confidence: 99%

“…To the best of our knowledge, there is no general standard accepted as a quality model for web services being orchestrated to automate business processes. However, web services and software modules share the same set of properties; therefore, if software components can be replaced by web services, then the quality requirements of both solutions must be compatible with [1]. As a result, software quality models can also be used to address quality characteristics of web services.…”

Section: Software Quality Modelsmentioning

confidence: 99%

Systematizing the Relationship Between Business Processes’ and Web Services’ Non-functional Requirements

CastroJr.

Fantinato

Aksu

et al. 2020

Enterprise Information Systems

View full text Add to dashboard Cite

We propose in this paper a conceptual framework for the hierarchical decomposition of Non-Functional Requirements (NFRs) from the business process level to the web service level. This framework seeks to reduce the dependence on a particular IT expert's knowledge by simplifying the dialog between the business and IT areas. The proposed framework relies on a structure of NFRs interdependence. The main reference was the ISO/IEC 25010 Product Quality Model, extended by additional software quality models and particular QoS attributes. This framework is accompanied by an extensive dictionary of non-functional requirements for both business processes and web services that can serve as a reference for researchers and industry practitioners. We assume that orchestrating web services to run business processes requires a rigorous definition of the functional requirements and NFRs of these web services. Web service NFRs are often defined as Quality of Service (QoS) attributes, which is done at the implementation level by IT teams. The definition of QoS attributes should consider the business process NFRs, since misinterpretations of web service NFRs may affect the behavior of the web services and hence achieving the business goals. The approaches proposed so far in the literature are still heavily dependent on an IT expert's knowledge to identify the appropriate QoS attributes required to meet particular business process NFRs. However, defining appropriate QoS attributes without reference to business process-level NFRs may be a costly, time-consuming task.

show abstract

Web Services Trustworthiness Model

Hofman¹,

Bassara²

2011

Towards a Service-Based Internet

View full text Add to dashboard Cite

Decomposition of SQuaRE – Based Requirements for the Needs of SOA Applications

Cited by 4 publications

References 5 publications

Designing service-based applications in the presence of non-functional properties: A mapping study

Designing service-based applications in the presence of non-functional properties: A mapping study

Systematizing the Relationship Between Business Processes’ and Web Services’ Non-functional Requirements

Web Services Trustworthiness Model

Contact Info

Product

Resources

About