Can one begin to design without analysis?

6 Answers

Relevance
  • Lv 7
    2 months ago

    sure, but it's like flying blind.

    • Login to reply the answers
  • Ivanex
    Lv 6
    2 months ago

    no, you analyze unconsciously, or you do it consciously. If you dont analize, how the hell you will do the task?

    if the project you are working on is small, maybe you wont need too much "analysis", but if the project is big and has a lot of ramifications, a proper analysis usually help

    • Login to reply the answers
  • 2 months ago

    Welcome to the real world, where the customer wants it all, wants it now, and what's a specification?

    • Login to reply the answers
  • EddieJ
    Lv 7
    2 months ago

    Well, your brain has an ability to do a certain amount of analysis without you having to consciously think about it, so, it's up to you do decide if you want to only consider "conscious analysis".

    If this is a homework question, then it's stupid.  People have a wide range of abilities and experience.  A student will be taught to analyze first, but, as time goes on, the now-experienced person may choose to skip the analysis.  Whether or not it works will be another learning experience for that individual.

    Geniuses exist.  The question doesn't say that we should exclude them.

    • Snezzy
      Lv 7
      2 months agoReport

      Sometimes the analysis gets skipped away from the designer or the coder. "Have this program ready by the 14th. The (computer-controlled) machine is shipping on the 28th." "But, but the machine isn't even working yet! Who came up with this plan? How will I test?"

    • Login to reply the answers
  • How do you think about the answers? You can sign in to vote the answer.
  • Snezzy
    Lv 7
    2 months ago

    It's the way we used to do it. There are several "Pointy Haired Boss" stories about that approach that far pre-date Dilbert.

    - "Have you started coding yet?"

    - "How many lines of code have you written this week?"

    - "When will you find the last bug?"

    We fiddled around with the bits, writing in assembler, and we hoped for the best. We often found that the program needed to be bigger than the available memory, and let me tell you, repetitively loading separate overlay modules via paper tape, rather than having them swap in from a drum memory, is tedious.

    Initial planning, using principles that we should have learned in our computer science classes, might have helped. For instance, we often used a bubble sort because we didn't know anything better. (Elapsed time for a bubble sort is order of n-squared. It's okay for tiny lists, but ridiculous for more than 50 or 100 items.) We spent a lot of time doing things Really Wrong, but were proud when we got anything to work at all. 

    Learn how to do analysis. Construct mathematical models that might lead you to better design. Don't fall into the trap of thinking that your initial analysis is the best analysis, but also don't get stuck in the analysis phase, trying only for further improvement. The perfect is the enemy of the good.

    • Login to reply the answers
  • 2 months ago

    They can.  But odds are anything they design will be worthless.  You can not design something that will work if you have not first figured out what they need and what it has to do.

    There are some generic functions that you know any program is going to have to do.  And certain functions that the type of program you are designing will have to do.  Usually you start with a pre-made template and code libraries that do this common functions.  So there are "some" things you can do before you do the analysis needed to design the program.  But it will be very limited.

    You need to figure out what the user's needs are and what the program has to do before you can begin doing coding of the program.  That is the analysis.

    • Login to reply the answers
Still have questions? Get your answers by asking now.