2.Software Myths Customer myths Myth:A general statement of objectives is sufficient to begin writing programs-we can fill in the details later. .5 Case 2.In the late 1960s,a bright-eyed young engineer'was chosen to "write a computer program for an automated manufacturing application.The reason for his selection was simple.He was the only person in his technical group who had attended a computer programming seminar.He knew the in's and out's of assembler language and Fortran,but nothing about software engineering and even less about project scheduling and tracking. His boss gave him the appropriate manuals and a verbal description of what: had to be done.He was informed that the project must be completed in two months. He read the manuals,considered his approach,and began writing code.After: two weeks,the boss called him into his office and asked how things were going. "Really great,"said the young engineer with youthful enthusiasm,"This was much simpler than I thought.I'm probably close to 75 percent finished." The boss smiled."That's really temrific,"he said.He then told the young engineerto keep up the good work and plan to meet again in a week's time.Slide 1.10 10/21 2. Software Myths