TOOLS AND TECHNIQUES

FOR SYSTEM ANALYSIS & DESIGN

WHAT ARE Requirement Gathering: Tools help capture and document user requirements,

SYSTEM ANALYSIS ensuring all stakeholder needs are considered and addressed.

AND DESIGN Modeling: They enable the creation of visual models, such as flowcharts, UML
diagrams, and data models, to represent the system's structure and behavior.

TOOLS? Design: Tools assist in designing the software architecture and detailed
design, including user interfaces, data storage, and system interactions.
Software analysis and design tools
Documentation: They help in generating and maintaining comprehensive
are specialized applications used to
documentation, which is crucial for communication among team members
support various stages of the
and future maintenance.
software development lifecycle. They
help developers and designers
Analysis: Tools provide capabilities to analyze software designs for potential
understand, plan, model, and issues, such as performance bottlenecks or design flaws, ensuring the
document software systems to robustness of the final product.
ensure that the final product meets
requirements and functions Collaboration: They support collaborative work by allowing multiple team
effectively. members to work together on the same project, facilitating coordination and
integration.
1. REQUIREMENT GATHERING 2. MODELING &
TOOLS & TECHNIQUES DOCUMENTATION TOOLS
Used to collect and clarify user needs. Used to represent system requirements visually.
Interviews – One-on-one or group sessions with Data Flow Diagrams (DFD) – Show the movement of data
stakeholders. between processes.
Questionnaires & Surveys – Structured or semi- Entity-Relationship Diagrams (ERD) – Depict data entities
structured written questions. and relationships.
Observation – Watching users perform their work to Unified Modeling Language (UML) diagrams:
capture workflow details. Use Case Diagram
Document Review – Studying existing forms, reports, Class Diagram
policies, manuals. Sequence Diagram
Workshops / JAD (Joint Application Development) – Activity Diagram
Facilitated sessions with stakeholders to define Flowcharts – Show process flow using symbols.
requirements collaboratively. Context Diagrams – Show system boundaries and external
Brainstorming – Generating ideas quickly without entities.
immediate evaluation. Wireframes / Mockups – Low-fidelity UI designs for user
Prototyping – Building a rough version of the system feedback.
to refine requirements. Storyboards – Sequential depiction of system interaction.
3. FEASIBILITY & ANALYSIS 4. PROBLEM ANALYSIS &
TECHNIQUES DECISION-MAKING TOOLS

Used to check if the project is viable. Used to explore issues and choose solutions.

Cost-Benefit Analysis (CBA) – Compare expected benefits Root Cause Analysis (RCA) – Find the true cause of a
with costs. problem.
SWOT Analysis – Identify Strengths, Weaknesses, Cause-and-Effect Diagram (Ishikawa / Fishbone) – Map
Opportunities, Threats. possible causes.
Technical Feasibility Study – Assess if required Decision Trees – Visual map of decisions and possible
technology/resources exist. outcomes.
Operational Feasibility – Check if the solution fits user needs Gap Analysis – Compare current vs. desired state.
& culture. Benchmarking – Compare with industry best practices.
Legal & Ethical Feasibility – Ensure compliance with laws and
ethics.
Risk Analysis – Identify and prioritize risks.
HALDIRAM’S
DIGITAL
CASE
TRANSFORMATION
Haldiram, one of India’s largest sweets
STUDY
and snacks manufacturers, is famous for
its bhujia, rasgulla, and namkeen.

Although business is booming, Haldiram’s

order processing and inventory
management are still done mostly
manually in many branches.

Due to increasing online orders, supply chain delays, and

customer complaints, the management decides to develop a
Centralized Order & Inventory Management System (COIMS).
PLANNING Problems Identified:
Stock shortages during festivals.
PHASE Orders from online platforms (Swiggy, Zomato) are not synced with
in-store orders.
Difficulty in predicting demand.

Haldiram’s Head Office in

Nagpur calls a meeting of
senior managers from
Tools & Techniques Used:
manufacturing, retail, and SWOT Analysis – To evaluate strengths (brand loyalty), weaknesses
online sales divisions. (manual process), opportunities (growing e-commerce), and threats
(competition from Bikaji).
Cost-Benefit Analysis – To compare the investment in a new system
vs. the benefits from reduced losses and increased sales.
Risk Analysis – To assess risks like system downtime
REQUIREMENT
What Happens:
GATHERING
Observation – Analyst watches how orders are processed at a
flagship store in Delhi.
Interviews – Talks to sales staff, warehouse managers, and online
The System Analyst visits order team.
multiple Haldiram outlets and Document Review – Examines old stock reports, supplier contracts,
and delivery records.
the central warehouse.
Questionnaires – Sent to store managers across India to understand
their pain points.
JAD Sessions – Conducted between IT team, store managers, and
online sales division to finalize key requirements.
Prototyping – A rough UI of the new order dashboard is shown for
feedback.
MODELING
Models Created:
THE SYSTEM
Context Diagram – Shows external entities like suppliers, customers,
and payment gateways interacting with the system.
Data Flow Diagram (DFD) – Depicts order flow from online platforms
The Analyst now prepares to central processing.
visual models for clarity. Entity-Relationship Diagram (ERD) – Models entities like Products,
Orders, Customers, Suppliers.
UML Use Case Diagram – Displays different roles (Store Manager,
Warehouse Staff, Customer).
Wireframes – Designed for the order tracking page and stock level
dashboard.
FEASIBILITY
VERIFICATION
Technical Feasibility – Can the new system integrate with
Swiggy/Zomato APIs? (Yes)
Operational Feasibility – Will store staff adapt easily? (Training
The team confirms: planned)
PROBLEM
ANALYSIS FOR
IMPROVEMENT Tool Used:

Root Cause Analysis (Fishbone Diagram) –

Causes found:
Before finalizing, they Overestimation of demand
investigate why last year’s late supplier deliveries
Diwali sales had 30% unsold poor inter-branch stock transfer
stock in certain cities.
 After 6 months, the Centralized Order & Inventory Management System
goes live:
Stock levels auto-update in real-time across outlets.
Online and offline orders are synced instantly.

OUTCOME Predictive analytics help prepare for festive demand.

Customer complaints drop by 40%, and sales increase during Diwali

season by 25%.