how to design

  • I'm very new for designing job

    how many design style in present?

    I know there are general design which includes DFD and ERD together

    and another style is OO which includes USECASE, CLASS DIAGRAM, ...

    what I know is correct or not ?

    I know that DFD is for designing data that comming in and out the process

    ERD for database designing

    And I know other thing else, but don't have clear understanding about it

    USECASE for ....

    SEQUENTIAL DIAGRAM for....

    ACTIVITY DIAGRAM for....

    so I'm very confuse now

    Can anyone give me some clearly understand for this

    thank you very much 😀

  • Ummmm... let me get this straight... you got a job as a designer and you don't really know how to design?

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • That's a huge collection of really fundamental questions that just aren't going to be answered easily in a little post in a discussion group.

    In terms of database design, you should pick up Fleming & von Halle's "Handbook of Relational Database Design." It will go over a lot of the questions you have, but not all. I don't have a good reference to recommend for fundamental software design, but do a search on Amazon and you'll come up with something.

    "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

  • Definitely not a trivial topic... and I haven't really found a good "starter" book on database design except for maybe some of the topics in Books Online. Before you do any database designing, Google "3rd normal form" and memorize it, the 1st two forms, and when you might want to use any of the 3. Lookup "Star" and "Snowflake" schemas... learn the advantages and disadvantages of each and how to "blend" the two for better performance and ease of maintenance. Then lookup indexing and DRI (Declared Referential Integity, ie Primary/Foreign Keys) and study the heck out of that subject being sure to truly understand the real differences between clustered and non-clustered indexes and how they impact performance. Then, create a couple of million row test tables and start trying to figure what performance actually means.

    Last but not least, hang around this forum and answer some questions... best way to learn is to do.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • hey,

    Sound like you have just completed a software application design course and trying to piece together the different phases of development. If SQL Server is your RDBMS of choice for physical design, you may want to look at this book "Pro SQL Server 2005 Database Design and Optimization", which touches on some of the life cycle phases.

    As Jeff and Grant's have already commented, there a lot to cover, so start with 3rd normal form, which will at least get you understanding basic DB design principals (e.g. ERD) and just absorb as much as you can, but test your understanding at each topic by "doing it", not just reading it.

    Good luck!

    Thanks,

    Phillip Cox

    MCITP - DBAdmin

  • Get some books about fundamental software development techniques.

    Just as an example: Systems Analysis & Design Methods from Whitten Bentley ISBN-13: 978-0-07-305233-5 (www.mhhe.com/whitten). Good book for students covers traditional (data) analysis methods and OO Design fundamentals.

    Have fun. 🙂

  • One book that I recommend that will cover the various design artifacts besides just those from "the database world" is David Hay's Requirements Analysis From Business Views to Architecture.

    As for getting more in depth on db design, the above suggestions are spot-on, and I'll also take the opportunity to shamelessly plug my short article on the topic:

    http://www.sqlservercentral.com/articles/Data+Modeling/61817/

    HTH,

    TroyK

  • What are you trying to design anyway? a database model, a data flow diagram, a business model ?

  • Thank you, everyone

    Actually I'm still a student. And as Phillip Cox said, I'm just finish the System analysis and design course.

    I have learned many model, so I'm very confuse. Thank you for your recommends, I'll find out it 😛

Viewing 9 posts - 1 through 8 (of 8 total)

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