Skip to content
Coming soon

Systems Analysis and Design

Bridge the critical gap between fuzzy business problems and technical system architecture through proven requirements elicitation, DFDs, and UML modeling.

  • 12 modules
  • 12 lessons
  • Shallows to Landfall
  • Video + reading

This course is being written. The outline below is what it will teach; follow the Telegram channel to hear the day it opens.

What you'll be able to do

  • Elicit and document unambiguous functional and non-functional requirements
  • Model business workflows with Data Flow Diagrams (DFDs) and UML diagrams
  • Design intuitive user interfaces and resilient system architectures
  • Produce professional Systems Requirements Specifications (SRS) ready for development

The full syllabus

12 modules, from the Shallows down. Open any module to see its lessons.

The Shallows

The role of the analyst, SDLC methodologies, and project feasibility.

  1. 1The analyst's roleBridging business stakeholders and software engineering teams.
    1. 1.1What does a systems analyst do?Soon
  2. 2The systems development life cyclePhases of the SDLC: planning, analysis, design, implementation, and maintenance.
    1. 2.1Navigating the SDLCSoon
  3. 3Project initiation and feasibilityTechnical, economic, operational, and schedule feasibility assessments.
    1. 3.1Assessing system feasibilitySoon

Currents

Requirements elicitation, process modeling with DFDs, use cases, and data modeling.

  1. 4Requirements elicitationStakeholder interviews, surveys, document analysis, and observation.
    1. 4.1Gathering true user needsSoon
  2. 5Process modeling with DFDsContext diagrams, Level 0 DFDs, and functional decomposition.
    1. 5.1Drawing data flow diagramsSoon
  3. 6Use cases and scenariosActors, use case diagrams, normal and alternative execution flows.
    1. 6.1Documenting use case specificationsSoon
  4. 7Data modeling for analystsLogical ER diagrams and data dictionaries for development teams.
    1. 7.1Logical data modelingSoon

Deep Water

UML modeling, UI/UX design, architecture specification, and testing strategies.

  1. 8Object-oriented analysis with UMLClass diagrams, sequence diagrams, and activity diagrams.
    1. 8.1Modeling systems with UMLSoon
  2. 9System architecture and UI designTiered architectures, wireframing, and interface design principles.
    1. 9.1Specifying architecture and UISoon
  3. 10Agile vs plan-driven approachesScrum, user stories, sprint planning versus traditional stage-gate governance.
    1. 10.1The analyst in agile environmentsSoon
  4. 11Implementation, testing, and cutoverSystem testing, User Acceptance Testing (UAT), cutover strategies, and maintenance.
    1. 11.1Testing and system transitionSoon

Landfall

Capstone project: a complete Software Requirements Specification.

  1. 12Capstone: Complete system specificationAuthor a complete Systems Requirements Specification (SRS) for a real organization.
    1. 12.1Delivering the SRS documentProjectSoon

Who it's for

  • Aspiring systems analysts, business analysts, and product managers
  • Software engineers looking to improve architectural specifications and scoping
  • Information Systems university students preparing for senior project capstones

What you need

  • Basic understanding of organizational workflows and technology systems
  • No programming experience required

Systems Analysis and Design is coming

Enrollment opens when the first modules are ready. The channel announces it first.

What it will include

  • Step-by-step video lectures on diagramming and specifications
  • Professional SRS templates, interview guides, and diagramming stencils
  • Private Telegram community with direct instructor project feedback