2013
DOI: 10.1007/978-3-642-37169-1_24
|View full text |Cite
|
Sign up to set email alerts
|

Software Engineering Practices and Principles to Increase Quality of Scientific Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
10
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
7

Relationship

1
6

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 6 publications
0
10
0
Order By: Relevance
“…The results obtained from the survey [5] confirmed the non-use of formal software engineering practices and as a consequence a number of development teams were not sure whether their software contains bugs or not. The bad development practices are also confirmed by the results from two other surveys [11] [2].…”
Section: Introductionmentioning
confidence: 80%
See 1 more Smart Citation
“…The results obtained from the survey [5] confirmed the non-use of formal software engineering practices and as a consequence a number of development teams were not sure whether their software contains bugs or not. The bad development practices are also confirmed by the results from two other surveys [11] [2].…”
Section: Introductionmentioning
confidence: 80%
“…The motivation for writing this paper comes from the results obtained from the survey conducted among the scientists that are part of the project [5]. The results showed that the majority of the development teams do not perform software release version tracking and only few development teams think that it is an important process.…”
Section: Introductionmentioning
confidence: 99%
“…Each block in the blockchain system contains the data of the previous block and the transaction data with timestamp [5]. Whenever a new transaction is made or a new contract is signed, the relevant information will be re-verified and the block can be successfully established only when all nodes agree to the transaction in the data block, and a single participant cannot change or delete these data in the block [6]. This ensures that all information is credible, transparent, and traceable, and facilitates the supervision and the efficient circulation of supply chain information during the project.…”
Section: Information Is Transparent and Traceable Breaking Informatio...mentioning
confidence: 99%
“…Focus on SE practices might be perceived as bureaucratic and demotivate scientists (Spencer 2015). On the other hand, both SC and SE communities agree that SS quality could be increased by the adoption of SE practices (Mohammad 2010); Heaton and Carver 2015), including well-specified requirements, automated testing, and documentation (Koteska and Mishev 2013). Likewise, it would be advisable for software engineers to gain knowledge on the scientific domain in question (Marinovici, Kirkham and Glass 2014), and on how scientists work and report their progress (Killcoyne and Boyle 2009).…”
Section: How Is Scientific Software Developed and Used?mentioning
confidence: 99%