Barely Sufficient Software Design: Difference between revisions

From charlesreid1

(Created page with "Link to paper: Barely Sufficient Software Design.pdf =The Ten Practices= # Use issue-tracking software for requirements, features, and bugs # Manage source (beyond the basi...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
Link to paper: [[Barely Sufficient Software Design.pdf]]
#REDIRECT [[10 Best Practices for Software Engineering]]
 
=The Ten Practices=
 
# Use issue-tracking software for requirements, features, and bugs
# Manage source (beyond the basics)
# Use mail lists to communicate
# Use checklists for repeated processes
# Create barely-sufficient, source-centric documentation
# Use configuration management tools
# Write tests first, run them often
# Program tough stuff together
# Use a formal release process
# Perform continual process improvement

Latest revision as of 02:38, 17 April 2017

Redirect to:

Retrieved from "https://charlesreid1.com/w/index.php?title=Barely_Sufficient_Software_Design&oldid=16631"