Applying Systems Analysis and Design in Business Settings

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

Applying Systems Analysis and Design in Business Settings

System Analysis and Design · Chapter 2: Business Analysis Tools and Development MethodsSection 2.1 · lesson 7 of 6910 min · free with a free account

← The Systems Analyst: What They Do and Why It MattersNext lesson: Essential Tools, Methods, and Software for Business Analysis →

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

Organizational levels, systems requests, business cases, and strategic alignment.

  • Identify the operational, tactical, and strategic levels and what each needs
  • Explain where systems requests originate
  • Describe a business case and why a project needs one
  • Explain strategic alignment, across retail, banking, and healthcare

Transcript

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

Business Analysis Tools and Development Methods

Systems Analysis in Business Settings

Chapter one introduced systems analysis in general terms. This chapter puts it to work inside real businesses. We start with the three levels every organization operates on, and what each one needs from a system. Then we look at where systems requests come from. We will see why a project needs a business case before any work begins. We will define strategic alignment. And we will see how all of this plays out in retail, banking, and healthcare.

Figure 2.1

The 3 Organizational Levels

Every organization, whatever its industry, can be pictured as three layers stacked on top of one another. At the bottom is the operational layer. It carries out the day-to-day work. That is where front-line staff and supervisors sit. In the middle is the tactical layer. It monitors and directs that work, over weeks and months. That is the territory of middle managers. At the top is the strategic layer. It sets the organization's long-range direction, and that is where senior executives sit. Why does an analyst care which layer a project serves? Because the layer determines who the users are. It determines how often the information needs to change. And it determines how far ahead the system needs to plan.

What Each Level Needs

One Bank, 3 Levels

Let's make the three levels concrete, using a bank. At the operational level, front-line staff carry out routine, repeatable tasks, and record what happens as it happens. A bank teller processing a deposit is operational work. At the tactical level, middle managers monitor operational activity, allocate resources, and adjust plans over weeks or months. A branch manager reviewing weekly teller productivity is tactical work. At the strategic level, senior executives set long-range goals, and decide the direction the organization will move in over years. The bank's leadership deciding whether to expand into a new region is strategic work. Same organization, three very different kinds of information need.

Connected Layers

An Operational Request, a Strategic Root

These three levels do not operate in isolation. Strategic decisions set the direction that tactical plans must support. And tactical plans, in turn, shape what operational staff are asked to do day to day. That has a practical consequence for analysts. Consider a request to speed up how quickly a teller can process a deposit. On the surface, that looks purely operational. But it can trace back to a strategic goal. For instance, reducing customer wait times, to compete with a rival bank's mobile-first service. Seeing that link changes how the analyst treats the request. It is not just a convenience. It is part of the strategy.

Where Projects Begin

The Systems Request

So where do projects actually begin? A systems project rarely begins because an analyst decides, on their own, that something should be built. It begins with a systems request. That is a formal or informal statement that a new system is needed, or that an existing one should change. Requests can originate at any of the three organizational levels. Recognizing the source helps an analyst understand how urgent the request is, who has the authority to approve it, and how large its scope is likely to be. Organizations handle requests differently. Some route every request through a formal intake process, often a systems request form reviewed by a steering committee. Others allow requests to surface informally, through a conversation between a manager and an analyst. Either way, the request is only a starting point. No analysis has yet confirmed whether, or how, it should be pursued.

4 Sources

Who Asks, and What Triggers It

Requests come from four broad sources. The first is users and front-line staff, usually because of a recurring frustration or bottleneck in daily work. Think of a pharmacy technician, repeatedly re-entering the same insurance data, because two systems do not talk to each other. The second is managers, when there is a gap between current performance and a tactical target. For example, a retail regional manager who cannot get an up-to-date view of stock levels across stores. The third is senior executives, when a new strategic direction cannot be supported by existing systems. A hospital network's leadership deciding to offer telehealth visits is one example. The fourth source sits outside the organization entirely. A change in regulation, technology, or competitive pressure can force a request. For instance, a new data-privacy law that requires banks to change how customer records are stored.

Justifying the Work

The Business Case

