Classic Mistakes in Software Development: Case Study

Shared by SteadyAtlas9417 October 22, 2026 PDF
Computer Science Management 12 pages $12
Page 1 shows the title 'A Case Study in Classic Mistakes' and the start of a story about a technical lead at a medical insurance company.
Page 1 · free preview
Page 2
Page 3
Page 4
Page 5
Page 6

Unlock all 12 pages

Get it free by sharing your own notes, buy just this one, or become a member and unlock documents with your plan.

How to unlock this document

Choose the way that suits you. Each one gives you all 12 pages to read online and the PDF to download.

Free

Share your notes, unlock for free

2 free unlocks for every 5 approved uploads

  • Upload your own lecture notes, assignments, essays or past papers
  • PDF, Word, PowerPoint and Excel files all work, and you can send many at once
  • We check each upload; you get a notification when it is approved
  • Spend a free unlock on this document or any other, and keep it for good
  • Shared under your public username, never your email
Create a free account

Then upload your notes from your profile.

Just this one

Buy this document

$12 one-time payment

  • All 12 pages of this document, yours to keep
  • Download the PDF and read it any time, also offline
  • No subscription and nothing to cancel
  • Find it again any time under My Profile → Library

You log in or create a free account first, then pay securely.

Best value

Become a member

Unlock documents from the whole library, which keeps growing

  • Choose any documents you like, up to your plan’s unlocks
  • Documents you unlock stay yours, even if you cancel later
  • Your unlocks start again with every renewal
  • Secure checkout by Dodo Payments
10 tokens every month
60 tokens every 6 months · Save 17%
130 tokens every year · Best value

You log in or create a free account first, then pay securely.

Compare the plans

About this document

Pages
12 pages
Price
$12 one-time, yours to keep
Membership
Included in every plan
Format
PDF
Subject
Computer Science, Management

This case study follows a technical lead at a medical insurance company as he navigates the challenges of a software development project. It helps students understand common pitfalls in project management and software engineering.

What's inside

  • Introduction to the Giga-Quote program
  • Initial project approval and changes
  • Schedule and team management challenges
  • Design and coding phases
  • Handling unexpected requirements changes

Who it is for: Students of project management and software engineering. (Undergraduate)

#case study #classic mistakes #medical insurance #project management #requirements changes #schedule management #software development #team dynamics

Share with classmates: WhatsApp Telegram X LinkedIn Facebook

Summary

Classic mistakes in software development are shown through a case study. Students learn about project management, software engineering and the consequences of poor decisions.

The project begins

A technical lead for an insurance company gets funding for a software program. The project's requirements and deadline change. The team looks for ways to shorten the schedule.

Design and development

The team starts work on the project. They use a new programming language and a report-building tool. They make decisions about how to meet the project's requirements.

Problems arise

The team realises that they will not meet the deadline. They agree to work longer hours. They start testing the software and training users at the same time.

The project is delayed

The team finds more problems with the software. They take a break and write a detailed report about what remains to be done.

Key terms

client-server project
A project where one program acts as a server, providing services to other programs, the clients.
GUI
Graphical user interface, a way for users to interact with software using visual elements.
feature-complete build
A version of the software that has all the planned features, but may not be fully tested.
QA
Quality assurance, the process of checking that the software meets the required standards.
bug
A problem or error in the software that causes it to behave incorrectly.
Sev-1
A severity level for a bug, meaning it is a high-priority problem that must be fixed.

Questions this document helps with

  • What are the risks of changing a project's requirements and deadline?
  • How can a team shorten a software development schedule?
  • What are the consequences of not testing software thoroughly?

Summary written with AI from the document's text.

Ask the AI Teacher

Ask any question about this document or your course, and get a clear explanation.

Free accounts can ask 5 questions a day.