CSC/ECE 517 Fall 2011/ch7 7d df - Revision history

Dgfleisc at 20:00, 12 December 2011

2011-12-12T20:00:04Z

@@ Line 23: / Line 23: @@
 ===Call Super===
-Call Super is similar to BaseBean in which one class subclasses another.  The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function.  The fact that this is required makes this an anti-patern.  The solution to this problem is to use the Template Method Pattern.  The Template Method pattern separates the superclass method into two distinct methods.  The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method.  That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden [http://en.wikipedia.org/wiki/Call_super].
+Call Super is similar to BaseBean in which one class subclasses another.  The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function.  The fact that this is required makes this an anti-patern.  The solution to this problem is to use the Template Method Pattern.  The Template Method pattern separates the superclass method into two distinct methods.  The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method.  That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden [http://en.wikipedia.org/wiki/Call_super].  Here is an example:
 ==Programming==

Dgfleisc at 19:39, 12 December 2011

2011-12-12T19:39:57Z

← Older revision		Revision as of 19:39, 12 December 2011
Line 1:		Line 1:
	=~~DesignPatters~~=		=Design Patterns=
	==Introduction==		==Introduction==
	In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, an anti-pattern is considered a bad solution to a problem[http://c2.com/cgi/wiki?AntiPattern]. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlined a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-~~patters~~ can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].		In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, an anti-pattern is considered a bad solution to a problem[http://c2.com/cgi/wiki?AntiPattern]. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlined a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patterns can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].

	==Organizational==		==Organizational==
	Organizational anti-~~patters~~ are those that deal with how the team working on the project is organized and managed. A good example of these types of patterns is the Cash Cow.		Organizational anti-patterns are those that deal with how the team working on the project is organized and managed. A good example of these types of patterns is the Cash Cow.
	===Cash Cow===		===Cash Cow===
	A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them [http://en.wikipedia.org/wiki/Cash_cow].		A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them [http://en.wikipedia.org/wiki/Cash_cow].
Line 18:		Line 18:

	==Software Design==		==Software Design==
	Software design anti-~~patters~~ are anti-patterns that deal with the overall design of a program. They deal more with how the object in a program fit together rather than the actual code itself. Some examples of Software Design anti-~~patters~~ are BaseBean and Call Super.		Software design anti-patterns are anti-patterns that deal with the overall design of a program. They deal more with how the object in a program fit together rather than the actual code itself. Some examples of Software Design anti-patterns are BaseBean and Call Super.
	===BaseBean===		===BaseBean===
	A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the child class to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation [http://en.wikipedia.org/wiki/BaseBean].		A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the child class to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation [http://en.wikipedia.org/wiki/BaseBean].
Line 26:		Line 26:

	==Programming==		==Programming==
	Anti-patterns that fall under this category are ones that deal with how the code is implemented rather than how the code fits together. Some examples of these ~~patters~~ are Blind Faith, Law of Instrument, Cut and Paste, and God Object.		Anti-patterns that fall under this category are ones that deal with how the code is implemented rather than how the code fits together. Some examples of these patterns are Blind Faith, Law of Instrument, Cut and Paste, and God Object.
	===Blind Faith===		===Blind Faith===
	Bild Faith occurs when a bug is fixed in a program but never tested before released. The programmer just assumes the fix will work so does not bother to test it. This can be detrimental if a bug did end up in the code that was "fixed" [http://en.wikipedia.org/wiki/Blind_faith_(computer_science)]. A solution to this problem is Test-Driven Development. In Test-Driven Development, the test cases are written before the code. This ensures that all code is tested and that Blind Faith can not occur [http://en.wikipedia.org/wiki/Test-driven_development].		Bild Faith occurs when a bug is fixed in a program but never tested before released. The programmer just assumes the fix will work so does not bother to test it. This can be detrimental if a bug did end up in the code that was "fixed" [http://en.wikipedia.org/wiki/Blind_faith_(computer_science)]. A solution to this problem is Test-Driven Development. In Test-Driven Development, the test cases are written before the code. This ensures that all code is tested and that Blind Faith can not occur [http://en.wikipedia.org/wiki/Test-driven_development].

Dgfleisc at 19:17, 12 December 2011

2011-12-12T19:17:20Z

← Older revision		Revision as of 19:17, 12 December 2011
Line 1:		Line 1:
	=DesignPatters=		=DesignPatters=
	==Introduction==		==Introduction==
	In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, an anti-pattern is considered a bad solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlined a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].		In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, an anti-pattern is considered a bad solution to a problem[http://c2.com/cgi/wiki?AntiPattern]. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlined a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].

	==Organizational==		==Organizational==
Line 40:		Line 40:

	==References==		==References==
	[1] http://en.wikipedia.org/wiki/Anti-pattern <br />		[1] http://c2.com/cgi/wiki?AntiPattern <br/>
	[2] http://en.wikipedia.org/wiki/Cash_cow <br />		[2] http://en.wikipedia.org/wiki/Anti-pattern <br />
	[3] http://en.wikipedia.org/wiki/Overengineering <br />		[3] http://en.wikipedia.org/wiki/Cash_cow <br />
	[4] http://en.wikipedia.org/wiki/Software_bloat <br />		[4] http://en.wikipedia.org/wiki/Overengineering <br />
	[5] http://en.wikipedia.org/wiki/BaseBean <br />		[5] http://en.wikipedia.org/wiki/Software_bloat <br />
	[6] http://en.wikipedia.org/wiki/Call_super <br />		[6] http://en.wikipedia.org/wiki/BaseBean <br />
	[7] http://en.wikipedia.org/wiki/Blind_faith_(computer_science) <br />		[7] http://en.wikipedia.org/wiki/Call_super <br />
	[8] http://en.wikipedia.org/wiki/Test-driven_development <br />		[8] http://en.wikipedia.org/wiki/Blind_faith_(computer_science) <br />
	[9] http://en.wikipedia.org/wiki/Golden_hammer <br/>		[9] http://en.wikipedia.org/wiki/Test-driven_development <br />
	[10] http://sourcemaking.com/antipatterns/cut-and-paste-programming <br />		[10] http://en.wikipedia.org/wiki/Golden_hammer <br/>
	[11] http://blog.decayingcode.com/post/anti-pattern-god-object.aspx <br />		[11] http://sourcemaking.com/antipatterns/cut-and-paste-programming <br />
			[12] http://blog.decayingcode.com/post/anti-pattern-god-object.aspx <br />

Dgfleisc at 19:15, 12 December 2011

2011-12-12T19:15:40Z

← Older revision		Revision as of 19:15, 12 December 2011
Line 1:		Line 1:
	=DesignPatters=		=DesignPatters=
	==Introduction==		==Introduction==
	In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, ~~and~~ anti-pattern is considered a bad solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had ~~outlines~~ a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].		In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, an anti-pattern is considered a bad solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlined a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].

			==Organizational==
			Organizational anti-patters are those that deal with how the team working on the project is organized and managed. A good example of these types of patterns is the Cash Cow.
	===Cash Cow===		===Cash Cow===
	A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them [http://en.wikipedia.org/wiki/Cash_cow].		A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them [http://en.wikipedia.org/wiki/Cash_cow].

			==Project Management==
			Project Management anti-patterns are anti-patterns that deal with how the programmers and the whole team in general work together to complete the project at hand. Some examples of this are Over Engineering and Software Bloat.

	===Over Engineering===		===Over Engineering===
Line 12:		Line 17:
	Software Bloating happens when after every new release of a piece of software, more and more features are added that are not necessarily used by the consumer or stray from the original purpose of the program. These features use more computer resources and can ultimately slow down the program. Also, not every user will use all of the features, causing in some cases unnecessary slowdown of the program. A good example of Software Bloating is Apple's iTunes. iTunes was originally created to simply download and play music. Now, iTunes can do so much more to the point where the features are detracting from the original functions. A good alternative to software bloating is the use of plugins. Plugins add extra functionality to a program without forcing the user to have it. This way a user can pick and choose which extra features he or she wants [http://en.wikipedia.org/wiki/Software_bloat].		Software Bloating happens when after every new release of a piece of software, more and more features are added that are not necessarily used by the consumer or stray from the original purpose of the program. These features use more computer resources and can ultimately slow down the program. Also, not every user will use all of the features, causing in some cases unnecessary slowdown of the program. A good example of Software Bloating is Apple's iTunes. iTunes was originally created to simply download and play music. Now, iTunes can do so much more to the point where the features are detracting from the original functions. A good alternative to software bloating is the use of plugins. Plugins add extra functionality to a program without forcing the user to have it. This way a user can pick and choose which extra features he or she wants [http://en.wikipedia.org/wiki/Software_bloat].

			==Software Design==
			Software design anti-patters are anti-patterns that deal with the overall design of a program. They deal more with how the object in a program fit together rather than the actual code itself. Some examples of Software Design anti-patters are BaseBean and Call Super.
	===BaseBean===		===BaseBean===
	A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the child class to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation [http://en.wikipedia.org/wiki/BaseBean].		A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the child class to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation [http://en.wikipedia.org/wiki/BaseBean].
Line 18:		Line 25:
	Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden [http://en.wikipedia.org/wiki/Call_super].		Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden [http://en.wikipedia.org/wiki/Call_super].

			==Programming==
			Anti-patterns that fall under this category are ones that deal with how the code is implemented rather than how the code fits together. Some examples of these patters are Blind Faith, Law of Instrument, Cut and Paste, and God Object.
	===Blind Faith===		===Blind Faith===
	Bild Faith occurs when a bug is fixed in a program but never tested before released. The programmer just assumes the fix will work so does not bother to test it. This can be detrimental if a bug did end up in the code that was "fixed" [http://en.wikipedia.org/wiki/Blind_faith_(computer_science)]. A solution to this problem is Test-Driven Development. In Test-Driven Development, the test cases are written before the code. This ensures that all code is tested and that Blind Faith can not occur [http://en.wikipedia.org/wiki/Test-driven_development].		Bild Faith occurs when a bug is fixed in a program but never tested before released. The programmer just assumes the fix will work so does not bother to test it. This can be detrimental if a bug did end up in the code that was "fixed" [http://en.wikipedia.org/wiki/Blind_faith_(computer_science)]. A solution to this problem is Test-Driven Development. In Test-Driven Development, the test cases are written before the code. This ensures that all code is tested and that Blind Faith can not occur [http://en.wikipedia.org/wiki/Test-driven_development].
Line 23:		Line 32:
	===Law of Instrument===		===Law of Instrument===
	THe Law of Instrument or golden hammer refers to the overuse of a good tool. The well known phrase "if all you have is a hammer, everything looks like a nail" is derived from this law. A good example of this would be a programmer writing all of his programs in the Java programming language. Java is a great tool but is not suited for writing all programs. The fix for this would be the opposite: Use the right tool for the job [http://en.wikipedia.org/wiki/Golden_hammer].		THe Law of Instrument or golden hammer refers to the overuse of a good tool. The well known phrase "if all you have is a hammer, everything looks like a nail" is derived from this law. A good example of this would be a programmer writing all of his programs in the Java programming language. Java is a great tool but is not suited for writing all programs. The fix for this would be the opposite: Use the right tool for the job [http://en.wikipedia.org/wiki/Golden_hammer].

			===Cut and Paste===
			The Cut and Paste anti-pattern deals with the programmer cutting and pasting code from one section to another and then altering it. The problem with this is duplication of code. Although copy and paste seems like an easier and quicker way to add certain functionality to your program, it could end up making your code run slower. This pattern goes against the DRY principle. The refactored approach is to use a black box reuse design. Black Box reuse does not allow the user to change how the code is implemented. They can only interact with it the way it was intended [http://sourcemaking.com/antipatterns/cut-and-paste-programming].

			===God Object===
			This anti-pattern is when one class does too much. Classes and methods should only have one method or purpose. If it has more than that, it goes against the single responsibility principal. The solution to this is to refactor the code. Try and break up the code into the individual responsibilities and create new classes for them[http://blog.decayingcode.com/post/anti-pattern-god-object.aspx].

	==References==		==References==
Line 34:		Line 49:
	[8] http://en.wikipedia.org/wiki/Test-driven_development <br />		[8] http://en.wikipedia.org/wiki/Test-driven_development <br />
	[9] http://en.wikipedia.org/wiki/Golden_hammer <br/>		[9] http://en.wikipedia.org/wiki/Golden_hammer <br/>
			[10] http://sourcemaking.com/antipatterns/cut-and-paste-programming <br />
			[11] http://blog.decayingcode.com/post/anti-pattern-god-object.aspx <br />

Dgfleisc at 06:08, 2 December 2011

2011-12-02T06:08:15Z

← Older revision		Revision as of 06:08, 2 December 2011
Line 1:		Line 1:
	=DesignPatters=		=DesignPatters=
	==Introduction==		==Introduction==
	In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a bad solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlines a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist.		In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a bad solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlines a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist [http://en.wikipedia.org/wiki/Anti-pattern].

	~~==Organizational Anti-Patterns==~~
	===Cash Cow===		===Cash Cow===
	A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them.		A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them [http://en.wikipedia.org/wiki/Cash_cow].

	~~==Project Management==~~
	===Over Engineering===		===Over Engineering===
	Over Engineering is when a product is made more complex than is practical. This results in a waste of time and resources. For instance, a push lawnmower with 100 HP would be a product of over engineering. A lawnmower with a tenth of that power would work just as well without all the time and money spent upping the Horse Power.		Over Engineering is when a product is made more complex than is practical. This results in a waste of time and resources. For instance, a push lawnmower with 100 HP would be a product of over engineering. A lawnmower with a tenth of that power would work just as well without all the time and money spent upping the Horse Power [http://en.wikipedia.org/wiki/Overengineering].

			===Software Bloat===
			Software Bloating happens when after every new release of a piece of software, more and more features are added that are not necessarily used by the consumer or stray from the original purpose of the program. These features use more computer resources and can ultimately slow down the program. Also, not every user will use all of the features, causing in some cases unnecessary slowdown of the program. A good example of Software Bloating is Apple's iTunes. iTunes was originally created to simply download and play music. Now, iTunes can do so much more to the point where the features are detracting from the original functions. A good alternative to software bloating is the use of plugins. Plugins add extra functionality to a program without forcing the user to have it. This way a user can pick and choose which extra features he or she wants [http://en.wikipedia.org/wiki/Software_bloat].

	~~==Software Design==~~
	~~A Software Design Anti-Pattern is an Anti-Pattern that deals with the big picture of a program and how all the different classes work together.~~
	===BaseBean===		===BaseBean===
	A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the ~~subclass~~ to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation.		A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the child class to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation [http://en.wikipedia.org/wiki/BaseBean].

	===Call Super===		===Call Super===
	Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden.		Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden [http://en.wikipedia.org/wiki/Call_super].

			===Blind Faith===
			Bild Faith occurs when a bug is fixed in a program but never tested before released. The programmer just assumes the fix will work so does not bother to test it. This can be detrimental if a bug did end up in the code that was "fixed" [http://en.wikipedia.org/wiki/Blind_faith_(computer_science)]. A solution to this problem is Test-Driven Development. In Test-Driven Development, the test cases are written before the code. This ensures that all code is tested and that Blind Faith can not occur [http://en.wikipedia.org/wiki/Test-driven_development].

			===Law of Instrument===
			THe Law of Instrument or golden hammer refers to the overuse of a good tool. The well known phrase "if all you have is a hammer, everything looks like a nail" is derived from this law. A good example of this would be a programmer writing all of his programs in the Java programming language. Java is a great tool but is not suited for writing all programs. The fix for this would be the opposite: Use the right tool for the job [http://en.wikipedia.org/wiki/Golden_hammer].

	==~~programming~~==		==References==
			[1] http://en.wikipedia.org/wiki/Anti-pattern <br />
			[2] http://en.wikipedia.org/wiki/Cash_cow <br />
			[3] http://en.wikipedia.org/wiki/Overengineering <br />
			[4] http://en.wikipedia.org/wiki/Software_bloat <br />
			[5] http://en.wikipedia.org/wiki/BaseBean <br />
			[6] http://en.wikipedia.org/wiki/Call_super <br />
			[7] http://en.wikipedia.org/wiki/Blind_faith_(computer_science) <br />
			[8] http://en.wikipedia.org/wiki/Test-driven_development <br />
			[9] http://en.wikipedia.org/wiki/Golden_hammer <br/>

Dgfleisc at 04:56, 2 December 2011

2011-12-02T04:56:29Z

← Older revision		Revision as of 04:56, 2 December 2011
Line 1:		Line 1:
	=DesignPatters=		=DesignPatters=
	==Introduction==		==Introduction==
	In Software Engineering, Anti-~~Patters are~~ a ~~class~~ of ~~patterns~~ that may appear to ~~improve code at first~~ but ~~end~~ up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a ~~<i>~~bad~~</i>~~ solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four ~~but was~~ not commonplace until the book, AntiPatterns. In the book, the authors had ~~written about many bad design decisions they had seen used over and over~~ in the workplace. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Listed below are ~~some~~ of the ~~most common anti~~-~~patterns~~.		In Software Engineering, an Anti-Pattern is a type of pattern that, at first, may appear to solve a problem but ends up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a bad solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four. However, the term did not become commonplace until after the book, AntiPatterns, came out. In the book, the authors had outlines a few patterns that were fairly common in the workplace that they saw as an anti-pattern. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Anti-Patterns can be found not only in programming but a number of different areas in the design process. Because of this, anti-patters can fall into different groups such as Organizational, Project Management, Software Design, and Programming. Listed below are a select few of the many Anti-Patterns that exist.

	==~~BaseBean~~==		==Organizational Anti-Patterns==
	A ~~BaseBean~~ is ~~an object where concrete entities have subclassed it~~. ~~As you~~ may ~~know from class~~, ~~subclassing does not always exhibit good program design~~. ~~Subclassing causes~~ the ~~subclass to rely too heavily on~~ the ~~superclass~~. If the ~~super class were to change~~, ~~it could break something in~~ the ~~subclass~~. A ~~class should not subclass another class just because there is similar code~~. ~~Rather~~, the ~~classes should interact using delegation~~.		===Cash Cow===
			A Cash Cow is a product that makes up the majority of a companies profits. The problem with Cash Cows is they may be making a great deal of money for the money now, but may later fall out of popularity due to newer or better technology. The sheer popularity of the product can sometimes hinder the development of newer alternatives. Take for example the company RIM, the maker of the BlackBerry line of smartphones. A couple years ago RIM's BlackBerry smartphones were considered cash cows. RIM was dominating the market. Over the years, new players have come into the market with revolutionary ideas and have been slowly eating away at RIMs marketshare. During this same time, BlackBerry smartphones have changed little. Their management had been blinded by the sheer success of their products that they allowed others to come in and take that success away from them.

	==Call Super==		==Project Management==
			===Over Engineering===
			Over Engineering is when a product is made more complex than is practical. This results in a waste of time and resources. For instance, a push lawnmower with 100 HP would be a product of over engineering. A lawnmower with a tenth of that power would work just as well without all the time and money spent upping the Horse Power.

			==Software Design==
			A Software Design Anti-Pattern is an Anti-Pattern that deals with the big picture of a program and how all the different classes work together.
			===BaseBean===
			A BaseBean is a class where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the subclass to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation.

			===Call Super===
	Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden.		Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden.

			==programming==

Dgfleisc at 13:59, 1 December 2011

2011-12-01T13:59:34Z

← Older revision		Revision as of 13:59, 1 December 2011
Line 2:		Line 2:
	==Introduction==		==Introduction==
	In Software Engineering, Anti-Patters are a class of patterns that may appear to improve code at first but end up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a <i>bad</i> solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four but was not commonplace until the book, AntiPatterns. In the book, the authors had written about many bad design decisions they had seen used over and over in the workplace. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Listed below are some of the most common anti-patterns.		In Software Engineering, Anti-Patters are a class of patterns that may appear to improve code at first but end up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a <i>bad</i> solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four but was not commonplace until the book, AntiPatterns. In the book, the authors had written about many bad design decisions they had seen used over and over in the workplace. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Listed below are some of the most common anti-patterns.

			==BaseBean==
			A BaseBean is an object where concrete entities have subclassed it. As you may know from class, subclassing does not always exhibit good program design. Subclassing causes the subclass to rely too heavily on the superclass. If the super class were to change, it could break something in the subclass. A class should not subclass another class just because there is similar code. Rather, the classes should interact using delegation.

			==Call Super==
			Call Super is similar to BaseBean in which one class subclasses another. The different is, in Call Super, the superclass requires the subclass to override a method in order for it to function. The fact that this is required makes this an anti-patern. The solution to this problem is to use the Template Method Pattern. The Template Method pattern separates the superclass method into two distinct methods. The first method executes all of the needed code by the subclass and then delegates the part that needs to be subclassed into an abstract method. That way the superclass is able to separate out the information that needs to be accessed by the subclass and the method that needs to be overridden.

Dgfleisc: Created page with "=DesignPatters= ==Introduction== In Software Engineering, Anti-Patters are a class of patterns that may appear to improve code at first but end up hindering it in the long run. ..."

2011-12-01T04:41:41Z

Created page with "=DesignPatters= ==Introduction== In Software Engineering, Anti-Patters are a class of patterns that may appear to improve code at first but end up hindering it in the long run. ..."

New page

=DesignPatters=
==Introduction==
In Software Engineering, Anti-Patters are a class of patterns that may appear to improve code at first but end up hindering it in the long run. While a pattern can be looked at as a solution to a problem, and anti-pattern is considered a <i>bad</i> solution to a problem. The name anti-patern was coined by Andrew Koenig in response to the book, Design Patterns, by Gang of Four but was not commonplace until the book, AntiPatterns. In the book, the authors had written about many bad design decisions they had seen used over and over in the workplace. An anti-pattern is not to be confused with bad programming habits. There are two main distinctions between an anti-pattern and bad programming. First, for a bad idea to be an anti-pattern, it has to have some sort of structure and is reusable and second, the anti-pattern has to have a well documented, correct solution. Listed below are some of the most common anti-patterns.