Preview

Principles of Software Engineering

Powerful Essays
Open Document
Open Document
2331 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Principles of Software Engineering
1) Describe each law in your own words. Illustrate with a practical example.

Glass’ law
Requirement deficiencies are the prime source of project failures. (Endre & Rombach, 2003)

Requirements are the basic Phase which lead to the development of a project. In fact, it is the first step for any project The main problem in a project failure is the lack of requirements.
The common requirement error is due to human (i.e lack of Communication between customer and the analyst), software, etc.
Example: Denver International Airport Reason: Underestimation of complexity, Complex architecture, Changes in requirements, Underestimation of schedule and budget, Dismissal of advice from experts, Failure to build in backup or recovery process to handle situations in which part of the system failed.

Boehm’s first law
Errors are most frequent during the requirements and design activities and are the more expensive the later they are removed. (Endre & Rombach, 2003)

Errors occurred at the later stages of the project are very expensive in terms of both time and cost because every project goes through software development life cycle, and any changes made in the later stages would result in re-consideration for all the previous stages and this would cause lot of delay in project and even cost of the project increases Example: According to a study done at TRW in 1974, the percentage of errors in design stage was 64 where as coding errors account to 36 percent and also 54 percent of errors were not found earlier than acceptance testing. Design errors took twice as much time to diagnose and correct than coding errors. The cost of fixing a problem at later stages will be much more when compared to that of fixing problems at earlier stages.

Boehm’s second law
Prototyping (significantly) reduces requirement and design errors, especially for user interfaces. (Endre & Rombach, 2003)

Example: Software applications that are relatively easy to

You May Also Find These Documents Helpful

  • Powerful Essays

    errors that tend to happen when calculations are done manually. Ultimately, the goal of the entire…

    • 1203 Words
    • 4 Pages
    Powerful Essays
  • Satisfactory Essays

    All of these problems may result of wrong requirements gathering, of course it will be a result of serious errors in requirements.…

    • 475 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Unit 1 Assignments

    • 404 Words
    • 2 Pages

    Completed all tasks to specified requirements; one or two small details may be missing, or there may be minor errors in spelling or grammar…

    • 404 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Mistakes and errors have another purpose; they tell when to change direction. When things aren’t going smoothly, people think of new ideas. Roger Von oech mentions a client, a division manager from a high-tech company, asking his vice president of engineering what percentage of their new products should be a success in the market business. The answer he received was “about 50%.” The division manager replied, “That’s too high. 30% is a better target; otherwise we’ll be too conservative in our planning. In conclusion Roger Von Oech wants everyone to take advantage of their mistakes and learn from them for new better…

    • 300 Words
    • 2 Pages
    Satisfactory Essays
  • Good Essays

    When can a project fail? 3 points - during the project, into implementation, or into operation.…

    • 779 Words
    • 3 Pages
    Good Essays
  • Good Essays

    The cold hard truth is that projects always look better on paper; this is because in the development phase they are still lacking the human element. When projects are actually implemented you have to consider laziness, incompetence, and level of knowledge. In short you have to account for human error. There are systems glitches that can be unexpected as well. Just as with people, software does not always perform up to expectations. Files can get corrupted and will not run as planned. You can never plan for everything but through risk management you can help to mitigate the impact.…

    • 618 Words
    • 3 Pages
    Good Essays
  • Good Essays

    The first reason is poor planning. Big projects can be very complicated, if your team are not sure what they are supposed to be doing there will be sections missing, there may even be people working on the exact same thing. Also, as shown by the second example bellow, not accounting for all factors when planning can result in failure.…

    • 849 Words
    • 4 Pages
    Good Essays
  • Good Essays

    The section also briefly describes impact, assessment and counter measures or contingencies which may reduce the likelihood and/or cushion the impact.…

    • 740 Words
    • 3 Pages
    Good Essays
  • Powerful Essays

    Management Action Plan

    • 1164 Words
    • 5 Pages

    | * Lack of communication amongst team, particularly with major objectives * Quality of work (lack of experience in suitable reporting techniques, etc) * Unable to…

    • 1164 Words
    • 5 Pages
    Powerful Essays
  • Satisfactory Essays

    The IT projects are unique and complex, the majority of IT projects fail to meet at least one measure of success. The author of the article “IT Project management: Infamous failures, classic mistakes and best practices “consider some of the common causes of failures and best practices to avoid them. For a project to be successful every project manager must consider the triple constraint scope, cost, time and balance these three competing goals. A number of key factors contribute towards project failures. In this article it cited Steve McConell grouping the factors in four categories as people, process, product and technology. The article ranked top mistakes as poor estimation, ineffective stakeholder management, insufficient risk management, insufficient planning, poor quality, team issues and insufficient project sponsorship. The interesting finding is the mistakes are due to people or process-related, as opposed to product or technology related. The other interesting finding is given the importance given to scope in IT projects but scope creep was not in the top reason for project failure. The article also identifies that one-half of projects fails due to estimation and scheduling, stakeholder management and risk management. In conclusion, the author integrates different areas of failure and analyzed the reasons for failure and has proposed a framework for success.…

    • 363 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Free Upload

    • 7325 Words
    • 30 Pages

    Completed all tasks to specified requirements; one or two small details may be missing, or there may be minor errors in spelling or grammar…

    • 7325 Words
    • 30 Pages
    Satisfactory Essays
  • Good Essays

    Patient Safety Risk

    • 488 Words
    • 2 Pages

    'The fact that some errors are being made over and over again needs to be looked at much more closely.'…

    • 488 Words
    • 2 Pages
    Good Essays
  • Powerful Essays

    Gosh from Appex

    • 2074 Words
    • 9 Pages

    * Company started missing the installation dates and fell behind schedules, there were failures in product development.…

    • 2074 Words
    • 9 Pages
    Powerful Essays
  • Good Essays

    There are many ways to collect necessities for a project, such as interviewing stakeholders, holding focus groups, using questionnaires and surveys, observation, and prototyping. It can be difficult to collect requirements because of different stakeholders often have different needs, they can change quickly, and many are difficult to implement with the present systems.…

    • 1086 Words
    • 5 Pages
    Good Essays
  • Satisfactory Essays

    Error Analisis

    • 329 Words
    • 2 Pages

    The paper is divided into the following 3 parts. They are Recognition of Errors (1), Description of Errors (2), and Conclusion (3).…

    • 329 Words
    • 2 Pages
    Satisfactory Essays