Lessons learned and perspectives on successful HPC software engineering and development

被引:0
|
作者
Shires, DR [1 ]
Henz, BJ [1 ]
机构
[1] USA, Res Lab, High Performance Res Lab, Aberdeen Proving Ground, MD 21005 USA
关键词
high performance computing; software engineering; software quality engineering; parallel computing;
D O I
暂无
中图分类号
TP31 [计算机软件];
学科分类号
081202 ; 0835 ;
摘要
Massively parallel computing platforms have reached the teraflop threshold of computing power, with research groups around the world targeting a time frame of roughly 2010 to field the first production petaflop system. Successful development of software applications for these systems, as well as the current teraflop architectures, depends upon quality software engineering research and methodologies. Software engineering practices that lead to successful project completion and boost productivity need to be understood and addressed If not, the capabilities of current and future computer systems will easily outpace our ability to effectively use them. This paper discusses several "lessons learned" for parallel software development projects in the context of mid- to large-scale scientific computing development efforts. It also addresses issues that must be dealt with to facilitate effective software developments for scaling to even larger systems.
引用
收藏
页码:769 / 775
页数:7
相关论文
共 50 条
  • [1] A software engineering lessons learned repository
    Harrison, W
    27TH ANNUAL NASA GODDARD/IEEE SOFTWARE ENGINEERING WORKSHOP - PROCEEDINGS, 2003, : 139 - 143
  • [2] AN INDUSTRIAL SOFTWARE ENGINEERING RETRAINING COURSE - DEVELOPMENT CONSIDERATIONS AND LESSONS LEARNED
    BENDAVID, A
    BENPORATH, MI
    LOEB, JZ
    RICH, M
    IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 1984, 10 (06) : 748 - 755
  • [3] A REQUIREMENTS ENGINEERING PROCESS MODEL FOR DISTRIBUTED SOFTWARE DEVELOPMENT Lessons Learned
    Lopes, Leandro Teixeira
    Audy, Jorge Luis Nicolas
    ICEIS 2008: PROCEEDINGS OF THE TENTH INTERNATIONAL CONFERENCE ON ENTERPRISE INFORMATION SYSTEMS, VOL ISAS-2: INFORMATION SYSTEMS ANALYSIS AND SPECIFICATION, VOL 2, 2008, : 117 - 122
  • [4] Software engineering masters programs - Lessons learned
    Jovanovic, V
    MacNeil, P
    Matlen, D
    Modesitt, K
    Shoemaker, D
    15TH CONFERENCE ON SOFTWARE ENGINEERING EDUCATION AND TRAINING, PROCEEDINGS, 2002, : 253 - 255
  • [5] Software Engineering Team Project lessons learned
    Hnatkowska, Bogumila
    E-INFORMATICA SOFTWARE ENGINEERING JOURNAL, 2013, 7 (01) : 77 - 85
  • [6] INDUSTRIAL SOFTWARE ENGINEERING RETRAINING COURSE: DEVELOPMENT CONSIDERATIONS AND LESSONS LEARNED.
    Ben-David, Amram
    Ben-Porath, Moshe I.
    Loeb
    Rich, Michael
    IEEE Transactions on Software Engineering, 1984, SE-10 (06) : 748 - 755
  • [7] Teaching global software engineering: experiences and lessons learned
    Niazi, Mahmood
    IET SOFTWARE, 2015, 9 (04) : 95 - 102
  • [8] Lessons Learned Managing Distributed Software Engineering Courses
    Holmes, Reid
    Craig, Michelle
    Reid, Karen
    Stroulia, Eleni
    36TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING (ICSE COMPANION 2014), 2014, : 321 - 324
  • [9] LESSONS LEARNED TEACHING ADA IN THE CONTEXT OF SOFTWARE ENGINEERING
    TOMAYKO, JE
    JOURNAL OF SYSTEMS AND SOFTWARE, 1989, 10 (04) : 281 - 283
  • [10] Applying empirical software engineering to software architecture: challenges and lessons learned
    Davide Falessi
    Muhammad Ali Babar
    Giovanni Cantone
    Philippe Kruchten
    Empirical Software Engineering, 2010, 15 : 250 - 276