SANE 1.1 Who is a Systems Analyst?

SANE 1.2 Systems Analyst vs. Business Analyst

SANE 1.3 Where Do Analysts Work?

SANE 1.4 Why Systems Analysis Matters

SANE 2.1 Software Development Lifecycle and Analyst’s Role

SANE 2.2 Types of Requirements: Business, User, System

SANE 2.3 Requirements Gathering Methods

SANE 2.4 Documenting Requirements: User Stories, Use Cases, Diagrams

SANE 2.5 Good vs. Bad Requirements

SANE 3.1 What Are Business Processes?

SANE 3.2 Modeling Techniques: BPMN, IDEF0

SANE 3.3 Common Modeling Mistakes

SANE 3.4 Diagrams: BPMN, UML, ERD

SANE 4.1 Types of Documentation: BRD, SRS, Vision, Live Specs

SANE 4.2 Writing Clear Specifications

SANE 4.3 Data Formats: JSON, XML, YAML

SANE 4.4 Tools for Analysts: Miro, Draw.io, Figma, Confluence, Jira, Notion

SANE 5.1 Analyst’s Interaction with Development Teams

SANE 5.2 Collaboration with QA and Requirement Handover

SANE 5.3 The Analyst’s Role in Agile Teams

SANE 5.4 Avoiding Bottlenecks

SANE 6.1 Basics of Software Architecture

SANE 6.2 Client-Server Architecture and HTTP Basics

SANE 6.3 Backend, Frontend, and Databases

SANE 6.4 SQL Essentials for Analysts

SANE 6.5 Feature Lifecycle and CI/CD

SANE 6.6 Understanding Development Constraints