2006
DOI: 10.1016/j.csi.2005.07.012
|View full text |Cite
|
Sign up to set email alerts
|

An overview of guidance documents for software in metrological applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2008
2008
2023
2023

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 9 publications
(5 citation statements)
references
References 3 publications
0
5
0
Order By: Relevance
“…However, deciphering these requirements can be a difficult and onerous task as the requirements for traceability vary between the documents. The variation between the documents extends to other areas such that "In already developed guidance documents different software quality issues, software lifecycle phases and consequences of risk evaluation for software malfunction or fraud are addressed to different extents" [6]. This paper identifies the references to traceability within each of the relevant medical device standards and guidelines and defines the requirements for traceability during each stage of the software development lifecycle.…”
Section: Introductionmentioning
confidence: 99%
“…However, deciphering these requirements can be a difficult and onerous task as the requirements for traceability vary between the documents. The variation between the documents extends to other areas such that "In already developed guidance documents different software quality issues, software lifecycle phases and consequences of risk evaluation for software malfunction or fraud are addressed to different extents" [6]. This paper identifies the references to traceability within each of the relevant medical device standards and guidelines and defines the requirements for traceability during each stage of the software development lifecycle.…”
Section: Introductionmentioning
confidence: 99%
“…The software is then validated to fulfill the requirement requested by standards [19][20][21][22] . The validation is conducted to verify the functionality by comparing the automatic and manual measurements [23][24][25] .…”
Section: Fig 6: Measurement Panelmentioning
confidence: 99%
“…In [12], approaches to software quality requirements and software testing methods are compared, and different approaches to software quality assessment in different international standards and guidelines, in particular on issues related to the quality assessment of MI software, are determined.…”
Section: Literature Review and Problem Statementmentioning
confidence: 99%
“…However, [11][12][13][14][15] do not provide a comparative analysis of the importance of the impact of specific characteristics of MI software on the overall result of the software quality assessment. The requirements of the international document [2] and the possibility of software application for local MI are not taken into account in [16][17][18].…”
Section: Literature Review and Problem Statementmentioning
confidence: 99%