Preview

No Silver Bullet

Satisfactory Essays
Open Document
Open Document
252 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
No Silver Bullet
"No Silver Bullet"
A review of the article "No Silver Bullet: Essence and Accidents of Software Engineering" written by F. P. Brooks and published in "Computer Magazine".
Written in 2004; 1,293 words; 5 sources;
Paper Summary:
This paper discusses the state of the software industry, claiming that there are many theories regarding lack of software productivity. The paper examines Brooks' ideas as they appeared in his "Computer Magazine" article, "No Silver Bullet", as well as the opinions of Cox and others. The paper contends that these theories and others, all help to shed light on barriers to software productivity.
From the Paper:
"During the 1970's, companies had difficulty delivering software within the constraints of schedule, budget, and quality (Food for Thought, 2005). The problem grew worse over time. Many projects undertaken in the 1980's and 1990's were complete disasters, failing to deliver anything, grossly exceeding budget and schedule deadlines, and delivering poor quality. Also, during the 1980's a "software crisis" occurred in which the spending on software maintenance exceeded spending on creating new software products. So, why can't software be mass produced in a way that is reliable and consistent just as manufactured goods are delivered today? There are many theories regarding lack of software productivity. Brooks (1987) holds that the fundamental nature of software prevents meaningful automation. Cox (1996), on the other hand, makes the interesting assertion that software development issues stem from market dynamics, namely the way software is bought and

