Session Plan

Module title:** Designing Program Logic

Module code: EIS WDDBA3 M04 0323

Lo1: Program Logic Design nominal hour (.......30 hrs.)

time Content Learning Method Aids & material

Session Objective: At the end of this Session, learners shall be able to:
• Understand the Systems Development Life Cycle (SDLC).
• Understand and create design documentation.
• Demonstrate design approach coding using algorithms, pseudocode, and flowcharts.

Activity Time Content Learning Aids & material

Method

Introduction 1 hr • Overview of Lecture • Projector

the module (50 Discussion • Slide
hrs). presentation
• Importance of •
planning and Whiteboard/Fli
logic in p chart
programming.
• Introduction
to Unit 1:
Program Logic
Design.

Body 5 hrs 1.1. Systems - Interactive - Teacher made

development Presentation hand outs
life cycle - Group - Text book
(SDLC) Discussion on - Diagram of
• Definition and real-world SDLC phases
purpose of project
SDLC. examples
• Detailed - Case study
breakdown of review of a
SDLC phases: simple project's
Preliminary life cycle
Investigation,
Analysis,
 Design,
Implementatio
n, Deployment
& Testing,
Maintenance.
• Benefits of
using SDLC.

4 hrs 1.2. Design - Lecture - Sample logic

documentation - Group activity: model
(Part 1) Create a simple templates
• Importance of logic model for - Whiteboard
design a daily task
documentation. (e.g., making
• What is tea).
Program Logic?
• Introduction
to Logic Models
and their
purpose
(planning,
monitoring,
evaluation).

4 hrs 1.2. Design - Lecture - Text book

documentation - Discussion on - Handouts
(Part 2) common summarizing
• pitfalls in each the 6 phases
Understanding phase.
the
Programming
Process:
1. Understand
the problem
2. Plan the logic
3. Code the
program
4. Translate to
machine
language
5. Test the
program
6. Put into
 production

4 hrs 1.3. Design - Lecture - Computer

approach - Problem- with code/text
coding: solving editor
Algorithms exercise: Write - Projector
• What is an an algorithm
algorithm? for a simple
• problem (e.g.,
Characteristics finding the
of a good largest of three
algorithm numbers).
(precise,
correct, finite,
efficient).
• Data
Structures vs.
Algorithms.
• Introduction
to Pseudo-code
as an algorithm
development
tool.

6 hrs 1.3. Design - Interactive - Computer

approach lecture with with code/text
coding: Pseudo- live coding editor
code examples. - Handouts with
• In-depth look - Hands-on pseudo-code
at Pseudo-code. activity: examples and
• Advantages of Convert simple exercises
using pseudo- problems into
code. pseudo-code.
• Pseudo-code
constructs:
SEQUENCE,
LOOP (WHILE),
SELECTION (IF-
THEN-ELSE).
• Examples and
exercises on
writing pseudo-
code
(calculating
 bonus, interest,
grades).

6 hrs 1.3. Design - - Computer

approach Demonstration: with
coding: Creating flowcharting
Flowcharts flowcharts software (Visio
• What is a using software or online tool
flowchart? (e.g., MS Visio, like [Link])
• Standard [Link]). - Projector
flowchart - Group - Handouts with
symbols exercise: Draw flowchart
(Terminator, a flowchart for symbols and
Process, a given DFD examples
Input/Output, problem.
Decision, - Lecture on
Connectors). DFDs with
• Examples of examples
flowcharts (Course
(Adding Registration,
numbers, Food Ordering
getting out of System).
bed, average
temperature).
• Difference
between
Flowchart and
Pseudo-code.
• Introduction
to DFDs (Data
Flow Diagrams)
and their
symbols.
• Levels of
DFDs (Context,
Level 0).
• Brief
overview of
Structure
Charts, RAD
Model,
Prototyping
Model, and
 CASE tools.

Summary and 1 hr Summary of - Group - Whiteboard

Evaluation Unit 1: discussion
Recap of SDLC, - Q&A session
documentation,
and design
approaches
(algorithms,
pseudo-code,
flowcharts).

Evaluation 1 hr Self-check 1 Paper

(from page 38- Pen
39 of the Computer with
module) Visio/[Link]
Operation
Sheet 1.1
(create a
flowchart using
MS Visio)
Lo1 exam
(Written +
Practical)

Trainer's signature_________________________________ approved by__________________________________

Date__________________________________ signature__________________________________
Session Plan (Continued)

Module title:** Designing Program Logic

Module code: EIS WDDBA3 M04 0323

Lo2: Program Logic Documentation nominal hour (.......20 hrs.)

time Content Learning Method Aids & material

Session Objective: At the end of this Session, learners shall be able to:
• Understand project planning standards.
• Understand and document project scope.
• Identify and revise references.
• Understand logic design templates and validation.

Activity Time Content Learning Aids & material

Method

Introduction 1 hr • Recap of Unit Lecture • Projector

1 (Program Discussion • Whiteboard
Logic Design).
• Introduction
to Unit 2:
Program Logic
Documentation
and its
importance for
project success.

Body 3 hrs 2.1. Project - Lecture - Teacher made

planning - Group hand outs
standards Discussion on - Sample
• What are why standards project plan
project are important.
planning
standards?
• Setting
standards for
project
management.
• Parameters
and
 applications of
project
planning
standards
(Quality
Assurance, Risk
Management,
Security, etc.).

4 hrs 2.2. & 2.3. - Lecture with - Sample SOW

Documentation real-world documents
of Project scope examples. - Handouts
& Project scope - Activity: Draft listing scope
statement a mini project elements
• What is a scope
project scope statement for a
document simple project
(Scope of Work (e.g., "Design a
- SOW)? login page for a
• Key elements website").
of a scope
document:
Goals,
Requirements,
Deliverables,
Milestones,
Assumptions,
Constraints.
• Detailed
breakdown of a
Project Scope
Statement:
Business case,
description,
acceptance
criteria,
limitations,
assumptions,
exclusions,
costs,
agreement.

2 hrs 2.4. - Lecture - Computer

Identification - with database
 and revising Demonstration software (e.g.,
References of a simple MS Access,
• Introduction reference table MySQL)
to Master Data in a database. - Projector
Services (MDS).
• Purpose and
use of
Reference
Tables (e.g.,
Calendar
Tables).

3 hrs 2.5. Logic - Lecture - Copies of the

design - Group activity: sample logic
templates Populate a logic design template
• Purpose of design template from page 52.
logic design for a given
templates. project
• Example of a scenario.
sample logic
design template
(inputs,
activities,
outcomes).

4 hrs 2.6. Logic - Lecture with - Whiteboard

design clear examples for diagrams
validation differentiating
• Software verification and
Verification vs. validation.
Validation. - Role-playing:
• Importance of Conducting a
verification feedback
(checking session with a
design outputs "customer."
against
requirements).
• Importance of
validation
(ensuring the
software meets
user needs).
• Gaining
feedback or
 input from
customers and
stakeholders.

Summary and 1 hr Summary of - Final Q&A - Whiteboard

Evaluation Unit 2: session
Recap of - Group
project scope, discussion
documentation,
templates, and
validation.
Overall Module
Wrap-up.

Evaluation 2 hrs Self-check 2 Paper

(from page 56 Pen
of the module) Computer with
Lap Tests (from flowcharting
page 44: software
Recognize
symbols and
draw a
flowchart)
Lo2 exam
(Written +
Practical)

Trainer's signature_________________________________ approved by__________________________________

Date__________________________________ signature__________________________________