2008
DOI: 10.1007/s10796-008-9143-y
|View full text |Cite
|
Sign up to set email alerts
|

Method of design and specification of web services based on quality system documentation

Abstract: In this paper, we present a method for development and specification of web services based on the quality system documentation. The general assumption is that service oriented architecture is based on business services and these business services mostly correspond to exchanged documentation in a real business system. Documentation of a quality system is recognized in form of documents that describe business processes in a real business system and identify exchanged documentation with environment. Presented met… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
3
0

Year Published

2012
2012
2023
2023

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 5 publications
0
3
0
Order By: Relevance
“…For instance Syntax based service descriptions work nicely only if specification documents are available to explain the details of the capabilities of the service as well as the conditions necessary for using the service [22]. But if such specification document is not available, verbose service description methods ( [19]) come in to play. Syntax based and semantic based service description methods can be combined to provide rich service description approaches [20].…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…For instance Syntax based service descriptions work nicely only if specification documents are available to explain the details of the capabilities of the service as well as the conditions necessary for using the service [22]. But if such specification document is not available, verbose service description methods ( [19]) come in to play. Syntax based and semantic based service description methods can be combined to provide rich service description approaches [20].…”
Section: Discussionmentioning
confidence: 99%
“…Table 2 shows the major problems discovered in the literature study. [4], [9], [14], [18][19][20][21][22][23][24][25][26] Gap between business oriented and IT oriented Service Realizations. [7], [16], [17], [27] Lack of dynamic adaptability and situation awareness [9], [14], [23], [28] Producer only centric approaches [29], [31] Imprecise Requirements Specification…”
Section: Rq2: Problem Faced In Describing Servicesmentioning
confidence: 99%
See 1 more Smart Citation
“…QDMS as a prototype platform and catalyst for the ED paradigm. Application services, available from providers, map business services in a process-modeled business environment, which is described in detail by the QMS documentation [14]. In order for the mapping to be effective, it is necessary for the documentation to faithfully reflect the business system and all its changes, as well as for it to have a mechanism for prototypical testing of changes through the records of the documentation system.…”
Section: Development Of a Quality Model For The Evaluation Of Innovat...mentioning
confidence: 99%