Curious
|
| Posted: 09/23/2002, 7:49 AM |
|
Do most of you do Database stuff first or general web design.
Im still sort of confused on the relationships with html and the Asp part of the software..is it best to create frames so as not to screw up code?
|
|
|
 |
Robert
|
| Posted: 09/23/2002, 11:15 PM |
|
As my understanding goes, the method to create a website is far from simple.
1. You have to have an exact idea what do you want from your website. Let's say, you need a customer relations application for your XYZ company.
2. Collect info. Like what user informations want do you store in the Db. (Firstname, Lastname, Birthday, etc.)
3. Grab a piece of paper and organize your collected informations into fields, groups. Now, in the database the groups will be the tables, BUT! *pay attention* for the DB normalization (no duplicate and ambigous entries), primary keys, indexes. This is important because later on you can save time for yourself when you want to extend your application. Take it seriously.
4. Draw the tables with fields, and draw the relations. This will be your DB design map. Verify everithing, take a walk, have a beer, think, and re-think again.
5. Next step to create simple forms (it doesn't need to be working ones) and just see if all the informations what you want to collect is there. Best *again* to grab a piece of paper and draw :) ...
6. Design your forms, pages using CCS or anything (this method can be applied on hand-coding as well), and test. Then test again for invalid entries, validations, etc.
7. The last step is (when you are done with the functional design) to complete the visualization, the graphics design.
8. Then test and test and test.
Answer for your 2nd question: best to read the CC manual. They explain the difference between the "one file" and the template system.
This small writing is intended to provide very basic guidance to start a project. Take it seriously, it is easy to create a site with CC, but also easy to create a bad (aka. easy to crash) one.
Thanks for your kind attention.
Robert
|
|
|
|
RG
|
| Posted: 09/24/2002, 1:34 AM |
|
Traditionally you design your database first because it is the data what it is all about. Then you design the way you want the data to be manipulated or presented.
The other way you will probably need some tools like UML (Unified Modeling Language) etc. so you can design your application and your database hand in hand.
|
|
|
|
Curious
|
| Posted: 09/24/2002, 9:45 AM |
|
Great...I can do think drink bit...not sure bout the thinking at same time...
thanx a lot for a well thought out answer
|
|
|
|
|
