Skip to content

Commit 26cf768

Browse files
mariojmdavidmariojmdavid
committed
wip on references
1 parent 76c491d commit 26cf768

File tree

6 files changed

+13
-109
lines changed

6 files changed

+13
-109
lines changed

‎README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ functional suitability..
1919

2020
The Common Service Quality Assurance Baseline Criteria
2121
_establishes the minimum viable set of quality requirements_ provides an initial
22-
approach to service quality assessment, meant to be applied in the integration
22+
approach to Service Quality Assurance, meant to be applied in the integration
2323
process of the services existing under the EOSC-Synergy project, which eventually
2424
will be accessible as part of the EOSC offerings. In
2525
order to discern among them, the [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt)

‎content/03.intro.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ research infrastructures, including the underlying e-Infrastructures. Consequent
88
the ultimate success of the EOSC heavily relies on the quality aspects of those
99
services, such as their stability or functional suitability.
1010

11-
The meaning of **service** can be regarded from different perspectives.
12-
From an IT Service Management (ITSM) standpoint, such as the EOSC SMS process
13-
model, a service is devised as a means to "provide value to the customer".
14-
The same goal is shared by the DevOps paradigm, but in this case there is
15-
a more pragmatic vision the customer satisfaction is achieved through the
16-
continuous delivery of quality-assured services, with a shorter life cycle,
17-
as the final outcome of a comprehensive software development process.
11+
The meaning of **Service** can be regarded from different perspectives.
12+
From an IT Service Management (ITSM) standpoint, such as the EOSC Service Management
13+
System (SMS) process model, a service is devised as a means to "provide value
14+
to the customer". The same goal is shared by the DevOps paradigm, but in this
15+
case there is a more pragmatic vision the customer satisfaction is achieved
16+
through the continuous delivery of quality-assured services, with a shorter
17+
life cycle, as the final outcome of a comprehensive software development process.
1818

1919
The ITSM model has a broader focus. A service is an "intangible asset" that
2020
also includes additional activities such as customer engagement and support.
@@ -26,7 +26,7 @@ components in operation.
2626

2727
## Purpose
2828

29-
This document provides an initial approach to service quality assessment,
29+
This document provides an initial approach to Service Quality Assurance,
3030
meant to be applied in the integration process of the services existing
3131
under the EOSC-Synergy project, which eventually will be accessible as part
3232
of the EOSC offerings.

‎content/04.goals.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
The herein proposed baseline harnesses the capabilities of the quality factors
44
in the underlying software to lay out the principles for attaining quality in
5-
the enabled services within the EOSC context. According to this view, software
5+
the enabled services within the EOSC context. According to this view, service
66
quality is the foundation to shape user-centric, reliable and fit-for-purpose
77
services.
88

@@ -19,6 +19,7 @@ realization of the verification and validation processes.
1919
* Ensure the functional suitability of the service by promoting testing
2020
techniques that check the compliance of the user requirements.
2121

22-
* Improve the usability by identifying the set of criteria that fosters the service adoption.
22+
* Improve the usability by identifying the set of criteria that fosters the
23+
service adoption.
2324

2425
* Promote the automated validation of the service quality criteria.

