SAN REMIGIO NATIONAL HIGH SCHOOL

San Remigio, Cebu

Teacher-made Learner’s Home Task

Date: Week 3 & 4

Grade/Section: STE 10 – NEWTON & EINSTEIN

Subject Area/s: TLE: COMPUTER EDUCATION

I. MELC: Prepare hand tools and equipment in Computer programming.

II. Objective/s:
Knowledge: List hand tools and equipment based on job requirements.
Skills: Identify appropriate hand tools and equipment.
Values/Attitude: Appreciate computer software tools used in programming.
III. Subject Matter: Tools used in computer programming and software development
IV. References:
https://www.programiz.com/article/flowchart-programming
https://www.tutorialspoint.com/programming_methodologies
https://www.tutorialspoint.com/programming_methodologies/programmingm
ethodologies_flowchart_elements.htm
https://courses.lumenlearning.com/
IV. Procedure:

A. Readings

UNDERSTANDING THE PROBLEM

A typical software development process follows these steps:

 Requirement gathering
 Problem definition
 System design
 Implementation
 Testing
 Documentation
 Training and support
 Maintenance
The first two steps assist the team in understanding the problem, the most
crucial first step towards getting a solution.
Person responsible for gathering requirement, defining the problem and
designing the system is called system analyst.
Requirement Gathering
Usually, clients or users are not able to clearly define their problems or
requirements. They have a vague idea of what they want. So system
developers need to gather client requirements to understand the problem
that needs to be resolved, or what needs to be delivered. Detailed
understanding of the problem is possible only by first understanding the
business area for which the solution is being developed. Some key questions
that help in understanding a business include;

 What is being done?

 How is it being done?
 What is the frequency of a task?
 What is the volume of decisions or transactions?
 What are the problems being encountered?

Some techniques that help in gathering this information are;

 Interviews
 Questionnaires
 Studying existing system documents
 Analyzing business data

System analysts needs to create clear and concise but thorough

requirements document in order to identify SMART - specific, measurable,
agreed upon, realistic and time-based requirements. A failure to do so
results in;

 Incomplete problem definition

 Incorrect program goals
 Re-work to deliver required outcome to client
 Increased costs
 Delayed delivery

Problem Definition
After gathering requirements and analyzing them, problem statement must
be stated clearly. Problem definition should unambiguously state what
problem or problems need to be solved. Having a clear problem statement is
necessary to:

 Define project scope

 Keep the team focused
 Keep the project on track
  Validate that desired outcome was achieved at the end of project
 Often, coding is supposed to be the most essential part of any software
development process. However, coding is just a part of the process and
may actually take the minimum amount of time if the system is
designed correctly. Before the system can be designed, a solution must
be identified for the problem at hand.
 The first thing to be noted about designing a system is that initially the
system analyst may come up with more than one solutions. But the
final solution or the product can be only one. In-depth analysis of data
gathered during the requirement gathering phase can help in coming to
a unique solution. Correctly defining the problem is also crucial for
getting to the solution.
 When faced with the problem of multiple solutions, analysts go for
visual aids like flowcharts, data flow diagrams, entity relationship
diagrams, etc. to understand each solution in depth.

Flowcharting
Flowcharting is the process of illustrating workflows and data flows in a
system through symbols and diagrams. It is an important tool to assist the
system analyst in identifying a solution to the problem. It depicts the
components of the system visually.
Advantages of Flowcharting:
 Visual representation helps in understanding program logic
 They act as blueprints for actual program coding
 Flowcharts are important for program documentation
 Flowcharts are an important aid during program maintenance

Pseudocode
After the system is designed, it is handed over to the project manager for
implementation, i.e. coding. The actual coding of a program is done in a
programming language, which can be understood only by programmers who
are trained in that language. However, before the actual coding occurs, the
basic operating principles, work flows and data flows of the program are
written using a notation similar to the programming language to be used.
Such a notation is called pseudocode.
Flowchart is a diagrammatic representation of sequence of logical steps of a
program. Flowcharts use simple geometric shapes to depict processes and
arrows to show relationships and process/data flow.

