The Five Core Phases of the Systems Analysis and Design Life Cycle

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

The Five Core Phases of the Systems Analysis and Design Life Cycle

System Analysis and Design · Chapter 1: Introduction to Systems Analysis and the Analyst's RoleSection 1.4 · lesson 4 of 698 min · free with a free account

← Where Systems Analysis Fits in Software EngineeringNext lesson: Why the Life Cycle Is Iterative: Feedback Loops, Phase Revisits, and Continuous Refinement →

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

Planning, analysis, design, implementation, and maintenance - and the gates between them.

  • Identify the 5 core phases in their correct order
  • Describe each phase's goal, activities, and deliverables
  • Explain what a phase gate is and why it matters
  • Connect this overview to the phase-specific material ahead

Transcript

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

Systems Analysis and the Analyst's Role

The 5 Core Phases of the Life Cycle

Every information system project follows a path, from the first idea to the day the system is retired. This section maps that path at a survey level. It is called the systems analysis and design life cycle, and it has five core phases. Planning, analysis, design, implementation, and maintenance. We will look at the goal, the key activities, and the deliverables of each one. We will also meet the phase gate, the formal checkpoint between phases. Think of this as the map of the whole course. Later sections zoom in on individual phases.

Why Phases?

Why Break the Work Into Phases

Why divide the work into phases at all? Because building or replacing an information system is expensive, and it is risky. Treat it as one long, undivided effort, and problems stay hidden until the very end. The life cycle breaks that effort into five sequential phases. That way, the project can be checked, corrected, and formally approved in stages, rather than all at once. The phases are chained together. Each phase takes the approved output of the phase before it, as its starting point. And each phase produces its own deliverable, which becomes the input to the phase that follows. So the quality of every phase depends on the quality of the one before it. Staging the work also limits how far a mistake can travel before someone checks it.

The Decision Point

What Is a Phase Gate?

The checkpoints between phases have a name. They are called phase gates. A phase gate is a formal decision point, at the boundary between two phases. A sponsor, a steering committee, or another designated authority reviews that phase's deliverable. Then they decide whether the project is ready to move forward. A gate can end in one of three ways. The project proceeds to the next phase. Or the current phase is reworked, to correct a gap. Or the project is cancelled, because it no longer justifies its cost. Notice that cancelling is a legitimate outcome. A gate that can never say no is not really a gate. Passing a gate is what turns a draft deliverable into an approved one. And only an approved deliverable is something later phases can safely build on.

Figure 1.2

The 5 Phases at a Glance

Here are all five phases in sequence. Planning, then analysis, then design, then implementation, and finally maintenance. Between each pair of phases sits a gate. Gate one sits between planning and analysis. Gate four sits between implementation and maintenance. A project moves forward only when the gate immediately before the next phase has been passed. Here is the detail worth noticing. Each phase's deliverable is exactly what the next gate reviews. The gates are not general progress meetings. Each one examines a specific piece of work. The next five slides walk through the phases one at a time. For each, listen for three things. The goal, the activities, and the deliverable the gate will review.

Phase 1

Planning

Phase one is planning. Its goal is to confirm that the project is worth pursuing, and to scope it, before committing resources. The key activities start with identifying the problem or opportunity. Then comes a feasibility check, along with an estimate of the resources and schedule required. The deliverables are a project charter, a preliminary scope statement, and a feasibility summary. At the gate, the sponsor approves the charter. And the sponsor funds the project, so it can proceed to analysis. Planning is where the organization decides whether to spend money at all. Everything else depends on that yes.

Phase 2

Analysis

Phase two is analysis, the focus of this course. Its goal is to understand the current process, and to define what the new system must do. The central activity is requirements gathering. That happens through interviews, observation, and document review. The analyst also models the current process, and validates the requirements. The deliverables are a requirements document, along with process and data models. At the gate, stakeholders sign off that the requirements are complete and correct. That sign-off matters. It is the business confirming that this is, in fact, what they need. Without it, the designers in the next phase would be building on a guess.

Phase 3

Design