‎content/05.notational_conventions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
44
“SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be
5-
interpreted as described in RFC 2119 @url:https://www.ietf.org/rfc/rfc2119.txt.
5+
interpreted as described in RFC 2119 [@url:https://www.ietf.org/rfc/rfc2119.txt].

‎content/90.back-matter.md

Lines changed: 0 additions & 4 deletions
This file was deleted.

‎content/manual-references.json

Lines changed: 0 additions & 93 deletions
Original file line numberDiff line numberDiff line change
@@ -6,98 +6,5 @@
66
"title": "Key words for use in RFCs to Indicate Requirement Levels",
77
"issued": {"date-parts": [[1997]]},
88
"author": [{"given": "Scott", "family": "Bradner"}]
9-
},
10-
{
11-
"type": "webpage",
12-
"standard_citation": "url:https://opensource.org/osd",
13-
"URL": "https://opensource.org/osd",
14-
"title": "The Open Source Definition, URL: https://opensource.org/osd",
15-
"author": [{"literal": "Open Source Initiative"}]
16-
},
17-
{
18-
"type": "webpage",
19-
"standard_citation": "url:https://opensource.org/licenses",
20-
"URL": "https://opensource.org/licenses",
21-
"title": "Licenses & Standards, URL: https://opensource.org/licenses",
22-
"author": [{"literal": "Open Source Initiative"}]
23-
},
24-
{
25-
"type": "webpage",
26-
"standard_citation": "url:https://semver.org",
27-
"URL": "https://semver.org",
28-
"title": "Semantic Versioning 2.0.0, URL: https://semver.org",
29-
"author": [{"given": "Tom", "family": "Preston-Werner"}]
30-
},
31-
{
32-
"type": "webpage",
33-
"standard_citation": "url:https://www.owasp.org/images/0/08/OWASP_SCP_Quick_Reference_Guide_v2.pdf",
34-
"URL": "https://www.owasp.org/images/0/08/OWASP_SCP_Quick_Reference_Guide_v2.pdf",
35-
"title": "OWASP Secure Coding Practices, Quick Reference Guide, URL: https://www.owasp.org/images/0/08/OWASP_SCP_Quick_Reference_Guide_v2.pdf",
36-
"issued": {"date-parts": [[2010]]},
37-
"author": [{"literal": "The OWASP Foundation"}]
38-
},
39-
{
40-
"type": "webpage",
41-
"standard_citation": "url:https://www.owasp.org/index.php/Source_Code_Analysis_Tools",
42-
"URL": "https://www.owasp.org/index.php/Source_Code_Analysis_Tools",
43-
"title": "Source Code Analysis Tools, URL: https://www.owasp.org/index.php/Source_Code_Analysis_Tools",
44-
"issued": {"date-parts": [[2008]]},
45-
"author": [{"literal": "The OWASP Foundation"}]
46-
},
47-
{
48-
"type": "webpage",
49-
"standard_citation": "url:https://www.owasp.org/index.php/Category:Vulnerability_Scanning_Tools",
50-
"URL": "https://www.owasp.org/index.php/Category:Vulnerability_Scanning_Tools",
51-
"title": "Dynamic Application Security Testing, URL: https://www.owasp.org/index.php/Category:Vulnerability_Scanning_Tools",
52-
"issued": {"date-parts": [[2008]]},
53-
"author": [{"literal": "The OWASP Foundation"}]
54-
},
55-
{
56-
"type": "webpage",
57-
"standard_citation": "url:https://www.owasp.org/images/2/2e/OWASP_Code_Review_Guide-V1_1.pdf",
58-
"URL": "https://www.owasp.org/images/2/2e/OWASP_Code_Review_Guide-V1_1.pdf",
59-
"title": "OWASP Code Review Guide, URL: https://www.owasp.org/images/2/2e/OWASP_Code_Review_Guide-V1_1.pdf",
60-
"issued": {"date-parts": [[2008]]},
61-
"author": [{"literal": "The OWASP Foundation"}]},
62-
{
63-
"type":"article-journal",
64-
"publisher":"PeerJ",
65-
"DOI":"10.7717/peerj-cs.86",
66-
"page":"e86",
67-
"source":"Crossref",
68-
"title":"Software citation principles",
69-
"volume":2,
70-
"author":[
71-
{
72-
"ORCID":"http://orcid.org/0000-0002-3957-2474",
73-
"authenticated-orcid":true,
74-
"given":"Arfon M.",
75-
"family":"Smith",
76-
"sequence":"first",
77-
"affiliation":[{"name":"GitHub, Inc., San Francisco, California, United States"}]
78-
},
79-
{
80-
"ORCID":"http://orcid.org/0000-0001-5934-7525",
81-
"authenticated-orcid":true,
82-
"given":"Daniel S.",
83-
"family":"Katz",
84-
"sequence":"additional",
85-
"affiliation":[{"name":"National Center for Supercomputing Applications & Electrical and Computer Engineering Department & School of Information Sciences, University of Illinois at Urbana-Champaign, Urbana, Illinois, United States"}]
86-
},
87-
{
88-
"ORCID":"http://orcid.org/0000-0003-4425-7097",
89-
"authenticated-orcid":true,
90-
"given":"Kyle E.",
91-
"family":"Niemeyer",
92-
"sequence":"additional",
93-
"affiliation":[{"name": "School of Mechanical, Industrial, and Manufacturing Engineering, Oregon State University, Corvallis, Oregon, United States"}]}
94-
],
95-
"container-title":"PeerJ Computer Science",
96-
"language":"en",
97-
"issued":{"date-parts":[[2016,9,19]]},
98-
"standard_citation":"url:http://dx.doi.org/10.7717/peerj-cs.86",
99-
"URL":"http://dx.doi.org/10.7717/peerj-cs.86",
100-
"ISSN":"2376-5992",
101-
"id":"temp_id_7660989779236345"
1029
}
10310
]

0 commit comments

Comments
 (0)