Decision on Classes in a database application

Question

1.00/5 (1 vote)

See more:

I am developing a database application for a university warehouse (stores a diverse range of products). This warehouse is a centralized place for temporarily holding of procured products, which are to be distributed to different departments. The application should be able to keep record of all transactions involved, such as, procurements, issuing items to departments, inventory of the warehouse etc....
Apart from basic classes such as classes relating to Data Access Layer etc. I have difficulty in deciding as to what classes should I have? Should there be a class for each entity in the database? or else?
Please give suggestion...

Posted 27-May-12 21:03pm

Member 9037864

Add a Solution

Comments

Sergey Alexandrovich Kryukov 28-May-12 3:21am

Too general question. There are not a cookbook recipe here, because this is a part of your application architecture and design. I cannot believe anyone can do it for you. At the same time, the question shows some lack of judgment. One basic advice would be: develop some less then perfect system at fist and learn code design on your mistakes.
--SA

db7uk 28-May-12 5:16am

Can you not use entity framework and use the generated classes from the tables?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)