Not every systems request becomes a systems project. Organizations have limited time, staff, and money, so a request has to make its case first. That justification is called a business case. It is a clear statement of the problem or opportunity, and why it matters to the organization. It also explains why addressing it now is worth the effort, compared with everything else the organization could be doing. A strong business case answers a small set of questions, in plain language. What problem or opportunity does this address? Who is affected, and how? What happens if the organization does nothing? And how does solving this support what the organization is already trying to achieve? Notice what is not required yet. The detailed costs and benefits are a separate, more technical step that comes later. At this stage, the business case is something an analyst must be able to build, and defend, in conversation with decision-makers.

Worked Example

A Hospital's Admitting Department

Here is what that looks like in practice. In a hospital's admitting department, staff manually re-key patient information. That information already exists in an insurance verification system. A business case for automating that step would state the problem. Duplicate data entry slows down admissions, and it introduces errors. It would name who is affected, the admitting staff and the incoming patients. It would explain what happens if nothing changes. Longer wait times, and a continued risk of mismatched records. And it would connect the fix to the hospital's broader goal of improving patient experience. Four plain answers. That is a business case a decision-maker can act on.

Strategic Alignment

Connected to a Goal Already Committed To

That last question, about what the organization is already trying to achieve, deserves its own name. It is called strategic alignment. Strategic alignment means a systems project is deliberately connected, to one or more of the organization's stated strategic goals. It is not pursued simply because the technology is available, or because a particular department wants it. Alignment is checked by tracing a line from the proposed system, back to a goal the organization has already committed to. Take a retailer whose strategy centers on same-day delivery. It has a clear reason to invest in a real-time inventory system. The same retailer would have a much harder time justifying in-store kiosks, if leadership has chosen not to compete on in-store experience. Here is the uncomfortable truth. A project can be technically excellent, and still fail the organization, if it does not support where the organization is going. Analysts who understand this can explain to skeptical stakeholders why a project deserves limited resources.

Across Industries

Same Levels, Different Systems

The three levels, and the idea of alignment, apply across industries. But the specific systems at each level look very different. In retail, the operational system is point-of-sale checkout. The tactical system is a weekly sales-by-store dashboard. And the strategic system supports market-expansion planning. In banking, it is teller transaction processing, then branch productivity and risk-monitoring reports, then customer-segment growth and product-strategy planning. In healthcare, it is patient registration and scheduling, then department staffing and patient-flow reports. And at the strategic level, service-line expansion planning, such as adding telehealth. Notice the same pattern in every row. Operational systems capture individual transactions. Tactical systems summarize and monitor them. Strategic systems support decisions about direction. So an analyst moving from retail to healthcare will find the structure familiar, even though the systems and their regulations are very different.

Key Takeaways

What to Carry Forward

Let's pull this together. Organizations operate at three levels, operational, tactical, and strategic, each with different users and different information needs. Systems requests can originate from users, managers, executives, or forces outside the organization. A business case justifies a project, by explaining the problem, its impact, and why the organization should act on it now. Strategic alignment means a project is deliberately connected to a goal the organization has already committed to. And retail, banking, and healthcare share the same three-level structure, even though their specific systems differ.

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 Applying Systems Analysis and Design in Business Settings

What are the operational, tactical, and strategic levels of an organization?
They are three layers of work, each with different users and information needs. The operational level carries out day-to-day work, such as a bank teller processing a deposit. The tactical level, run by middle managers, monitors and directs that work over weeks or months, such as reviewing weekly teller productivity. The strategic level, where senior executives sit, sets long-range direction, such as deciding whether to expand into a new region.
Where do systems requests come from?
Systems requests come from four broad sources: users and front-line staff, managers, senior executives, and forces outside the organization. Staff often raise recurring frustrations, such as re-entering the same data in two systems. Managers raise gaps between performance and targets. Executives raise new strategic directions that existing systems cannot support. External changes in regulation, technology, or competition, such as a new data-privacy law, can also force a request.
What is a business case in systems analysis?
A business case is a clear statement of a problem or opportunity that explains why it matters and why addressing it now is worth the effort compared with other work. It answers what problem the project addresses, who is affected and how, what happens if nothing is done, and how the fix supports goals the organization already has. Detailed cost and benefit figures typically come later, in a separate, more technical step.
What does strategic alignment mean for an IT project?
Strategic alignment means a systems project is deliberately connected to one or more goals the organization has already committed to, rather than pursued because the technology exists or one department wants it. A retailer whose strategy centers on same-day delivery can justify a real-time inventory system, but would struggle to justify in-store kiosks if it has chosen not to compete on in-store experience. A technically excellent project can still fail the organization without alignment.

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 →