Design is the devil, heard of intellectual property rights


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: Design is the devil, heard of intellectual property rights

  1. #1
    John Galt Guest

    Design is the devil, heard of intellectual property rights


    Design is the devil, ever heard of intellectual property rights, if you write
    a beautiful / ingenius piece of of code, would you want to share it!

    The generic code can be written according to the design. Still I myself have
    completed many projects with not one bit of design, here is what you have
    to do.

    1. Study the requirement
    2. Design a DataBase with all the data kept in mind
    a. Maybe create a non nonmalized table first then convert into the normalized
    one.
    b. Create a normalized table from requirements.
    3. Study Reporting patterns. Then change/add fieds in database to accomodate
    this. ( this may sound stupid, but trust me this point is very valid )
    4. Design the use interfact to capture data.
    5. Processing captured data depending of the type of application.
    6. Before you jump to edit or delete module, start with some of the basic
    reports. If the output is generated properly. Then great proceed..
    7. Start building edit/delete administer modules.

    During the completer process keep a end user with you to test and check what
    you have made.

    Trust me this works. I know we all like to use UML and what not to design
    then start with the coding.
    That is maybe because you cannot do it the other way round. No offence pun
    unintended

    Who is John Galt? ( Remember Ayn Rand? )

  2. #2
    MarkN Guest

    Re: Design is the devil, heard of intellectual property rights


    "John Galt" <JohnGalt@nospam.com> wrote:
    >
    >Design is the devil, ever heard of intellectual property rights, if you

    write
    >a beautiful / ingenius piece of of code, would you want to share it!


    Huh?

    >
    >The generic code can be written according to the design. Still I myself

    have
    >completed many projects with not one bit of design, here is what you have
    >to do.


    By design do you mean UML diagrams and DFDs and ERDs (etc)? Do you mean
    a formal design phase? Or do you just start coding and (like the big bang
    theory) suddenly a program that fits the requirements appears?

    >
    >1. Study the requirement


    I would if they would quit changing it.

    >2. Design a DataBase with all the data kept in mind
    > a. Maybe create a non nonmalized table first then convert into the normalized
    >one.
    > b. Create a normalized table from requirements.


    Sounds like design to me. By the way, I do this in my head most of the time.
    And I design my persistant objects instead of database tables. Then add
    some fields to accommodated the limitations of a relational datastore.

    >3. Study Reporting patterns. Then change/add fieds in database to accomodate
    >this. ( this may sound stupid, but trust me this point is very valid )


    Usually they don't know what they want till the end and when they see the
    end product they want more and different. Current reporting tools allow
    the use of things other than the database as the datasource (i.e. Objects
    and XML).

    >4. Design the use interfact to capture data.


    I try to do this last. The user interface is very important to the user
    but only the user. And since the 'user interface' could be anything from
    a thick client to a thin client to another system it should come after persistance
    and business logic.

    >5. Processing captured data depending of the type of application.

    Business logic?

    >6. Before you jump to edit or delete module, start with some of the basic
    >reports. If the output is generated properly. Then great proceed..


    Reports are a user interface (read only) and may need to have some business
    logic occur before they are generated. Once the business objects are done
    the reports can be built.


    >7. Start building edit/delete administer modules.

    I have this already done because it is part of persistance and persistance
    provides data to my reports.

    >
    >During the completer process keep a end user with you to test and check

    what
    >you have made.


    This is a great idea.

    >
    >Trust me this works. I know we all like to use UML and what not to design
    >then start with the coding.
    >That is maybe because you cannot do it the other way round. No offence pun
    >unintended


    No, because in a perfect world that is way to do it. But the reality is
    that 99.9% of the time it can't be done. Doing it your way is the 'easy'
    way. The best senario would be to get a basic design done (in your head
    or on paper) and do and iterative design using a tool that allows you to
    go from design diagram to code and back. There currently are tools that
    do this. And they are getting better - like Rational's XDE for WSAD and
    .Net. This is a really cool (but pricey) tool.

    >
    >Who is John Galt? ( Remember Ayn Rand? )


    Mark

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center