CSC/ECE 506 Fall 2007/wiki3 9 sm: Difference between revisions
Jump to navigation
Jump to search
(Created page with headers on the two required topics) |
(→Collective Ownership: Added introduction to Collective ownership) |
||
| Line 1: | Line 1: | ||
== Collective Ownership == | == Collective Ownership == | ||
In a software project, collective ownership of the code implies that any code written does not belong to any particular engineer. This means that anyone working on the project can modify any piece of code that has been previously written. According to Cunningham & Cunningham, Inc., a consulting firm specialized in object-oriented programming, there are several requirements to make Collective ownership work well: | |||
* All engineers use the same coding standards | |||
* The project use code management tools to detect and resolve conflicts | |||
* A comprehensive suite of unit tests exists | |||
* Powerful browsing and refactoring tools to find references to old methods and replace them with the new | |||
* Continuous Integration, so that conflicts are rare | |||
== Continuous Integration == | == Continuous Integration == | ||
Revision as of 02:40, 18 November 2007
Collective Ownership
In a software project, collective ownership of the code implies that any code written does not belong to any particular engineer. This means that anyone working on the project can modify any piece of code that has been previously written. According to Cunningham & Cunningham, Inc., a consulting firm specialized in object-oriented programming, there are several requirements to make Collective ownership work well:
- All engineers use the same coding standards
- The project use code management tools to detect and resolve conflicts
- A comprehensive suite of unit tests exists
- Powerful browsing and refactoring tools to find references to old methods and replace them with the new
- Continuous Integration, so that conflicts are rare