Software project management and quality engineering practices for complex, coupled multiphysics, massively parallel computational simulations: Lessons learned from asci

The International Journal of High Performance Computing Applications

Volumn 18, Issue 4, 2004, Pages 399-416

  Post, D E ^a   Kendall, R P ^a  

^a LOS ALAMOS NATIONAL LABORATORY   (United States)

Author keywords

computational science; management; Software engineering; software project; validation; verification

Indexed keywords

ALGORITHMS; COMPUTER OPERATING SYSTEMS; COMPUTER SCIENCE; COMPUTER SIMULATION; PROJECT MANAGEMENT; RISK MANAGEMENT;

COMPUTATIONAL SCIENCE; RISK IDENTIFICATION; RISK MITIGATION; SOFTWARE PROJECT MANAGEMENT; SOFTWARE QUALITY ENGINEERING;

SOFTWARE ENGINEERING;

EID: 9744257810     PISSN: 10943420     EISSN: None     Source Type: Journal    
DOI: 10.1177/1094342004048534     Document Type: Article

References (37)

1. Brooks, F. P. 1987. No silver bullet: essence and accidents of software engineering. Computer 20(4): 10-19.
2. Cockburn, A. and Highsmith, J. 2001. Agile software development, the people factor. Computer 34(11): 131-133.
3. Cox, L. et al. 2002. LANL ASCI Software Engineering Requirements. LA-UR-02-888. Los Alamos National Laboratory, Los Alamos.
4. DeMarco, T. 1997. The Deadline. Dorset House, New York.
5. DeMarco, T. and Boehm, B. 2002. The agile methods Fray. Computer 35(6): 90-92.
6. DeMarco, T. and Lister, T. 1999. Peopleware, Productive Projects and Teams. Dorset House, New York.
7. DeMarco, T. and Lister, T. 2002. Risk Management for Software. The Cutter Consortium, Arlington, MA.
8. Esque, T. J. 1999. No Surprises Project Management. ACT Publishing, Mill Valley, CA.
9. Herbsleb, J. et al. 1997. Software quality and the capability maturity model. Communications of the ACM 40: 30-40.
10. Highsmith, J. A. 2000. Adaptive Software Development. Dorset House, New York.
11. Highsmith, J. and Cockburn, A. 2001. Agile software development: the business of innovation. Computer 34(9): 120-127.
12. Humphrey, W. S. 2000. Introduction to the Team Software Process. Addision-Wesley, Reading, MA.
13. Humphrey, W. S. 2001. Winning with Software: An Executive Strategy. Software Engineering Institute, Pittsburg, PA.
14. Jones, T. C. 1998. Estimating Software Costs. McGraw-Hill, New York.
15. Laughlin, R. 2002. The physical basis of computability. Computing in Science and Engineering 4(3): 27-30.
16. Lewis, R. O. 1992. Independent Verification and Validation: A Life Cycle Engineering Process for Quality Software. Wiley, New York.
17. Lindl, J. 1998. Inertial Confinement Fusion. AIP Press, New York.
18. McBreen, P. 2001. Software Craftmanship. Addison-Wesley, Reading, MA.
19. McConnell, S. C. 1997. Software Project Survival. Microsoft Press.
20. Oldham, J. D. 2002. Scientific computing using POOMA. C/ C++ Users Journal 20: 6-22.
21. Paulk, M. 1994. The Capability Maturity Model. Addison-Wesley, Reading, MA.
22. Peters, J. and Pedrycz, W. 2000. Software Engineering: An Engineering Approach. Wiley, New York.
23. Phillips, D. 1997. The Software Project Manager's Handbook. IEEE Computer Society, Los Alamitos.
24. Post, D. and Cook, L. 2000. A Comparison of Software Engineering Practices used by the LLNL Nuclear Applications Codes and by the Software Industry. UCRL-MI-141464. Lawrence Livermore National Laboratory, Oakland, CA.
25. Post, D. and Kendall, R. 2002. Estimation of Software Project Schedules for Multi-Physics Simulations. LA-UR-02-7159. Los Alamos National Laboratory, Los Alamos.
26. Pressman, R. S. 2001. Software Engineering: A Practioner's Approach. McGraw-Hill, Boston.
27. Remer, D. 2000. Managing Software Projects. UCLA Technical Management Institute, UCLA Extension Courses, Los Angeles, CA.
28. Rifkin, S. 2002. Is process improvement irrelevant to produce new era software? Software Quality - ECSQ 2002 7th European Conference, Helsinki, Finland. Springer-Verlag, Berlin.
29. Roache, P. J. 1998. Verification and Validation in Computational Science and Engineering. Hermosa, Albuquerque, NM.
30. Roache, P. J. 2002. Code verification by the method of manufactured solutions. Transactions of the ASME 124: 4-10.
31. Salari, K. and Knupp, P. 2000. Code Verification by the Method of Manufactured Solutions. SAND2000-1444. Sandia National Laboratories, Albuquerque, NM.
32. Stewart, J. R. and Edwards, H. C. 2001. Parallel Adaptive Application Development using the SIERRA Framework. First MIT Conference in Computational Fluid and Solid Mechanics. Elsevier, Boston, MA.
33. Symons, C. R. 1988. Function point analysis: difficulties and improvements. IEEE Transactions on Software Engineering 14(1): 2-11.
34. Thomsett, R. 2002. Radical Project Management. Prentice-Hall, Englewood Cliffs, NJ.
35. Treacy, M. and Wiersema, F. 1995. The Discipline of Market Leaders: Choose Your Customers, Narrow Your Focus, Dominate Your Market. Perseus Books, Reading, MA.
36. Verzuh, E. 1999. The Fastforward MBA in Project Managemen t. Wiley, New York.
37. Yourdon, E. 1997. Death March. Prentice-Hall, Upper Saddle River, NJ.