Question

I have designed the following class that should work kind of like a method (usually the user will just run Execute()):

public abstract class ??? {
    protected bool hasFailed = false;
    protected bool hasRun = false;

    public bool HasFailed { get { return hasFailed; } }
    public bool HasRun { get { return hasRun; } }

    private void Restart() {
        hasFailed = false;
        hasRun = false;
    }

    public bool Execute() {
        ExecuteImplementation();
        bool returnValue = hasFailed;
        Restart();
        return returnValue;
    }

    protected abstract void ExecuteImplementation();        
}

My question is: how should I name this class? Runnable? Method(sounds awkward)?

Answer 1

Naming a class is all about a good design. You have to know which use cases this class will be part of, which responsibility it will take and what collaborations will this class take part in. Naming class without context can only do harm. Naming class after a pattern just because the pattern uses similar names is even worse, because it might confuse any reader who knows something about patterns, whcih is exactly opposite of what patterns try to achieve – name common decisions/solutions/designs/etc… Your class can be Runnable, Executable, Method, Procedure, Job, Worker, RestartableExecutor, Command, Block, Closure, Functor and virtually pretty much anything without further information.