1985
DOI: 10.1109/tns.1985.4333629
|View full text |Cite
|
Sign up to set email alerts
|

A Development Methodology for Scientific Software

Abstract: This reprm wunprcpurd nann u~wunl ofworkqnwmurcd hy ti,ltigcntyo(lhc llniMSlnlc(kwcrnmenl. N:ither!hc [Jnlt4Sla\cs (k)wrnt,lonl nor my agency Ihcrcof, nor unyofthcir cmployecn, makes any warrnnly, cRprcM or implkd, or qswmcn any Icgnl Iinhilily or rcupmsihihly for Ihc ncturnty, wmplacncm, or usdulmssof uny information, upparulus. prudud, m lrrlwmu rlklcned, or mprcwm Ihni k usc would not lnfrln~privatclyownod riuht~, Rckrcncc herein 10 any n~lfic commcrdnl prrwlucI. promnc, or ,mrwm hy Iradc name, trndcnmrkl m… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
1
0
1

Year Published

1985
1985
2016
2016

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(2 citation statements)
references
References 0 publications
0
1
0
1
Order By: Relevance
“…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). As early as 1986, Platz (1986) observed the need to balance SE measures with creative freedom.…”
Section: How Is Scientific Software Developed and Used?mentioning
confidence: 99%
“…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). As early as 1986, Platz (1986) observed the need to balance SE measures with creative freedom.…”
Section: How Is Scientific Software Developed and Used?mentioning
confidence: 99%
“…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. Já em 1986, Platz observou que problemas e soluções poderiam não ser detectados durante as primeiras fases do projeto, e criou um sistema para gerenciamento de projetos que, enquanto rigidamente PUC-Rio -Certificação Digital Nº 1512175/CA estruturado, era projetado para permitir mudanças de requisitos, reconhecendo a necessidade de equilíbrio entre medidas de engenharia de software e liberdade criativa (Platz, 1986).…”
Section: Aspectos De Cunho Colaborativounclassified