Skip to content
አማርኛEnglish

Theme

ይህ ገጽ ገና ወደ አማርኛ አልተተረጎመም፤ ስለዚህ በእንግሊዝኛ ቀርቧል። የእንግሊዝኛውን ገጽ ክፈቱ

በቅርቡ

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 ክፍሎች
  • 12 ትምህርቶች
  • Shallows to Landfall
  • Free to learn

This course is being written. Its lessons will be free here, like every lesson on Mawj. The outline below is what it will teach; follow the Telegram channel to hear the day it opens.

Get notified on Telegram

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. , coming soon
    1The analyst's roleBridging business stakeholders and software engineering teams.
    1. 1.1What does a systems analyst do?በቅርቡ
  2. , coming soon
    2The systems development life cyclePhases of the SDLC: planning, analysis, design, implementation, and maintenance.
    1. 2.1Navigating the SDLCበቅርቡ
  3. , coming soon
    3Project initiation and feasibilityTechnical, economic, operational, and schedule feasibility assessments.
    1. 3.1Assessing system feasibilityበቅርቡ

Currents

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

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

Deep Water

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

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

Landfall

Capstone project: a complete Software Requirements Specification.

  1. , coming soon
    12Capstone: Complete system specificationAuthor a complete Systems Requirements Specification (SRS) for a real organization.
    1. 12.1Delivering the SRS document (ፕሮጀክት)በቅርቡ

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