Skip to main content

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 static int _count = 0;

        public int AddEntry(string entry)
        {
            _entries.Add($"{++_count} : {entry}");
            return _count;
        }

        public void RemoveEntry(int index)
        {
            _entries.RemoveAt(index);
        }

        public override string ToString()
        {
            return string.Join(Environment.NewLine, _entries);
        }
    }

    public class Persistance
    {
        public void Save(TodoList todoList)
        {
            // saving logic
        }
    }


    class Program
    {
        static void Main(string[] args)
        {
            var todoList = new TodoList();
            todoList.AddEntry("dentist");
            todoList.AddEntry("shopping");
            todoList.AddEntry("wash the car");

            Console.WriteLine(todoList);

            var persistance = new Persistance();
            persistance.Save(todoList);
        }
    }
}

Comments

Popular posts from this blog

Software Development

Software Development Agile Agile is an insurance policy for market changes. By designing your solution according to this methodology, your project remains flexible and is always ready for change. It is always better to correct the mistake early in the process. With this method, you keep your finger on the pulse of a dynamic market and changing user expectations. As a result, you can continuously adapt, change your strategy, and create a product that will be in demand by the target audience, even if preferences have changed during the development process. DevOps DevOps is one more way to optimize the development budget of your application. A key DevOps approach is that this practice and its culture allow team members to better interact with each other and the customer. The software development team and those responsible for the operation of the application share responsibilities clearly, and it helps you avoid shifting responsibilities from one team member to another. DevOps involves th...

Fluent Builder Pattern

Fluent Builder Pattern Gamma Categorization: Creational Design Patten Summary: Extension of the Builder Pattern , that allows us to chain the operation calls. Problem examples We want to chain the operation calls for convenience purposes. Solution The methods now return the class itself. Sample Code Plese refer to the  Builder Pattern  article for the complete code. The main changes are made in the base abstract class of the ReportBuilder. public   abstract   class   ReportBuilder {      protected   Report   report ;      public   ReportBuilder   CreateReport ()     {          report  =  new   Report ();          return   this ;     }       public   ReportBuilder   SetHeader ( string   head...

XML Webservice (ASMX) - SOAP Request and Response Invocation logging

You are an integration developer. Eventualy you came into the state where there is nothing else you can debug, and you have to check which SOAP request it is built on the request, and which SOAP response you are getting from the server. C# XML Webservice (ASMX) - SOAP Request and Response Invocation logging In the legaccy .NET framework System.Web.Services , this means using soapExtensions to help you intersept the interaction with the webservice. This is done like so:  public class TraceExtension : SoapExtension     {         Stream oldStream;         Stream newStream;         string filename;         // Save the Stream representing the SOAP request or SOAP response into          // a local memory buffer.          public override Stream ChainStream(Stream stream)         {           ...