Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-29T03:15:05Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes! Microsoft, a well known industry leader in software development, is migrating towards a more agile methodology. This paper describes how Microsoft has become more successful by becoming more agile. They are shifting to a view that bugs are unacceptable, and, therefore, the development process should be more flexible. [http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744 Journey of enlightenment: the evolution of development at Microsoft]

In 2002, eighteen Agile experts got together to discuss the pros and cons of Agile methodology. They made the following conclusion about using Agile methodology to create reliable and safety-critical projects:
"Reliable and safety-critical projects can be conducted using Agile Methods. The key is that performance requirements are made explicit early, and proper levels of testing are planned. It is easier to address critical issues using Agile Methods since the customer gives requirements, makes important things explicit early and provides continual input." [http://www.lib.ncsu.edu:2097/content/54rr5mbq291rc5cy/ Taken from Empirical Findings in Agile Methods]

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]
* [http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744 Journey of enlightenment: the evolution of development at Microsoft]
* [http://www.lib.ncsu.edu:2097/content/54rr5mbq291rc5cy/ Taken from Empirical Findings in Agile Methods]
* [http://www.agilealliance.org/ Agile Alliance]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-29T03:07:15Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes! Microsoft, a well known industry leader in software development, is migrating towards a more agile methodology. This paper describes how Microsoft has become more successful by becoming more agile. They are shifting to a view that bugs are unacceptable, and, therefore, the development process should be more flexible. [http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744 Journey of enlightenment: the evolution of development at Microsoft]

In 2002, eighteen Agile experts got together to discuss the pros and cons of Agile methodology. They made the following conclusion about using Agile methodology to create reliable and safety-critical projects:
"Reliable and safety-critical projects can be conducted using Agile Methods. The key is that performance requirements are made explicit early, and proper levels of testing are planned. It is easier to address critical issues using Agile Methods since the customer gives requirements, makes important things explicit early and provides continual input." [http://www.lib.ncsu.edu:2097/content/54rr5mbq291rc5cy/ Taken from Empirical Findings in Agile Methods]

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-29T01:18:57Z

Ljhaywar: /* Can Agile Development Actually Produce a Robust Design? */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes! Microsoft, a well known industry leader in software development, is migrating towards a more agile methodology. This paper describes how Microsoft has become more successful by becoming more agile. They are shifting to a view that bugs are unacceptable, and, therefore, the development process should be more flexible. [http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744 Journey of enlightenment: the evolution of development at Microsoft]

http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-29T01:17:58Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes! Microsoft, a well known industry leader in software development, is migrating towards a more agile methodology. This paper describes how Microsoft has become more successful by becoming more agile. They are shifting to a view that bugs are unacceptable and therefore the development process should be more flexible. http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-29T00:14:00Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes! Microsoft, a well known industry leader in software development, is migrating towards a more agile methodology. This paper describes how Microsoft has become more successful by becoming more agile. http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T20:12:18Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes. http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T20:11:14Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

===When are Agile Methods Most Appropriate?===

Agile methodology evolved in the mid-1990s as software development teams began to notice that the rate of change of requirements was far larger than the rate of change allowed by the the current methodologies. Agile methodology is most appropriate when customers are unable to express the requirements upfront and when change in requirements in highly probable. [5]

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

Since Agile Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]).

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes. http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [http://www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T20:04:23Z

Ljhaywar: /* When are Plan-Driven Methods Most Appropriate? */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains, "Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes. http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T20:04:08Z

Ljhaywar: /* What is Plan-Driven Methodology? */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains,

"Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software." [5]

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes. http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T20:03:25Z

Ljhaywar: /* The Agile Debate */

=The Agile Debate=

==Project Description==

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

==What is Plan-Driven Methodology?==

Laurie Williams describes Plan-driven methods:
"Plan-driven methods are those that begin with the solicitation and documentation of a set of requirements that is as complete as possible. Based on these requirements, one can then formulate a plan of development. Usually, the more complete the requirements, the better the plan." [1]

Plan-driven methodology encompasses several different processes including [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and the [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes].

===When are Plan-Driven Methods Most Appropriate?===

Plan-driven methods are most appropriate when software is highly critical and the requirements can be determined to be stable at the beginning of the project.

As Barry Boehm explains,
"Plan-driven methods work best when developers can determine the requirements in advance...and when the requirements remain relatively stable...This emphasis is vital for stable, safety-critical embedded software."

==What is Agile Methodology?==

Laurie Williams describes agile methodology as:

"Agile methods are a subset of iterative and evolutionary methods (Larman, 2004; Larman and Basili, June 2003) and are based on iterative enhancement (Basili and Turner, 1975) and opportunistic development processes (Curtis, 1989). In all iterative products, each iteration is a self-contained, mini-project with activities that span requirements analysis, design, implementation, and test (Larman, 2004)."[1]

Agile methodology encompasses several different processes including [http://www.extremeprogramming.org/ Extreme Programming], [http://agile.csc.ncsu.edu/crystal.html Crystal], [http://agile.csc.ncsu.edu/scrum.html Scrum], and [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development].

==Benefits of Plan-Driven Methodology==

Since Plan-Driven Methodology encompasses several different processes, the following are general benefits common to all. For more specific and elaborated benefits, look into the individual processes ([http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html waterfall], [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process], and [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]).

* "Thorough documentation" [2]
* "Detailed plans, workflow, roles, responsibilities, and work product descriptions" [2]
* "On-going risk management" [2]
* "Focus on verification and validation" [2]
* "Predictability, stability, and high assurance" [3]
* Attractive methodology for highly critical systems [4]
* Allows for stable requirements [5]
* Good for large teams and requirements [5]
* Primary objective is "high assurance" [5]

==Benefits of Agile Methodology==

* Allows for changing requirements [1]
* Delivers working software frequently [1]
* Encourages interaction between business people and developers [1]
* Requires teams to regularly evaluate how to become more effective and modify accordingly [1]
* "Higher customer satisfaction, lower defect rates, faster development times" [3]
* Refactoring is inexpensive [5]
* Good for small teams and requirements [5]
* Primary objective is "rapid value" [5]

==Can Agile Development Actually Produce a Robust Design?==
Yes. http://portal.acm.org/citation.cfm?id=604255&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1062473&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744
http://portal.acm.org/citation.cfm?id=1030005&coll=ACM&dl=ACM&CFID=8022253&CFTOKEN=18011744

==What Methodology Is Best?==

While some will argue strongly for one methodology or the other, many software engineering teams are migrating to a hybrid methodology. Barry Beohm and Richard Turner suggest five critical dimensions when determining which methodology to use: size, criticality, dynamism, personnel, and culture [3].

"Both agile and plan-driven methods have a home ground of project characteristics in which each clearly works best, and where the other will have difficulties. Hybrid approaches that combine both methods are feasible and necessary for projects that combine a mix of agile and plan-driven home ground characteristics." [5]

For a fantastic spider-like diagram of how to choose the methodology best for your team, view Dr. Laurie Williams' slides: [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]. Slide #4 allows you to chart where your team lies in the five critical dimensions and determine whether plan-driven, agile, or a hybrid is best for you.

==Suggested Links==
* [http://courses.cs.vt.edu/~csonline/SE/Lessons/Waterfall/index.html Waterfall]
* [http://www.sei.cmu.edu/tsp/psp.html Personal Software Process]
* [http://en.wikipedia.org/wiki/Rational_Unified_Process Rational Unified Processes]
* [http://www.extremeprogramming.org/ Extreme Programming]
* [http://agile.csc.ncsu.edu/crystal.html Crystal]
* [http://agile.csc.ncsu.edu/scrum.html Scrum]
* [http://agile.csc.ncsu.edu/fdd.html Feature Driven Development]
* [http://courses.ncsu.edu/csc326/lec/001/lectures/ChooseProcess.pdf Choosing Your Software Development Process: Agile or Plan-driven?]

==References==
* [1] [http://agile.csc.ncsu.edu/SEMaterials/AgileMethods.pdf A Survey of Agile Development Methodologies]
* [2] [http://agile.csc.ncsu.edu/SEMaterials/PlanDriven.pdf A Survey of Plan-Driven Development Methodologies]
* [3] [http://portal.acm.org/citation.cfm?id=999485&coll=ACM&dl=ACM&CFID=43700200&CFTOKEN=87947446 Balancing Agility and Discipline: Evaluating and Integrating Agile and Plan-Driven Methods ]
* [4] [http://www.agilealliance.org/system/article/file/923/file.pdf Agile and Plan-Driven Methods Oil and Water?]
* [5] [www2.umassd.edu/swpi/xp/papers/r1064.pdf Get Ready for Agile Methods, with Care]

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T18:54:47Z

Ljhaywar: /* Can Agile Development Actually Produce a Robust Design? */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T18:52:42Z

Ljhaywar: /* Can Agile Development Actually Produce a Robust Design? */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-28T18:36:46Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-27T04:59:56Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-27T04:58:50Z

Ljhaywar: /* Benefits of Plan-Driven Methodology */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-27T04:54:42Z

Ljhaywar: /* Suggested Links */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-27T04:54:18Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-26T18:42:07Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-19T17:37:43Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-19T17:35:28Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-19T17:32:49Z

Ljhaywar: /* What Methodology Is Best? */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:33:34Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:23:12Z

Ljhaywar: /* References */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:23:01Z

Ljhaywar: /* References */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:21:00Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:20:36Z

Ljhaywar: /* References */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:19:53Z

Ljhaywar: /* Benefits of Plan-Driven Methodology */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:16:38Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:15:50Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T23:08:50Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:53:48Z

Ljhaywar: /* References */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:53:19Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:42:58Z

Ljhaywar: /* References */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:39:31Z

Ljhaywar: /* Benefits of Plan-Driven Methodology */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:33:31Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:31:00Z

Ljhaywar: /* What is Plan-Driven Methodology? */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:28:54Z

Ljhaywar: /* What is Agile Methodology? */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:12:22Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T22:07:40Z

Ljhaywar: /* The Agile Debate */

CSC/ECE 517 Fall 2007/wiki3 10 ljh

2007-11-18T21:57:17Z

Ljhaywar:

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:56:39Z

Ljhaywar: /* Best Sites for Model View Controller Examples */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
We have compiled a list of the following sites to introduce the Model View Controller concept. Model View Controller can be applied to a broad range of applications and we hope the following sites will give you insight into this pattern.

#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy! (Be sure to press "Listen" and not the "Download this song" link.)
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
Sometimes seeing a few examples can be really helpful, so here they are:

#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java==
Ruby on Rails has built-in support for Model View Controller. In fact, it is impossible to write a Rails application without following the pattern. The Ruby links below provide an introduction to writing rails applications and they each have a section dedicated to MVC.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

However, since Java does not have built-in support for Model View Controller, you must design your Java applications keeping MVC in mind. The following links detail the steps required.
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:56:25Z

Ljhaywar: /* Best Sites for How to Use the Pattern in Ruby and Java */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
We have compiled a list of the following sites to introduce the Model View Controller concept. Model View Controller can be applied to a broad range of applications and we hope the following sites will give you insight into this pattern.

#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy! (Be sure to press "Listen" and not the "Download this song" link.)
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
Sometimes seeing a few examples can be really helpful. So here they are:

#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java==
Ruby on Rails has built-in support for Model View Controller. In fact, it is impossible to write a Rails application without following the pattern. The Ruby links below provide an introduction to writing rails applications and they each have a section dedicated to MVC.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

However, since Java does not have built-in support for Model View Controller, you must design your Java applications keeping MVC in mind. The following links detail the steps required.
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:55:25Z

Ljhaywar: /* Best Sites for How to Use the Pattern in Ruby and Java */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
We have compiled a list of the following sites to introduce the Model View Controller concept. Model View Controller can be applied to a broad range of applications and we hope the following sites will give you insight into this pattern.

#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy! (Be sure to press "Listen" and not the "Download this song" link.)
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
Sometimes seeing a few examples can be really helpful. So here they are:

#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java==
Ruby on Rails has built-in support for Model View Controller. In fact, it is impossible to write a Rails application without following the pattern. The Ruby links below are introductions to writing rails applications that have a section dedicated to MVC.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

However, since Java does not have built-in support for Model View Controller, you must design your Java applications keeping MVC in mind. The following links detail the steps required.
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:47:47Z

Ljhaywar: /* Best Sites for Model View Controller Examples */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
We have compiled a list of the following sites to introduce the Model View Controller concept. Model View Controller can be applied to a broad range of applications and we hope the following sites will give you insight into this pattern.

#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy! (Be sure to press "Listen" and not the "Download this song" link.)
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
Sometimes seeing a few examples can be really helpful. So here they are:

#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:46:51Z

Ljhaywar: /* Best Sites for Learning the Model View Controller Concept */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
We have compiled a list of the following sites to introduce the Model View Controller concept. Model View Controller can be applied to a broad range of applications and we hope the following sites will give you insight into this pattern.

#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy! (Be sure to press "Listen" and not the "Download this song" link.)
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:44:09Z

Ljhaywar: /* Best Sites for Learning the Model View Controller Concept */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy! (Be sure to press "Listen" and not the "Download this song" link.)
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:43:09Z

Ljhaywar: /* Best Sites for Learning the Model View Controller Concept */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well. Discusses a few Java and web technologies, but no prior knowledge of these is necessary.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy!
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-28T21:38:33Z

Ljhaywar: /* Model View Controller */

''Wiki Topic: Model/view/controller. There are literally hundreds of pages describing MVC on the Web. If someone wants to learn about it, what should (s)he do? Look at the first few hits in Google? I expect we can do better than that. Write a review of the MVC sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which are best for explaining how to use the pattern in Ruby and Java? If you choose this topic, you should be sure to peruse at least several dozen sites.''

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy!
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-23T22:59:13Z

Ljhaywar: /* Best Sites for How to Use the Pattern in Ruby and Java */

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy!
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that comes built-in with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a project's architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.

CSC/ECE 517 Fall 2007/wiki2/3 rl

2007-10-23T22:56:18Z

Ljhaywar: /* Best Sites for Model View Controller Examples */

== Model View Controller ==

"Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present a large amount of data to the user, a developer often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface will not affect data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller." Taken from [http://en.wikipedia.org/wiki/Model-view-controller Wikipedia]

== Best Sites for Learning the Model View Controller Concept ==
#[http://java.sun.com/blueprints/patterns/MVC-detailed.html http://java.sun.com/blueprints/patterns/MVC-detailed.html] : This is a very brief introduction to the MVC concept, ideal if you are in a hurry :). I really like the illustration they used, it delimits the responsibilities of the components very well.
#[http://ootips.org/mvc-pattern.html http://ootips.org/mvc-pattern.html] : Nicely written introduction; however, it has ascii-art diagrams.
#[http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html http://www.oreillynet.com/onjava/blog/2003/07/new_way_to_learn_mvc_view_a_si.html] : The most innovative way to learn about MVC, through a song. Yes you heard it right, I would recommend this to everyone just because of the hilarious lyrics. Enjoy!
#[http://www.adobe.com/devnet/flash/articles/mv_controller.html http://www.adobe.com/devnet/flash/articles/mv_controller.html] : A fantastic article that details the three components of MVC, benefits of the pattern, how the classes of MVC communicate, and class responsibilities.
#[http://www.perlmonks.org/?node_id=402070 http://www.perlmonks.org/?node_id=402070] : An easy introduction to MVC with a handy sequence diagram example.

== Best Sites for Model View Controller Examples ==
#[http://www.enode.com/x/markup/tutorial/mvc.html http://www.enode.com/x/markup/tutorial/mvc.html] : This is an awesome introduction to the concept. Short, sweet and to the point explained with the help of a contrived spinner example. This site does not give many details but is really good to get you started.
#[http://csis.pace.edu/~bergin/mvc/mvcgui.html http://csis.pace.edu/~bergin/mvc/mvcgui.html] : This article is written very well. It gives a detailed example of a temperature gauge, complete with source code in Java. I especially like it when the author explains how the components are interconnected. It really helps in understanding the communication between the model, view and controller, as introduced in many of the MVC concept websites above.
#[http://www.caucho.com/articles/jsp_templates.xtp http://www.caucho.com/articles/jsp_templates.xtp] : An extremely detailed example of how to build a simple guestbook in JSP using the MVC pattern.
#[http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1 http://www.informit.com/guides/content.aspx?g=java&seqNum=117&rl=1] : Complete code example using Servlets as the controller, JSP files as the view, and JavaBeans as the model.

== Best Sites for How to Use the Pattern in Ruby and Java ==
#[http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/app-arch/app-arch5.html] : This is the design document for the pet store sample that come in built with Java EE. It goes into a lot of detail about how the MVC was used to design this sample. This page provides an excellent resource to understand the benefits of using patterns while working on a projects architecture. It bridges the gap between the theoretical concepts of the pattern and its practical implementations.
#[http://cristobal.baray.com/indiana/projects/mvc.html http://cristobal.baray.com/indiana/projects/mvc.html] : A detailed introduction to the use of MVC with a Java view point which spans several pages, complete with source code. Warning: This site throws many pop ups, so keep your pop up blocker handy.
#[http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/ http://www-128.ibm.com/developerworks/linux/library/l-rubyrails/] : This article gives the details on how to utilize the built-in features of Ruby on Rails to create a web application using MVC.
#[http://rails.homelinux.org/ http://rails.homelinux.org/] : Four Days on Rails is a 40 page pdf that takes you through learning the basics of rails. It includes both a description and code example for the model, view, and controller.