Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T15:27:37Z

Sbhatia2: /* References */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

http://pg.ece.ncsu.edu/mediawiki/images/3/36/Tradvsemerg.jpg

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are designed to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features of ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
*ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (An incentive system may backfire too)

*ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

*In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bringing together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama 
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007 
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004)

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T15:26:54Z

Sbhatia2: /* ASD doesn’t promote robust design */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

http://pg.ece.ncsu.edu/mediawiki/images/3/36/Tradvsemerg.jpg

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are designed to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features of ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
*ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (An incentive system may backfire too)

*ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

*In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bringing together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T15:25:46Z

Sbhatia2: /* ASD promotes robust design */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

http://pg.ece.ncsu.edu/mediawiki/images/3/36/Tradvsemerg.jpg

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are designed to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features of ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
*ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (A suitable incentive system may backfire too)

*ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

*In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bring together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T15:25:12Z

Sbhatia2: /* ASD promotes robust design */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

http://pg.ece.ncsu.edu/mediawiki/images/3/36/Tradvsemerg.jpg

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are designed to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features dof ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
*ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (A suitable incentive system may backfire too)

*ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

*In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bring together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T05:15:30Z

Sbhatia2: /* Agile software development */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

http://pg.ece.ncsu.edu/mediawiki/images/3/36/Tradvsemerg.jpg

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are design to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features dof ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
*ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (A suitable incentive system may backfire too)

*ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

*In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bring together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

File:Tradvsemerg.jpg

2007-11-12T05:15:04Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T05:14:43Z

Sbhatia2: /* ASD doesn’t promote robust design */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are design to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features dof ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
*ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (A suitable incentive system may backfire too)

*ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

*In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bring together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T05:14:27Z

Sbhatia2: /* ASD promotes robust design */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
*ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

*Problems are design to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

*ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features dof ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
#ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (A suitable incentive system may backfire too)

#ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bring together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T05:13:35Z

Sbhatia2: /* Structure/Robustness in Agile Software Development */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

===ASD promotes robust design===
ASD is a continuously self correcting process. The traditional model tries to do things right at the first time, however ASD tries to do things right at the first place as well, and fosters learning by looping in future iterations. [2]

Problems are design to be wicked and intractable and they can only be solved through repetitive emergent process and refinement, thus leading to a far better solution than granted by traditional models. [3]

ASD keeps room for future scalability of software. Software build on ASD principles remains lean, modular and scalable with every iteration. The waterfall model however produces code that is “fat”, monolithic and not scalable. These combined features dof ASD ensure that the code remains robust and reliable even after multiple releases. [3]

===ASD doesn’t promote robust design===
#ASD allows individual developer to prefer his/her own process. [3] This may lead to inefficiency and sloppy software, coded to meet the end of iteration. If a suitable incentive system is not in place ASD may backfire. (A suitable incentive system may backfire too)

#ASD depends largely on teamwork, self-organization, personal empowerment to achieve robust architechture[3]

In case of large projects, ASD promotes creation of software in a modular form by small teams or individuals in multiple iterations. However, there are multiple sources of evidence which suggest that the final step in bring together the smaller pieces takes much of time and results into an ineffective product. [5]

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T05:12:41Z

Sbhatia2: /* Conclusion */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

==Structure/Robustness in Agile Software Development==

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

#The ASD is a continuously self correcting process. Whereas the traditional models try to do things right at the first time, ASD tries to do things right at the first place as well, but fosters learning by looping. [2] As a result the software delivered after few iterations is more robust and reliable.

#The ASD

.
.
.
.
.
.......working......
.
.
.
.

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every release.

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T05:12:19Z

Sbhatia2: /* References */

'''Assignment''' 
''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.''

==Agile software development==
Agile software development (hereafter ASD) is a model in Software Engineering to develop software through multiple iterations throughout the life-cycle of project. The result is a complex, high-speed, self-correcting methodology that occurs under conditions of high uncertainty, high change and high stress resulting into delivery of value to customer along with providing an adequate quality of life to team members.

Each iteration of ASD is an entire software project. The iteration includes planning, requirements analysis, design, coding, testing, and documentation. At the end of every iteration we have a deliverable product. Only at this point of time, the project requirements are re-evaluated and the requirements with highest priority are chosen by peer review, and on-site customer participation.