You May Also Find These Documents Helpful

  • Good Essays

    Pt2520 Unit 3 Metrics

    • 544 Words
    • 3 Pages

    In this presentation, the author has explained different metrics and there attributed used to measure software. A person can only measure and represent it in number when he knows something about it. On the other hand, if has no idea about it then he doesn’t have any idea about it [1]. There are two types of software complexity metrics. One gives the efficiency of the machine while running the software which is called as computational complexity. Another one is giving us the factors which affect the software developer capacity to develop good software which is known as psychological complexity. There are two types of software metrics. The process metrics which gives details of the process used such as software life cycle used for development, the time consumed for the development etc. The…

    • 544 Words
    • 3 Pages
    Good Essays
  • Better Essays

    Caivano, D., Oivo, M., Baldassarre, M.T. & Visaggio, G. (2011). Product-Focused Software Process Improvement. Springer.…

    • 1550 Words
    • 7 Pages
    Better Essays
  • Satisfactory Essays

    Kizza Chapter *

    • 528 Words
    • 3 Pages

    1. Briefly state the main idea of this chapter. Since software in one form or another controls every computer or computer component, it becomes a more important and fundamental part of our life. Even though we may not understand the languages that make up the software, we must be aware of the elements of software that affect its use. Verification and Validation, reliability, security, safety, and quality are some of the major points examined and brought to light. It delves into the various reasons of why software fails and who is responsible. More importantly, it covers what consumer protection exists and the rights of software buyer's.…

    • 528 Words
    • 3 Pages
    Satisfactory Essays
  • Powerful Essays

    References: Apollo Group, Inc. (2006). Riordan Manufacturing. Information Technology – Overview. Retrieved March, 6 2010. MGT/449- Quality Management and Productivity https://ecampus.phoenix.edu/secure/aapd/cist/vop/Business/Riordan/IT/RioITNetwork001.htm…

    • 2187 Words
    • 9 Pages
    Powerful Essays
  • Satisfactory Essays

    Laudon Mis 6ce Ch14

    • 11622 Words
    • 55 Pages

    1) Between 30 and 40 percent of all software projects are "runaway" projects that far exceed original schedule and budget projections.…

    • 11622 Words
    • 55 Pages
    Satisfactory Essays
  • Better Essays

    Poston, Robin, Thomas F. Stafford, and Amy Hennington. "Software: A View From The (Online) Street." Communications Of The ACM 48.8 (2005): 96-99. Academic Search Premier. Web. 21 Mar. 2013.…

    • 2229 Words
    • 9 Pages
    Better Essays
  • Good Essays

    Software developers make effective software. It is an engineering endeavor that cannot be extracted from the context and systems with which it interoperates. The heart of a good software solution is not in turning the functional specification into code but rather in the use of available resources such as time and money to create desired outcomes for stakeholders, while satisfying constraints such as legal requirements through purposeful design.…

    • 1334 Words
    • 6 Pages
    Good Essays
  • Satisfactory Essays

    Swot Analysis

    • 386 Words
    • 2 Pages

    * Lack of software engineers to keep up with increased demand for software based consumer electronics…

    • 386 Words
    • 2 Pages
    Satisfactory Essays
  • Powerful Essays

    Sample Answer

    • 493 Words
    • 2 Pages

    4) UST Inc. has paid uninterrupted dividends since 1912. Will the recapitalization hamper future dividend payments?…

    • 493 Words
    • 2 Pages
    Powerful Essays
  • Best Essays

    As we will discuss in the course of our case study, the Trilogy Project would fail for a number of reasons. Despite failing, Project Trilogy is not alone when it comes to project management blunders. According to the Standish Group’s CHAOS report, only 16% of application development projects succeeded. The numbers gathered in 1995 report an astounding number of projects fail or are canceled before they can be completed.…

    • 4684 Words
    • 19 Pages
    Best Essays
  • Best Essays

    References: Gulla, J. (2012, February ). Seven Reasons IT Projects Fail. Retrieved October 28, 2012, from www.ibmsystemsmag.com: http://www.ibmsystemsmag.com/power/Systems-Management/Workload-Management/project_pitfalls/?page=3…

    • 4332 Words
    • 18 Pages
    Best Essays
  • Best Essays

    Managing information technology (IT) projects continues to be an ongoing challenge for many organizations worldwide. What is most humbling about this story of a software project begun with the best of intentions, and developed over years by a top, well-known firm, despite its best efforts, did not make the grade, and this is not uncommon. Most of other projects, if they were completed at all, came…

    • 2975 Words
    • 12 Pages
    Best Essays
  • Satisfactory Essays

    With today’s advances in technology, software development and usage is paramount. Software connects computer’s hardware to users. Without software, computers would be useless. Unfortunately due to the complex nature and high demand for many software systems, the prices have sharply risen. A Seattle man, Rex Yang and a few friends decided they could capitalize on this high demand, high price market. To keep their overhead down and maximize on profits, the group chose a less than ethical route.…

    • 379 Words
    • 2 Pages
    Satisfactory Essays
  • Good Essays

    Sapient Case Review

    • 1281 Words
    • 6 Pages

    All Sapient’s competitors charged their services on time and material basis with no guarantee of when the project would get done. As system development dragged on because of changes in scope, changes in user preferences, or changes in technology companies often ended up paying more that what they had budgeted Two-thirds of IT projects either were never implemented or failed to meet their objectives-usually at the customers expense.…

    • 1281 Words
    • 6 Pages
    Good Essays
  • Powerful Essays

    Why Learn Assembly Language

    • 3719 Words
    • 15 Pages

    The world is full of case studies outlining software engineering disasters. Almost every programmer has had to work on a project involving "less than stellar" source code that was difficult to read and maintain. On rare occasion, some programmers get the opportunity to work on a well-designed system, an awe-inspiring piece of craftsmanship that usually produces the exclamation, "This is truly great code!" Clearly, professional software engineers should strive to achieve this level of greatness in all their code. But the real question is, "What makes code great?" Simply "meeting specifications" is not how one writes great code. True, in today's software environment, some might actually believe that simply meeting the specifications sets an application apart, as many development projects fail to meet their basic design goals. However, in other areas greatness is rarely defined by doing the expected and succeeding; greatness is defined by going above and beyond what is expected. Software engineers should expect no less from great software--it should go above and beyond the standard conventions for software development. Efficiency Is the KeyBecause greatness is a multifaceted attribute, a short article such as this one cannot begin to describe all the possible components of a great piece of software. Instead, this article will describe one component of writing great code that has been neglected in recent years as computer systems have increased in capacity and power: efficiency.Anyone who has been around the computer industry for a decade or more is well aware of this phenomenon: machines are getting exponentially more powerful per unit cost, yet users do not perceive this improvement in the applications that they purchase. For example, while word processors are clearly faster today than they were 21 years ago, they aren't 16,384…

    • 3719 Words
    • 15 Pages
    Powerful Essays