Sure. A checking account has identity, state, and behavior, just like a software object.
In this chapter we will develop a checking account class. To start, we must decide what checking account objects will do and what data they will hold. This process is called requirements analysis and for industrial sized problems is the most important phase of writing programs. Even for small problems it is important to know what you want before you start writing.
The companies of the late, lamented, dot-com bubble were strong on sock-puppets and weak on requirements analysis.
For our small problem we will outline what the class looks like before we start coding. The class definition will be a blueprint for checking account objects. The data and behavior that we want for a checking account must be described in the class.
Think of three data items that will be part of a checking account.