===Pros===
#Emphasize face-to-face communication.
#Requirement changes at any stage are welcome, since they can be incorporated in next iteration [1].
#A working software is delivered at the end of every iteration
#Agile infuses positive environment and promotes culture of motivation, collaboration and trust.
#Continuous attention to design

===Cons===
#The requirement for next iteration along with its completion date/budget are known since iteration is quick. However, the project completion date/budget is not always clear.
#The management has to be willing, to let go of micro management.
#Requires competent and trustworthy team members.
#Success of Agile methods in case of large scale development efforts and mission critical software’s is under doubt.
#Unsuitable for telecommuters
#Produces very little written documentation

==Structure/Robustness in Agile Software Development==

Now that we have a good sense of what an Agile Software Development model means, we would elaborate on how it ensures that the deliverables are/aren’t robust.

#The ASD is a continuously self correcting process. Whereas the traditional models try to do things right at the first time, ASD tries to do things right at the first place as well, but fosters learning by looping. [2] As a result the software delivered after few iterations is more robust and reliable.

#The ASD

.
.
.
.
.
.......working......
.
.
.
.

==Conclusion==
Teams using Agile software development may not have a robust structure in the first iteration/version, however as the developmenet goes on, the code grows more robust and reliable unlike waterfall where the code deteriorates on every iteration manily because

==References==
[1] Extreme Programming Explained: Embrace Change, K. Beck, Addison-Wesley,2000 
[2] Ad Hoc Practices or Sound Principles, Lan Cao and Balasubramaniam Ramesh 
[3] Agile Software Process and Its Experience, Mikio Aoyama
[4] Theoretical reflections on agile development methodologies, Sridhar Nerur, VenuGopal Balijepally, 2007
[5] Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. Boehm, B.; R. Turner (2004).

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:36:42Z

Sbhatia2: /* Structure/Robustness in Agile Software Development */

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:18:47Z

Sbhatia2: /* Conclusion */

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:18:37Z

Sbhatia2: /* Conclusion */

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:18:17Z

Sbhatia2: /* Conclusion */

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:18:02Z

Sbhatia2: /* Structure/Robustness in Agile Software Development */

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:17:22Z

Sbhatia2: /* Conclusion */

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-12T03:16:34Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-11T15:37:53Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-11T02:25:10Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki3 10 sb

2007-11-11T01:19:03Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-29T21:01:01Z

Sbhatia2: /* What is a use case */

'''Assignment''' 
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

='''Introduction'''=
==What is a use case?==
===Definition===
''A use case is a methodology that helps identify the functional requirements of software. A use-case model describes actors, use cases, and relations among them. Actors represent entities that must exchange information with the system, including users. When an actor uses the system, the system performs a use case. A good use case is a sequence of transactions that yields a measurable result of value for an actor. The collection of use cases is the system's complete functionality.''
 
Use case gives us a list of events which occur from the time the actor begins interacting with the system till the time the final goal is achieved. Other details not relevant to the user are not a part of the use case.

