Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:59:36Z

Acbrady: /* Protected Variations Pattern */

File:MedicalResults.PNG

2010-12-01T02:58:32Z

Acbrady:

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:58:22Z

Acbrady: /* example 2 */

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:41:59Z

Acbrady: /* Document Plugin */

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:41:49Z

Acbrady: /* Document Plugin */

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:39:07Z

Acbrady: /* Protected Variations Pattern */

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:27:58Z

Acbrady: /* Document Plugin */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===Document Plugin===
Consider the example of an editor that is designed to open and edit different file types. The document type can be implemented as a type in the core application and document plugins can be designed to implement the interface for specific document types.

[[Image:DocPlugin.PNG]]

In this case, the Protected Variations pattern is similar to the Adapter pattern.

===example 2===
•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

File:DocPlugin.PNG

2010-12-01T02:25:09Z

Acbrady:

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:23:54Z

Acbrady: /* Document Plugin */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===Document Plugin===
Consider the example of an editor that is designed to open and edit different file types. The document type can be implemented as a type in the core application and document plugins can be designed to implement the interface for specific document types.

[[Image:DocPlugin.png]]

In this case, the Protected Variations pattern is similar to the Adapter pattern.

===example 2===
•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:23:31Z

Acbrady: /* Document Plugin */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===Document Plugin===
Consider the example of an editor that is designed to open and edit different file types. The document type can be implemented as a type in the core application and document plugins can be designed to implement the interface for specific document types.

[[Image:DocPlugin.png]]
[[Image:CVCSvsDVCS.png |center| Distributed VCS versus Centralized CVS]]

In this case, the Protected Variations pattern is similar to the Adapter pattern.

===example 2===
•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:22:39Z

Acbrady: /* Examples */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===Document Plugin===
Consider the example of an editor that is designed to open and edit different file types. The document type can be implemented as a type in the core application and document plugins can be designed to implement the interface for specific document types.

[[Image:DocPlugin.jpg]]

In this case, the Protected Variations pattern is similar to the Adapter pattern.

===example 2===
•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:20:44Z

Acbrady: /* Examples */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===Document Plugin===
Consider the example of an editor that is designed to open and edit different file types. The document type can be implemented as a type in the core application and document plugins can be designed to implement the interface for specific document types.

In this case, the Protected Variations pattern is similar to the Adapter pattern.

===example 2===
•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:15:18Z

Acbrady: /* Examples */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===example 1===
In this case, the Protected Variations pattern is similar to the Adapter pattern.

===example 2===
•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:11:53Z

Acbrady: /* Description */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. It is very broad in its scope. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===eee===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:11:16Z

Acbrady: /* example 1 */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===eee===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:10:37Z

Acbrady: /* Description */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]] The variations that are addressed could be data type, data format, different calculations, different object types, etc.

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T02:09:06Z

Acbrady: /* Advantages */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]]

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations of a particular module to handle a specific variation can be added to the software without impacting client software.[[#References|[3]]]

•Coupling between different parts of the software system are lowered.[[#References|[3]]][[#References|[4]]]

•The cost of changes to the system can be lowered by ensuring that new variations can be supported by only adding a new implementation of the interface.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:59:28Z

Acbrady: /* Advantages */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]]

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|[3]]]

