Software myths | Software Engineering Notes
Download as pptx, pdf1 like6,266 views
This document discusses common myths held by software managers, developers, and customers. It describes myths such as believing formal standards and procedures are sufficient, thinking new hardware means high quality development, adding people to late projects will help catch up, and outsourcing means relaxing oversight. Realities discussed include standards not being used effectively, tools being more important than hardware, adding people making projects later, and needing management and control of outsourced projects. Developer myths like thinking the job is done once code runs and quality can't be assessed until code runs are addressed. The document emphasizes the importance of requirements, documentation, quality processes, and addressing change impacts.
More Related Content
What's hot (20)
Similar to Software myths | Software Engineering Notes (20)
More from Navjyotsinh Jadeja (9)
Recently uploaded (20)
Software myths | Software Engineering Notes
- 1. SOFTWARE MYTHS Facilitator : Navjyotsinh Jadeja www.edtechnology.in
- 2. WHAT ARE SOFTWARE MYTHS • Pressman (1997) describes a number of common beliefs or myths that software managers, customers, and developers believe falsely. He describes these myths as ``misleading attitudes that have caused serious problems.''
- 3. TYPES OF SOFTWARE MYTHS • MANAGERS MYTH • DEVELOPERS MYTH • CUSTOMERS MYTH
- 4. MANAGEMENTS MYTH • MYTH: We already have a book that's full of standards and procedures for building software, won't that provide my people with everything they need to know? • REALITY: The book of standards may very well exist, but is it used? Are software practitioners aware of its existence? Does it reflect modern software engineering practice? Is it complete? Is it streamlined to improve time to delivery while still maintaining a focus on quality? In many cases, the answer to all of these questions is “no”. • MYTH: My people have state-of-the-art software development tools; after all, we buy them the newest computers. • REALITY: It takes much more than the latest model mainframe, workstation, or PC to do high-quality software development. Computer-aided software engineering (CASE) tools are more important than hardware for achieving good quality and productivity, yet the majority of software developers still do not use them effectively.
- 5. MANAGEMENTS MYTH • MYTH: If we get behind schedule, we can add more programmers and catch up (sometimes called the Mongolian horde concept). • REALITY: Software development is not a mechanical process like manufacturing, adding people to a late software project makes it later • MYTH: If I decide to outsource the software project to a third party, I can just relax and let that firm build it. • REALITY: If an organization does not understand how to manage and control software projects internally, it will invariably struggle when it outsources software projects.
- 6. DEVELOPER’S MYTH • MYTH: Once we write the program and get it to work, our job is done. • REALITY: Someone once said that "the sooner you begin 'writing code', the longer it'll take you to get done. Industry data indicate that between 60 and 80 percent of all effort expended on software will be expended after it is delivered to the customer for the first time. • MYTH: Until I get the program "running“, I have no way of assessing its quality. • REALITY: One of the most effective software quality assurance mechanisms can be applied from the inception of a project—the formal technical review. Software reviews are a "quality filter" that have been found to be more effective than testing for finding certain classes of software defects. • MYTH: The only deliverable work product for a successful project is the working program. • REALITY: A working program is only one part of a software configuration that includes many elements. Documentation provides a foundation for successful engineering and, more important, guidance for software support. • MYTH: Software engineering will make us creates voluminous and unnecessary documentation and will invariably slow us down. • REALITY: Software engineering is not about creating documents. It is about creating quality. Better quality leads to reduced rework. And reduced rework results in aster delivery times.
- 7. CUSTOMER’S MYTH • MYTH: A general statement of objectives is sufficient to begin writing programs— we can fill in the details later. • REALITY: A poor up-front definition is the major cause of failed software efforts. A formal and detailed description of the information domain, function, behavior, performance, interfaces, design constraints, and validation criteria is essential. These Characteristics can be determined only after thorough communication between customer and developer. • MYTH: Project requirements continually change, but change can be easily accommodated because software is flexible. • REALITY: It is true that software requirements change, but the impact of change varies with the time at which it is introduced.
- 8. Queries • For queries you can contact in the comment section of YOUTUBE channel Edtechnology • Refer http://www.edtechnology.in/ for more information on related topics.