2015 IEEE 28th Canadian Conference on Electrical and Computer Engineering (CCECE) 2015
DOI: 10.1109/ccece.2015.7129513
|View full text |Cite
|
Sign up to set email alerts
|

A medical computing lab and a model of learning

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
2
0
2

Year Published

2016
2016
2016
2016

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(4 citation statements)
references
References 6 publications
0
2
0
2
Order By: Relevance
“…Recently, a poll indicated that seven out of ten UK researchers consider research without software an impossibility (Hettrick 2014). Moreover, although only a minority uses SS, a vast majority benefits from the advancements it brings (Kelly and Skordaki 2015). Very often, SS is built for the developer himself or groups under ten people-although there is a significant number of projects intended for larger groups (over 100 people), and cases of SS reaching over 5,000 users-mostly the case for open-source or commercial packages (Hannay et al 2009;Nguyen-Hoan, Flint, and Sankaranarayana 2010).…”
Section: How Is Scientific Software Developed and Used?mentioning
confidence: 99%
See 1 more Smart Citation
“…Recently, a poll indicated that seven out of ten UK researchers consider research without software an impossibility (Hettrick 2014). Moreover, although only a minority uses SS, a vast majority benefits from the advancements it brings (Kelly and Skordaki 2015). Very often, SS is built for the developer himself or groups under ten people-although there is a significant number of projects intended for larger groups (over 100 people), and cases of SS reaching over 5,000 users-mostly the case for open-source or commercial packages (Hannay et al 2009;Nguyen-Hoan, Flint, and Sankaranarayana 2010).…”
Section: How Is Scientific Software Developed and Used?mentioning
confidence: 99%
“…Instead of embracing an established methodology, developers might adopt a "loose version(s)" (Basili et al 2008, 35) or a few selected practices (Nanthaamornphong and Carver 2015). Sometimes, developers decide for an "amethodological" approach (Kelly 2015). Methodologies tailored to SS have been outlined a number of times (Platz 1986;Pereira Junior 2007;Ahmed, Zeeshan, and Dandekar 2014), often emphasizing neglected (or difficult) aspects such as requirements, testing, and design (Cort et al 1985).…”
Section: How Is Scientific Software Developed and Used?mentioning
confidence: 99%
“…De fato, ao invés de se adaptarem a uma metodologia pré-estabelecida, desenvolvedores podem adotar apenas algumas práticas selecionadas (Nanthaamornphong & Carver, 2015) ou "adaptações livres" daquelas metodologias (Basili et al, 2008). Em alguns casos, equipes de desenvolvimento optam, em nome da praticidade e eficiência, por uma abordagem "ametodológica" (Kelly, 2015). Por várias vezes, metodologias especializadas, voltadas para o software científico, foram criadas (Cort et al, 1985, Platz, 1986Pereira Júnior, 2007;Ahmed et al, 2014), reforçando aspectos normalmente negligenciados (ou difíceis) como requisitos, teste e design.…”
Section: Aspectos De Cunho Colaborativounclassified
“…Cabe ressaltar a grande diversidade, em tamanho e escopo, daquilo que pode ser considerado software científico: dependendo do contexto, o termo pode descrever um aplicativo completo, um plug-in ou um único arquivo de biblioteca, podendo PUC-Rio -Certificação Digital Nº 1512175/CA ser desenvolvido a partir do zero ou como um módulo para soluções desenvolvidas por terceiros (Frank et al, 2007). Finalmente, além de sua importância para aqueles que, de fato, o utilizam, cabe ressaltar que a vasta maioria das pessoas se beneficia dos avanços resultantes deste tipo de software (Kelly & Skordaki, 2015). O software científico é, geralmente, desenvolvido para as seguintes finalidades: 1pesquisa científica em primeira mão;…”
Section: Introdução Ao Software Científicounclassified