•Coupling is lowered.[[#References|[3]]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|[4]]]

•The impact of cost of changes can be lowered.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:58:48Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are present in the programming languages for similar reasons as the Protected Variations pattern.[[#References|[3]]]

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

•The impact of cost of changes can be lowered.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:57:42Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are similar in nature to the Protected Variations pattern.[[#References|[3]]]

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

•The impact of cost of changes can be lowered.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==
• Increases the complexity of the design by requiring the interface and implementations to be separate

• Forces the programmer to spend extra development time during initial programming development to ensure that the interface is generic enough to handle future implementations

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:54:59Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are similar in nature to the Protected Variations pattern.[[#References|[3]]]

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

•The impact of cost of changes can be lowered.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:54:35Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

The basic object-oriented programming concepts of data encapsulation, interfaces, and polymorphism are all mechanisms that are similar in nature to the Protected Variations pattern.[[#References|[3]]]

==Examples==
===example 1===

===example 2===

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

•The impact of cost of changes can be lowered.[[#References|[3]]]

•Extensions required for new variations are easy to add.[[#References|[3]]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:46:40Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Extensions required for new variations are easy to add.

•The impact of cost of changes can be lowered.

[[#References|3]]

==Examples==
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.[[#References|[3]]]

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:46:02Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Extensions required for new variations are easy to add.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Examples==
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.[[#References|[3]]]

•Externalizing properties in a property file is another example of PV.[[#References|[3]]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:44:17Z

Acbrady: /* Description */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type.[[#References|[2]]] The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:43:23Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type. The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|[1]]]

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:42:49Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern]. Any object that presents a potential instability within the system due to variations of type is implemented with an interface and [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) is used to wrap the type. The interface could be a small enough to cover only one method or a very broad piece of the total subsystem.[[#References|1]]

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:30:57Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]
•Coupling is lowered.[[#References|3]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:29:40Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•Coupling is lowered.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Advantages==
•New implementations can be introduced without affecting clients.[[#References|3]]

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T01:05:41Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•New implementations can be introduced without affecting clients.

•Coupling is lowered.

•The impact of cost of changes can be lowered.

[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Advantages==

==Disadvantages==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T00:06:05Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=

__TOC__

==Description==
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•New implementations can be introduced without affecting clients.

•Coupling is lowered.

•The impact of cost of changes can be lowered.

•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-12-01T00:05:09Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.

•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.

•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.

•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.

•Externalizing properties in a property file is another example of PV.

•Extensions required for new variations are easy to add.

•New implementations can be introduced without affecting clients.

•Coupling is lowered.

•The impact of cost of changes can be lowered.

•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:25:54Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] (discussed in chapter 3) to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.
•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.
•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.
•Externalizing properties in a property file is another example of PV.
•Extensions required for new variations are easy to add.
•New implementations can be introduced without affecting clients.
•Coupling is lowered.
•The impact of cost of changes can be lowered.
•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:25:09Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch3_3i_ls#Polymorphism_and_types polymorphism] to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.
•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.
•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.
•Externalizing properties in a property file is another example of PV.
•Extensions required for new variations are easy to add.
•New implementations can be introduced without affecting clients.
•Coupling is lowered.
•The impact of cost of changes can be lowered.
•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:24:31Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using [/ch3_3i_ls#Polymorphism_and_types polymorphism] to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.
•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.
•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.
•Externalizing properties in a property file is another example of PV.
•Extensions required for new variations are easy to add.
•New implementations can be introduced without affecting clients.
•Coupling is lowered.
•The impact of cost of changes can be lowered.
•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:23:28Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism[ch3_3i_ls#Polymorphism_and_types] to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.
•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.
•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.
•Externalizing properties in a property file is another example of PV.
•Extensions required for new variations are easy to add.
•New implementations can be introduced without affecting clients.
•Coupling is lowered.
•The impact of cost of changes can be lowered.
•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:19:03Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface.[[#References|2]]

•Problem: How to design objects, subsystems and systems so that the variations or instability in these elements does not have an undesirable impact on other elements.
•Solution: Identify points of predicted variation or instability; assign responsibilities to create a stable interface (or protection mechanism) around them.
•Data encapsulation, interfaces, polymorphism, indirection and standards are motivated by PV.
•Technology like Service Lookup is an example of PV because clients are protected from variations in the location of services using the lookup service.
•Externalizing properties in a property file is another example of PV.
•Extensions required for new variations are easy to add.
•New implementations can be introduced without affecting clients.
•Coupling is lowered.
•The impact of cost of changes can be lowered.
•Related patterns are most of the GoF.[[#References|3]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:18:16Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface.[[#References|2]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:17:25Z

Acbrady: /* Section 1 */

=Protected Variations Pattern=
The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

Protected Variations addresses the problem of assigning responsibilities in such a way that variations that might occur do not have undesirable effects upon other elements in the system.
The solution is to identify the points of predicted variation or instability and assign responsibilities to create a stable interface around them. In this case, interface is used in the broadest sense. It might be a complete subsystem fronting a much larger set of variable subsystem.This pattern, or rule, is very broad and complex. There is an assigned reading that goes into depth on the topic. We will examine this pattern from the discussion of the reading.[[#References|1]]

Protected Variations decouples clients from the changes in the system being
used.[[#References|4]]

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

[4] Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition). Prentice Hall, Upper Saddle River, NJ, 2004

==TO BE REMOVED (included for development reference only)==
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

ACM books
Authors. Title. Publisher, City of Publication, Year of Publication.

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:15:25Z

Acbrady: /* Protected Variations Pattern */

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:12:19Z

Acbrady: /* Protected Variations Pattern */

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T18:09:13Z

Acbrady:

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:47:42Z

Acbrady:

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:46:10Z

Acbrady: /* References */

=Protected Variations Pattern=
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

==TO BE REMOVED (included for development reference only)==
Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:45:50Z

Acbrady: /* References */

=Protected Variations Pattern=
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

==Section 2==

==References==
[1] http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html
[2] http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations
[3] http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

==TO BE REMOVED (included for development reference only)==
Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:45:02Z

Acbrady:

=Protected Variations Pattern=
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

==Section 2==

==References==
http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html
http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations
http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

==TO BE REMOVED (included for development reference only)==
Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:39:11Z

Acbrady:

=Protected Variations Pattern=
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

The Protected Variations pattern is a specific example of a [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] [http://en.wikipedia.org/wiki/Design_pattern_(computer_science) design pattern].

__TOC__

==Section 1==

==Section 2==

==Section 3==

http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:36:24Z

Acbrady: /* Protected Variations Pattern */

=Protected Variations Pattern=
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

The Protected Variations pattern is one of the [http://en.wikipedia.org/wiki/GRASP_(object-oriented_design) GRASP] design patterns.

__TOC__

==Section 1==

==Section 2==

==Section 3==

http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-30T17:20:00Z

Acbrady:

=Protected Variations Pattern=
7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

__TOC__

==Section 1==

==Section 2==

==Section 3==

http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?

CSC/ECE 517 Fall 2010/ch7 7e ab

2010-11-29T19:27:13Z

Acbrady:

Protected Variations pattern

7e. Protected Variations pattern. This is one of the GRASP patterns. Wikipedia: The Protected Variations pattern protects elements from the variations on other elements (objects, systems, subsystems) by wrapping the focus of instability with an interface and using polymorphism to create various implementations of this interface. Describe the pattern, and give examples of its use.

http://web.cs.wpi.edu/~gpollice/cs4233-a05/CourseNotes/maps/class4/ProtectedVariations.html

http://en.wikipedia.org/wiki/GRASP_(object-oriented_design)#Protected_Variations

http://www.objectsbydesign.com/books/larman_notes/6-DesignAndImplementationTechniques.html

Originality. Chapter is not constructed by copy-and-paste, but rather is the writer's own work. Nor does it duplicate the organization of Wikipedia's article, or any other description of the topic. Rather, it should be presented in a way that differs from each of the sources.

Clarity. The language should be simple and basic. Sentences should be short enough to be understood by a student in this class without rereading. Jargon should be avoided, except for technical terms that are introduced before being used. For a more technical treatment, the reader should be referred to appropriate sources.

Coverage. All relevant material should be discussed, at about the same level of detail. If it is too involved, it is OK to reference external sources, but the entire chapter should not consist of references. Earlier sections should not be covered in more depth than later sections.

Organization. The chapter should begin with an overview suitable for readers who are new to the topic, and proceed from simpler material to more involved. The progression should be logical, and should not jump from one topic to another without transition.

Definitions. Definitions should be clear and concise, and should be supported by explanations or examples. Definitions should be just that--not descriptions. Definitions should should be composed by the author, not taken from other textbooks.

Examples. Examples should be clear, succinct, and unambiguous. Diagrams and realistic examples are encouraged, but diagrams need to be explained with accompanying text.

Citations. All major concepts should have citations to more detailed treatments. Citations should include a good mix of sources, such as Web sites, scientific papers, and books. Citations should be in a common format, such as ACM reference format; do not use just a Web link without any title or author.

Diagrams. If the coverage of this topic would benefit from diagrams, are sufficient diagrams included? Are they easily understandable and well explained?

Flow. Chapters should build on--and reference--earlier chapters. Coverage in this chapter should not duplicate earlier chapters, but use hyperlinks to refer to those earlier sections.

Accuracy. Is the information in this chapter consistent with other descriptions of the same material? Can any errors be identified? Is information purported to be factual indeed a matter of fact rather than opinion?