data modeling

Question

data modeling

HBK_4700

SSCrazy Eights

Points: 8932
More actions
December 15, 2009 at 3:45 pm

#228547

What are the things needs to take care in adding a new module to existing data model and which documents need to prepare, please advice

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Grant Fritchey SSC Guru Points: 398886 More actions · Answer 1

I'm sorry, but the question is a bit vague. I'm assuming you're tasked with doing this at work and you've never done it before.

First, you need to differentiate between new objects for the database and changes to existing objects. For new objects, you only need the business requirements to begin the modelling process. For changes to existing objects, you need the business requirements and you'll need the previous business requirements as well as some type of dependency tree that shows the objects, code, and applications that you might be affecting with a given change. Then you can begin modelling an impact statement that shows the things that will be affected by the changing objects.

That's a general approach. If you have specific issues or needs, you'll need to outline them.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Steve Jones - SSC Editor SSC Guru Points: 736255 More actions · Answer 2

If this is homework/exam question, you need to do some more work, or show us what you think needs to happen to answer the question. We are happy to help you, but we should not be doing the work for you.

HBK_4700 SSCrazy Eights Points: 8932 More actions · Answer 3

Grant Fritchey (12/16/2009)
I'm sorry, but the question is a bit vague. I'm assuming you're tasked with doing this at work and you've never done it before.
First, you need to differentiate between new objects for the database and changes to existing objects. For new objects, you only need the business requirements to begin the modelling process. For changes to existing objects, you need the business requirements and you'll need the previous business requirements as well as some type of dependency tree that shows the objects, code, and applications that you might be affecting with a given change. Then you can begin modelling an impact statement that shows the things that will be affected by the changing objects.
That's a general approach. If you have specific issues or needs, you'll need to outline them.

A big thank to you, this really helped me to start process.