SDLC, DFD vs Flowchart | MAD - 2.0

Main ideas / lessons

1) SDLC (Software Development Life Cycle)

• Definition: A step-by-step process software companies use to design, build, and test high-quality software.
• Role: Acts like a detailed plan/roadmap guiding the development team from the initial idea to final launch.

Main goals

• Produce software that meets customer needs
• Be completed on time
• Stay within budget

SDLC phases (methodology / step-by-step instructions)

1. Planning
   • Collect all customer requirements
   • Estimate cost and development time
2. Defining
   • Convert gathered requirements into an SRS document (Software Requirement Specification)
   • Specify what the software will be built to do
3. Designing
   • Create/design the user interface
   • Define/structure the system design
4. Building
   • Developers begin writing the actual code
5. Testing
   • Check software for errors/bugs
   • Fix bugs early (at the stage where they are found) to prevent escalation
6. Deployment (Release)
   • When complete, deploy software for release to the market
   • Users download and use the software

Significance / benefits of SDLC

• Organized process: Uses a standard structure so work doesn’t become chaotic or misaligned late in development.
• Ensures quality: Errors are checked and fixed early, so they don’t become bigger problems later.
• Cost and time management:
  • Planning estimates time and cost in advance
  • Customer requirements are defined early to increase the chance the final product matches expectations
• Easy maintenance: Structured development and documentation make it easier for new developers to understand and update the software later.

---

2) DFD (Data Flow Diagram) vs Flowchart

DFD (Data Flow Diagram)

• Purpose: Represents how data flows through a system.
• What it shows:
  • How information is entered into the system
  • Who changes the data
  • Where data is stored
  • How stored data is retrieved and used as input/output
• Example concept described:
  • Student provides an enrollment number
  • Enrollment data is used to retrieve the result from the database
  • The system outputs/displays the result on a web page
• Key uses:
  • Visual representation of data movement
  • Understanding the flow: input → processing → output, without heavy logic detail
  • Communication tool: even non-technical people can understand it
• Typical structure elements mentioned:
  • Use simple shapes (boxes/circles/arrows)
  • Arrows show movement of data between steps/storage

Flowchart

• Purpose: Represents a complete algorithm/workflow/process, i.e., step-by-step logic and control flow.
• What it shows:
  • The logic of the program using many shapes
  • Control flow from step to step
  • Decision-making and sequence of actions
• Key uses:
  • Modeling algorithmic loops and decision logic
• Typical structure elements mentioned:
  • Various shapes such as diamonds (for decisions) and rectangles (for steps)
  • Arrows connect steps and represent process sequence

Direct comparison (DFD vs Flowchart)

• Flowchart = flow of control / logic
  • Focuses on how the process takes place
  • Represents step-by-step algorithmic logic (including complex decision rules/loops)
• DFD = flow of data
  • Focuses on how information/data moves
  • Shows input, processes, storage, and output
• Complexity and audience:
  • Flowcharts may be harder for non-technical people to understand
  • DFDs are simpler and more accessible

---

Speakers / sources featured

• No specific speaker name or external source is mentioned in the subtitles.