Programming Language: C#
UML Class Diagram Concrete Creator *Factory Methodi) -- The classes and objects participating in the above UML class diagram are as follows: 1. Product This defines the interface of objects the factory method creates 2. Concrete Product This is a class which implements the Product interface. 3. Creator This is an abstract class and declares the factory rehad, which returris an object of type Proxluct. This may also define a default implementation of the factory method that returns i default Concrete Proxect ohject This may call the factory method to create a Product object. 4. Concretcreator This is a class which implernents the Creator class and overrides the factory method to return an instanceola Concrete Product. Now let's understand this with a real world example Assume you bave three different bealthcare plans which are considered here as classes HMO.PPO. Obamacare, all of them implemcut abstract class HealthPlan. You need to instantiatc one of these classes, but you don't know which of them, it depends on the user. This is perfect scenario for the Factory Method design pattern. Each plan should have annual chatye, dexluction inclunt, plan type (TIMO, PPO, Ohmalare). Write a console application that asks the users the healtbcare plan they want to apply and output the information about the plan (plan type, annual charge. and deduction amount). UML Class Diagram Concrete Creator *Factory Methodi) -- The classes and objects participating in the above UML class diagram are as follows: 1. Product This defines the interface of objects the factory method creates 2. Concrete Product This is a class which implements the Product interface. 3. Creator This is an abstract class and declares the factory rehad, which returris an object of type Proxluct. This may also define a default implementation of the factory method that returns i default Concrete Proxect ohject This may call the factory method to create a Product object. 4. Concretcreator This is a class which implernents the Creator class and overrides the factory method to return an instanceola Concrete Product. Now let's understand this with a real world example Assume you bave three different bealthcare plans which are considered here as classes HMO.PPO. Obamacare, all of them implemcut abstract class HealthPlan. You need to instantiatc one of these classes, but you don't know which of them, it depends on the user. This is perfect scenario for the Factory Method design pattern. Each plan should have annual chatye, dexluction inclunt, plan type (TIMO, PPO, Ohmalare). Write a console application that asks the users the healtbcare plan they want to apply and output the information about the plan (plan type, annual charge. and deduction amount)
