SOLID (2/5) - Open Close Principle

In object-oriented programming, the open–closed principle states "software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification"; that is, such an entity can allow its behaviour to be extended without modifying its source code.

using System;

namespace Invoice
{
    public abstract class Invoice
    {
        public virtual double GetInvoiceDiscount(double amount)
        {
            return amount - 10;
        }
    }
    
    public class FinalInvoice : Invoice
    {
        public override double GetInvoiceDiscount(double amount)
        {
            return base.GetInvoiceDiscount(amount) - 50;
        }
    }
    public class ProposedInvoice : Invoice
    {
        public override double GetInvoiceDiscount(double amount)
        {
            return base.GetInvoiceDiscount(amount) - 40;
        }
    }
    public class RecurringInvoice : Invoice
    {
        public override double GetInvoiceDiscount(double amount)
        {
            return base.GetInvoiceDiscount(amount) - 30;
        }
    }

    class Program
    {
        static void Main(string[] args)
        {
            Invoice FInvoice = new FinalInvoice();
            Invoice PInvoice = new ProposedInvoice();
            Invoice RInvoice = new RecurringInvoice();

            double FInvoiceAmount = FInvoice.GetInvoiceDiscount(10000);
            double PInvoiceAmount = PInvoice.GetInvoiceDiscount(10000);
            double RInvoiceAmount = RInvoice.GetInvoiceDiscount(10000);

            Console.WriteLine($"FinalInvoice value: {FInvoiceAmount}");
            Console.WriteLine($"ProposedInvoice value: {PInvoiceAmount}");
            Console.WriteLine($"RecurringInvoice value: {RInvoiceAmount}");
        }
    }
}

Comments

C# Extension Methods

C# Extension Methods Extension methods public static class ExtensionMethods { public static Stopwatch Measure ( this Func < int > f ) { var sw = new Stopwatch (); sw . Start (); f (); sw . Stop (); return sw ; } public static void Save ( this ISerializable s...

SOLID (4/5) - Interface segregation principle

Interface segregation principle In the field of software engineering, the interface-segregation principle (ISP) states that no client should be forced to depend on methods it does not use. ISP splits interfaces that are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them. Such shrunken interfaces are also called role interfaces. ISP is intended to keep a system decoupled and thus easier to refactor, change, and redeploy. using System ; namespace interfacesegregation { public class Document { } public interface IMachine { void Print ( Document d ); void Scan ( Document d ); ...

SOLID (1/5) - Single Resposibility Principle

SOLID (1/5) - Single Resposibility Principle The single-responsibility principle (SRP) is a computer-programming principle that states that every class in a computer program should have responsibility over a single part of that program's functionality, which it should encapsulate. All of that module, class or function's services should be narrowly aligned with that responsibility. In the following example we have a TodoList class which only handles it's own functionality logic, and then we have a Persistance class which handles the saving logic, hence keeping the concerns separeted. using System ; using System . Collections . Generic ; namespace Journal { public class TodoList { private readonly List < string > _entries = new List < string >(); private...

bebop.code

Search This Blog