pclarke7
asked on
Defining a Class
Hello,
I am relatively new to c#. I understand what a Class is but I am unsure about how small/large a class definition should be. For example I have an application in mind which I am about to start working on. This application will take a series of rules which have been defined within a ms database and given a transaction name and it will execute these rules in a predefined sequence defined within the database. Database rules can be input rules, output rules, logic rules, constant rules, menu rules etc.. and each database rule can consist of 40-50 field definition. When a particular transaction is selected then the sequence of rules for that transaction will be load up into arrays or containers and the transaction will execute from these arrays. The transaction will have if/then/else logic , error checking, database input/output.
My Questions is:
do I define just 1 class called "transaction" and get this the class members to perform the database I/O , array/container processing, error checking etc. etc.. or should I break this down into much smaller classes ? Appreciate if someone could point me towards some reading material which would help me understand what should be contained within a class ?
regards
Pat
I am relatively new to c#. I understand what a Class is but I am unsure about how small/large a class definition should be. For example I have an application in mind which I am about to start working on. This application will take a series of rules which have been defined within a ms database and given a transaction name and it will execute these rules in a predefined sequence defined within the database. Database rules can be input rules, output rules, logic rules, constant rules, menu rules etc.. and each database rule can consist of 40-50 field definition. When a particular transaction is selected then the sequence of rules for that transaction will be load up into arrays or containers and the transaction will execute from these arrays. The transaction will have if/then/else logic , error checking, database input/output.
My Questions is:
do I define just 1 class called "transaction" and get this the class members to perform the database I/O , array/container processing, error checking etc. etc.. or should I break this down into much smaller classes ? Appreciate if someone could point me towards some reading material which would help me understand what should be contained within a class ?
regards
Pat
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER