MODULE 4

đź§© 1. Needs Analysis (Software Engineering 1)

🔹 Definition

A needs analysis is the first step in system development. It identifies what a client or organization needs to solve their problems or improve performance.

Analogy:
Think of it as a doctor’s diagnosis — before prescribing medicine (a system), the doctor (developer) needs to know the patient’s symptoms (problems).


🔹 Purpose

To understand why a solution is needed and what goals must be achieved.

Analogy:
Like asking “Why are we building this bridge?” before drawing blueprints.


🔹 Tools

Interviews, surveys, focus groups, observations, SWOT analysis, Fishbone diagrams, etc.

Analogy:
Like detectives using different tools to gather clues about what’s really going wrong.


🔹 Types of Needs Analysis

Type

Focus

Analogy

User Needs Analysis

End-user requirements, preferences, and expectations.

Like asking customers what kind of food they want before opening a restaurant.

System Needs Analysis

Functional and technical system requirements.

Like checking what parts a car engine needs before assembling it.

Organizational Needs Analysis

Company-wide goals, resources, and structure.

Like assessing a team’s strengths and weaknesses before starting a tournament.


🔹 Steps in Needs Analysis
  1. Understand short- and long-term business goals.

  2. Identify desired performance results.

  3. Examine current performance.

  4. Propose solutions to close the gap.

Analogy:
Like mapping where you are, where you want to go, and how to get there.


🔹 Conducting User Interviews
  • Before: Set goals, prepare questions, get consent.

  • During: Build rapport, ask open-ended questions, avoid leading questions.

  • After: Thank participants, record findings, summarize key points.

Analogy:
Like a journalist gathering real stories — not putting words in people’s mouths.


đź§­ 2. Project Management Tools

Tool

Purpose

Analogy

ProjectLibre

Open-source software for creating tasks, dependencies, and Gantt charts.

Like a digital planner that helps track a project’s progress.

Kanban Boards (Trello, Jira)

Visual task management with “To Do → Doing → Done” stages.

Like sticky notes on a wall showing each task’s status.

Gantt Charts (MS Project, Smartsheet)

Visual timeline showing when tasks start and end.

Like a train schedule showing when each train (task) departs and arrives.

Validation Board (Leanstack, Miro)

Tests assumptions and validates project hypotheses.

Like a scientist’s experiment board that confirms if your guesses are right.


đź’° 3. Financial Analysis (Overview)

Key Methods:
  • Horizontal & Vertical Analysis: Compare trends over time or within one report.

  • Ratio Analysis: Evaluate financial health using mathematical relationships.

  • Cash Flow Analysis: Tracks movement of money in and out.

  • Break-even Analysis: Finds the point where income = expenses.

Analogy:
Like checking whether your monthly allowance (income) covers your snacks, bills, and savings.



âš™ 4. Business Process Analysis (BPA)

🔹 Definition

A business process is a sequence of steps to achieve a purpose — often involving people, documents, and systems.

Analogy:
Like a recipe — it has steps, ingredients (inputs), and results (outputs).


🔹 Purpose of BPA

To understand how processes work, identify bottlenecks, and suggest improvements that make business operations more efficient.

Analogy:
Like reorganizing your desk to make it easier to find your supplies.


🔹 Components of BPA
  1. Use Case Diagram: Shows actors (people/systems) and their interactions with business processes.

  2. Activity Diagram: Shows the step-by-step flow of activities and information.

  3. Repository Tools: Store and manage process diagrams (e.g., Enterprise Architect, StarUML).

Analogy:
Use Case = “Who does what”,
Activity Diagram = “How they do it”,
Repository = “The filing cabinet for all diagrams.”


🔹 UML (Unified Modeling Language)

A standardized visual language for modeling processes — includes:

  • Actors (people/systems)

  • Use Cases (actions/processes)

  • Activities (steps)

  • Objects (documents)

  • Decisions (branches/choices)

Analogy:
Like comic panels showing who’s in the scene, what they’re doing, and what happens next.


🔹 Outputs of BPA
  • Use Case Diagram

  • Activity Diagrams

  • Process Descriptions

  • Time-procedure charts

  • Bottlenecks and recommendations

Analogy:
Like creating a blueprint for how your business “machine” runs and where it can be oiled.


đź§ľ Summary Table

Term / Concept

Definition

Simple Analogy

Needs Analysis

Identifies what a client or organization truly needs before building a system.

Doctor diagnosing before treatment.

User Needs Analysis

Finds out what users want and expect.

Asking diners what food they like before opening a restaurant.

System Needs Analysis

Determines what features or specs the system must have.

Listing parts before building a car.

Organizational Needs Analysis

Examines company goals and structure.

Studying a team’s strengths before a game.

User Interview

Gathering firsthand info from users through conversation.

Like a reporter interviewing people for real stories.

ProjectLibre

Free tool for managing project timelines and tasks.

A digital planner for projects.

Kanban Board

Visual tool showing tasks’ progress.

Sticky notes moving from “To Do” to “Done.”

Gantt Chart

Timeline showing when tasks start and finish.

Train schedule for project tasks.

Validation Board

Tool for testing assumptions and validating ideas.

Science lab board for confirming hypotheses.

Business Process

Series of connected steps achieving a goal.

Recipe with ingredients and steps.

Business Process Analysis (BPA)

Study of how a process works to improve it.

Cleaning and organizing your workspace for efficiency.

Use Case Diagram

Visual overview of actors and processes.

Map of who’s doing what.

Activity Diagram

Detailed step-by-step process map.

Flowchart of actions and decisions.

UML

Standard language for creating process diagrams.

Universal “grammar” for visual system blueprints.

Repository Tools

Software for storing process models.

Digital filing cabinet.

Break-even Analysis

Finds the point where profit = zero.

When your earnings just cover your expenses.

Cash Flow Analysis

Tracks money coming in and going out.

Checking your wallet balance daily.