need help for planning software development , database design

Question

I have been doing a coding in for last 7 months. Most part of it has been the updations to the very poorly coded software in asp. Now I am going to redevelop entire software in asp.net. I want it to be very efficient. I need some tips and guidance about how to plan project and design a good database. Thanks in advance for help.

Answer 1

I'm guessing you're going to be using a relational database. Look up "Normalization of Relational Databses". Make sure your data meets the criteria for "Normal Form 3" (which means it meets the criteria for "Normal Forms 0 through 3".

You will have a huge head start because most of the data that doesn't conform to your application will not be able to be stored in your database.

Answer 2

The first thing you need to do is to have a very clear understanding of what you want to do. I'm not referring to having a huge design and documentation detailing everything, but make sure you know as best as you can what are you going to be working on (project objectives, limitations, etc.) You don't need to have anything set in stone at this time.

Second, look at the different technologies that could help you. Advantages and disadvantages of a platform (form example ASP.NET WebForms vs. MVC). While you do this, you should also read some information on the theory behind computer science. Big-O notation and other related concepts on algorithmic complexity are very useful when you want to build efficient software.

Third look at the best way to store your data. This step is critical, an incorrectly chosen storage mechanism can cripple a project. Most probably the chosen solution will be (especially considering you will be using ASP.NET) a relational database but don't assume it will be the best solution (for some projects, a plain text file could be a great solution).

If you so decide to use a Relational Database, I would advise you to first of all learn how to create an Entity-Relationship diagram. The diagram will help you visualize your data way better than any other mechanism I know of. Afterwards look for how to translate an Entity-Relationship diagram into a Relational Database and if necessary transform it as Edwin said into a useful Normal Form.

Finally, my last tip is to read as much as you can (on the web and on books) and ask as much as you can. The best way to learn is to be curious about something.

Hope this helped!