Phase three is design. Its goal is to turn the approved requirements into a technical blueprint that developers can build from. The activities include database design, interface and screen design, and architecture and component design. The phase ends with a design review. The deliverables are a design specification, a database schema, interface mockups, and an architecture diagram. At the gate, the design review authority approves the specification for build. Notice the word approved in the goal. Design starts from requirements that have already passed a gate. Analysis said what. Design now says how.

Phase 4

Implementation

Phase four is implementation. Its goal is to build, test, and deploy a working system. The activities include coding or configuration. They include unit testing, integration testing, and system testing. They also include converting existing data, and training the users. And finally, there is cutover, the moment the organization switches to the new system. The deliverables are a tested system, training materials, converted data, and a cutover plan. At the gate, acceptance testing passes, and the sponsor approves go-live. Only then does the system go into daily use.

Phase 5

Maintenance

Phase five is maintenance. Its goal is to keep the system running correctly, and to adapt it as needs change after go-live. The activities are monitoring, defect correction, handling enhancement requests, and periodic review. The deliverables are change requests, release notes, and periodic review reports. And maintenance has a gate too. It is a formal decision to retire the system, or to substantially redesign it, when that time comes. This is a point people often miss. Maintenance is a phase of the life cycle, not an afterthought that begins once the life cycle is done. A running system still needs planned, accountable work, and treating maintenance as a phase keeps it that way.

Why Gates Matter

Skipping a Gate Does Not Skip the Work

Now back to why the gates matter. The analysis phase cannot begin in earnest until the planning phase's charter is approved. And the design phase cannot begin until the analysis phase's requirements document is signed off. It can be tempting to skip a gate, to save time. But skipping a gate does not remove the underlying work. It just moves the risk of an incomplete deliverable further into the project. And further into the project is exactly where it is far more expensive to fix. A skipped gate is not saved time. It is borrowed time, with interest. Picture a team that starts coding before the requirements are signed off. They may build something technically complete that nobody has confirmed is correct.

Key Takeaways

What to Carry Forward

Let's pull this together. The life cycle has five sequential phases. Planning, analysis, design, implementation, and maintenance. Each phase has its own goal, key activities, and deliverable. And that deliverable becomes the input to the next phase. A phase gate is the formal decision point between two phases. There, a deliverable is approved, or sent back for rework, or the project is cancelled. And maintenance is a genuine phase, not something that begins once the life cycle is over. This section has stayed at the overview level on purpose. Planning, design, and implementation each get their own in-depth treatment later in the course.

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 The Five Core Phases of the Systems Analysis and Design Life Cycle

What are the five phases of the systems analysis and design life cycle?
The five phases, in order, are planning, analysis, design, implementation, and maintenance. Planning confirms the project is worth pursuing and scopes it. Analysis defines what the new system must do. Design turns approved requirements into a technical blueprint. Implementation builds, tests, and deploys the system, including data conversion, user training, and cutover. Maintenance keeps the system running correctly and adapts it as needs change after go-live.
What is a phase gate in a project life cycle?
A phase gate is a formal decision point between two phases, where a sponsor, steering committee, or other designated authority reviews the phase's deliverable and decides what happens next. The project can proceed, the current phase can be reworked to fix a gap, or the project can be cancelled because it no longer justifies its cost. Passing a gate turns a draft deliverable into an approved one that later phases can safely build on.
What deliverables does each phase of the systems development life cycle produce?
Each phase produces a deliverable that the next gate reviews. Planning yields a project charter, preliminary scope statement, and feasibility summary. Analysis yields a requirements document with process and data models. Design yields a design specification, database schema, interface mockups, and architecture diagram. Implementation yields a tested system, training materials, converted data, and a cutover plan. Maintenance yields change requests, release notes, and periodic review reports.
Is it a good idea to skip a phase gate to save time?
Skipping a phase gate usually does not save time, because the underlying work is still needed; it just moves the risk of an incomplete deliverable later into the project, where fixing it costs far more. A team that starts coding before requirements are signed off may build something technically complete that nobody has confirmed is correct. A skipped gate is better thought of as borrowed time, repaid with interest.

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 →