Question on Application Architecture / Design Process

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have a Business Requirements Document and Functional Spec from my customer
/ user.

How should I go about approaching the Database Design and Object Model
Design? Generally I have done this on an adhoc basis. What is the "correct"
or formal way of doing this?

Thanks.
 
Hello C,

C> I have a Business Requirements Document and Functional Spec from my
C> customer / user.
C> How should I go about approaching the Database Design and Object
C> Model Design? Generally I have done this on an adhoc basis.

How does your "adhoc" looks like?

C> What is the "correct" or formal way of doing this?
Depends on methodology u use.
In general it's the ER diagrams for DB and class diagrams

---
WBR,
Michael Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
I think you may find that "adhoc" might not sound like the correct way, but
in most cases it is the most practical.

I have found, with a customer request, getting the program running quick is
important. So adding what I need to into the database, on the fly, is not a
problem. Give the user a description of the new fields in the database so
they can run their reports off the database and know how they link up.

If a better solution is found later with different fields / a smarter way,
the change is made.

I guess you should ask yourself / your customer, - At what point does
documentation & Field / DB change Costs overcome the program $$$ savings
change.

M.
 
Back
Top