cambot wroteHi all
I am currently designing a web based application for a local company.
I intend to use DNN 4, i have the db design.
i am unsure about and was interested in your opinions.
I have a number of main functional areas, and was wondering how i
would implement these as modules. Would I have them all in one large
module, or each in separate modules??
Some of the areas are
- Contacts
- Sites/Offices
- Calendar
- Products/Suppliers/Stock
- Projects
- Marketing/Mailing
- Files/Documents
Would it be the best apporach to develop each of these as separate
modules, or would I take it even further and create modules for each
separate table.
Eg:
I have a base contacts table for contacts, a separate table to hold
addresses, another holding all comm details (phone, fax, etc).
Any opinions would be appreciated.
Thanks All
I don't consider myself the last word on this, but my opinion is
"Divide and Conquer". This allows you to make sure a small piece
of the overall picture is working then move on.
You can have many modules on one page, a user is not going to realize this when they view that page.
Plus another important Feature is realized! Think of how much
more control the portal will have when assigning new roles to all the
users. And subsequently assigning those priviledges to the
different modules to match the roles scenerio.
Example: you could create seven different roles to match your list of
seven above. The people who use your portal can have any
combination of those roles. Plus, those people can have different
viewing and editing roles.
I would concentrate on your database design, then move on to creating the modules to correspond.