10 Best Practices for Software Engineering - Revision history

Admin: /* Also See */

2019-10-09T02:04:54Z

Also See

← Older revision		Revision as of 02:04, 9 October 2019
Line 84:		Line 84:
	[[Category:Top 10]]		[[Category:Top 10]]
	[[Category:Scientific Computing]]		[[Category:Scientific Computing]]
			[[Category:Best Practices]]

2018-04-16T22:14:31Z

← Older revision		Revision as of 22:14, 16 April 2018
Line 51:		Line 51:
	Continuous improvement		Continuous improvement

	=~~Full~~=		=Also See=

	See Also: [[The Cathedral and the Bazaar]] (19 best practices for creating open-source software)		See Also: [[The Cathedral and the Bazaar]] (19 best practices for creating open-source software)

			<!--

	Following Heroux and Willenbring's paper (http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf), here are 10 "best practices" for software engineering:		Following Heroux and Willenbring's paper (http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf), here are 10 "best practices" for software engineering:
Line 76:		Line 78:

	10 Continuous process improvement		10 Continuous process improvement

			-->

	[[Category:Programming]]		[[Category:Programming]]
	[[Category:Top 10]]		[[Category:Top 10]]
	[[Category:Scientific Computing]]		[[Category:Scientific Computing]]

2018-01-04T09:58:04Z

← Older revision		Revision as of 09:58, 4 January 2018
Line 1:		Line 1:
			Also see: [[NASA 10 Best Practices for Software Engineering]]

	=Heroux and Willenbring's 10 Best Practices=		=Heroux and Willenbring's 10 Best Practices=

2017-04-17T02:38:06Z

← Older revision		Revision as of 02:38, 17 April 2017
Line 1:		Line 1:
	=Heroux and Willenbring's 10 Best Practices=		=Heroux and Willenbring's 10 Best Practices=

	In a draft paper called [http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf Barely Sufficient Software Engineering] that I find myself returning to again and again as a computational chemical engineer, Michael Heroux and James Willenbring, both of Sandia National Laboratories, wrote up 10 (actually, 11) guidelines for writing scientific code that is high quality and encourages collaboration.		In a draft paper called [http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf Barely Sufficient Software Engineering (pdf file)] that I find myself returning to again and again as a computational chemical engineer, Michael Heroux and James Willenbring, both of Sandia National Laboratories, wrote up 10 (actually, 11) guidelines for writing scientific code that is high quality and encourages collaboration.

	They are:		They are:

2017-04-17T02:14:13Z

← Older revision		Revision as of 02:14, 17 April 2017
Line 77:		Line 77:
	[[Category:Programming]]		[[Category:Programming]]
	[[Category:Top 10]]		[[Category:Top 10]]
			[[Category:Scientific Computing]]

2016-06-21T17:20:00Z

2014-04-08T21:22:45Z

Abbreviated

← Older revision		Revision as of 21:22, 8 April 2014
Line 1:		Line 1:
	=Abbreviated=		=Heroux and Willenbring's 10 Best Practices=

			In a draft paper called [http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf Barely Sufficient Software Engineering] that I find myself returning to again and again as a computational chemical engineer, Michael Heroux and James Willenbring, both of Sandia National Laboratories, wrote up 10 (actually, 11) guidelines for writing scientific code that is high quality and encourages collaboration.

			They are:

			0. Manage your source (the basics)

			1. Use issue-tracking software for requirements, features, and bugs

			2. Manage your source (beyond the basics)

			3. Use mailing lists to communicate

			4. Use checklists for repeated processes

			5. Create barely sufficient, source-centric documentation

			6. Use configuration management tools

			7. Write tests first, run them often

			8. Program tough stuff together

			9. Use a formal release process

			10. Perform continual process improvement

			=An Abbreviated Version=

	Issue tracking		Issue tracking

2013-07-06T02:38:36Z

← Older revision		Revision as of 02:38, 6 July 2013
Line 1:		Line 1:
			=Abbreviated=

			Issue tracking

			Version control

			Mailing list

			Checklists! Checklists!

			Self documenting

			Configuration management

			Test driven

			Pair programming

			Formal release

			Continuous improvement

			=Full=

	See Also: [[The Cathedral and the Bazaar]] (19 best practices for creating open-source software)		See Also: [[The Cathedral and the Bazaar]] (19 best practices for creating open-source software)

2013-06-10T15:27:56Z

← Older revision		Revision as of 15:27, 10 June 2013
Line 22:		Line 22:

	10 Continuous process improvement		10 Continuous process improvement

			[[Category:Programming]]

2013-06-10T15:25:30Z

← Older revision		Revision as of 15:25, 10 June 2013
Line 1:		Line 1:
			See Also: [[The Cathedral and the Bazaar]] (19 best practices for creating open-source software)

	Following Heroux and Willenbring's paper (http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf), here are 10 "best practices" for software engineering:		Following Heroux and Willenbring's paper (http://www.sandia.gov/~maherou/docs/BarelySufficientSoftwareEngineering.pdf), here are 10 "best practices" for software engineering: