Why Systems Analysis Matters | System Analysis and Design

UPI Study › Courses › System Analysis and Design › Free lessons › Lesson 1.2 Free with a free account

Why Systems Analysis Matters

System Analysis and Design · Chapter 1: Introduction to Systems Analysis and the Analyst's RoleSection 1.2 · lesson 2 of 6910 min · free with a free account

← What Is Systems Analysis?Next lesson: Where Systems Analysis Fits in Software Engineering →

Earn 3 college credits for System Analysis and DesignRecommended for credit by NCCRS · Computer Science 390 · self-paced · one payment, lifetime access
Enroll in System Analysis and Design · $250 →Download the syllabus (PDF)

In this lesson

What goes wrong without it, what it costs, and what it buys.

  • Explain what goes wrong when analysis is skipped or rushed
  • Describe why a defect costs more the later it is found
  • Identify the business benefits of doing analysis well
  • Connect real project outcomes to the analysis decisions behind them

Transcript

Everything said in the video, section by section (1,397 words). Read along, or search it.

Systems Analysis and the Analyst's Role

Why Systems Analysis Matters

Here is an uncomfortable fact about failed software projects. Most of them were not short of good programmers. They were short of a clear answer to one question. What was this system actually supposed to do? This section is about why that question deserves serious time. We will look at what goes wrong when analysis is skipped or rushed. We will see why a defect costs more and more, the later it is found. We will walk through three well-documented failures, and trace each one back to its analysis gap. And we will close with what good analysis buys a business, beyond simply avoiding disaster.

From Idea to System

The Step Between the Idea and the Build

Every information system starts as an idea. Maybe it is automating a manual process, or replacing an aging platform. Maybe it gives a business a capability it does not have yet. Between that idea and a working system, there is a critical step. Figuring out, in detail, what the system needs to do, for whom, and under what constraints. That step is systems analysis. Now, here is the subtle part. Skip analysis, or rush it to save time, and the project usually does not fail on day one. It fails quietly, one decision at a time. Eventually, the gap between what was built and what was needed becomes too expensive to close. That slow failure is exactly why analysis gets skipped. The damage is not visible when the shortcut is taken.

The Price of Skipping Analysis

3 Consequences That Show Up Again and Again

Three consequences show up again and again, on projects that under-invest in analysis. The first is rework. Requirements that were assumed, rather than confirmed, have to be revisited in the middle of the build. Then code, screens, and data models all get rebuilt around the correction. The second is missed deadlines and blown budgets. Rework eats the schedule and budget buffer that the project was counting on. And problems discovered late are almost always more expensive to fix than early ones. The third consequence is the most painful. A system nobody wanted. A system can be delivered on time and on budget, and still fail. If it solves the wrong problem, because no one analyzed what the business actually needed, the success is hollow.

The Cost of Change Curve

A Defect Costs More the Later It Is Caught

That second consequence deserves a closer look. It is the single most persuasive argument for taking analysis seriously. A defect does not cost the same amount to fix, no matter when it is caught. Look at the relative costs. Call the cost of fixing a defect during requirements one unit. Caught during design, the same defect costs about five times as much. During coding, about ten times. During testing, about fifteen times. And once the system is in maintenance, it can cost around sixty times as much. Notice the shape. The climb is gentle at first, and then it jumps. This pattern is called the cost of change curve. The earlier a misunderstanding is found, the cheaper it is to correct.

Why Analysts Front-Load

A Conversation Now, or a Rewrite Later

Why does the cost climb like that? Think about what has been built on top of the mistake. A misunderstanding found while gathering requirements might cost a short conversation to resolve. Nothing has been built around it yet. The same misunderstanding, found after the system is in daily use, is a different story. Now it can mean rewriting code, retesting, and redeploying. Often at many times the original cost. This is why experienced analysts front-load their questions. Time spent confirming a requirement, before a single line of code is written, is one of the highest-return investments a project can make. A question that feels slow today is usually the cheapest work on the whole project.

Case Study 1

Denver International Airport Baggage System (1990s)

This pattern is not theoretical. Some of the best-known failures in information systems history trace back to a gap in analysis, not a gap in programming skill. Start with the automated baggage system at Denver International Airport, in the nineteen nineties. The airport's opening was delayed by sixteen months. The automated baggage system was eventually scrapped, after cost overruns estimated in the hundreds of millions of dollars. So where was the analysis gap? Different airlines had very different baggage-handling needs. How those needs would be reconciled into one automated design was never fully worked out. And construction and coding began anyway. The scope and complexity of the system were simply never pinned down first.

Case Study 2

The HealthCare.gov Launch (2013)

The second case is the launch of HealthCare dot gov, in twenty thirteen. This was the federal health insurance marketplace website. It crashed within hours of its public launch. Most visitors could not create an account, or enroll. The analysis gap here had two parts. First, the site's components were built by dozens of separate contractors. Those components were never analyzed and tested together, as one system, before launch. Second, realistic estimates of opening-day demand were never built into the requirements. Each piece may have worked on its own. The system as a whole had never been analyzed as a whole.

Case Study 3

The FBI Virtual Case File (2000-2005)

The third case is the F B I's Virtual Case File, which ran from two thousand to two thousand five. The goal was to replace the bureau's paper-based case management system. The effort was abandoned after roughly one hundred seventy million dollars had been spent. The software was judged unusable for agents' daily work. Here, the requirements kept changing during development. Why? Because the initial analysis never pinned down, in enough detail, how agents actually used the existing paper process. That paper process was the very thing the new system was meant to replace. When you do not understand the current process, every new discovery becomes a requirement change mid-build.

The Common Thread

Not a Coding Failure

Put the three cases side by side, and a common thread appears. None of these projects failed because engineers could not write code. Each one failed because the system that got built, did not match the system that was actually needed. And that mismatch traces back to the analysis phase. Not the construction phase. This matters for how you think about your own role. Better programming would not have rescued any of these projects. Better analysis might have.

What Good Analysis Buys

3 Business Benefits

The case for systems analysis is not only about avoiding failure. Done well, it delivers three concrete business benefits. The first is aligning I T with business goals. The system is built to advance a specific business objective, not just to automate a process for its own sake. Imagine an analyst on a retailer's new order system. Sales leadership confirms that faster checkout, not more payment options, will actually move revenue. So the design follows that goal. The second benefit is stakeholder value. Everyone who will use, manage, or be affected by the system gets one that fits how they actually work. Interviewing warehouse staff, and not only the operations manager, can surface a barcode-scanning requirement that management never thought to mention. The third benefit is competitive advantage. Clear, well-understood requirements let a system be delivered faster, and adapted sooner, than a competitor's. A company that accurately analyzes its customers' self-service needs can launch a portal months ahead of a rival still discovering requirements.

Key Terms

The Vocabulary of This Section

Let's lock in the vocabulary from this section. Systems analysis is the process of studying a business problem or opportunity in detail. Its aim is to determine exactly what a proposed system needs to do, before it is designed or built. A requirement is a specific capability or condition a system must satisfy, to meet a stakeholder's need. A stakeholder is anyone with an interest in how a system is built or how it performs. That includes users, managers, and the people who fund the project. Rework is work that has to be redone, because it was based on an incorrect or incomplete understanding. And the cost of change curve is the pattern, in which the cost of fixing a defect rises sharply, the later it is discovered.

Key Takeaways

What to Carry Forward

To pull this together. Skipping or rushing systems analysis does not usually cause immediate failure. Instead, it causes rework, schedule slippage, and systems that solve the wrong problem. A defect is cheapest to fix at the moment it is found. The longer it goes unnoticed, the more it costs to correct. Some of the most expensive failures on record, including Denver's baggage system and HealthCare dot gov's launch, trace back to gaps in analysis. Not gaps in coding. And good analysis pays for itself. It aligns the system with business goals, delivers value to every stakeholder, and gets a working system to market ahead of competitors.

About System Analysis and Design at UPI Study

System Analysis and Design (Computer Science 390) is a self-paced online course of 69 video lessons in 9 chapters, from the analyst's role and requirements to UML modeling, interface and database design, testing, maintenance and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take System Analysis and Design with UPI Study

From business problem to working systemSystem Analysis and Design teaches how analysts study a business need and turn it into a system design: requirements, UML and data-flow models, interface and database design, implementation and project management. It is a core course in information systems and IT degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

System Analysis and Design carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Why Systems Analysis Matters

What happens when systems analysis is skipped or rushed?
Skipping or rushing analysis rarely causes immediate failure; instead it leads to rework, missed deadlines, blown budgets, and sometimes a system nobody wanted. Requirements that were assumed rather than confirmed must be revisited mid-build, forcing code, screens, and data models to be rebuilt. A project can even finish on time and on budget yet still fail, because it solves the wrong problem.
Why does a software defect cost more to fix the later it is found?
A defect costs more later because more work has been built on top of it. A misunderstanding caught during requirements gathering may take a short conversation to fix, but once the system is in daily use it can mean rewriting, retesting, and redeploying code. One illustrative scale puts the cost at about 5 times the requirements-stage cost during design, 10 times in coding, 15 times in testing, and around 60 times in maintenance. This is the cost of change curve.
What caused IT project failures like the Denver airport baggage system and the FBI Virtual Case File?
These failures trace back mainly to gaps in analysis rather than poor programming. At Denver International Airport in the 1990s, the differing baggage needs of the airlines were not fully reconciled before construction and coding began, and the airport's opening was delayed by 16 months. The FBI's Virtual Case File was abandoned after roughly $170 million was spent, largely because the initial analysis did not pin down how agents actually used the paper process it was replacing.
What are the business benefits of doing systems analysis well?
Good systems analysis aligns IT with business goals, delivers value to stakeholders, and creates competitive advantage. Alignment means the system advances a specific objective, such as faster checkout, rather than automating for its own sake. Stakeholder value comes from building around how people actually work, for example by interviewing warehouse staff as well as managers. Clear requirements also let a company deliver and adapt a system faster than rivals still discovering their needs.

About the System Analysis and Design course

How many college credits is System Analysis and Design?
System Analysis and Design (Computer Science 390) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does System Analysis and Design cost and what is included?
$250, paid once, with lifetime access: all 69 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does System Analysis and Design take?
It is self-paced with no deadlines. The 69 lessons total about 9 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in System Analysis and Design.

69 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in System Analysis and Design →Download the syllabusEvery course with PRO →
System Analysis and Design
3 credits · NCCRSEnroll →