Flowchart Symbols
Here is a chart for some of the common symbols used in drawing flowcharts.
SYMBOL SYMBOL PURPOSE
NAME
Start/Stop Used at the beginning and end
of the algorithm to show start
and end of the program.
Process Indicates processes like
mathematical operations.
Input/ Output Used for denoting program
inputs and outputs.
Decision Stands for decision statements
in a program, where answer is
usually Yes or No.
Arrow / Shows relationships between
Flow Line different shapes.
On-page Connects two or more parts of
Connector a flowchart, which are on the
same page.
Off-page Connects two parts of a
Connector flowchart which are spread
over different pages.
Preparation / Shows operations which have
Initialization no effect other than preparing a
value for a subsequent
conditional or decision step.

Guidelines for Developing Flowcharts

These are some points to keep in mind while developing a flowchart:
 Flowchart can have only one start and one stop symbol
 On-page connectors are referenced using numbers
 Off-page connectors are referenced using alphabets
 General flow of processes is top to bottom or left to right
 Arrows should not cross each other
 Here are some of the examples on Flowcharting:

1. Get the sum of two numbers inputted by a user. 2. A program that will evaluate the inputted
number if it’s “odd” or “even”.
START
START

Initialize first_number,
Second_Number Initialize Number

Get First_Number,
Second_Number
Read Number

Sum =First_Number + Second_Number

Number%2==0
NO YES

Print/Display Sum
ODD EVEN

END
END

1. In getting the sum of two numbers, we 2. To evaluate the inputted number if it’s odd or
even,
need to declare / initialize two variable
First, we need to declare or initialize the variable for
names.
the inputted value.
Here, variables are: Sum, First_Number, Since, we only need to evaluate the value, so after
the input, decision symbol is used to test if the
Second_Number. After the initialization,
inputted number is odd or even. No “process”
read inputs for, First_Number,
symbol since there’s no computation involved in the
Second_Number in order to get the Sum. problem – only, to evaluate the input.
The statement, Number%2==0, means Number
For the process, the formula in getting the
modulo (%) 2 == 0. Modulo operator in
sum is:
programming, always return a remainder value.
Sum =First_Number + Second_Number (Number divided by 2, remainder zero (0), if
remainder is 1 means the number is an “odd”, if
Display the result which is the Sum.
zero (0), the number is even.
 B. Exercises for skill subjects’ / Analysis questions using HOTS
for content subjects

Exercise 1
FLOWCHARTING
Direction: Create a flowchart on the problems below. Use a separate sheet of paper
for your answers.

1. Create a flowchart of a program that will compute for the sum of 3 numbers
and will evaluate if the sum is “odd” or “even”.
(Use variable names: num1, num2, num3, sum)

2. Create a flowchart of a program that will compute for the area and perimeter
of a square. Display the result. (Use variable names: side, perimeter, area)

3. Create a flowchart of a program that will compute for the average of 5 grades.
Display the result. (use variable names, g1, g2, g3, g4, g5, average)

Exercise 2
Direction: Create a flowchart on the problems below. Fill in each symbol with the
best command. Use a separate sheet of paper for your answers.
1. Create a flowchart of a C program that will compute for the average of 8
grades and evaluate the average if “Passed” or “Failed”. Note: Passing grade
is 75%.
 Exercise 3
FLOWCHARTING
Direction: Give at least 1 sample flowcharting showing the step by step process of
computer operations. (Hint: Start with turning on the computer unit)

Exercise 4
FLOWCHARTING
Direction: Identify the flowcharting symbols below. Write your answer in a separate
sheet of paper.

5.
1.

2. 6.

3.
7.

4.
8.
 C. Assessment/Application

Prepared by:
MELROSE R. CONDE
Teacher

Approved by:
Verified by:
ALLAN C. CANETE JOSEPHUS G. ARELLANO
MT-I, TLE
ASP II, SHS

Address: IPHO Bldg., Sudlon, Lahug, Cebu City

Telephone Nos.: (032) 520-3216 – 520-3217; SDS Office: (032) 255-6405; ASDS Apao: (032) 236-
4628