methodology Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > methodology

Next subject: milestone Up: subject Previous subject: message

methodology comparison table

Subject use have web site function as help has definition be is a subtopic of have principles promote is an instance of have philosophy

extreme programming www.extremeprogramming.org an aid to thinking, not as a rigid prescription of the way to do things the project manager and his or her team to decide what work should be done and in what sequence to perform the work A process model and methodology that provides a disciplined approach to highly incremental and user-centred development of small projects popular for small projects that involve uncertain, changing requirements and other sources of high risk 11.2 - Software Process Models
The development team includes all the stakeholders
Large requirements documents are replaced by short user stories which dictate project planning
Releases are small and frequent
Planning takes place just before the start of each iteration
Scope, resources and time are the three project variables that can be changed. Management can only dictate two of these; the developers determine the third
Quality should not be sacrificed
In order to ensure high quality, design for testability is emphasized: Automated test cases are written before the software is developed
the use of CRC cards, a focus on simplicity, creation of 'spike' throwaway prototypes when difficult technical issues are encountered, merciless restructuring of code, frequent integration, programming in pairs, and continual improvement process model software developers should not need to be overworked, so overtime should not be needed

Rational Unified Process UML to represent models 5.1 - What is UML? methodology

Subject	use	have web site	function as	help	has definition	be	is a subtopic of	have principles	promote	is an instance of	have philosophy
extreme programming		www.extremeprogramming.org	an aid to thinking, not as a rigid prescription of the way to do things	the project manager and his or her team to decide what work should be done and in what sequence to perform the work	A process model and methodology that provides a disciplined approach to highly incremental and user-centred development of small projects	popular for small projects that involve uncertain, changing requirements and other sources of high risk	11.2 - Software Process Models	The development team includes all the stakeholders Large requirements documents are replaced by short user stories which dictate project planning Releases are small and frequent Planning takes place just before the start of each iteration Scope, resources and time are the three project variables that can be changed. Management can only dictate two of these; the developers determine the third Quality should not be sacrificed In order to ensure high quality, design for testability is emphasized: Automated test cases are written before the software is developed	the use of CRC cards, a focus on simplicity, creation of 'spike' throwaway prototypes when difficult technical issues are encountered, merciless restructuring of code, frequent integration, programming in pairs, and continual improvement	process model	software developers should not need to be overworked, so overtime should not be needed
Rational Unified Process	UML to represent models						5.1 - What is UML?			methodology

Next subject: milestone Up: subject Previous subject: message