[http://www.ibm.com/developerworks/webservices/library/co-design5.html OO design process: Use cases, an introduction]

='''Best for learning about the concept'''=
==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding. 
Also provides Use case templates. 
Discusses benefits and limitations of use cases. 
Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old. 
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links. 

== [http://en.wikipedia.org/wiki/Use_case_diagram Use Case Diagram Wikipedia] ==

=== '''Likes''' ===
-Precise explanation of Use Case Diagrams and its notations. 
-Also explains advanced concepts like different types of relationships. 
-Illustrates the concept with an easy example making it easier for first time readers.

=== '''Drawbacks''' ===
-Does not provide a basic understanding of why use cases are required. 
-The page uses technical language which might be deterrent for novices. 
-Again since it is a wiki page the information could be tampered by anyone.

=== '''Review''' ===
-Though the page contains all elements which are instrumental in understanding use cases and use cases diagrams the semantics of use cases could have been better expressed if simple language was used. 

='''Teaches advanced concepts '''=
==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion. 
Also talks about cases where goal-phrase structure can be used. 
Identifies shortcomings of Use Case.

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing.

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting. 

='''Has the most instructive examples'''=
==[http://www.gatherspace.com/static/use_case_example.html Writing effective Use Case Examples]==

==='''Likes'''===
Gets right to point without any fluff. 
Easy to understand, with diagrams and examples.

==='''Drawbacks'''===
Has lot of ads and the “Try it” (example) link takes you somewhere else.

==='''Review'''===
Simply loved the website, its just what someone like me looks for to gets things done. Explains howto write Use Cases alongwith an example. 

==[http://www.developer.com/design/article.php/10925_2109801_1 Excellent walkthrough with understanding and example]==

==='''Likes'''===
-The page serves as an excellent resource for learning all facets of Use Cases and Use Case diagrams. 
-The entire tutorial is divided in a logical manner starting from basic topics right through advanced stuff. 
-The page uses very natural examples from the real world to explain each concept related to Use cases.

==='''Drawbacks'''===
-Very little has been said about the theory behind Use cases and its evolution i.e. why was a need felt to create an Object Oriented instrument like use cases.

==='''Review'''===
- An excellent page for people who wish to start off developing Use cases and use cases diagrams just by reading a single webpage. 

==[http://www.math-cs.gordon.edu/courses/cs320/ATM_Example/UseCases.html Use Cases for Example ATM System]==

==='''Likes'''===
One of the best pages found, which explains an example in full length.

==='''Drawbacks'''===
Has no diagrams 
Skips on basic explaining basic terms 
Has no inline links to explain, some of the terms used.

==='''Review'''===
A very good page for anyone who’s looking for a Use Cases for Example ATM System or for an example Use case application for that matter. 

='''Some Questions answered '''=

==[http://www.usability.gov/methods/usecases.html Answers Basic Questions]==

==='''Likes'''===
-Answers basic questions like 
•What is a use case? 
•What does a use case describe? 
•How do you write a use case?

==='''Drawbacks'''===
-The concept is explained from the point of view of website usability. 
-Only the concept is explained without example.

==='''Review'''===
-A simple page for understanding the concept of use cases. 

==[http://ootips.org/use-cases-vs-requirements.html Questions on advanced topics]==

==='''Likes'''===
Can be considered as set of pages which will help you decide while you start developing use cases for your system. It will help you answer questions like “How Many use cases are required for my system?”

==='''Drawbacks'''===
-Only the concept is explained without example.

==='''Review'''===
-A simple page for answering certain questions which arise while development of use cases.

='''External Links'''=
http://www.protoolkits.com/Analysisandrequirements/Analysistechniques/usecases.html 
http://web.cecs.pdx.edu/~maier/386/usecase06.pdf 
http://ootips.org/use-cases-done.html 
http://alistair.cockburn.us/index.php/Use_case_fundamentals 
http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases 
http://alistair.cockburn.us/index.php/Use_cases%2C_ten_years_later

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-29T21:00:01Z

Sbhatia2:

'''Assignment''' 
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

='''Introduction'''=
==What is a use case==
===Definition===
''A use case is a methodology that helps identify the functional requirements of software. A use-case model describes actors, use cases, and relations among them. Actors represent entities that must exchange information with the system, including users. When an actor uses the system, the system performs a use case. A good use case is a sequence of transactions that yields a measurable result of value for an actor. The collection of use cases is the system's complete functionality.''

Use case gives us a list of events which occur from the time the actor begins interacting with the system till the time the final goal is achieved. Other details not relevant to the user are not a part of the use case.

[http://www.ibm.com/developerworks/webservices/library/co-design5.html OO design process: Use cases, an introduction]

='''Best for learning about the concept'''=
==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding. 
Also provides Use case templates. 
Discusses benefits and limitations of use cases. 
Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old. 
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links. 

== [http://en.wikipedia.org/wiki/Use_case_diagram Use Case Diagram Wikipedia] ==

=== '''Likes''' ===
-Precise explanation of Use Case Diagrams and its notations. 
-Also explains advanced concepts like different types of relationships. 
-Illustrates the concept with an easy example making it easier for first time readers.

=== '''Drawbacks''' ===
-Does not provide a basic understanding of why use cases are required. 
-The page uses technical language which might be deterrent for novices. 
-Again since it is a wiki page the information could be tampered by anyone.

=== '''Review''' ===
-Though the page contains all elements which are instrumental in understanding use cases and use cases diagrams the semantics of use cases could have been better expressed if simple language was used. 

='''Teaches advanced concepts '''=
==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion. 
Also talks about cases where goal-phrase structure can be used. 
Identifies shortcomings of Use Case.

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing.

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting. 

='''Has the most instructive examples'''=
==[http://www.gatherspace.com/static/use_case_example.html Writing effective Use Case Examples]==

==='''Likes'''===
Gets right to point without any fluff. 
Easy to understand, with diagrams and examples.

==='''Drawbacks'''===
Has lot of ads and the “Try it” (example) link takes you somewhere else.

==='''Review'''===
Simply loved the website, its just what someone like me looks for to gets things done. Explains howto write Use Cases alongwith an example. 

==[http://www.developer.com/design/article.php/10925_2109801_1 Excellent walkthrough with understanding and example]==

==='''Likes'''===
-The page serves as an excellent resource for learning all facets of Use Cases and Use Case diagrams. 
-The entire tutorial is divided in a logical manner starting from basic topics right through advanced stuff. 
-The page uses very natural examples from the real world to explain each concept related to Use cases.

==='''Drawbacks'''===
-Very little has been said about the theory behind Use cases and its evolution i.e. why was a need felt to create an Object Oriented instrument like use cases.

==='''Review'''===
- An excellent page for people who wish to start off developing Use cases and use cases diagrams just by reading a single webpage. 

==[http://www.math-cs.gordon.edu/courses/cs320/ATM_Example/UseCases.html Use Cases for Example ATM System]==

==='''Likes'''===
One of the best pages found, which explains an example in full length.

==='''Drawbacks'''===
Has no diagrams 
Skips on basic explaining basic terms 
Has no inline links to explain, some of the terms used.

==='''Review'''===
A very good page for anyone who’s looking for a Use Cases for Example ATM System or for an example Use case application for that matter. 

='''Some Questions answered '''=

==[http://www.usability.gov/methods/usecases.html Answers Basic Questions]==

==='''Likes'''===
-Answers basic questions like 
•What is a use case? 
•What does a use case describe? 
•How do you write a use case?

==='''Drawbacks'''===
-The concept is explained from the point of view of website usability. 
-Only the concept is explained without example.

==='''Review'''===
-A simple page for understanding the concept of use cases. 

==[http://ootips.org/use-cases-vs-requirements.html Questions on advanced topics]==

==='''Likes'''===
Can be considered as set of pages which will help you decide while you start developing use cases for your system. It will help you answer questions like “How Many use cases are required for my system?”

==='''Drawbacks'''===
-Only the concept is explained without example.

==='''Review'''===
-A simple page for answering certain questions which arise while development of use cases.

='''External Links'''=
http://www.protoolkits.com/Analysisandrequirements/Analysistechniques/usecases.html 
http://web.cecs.pdx.edu/~maier/386/usecase06.pdf 
http://ootips.org/use-cases-done.html 
http://alistair.cockburn.us/index.php/Use_case_fundamentals 
http://alistair.cockburn.us/index.php/Resources_for_writing_use_cases 
http://alistair.cockburn.us/index.php/Use_cases%2C_ten_years_later

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:44:11Z

Sbhatia2: /* '''External Links''' */

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:43:54Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:43:00Z

Sbhatia2: /* '''Has the most instructive examples''' */

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:42:04Z

Sbhatia2: /* '''Has the most instructive examples''' */

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:31:13Z

Sbhatia2: /* '''Teaches advanced concepts ''' */

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:30:31Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:27:17Z

Sbhatia2:

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:26:41Z

Sbhatia2:

'''Assignment'''
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

='''Best for learning about the concept'''=
==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

='''Teaches advanced concepts '''=
[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]
==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

='''Has the most instructive examples'''=

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-24T00:25:42Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

='''Best for learning about the concept'''=
==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T23:56:15Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

=='''Our Opinion'''==
==='''Best for learning about the concept'''===
[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]
==='''Has the most instructive examples'''===
==='''Teaches advanced concepts '''===
[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T23:55:24Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

=='''Our Opinion'''==
==='''Best for learning about the concept'''===
==='''Has the most instructive examples'''===
==='''Teaches advanced concepts '''===

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T22:20:25Z

Sbhatia2: /* '''Likes''' */

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed and practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T22:19:28Z

Sbhatia2: /* '''Likes''' */

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn, the author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed yet practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T22:18:41Z

Sbhatia2: /* '''Review''' */

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits and limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed yet practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:37:40Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding 
Also provides Use case templates 
Discusses benefits and limitations of use cases. 
Provides good references and External links. 

==='''Drawbacks'''===
Information maybe incorrect/ old 
No examples are provided to ease learning. 

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases. 
Provides a more detailed yet practical view of Use Case usage. 
Describes scenarios and howto control Scenario explosion 
Also talks about cases where goal-phrase structure can be used 
Identifies shortcomings of Use Case 

==='''Drawbacks'''===
Maybe too much information for some people. 
Text is difficult to understand and read. 
Text is not formatted, to make it visually appealing 

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:36:49Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding
Also provides Use case templates
Discusses benefits and limitations of use cases.
Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

==='''Drawbacks'''===
Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:36:37Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==Webpage [http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]==

==='''Likes'''===
Provides good basic understanding
Also provides Use case templates
Discusses benefits and limitations of use cases.
Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

==='''Drawbacks'''===
Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:36:16Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

==Webpage: Use case Wikipedia==
[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]

==='''Likes'''===
Provides good basic understanding
Also provides Use case templates
Discusses benefits and limitations of use cases.
Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

==[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]==

==='''Likes'''===
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

==='''Drawbacks'''===
Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:35:17Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]

==='''Likes'''===
Provides good basic understanding
Also provides Use case templates
Discusses benefits and limitations of use cases.
Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]

==='''Likes'''===
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

==='''Drawbacks'''===
Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

==='''Review'''===
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:34:40Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]

==='''Likes'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:30:29Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

#[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]

==='''Likes'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

#[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:30:04Z

Sbhatia2:

=='''Assignment'''==
''Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview. ''

[http://en.wikipedia.org/wiki/Use_case Use case Wikipedia]

==='''Likes'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

==='''Drawbacks'''===
Information maybe incorrect/ old
No examples are provided to ease learning.

==='''Review'''===
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:26:41Z

Sbhatia2:

==Assignment'''==
Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview.

[Use case Wikipedia en.wikipedia.org/wiki/Use_case]

==='''Likes:'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

Drawbacks:
Information maybe incorrect/ old
No examples are provided to ease learning.

Review:
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals Structuring use cases with goals – AC ]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:26:24Z

Sbhatia2:

==Assignment'''==
Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview.

[Use case Wikipedia en.wikipedia.org/wiki/Use_case]

==='''Likes:'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

Drawbacks:
Information maybe incorrect/ old
No examples are provided to ease learning.

Review:
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[[Structuring use cases with goals – AC http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals]]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:26:11Z

Sbhatia2:

==Assignment'''==
Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview.

[Use case Wikipedia en.wikipedia.org/wiki/Use_case]

==='''Likes:'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

Drawbacks:
Information maybe incorrect/ old
No examples are provided to ease learning.

Review:
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[Structuring use cases with goals – AC http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:22:05Z

Sbhatia2:

==Assignment'''==
Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview.

[Use case Wikipedia en.wikipedia.org/wiki/Use_case]

==='''Likes:'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

Drawbacks:
Information maybe incorrect/ old
No examples are provided to ease learning.

Review:
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[Structuring use cases with goals – AC http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.

CSC/ECE 517 Fall 2007/wiki2 4 dj

2007-10-23T18:21:50Z

Sbhatia2:

==Assignment'''==
Use cases. There are even more pages on the Web on use cases than on MVC. If someone wants to learn about them, 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 use-case sites on the Web. Which are best for learning about the concept? Which have the most instructive examples? Which teach advanced concepts that are not apparent in perusing most use-case sites? Read at least several dozen pages before deciding how to organize your overview.

[en.wikipedia.org/wiki/Use_case Use case Wikipedia]

==='''Likes:'''===
#Provides good basic understanding
#Also provides Use case templates
#Discusses benefits and limitations of use cases.
#Provides good references and External links.

Drawbacks:
Information maybe incorrect/ old
No examples are provided to ease learning.

Review:
Wikipedia, the most common information source, seems to carry lot of information on Use Cases and also goes into discussing their benefits an limitations. The page also provides references and external links

[Structuring use cases with goals – AC http://alistair.cockburn.us/index.php/Structuring_use_cases_with_goals]

Likes:
Written by Alistair Cockburn. The author of Jolt Productivity Award winning book Writing Effective Use Cases.
Provides a more detailed yet practical view of Use Case usage.
Describes scenarios and howto control Scenario explosion
Also talks about cases where goal-phrase structure can be used
Identifies shortcomings of Use Case

Maybe too much information for some people.
Text is difficult to understand and read.
Text is not formatted, to make it visually appealing

Review
A very good page written, by a well known person on Use cases. The page has been written in a very informal tone and contains more information than the space. However, the page is not properly formatted which desont make reading it very intresting.