Compiled By: (Jashmi Khadka) Computer

Engineer

Unit 2: Problem Solving Using Computer (5 hrs)

2.1. Problems Analysis (Understanding of the problem, feasibility and
requirement analysis)
Problem analysis is the process of defining a problem and decomposing overall system
into smaller parts to identify possible inputs, processes and outputs associated with the
problem.
Problem analysis takes following subtasks.
1. Specifying the Objective :
First, we need to know what problem is actually being solved. Making a clear statement
of the problem depends upon the size and complexity of the problem.
2. Specifying the Output :
Before identifying inputs required for the system, we need to identify what comes out
of the system. The best way to specify output is to prepare some output forms and
required format for displaying result.
3. Specifying Input Requirements :
After having specified the outputs, the input and data required for the system need to
be specified as well.
4. Specifying Processing Requirements :
When output and inputs are specified, we need to specify process that converts
specified inputs into desired output. If the proposed program is to replace or
supplement an existing one, a careful evaluation of the present processing procedures
needs to be made, noting any improvements that could made.
5. Evaluating the Feasibility :
After the successful completion of all the above four steps one needs to see whether
the things accomplished so far in the process of problem solving are practical and
feasible. To replace an existing system one needs to determine how the potential
improvements outperforms existing system or other similar system.
6. Problem Analysis Documentation
Before concluding the program analysis stage, it is best to record whatever has been
done so far in the first phase of program development. The record should contain the
statement of program objectives, output and input specifications, processing
requirements and feasibility.
Understanding of the problem
Problem-solving in computer programming is the process of analyzing a problem, designing
a logical solution, and implementing it in a way that a computer can execute effectively. It is a
fundamental skill that combines logical thinking, algorithm development, and technical
implementation to address specific challenges or tasks.
Before finding the solution we should understand the problem well. If we fail to understand
the problem we may end up with a useless solution for it. Hence, a wrong solution will not
solve our purpose of problem-solving. Therefore, we need to read the problem carefully and
decide the different functions which the solution will contain.
Following are the key steps in problem solving.
 Compiled By: (Jashmi Khadka) Computer
Engineer

o Asking Questions
o Plan the solutions
o Design the program
o Write the code
o Test and debug
o Refine and optimize
o Document and deploy

Feasibility Analysis
Feasibility Analysis in Software Engineering is analysis to evaluate feasibility of
proposed project or system. It assesses whether a project can be completed successfully,
given the available resources, technology, and constraints. Feasibility analysis is one of
stage among important four stages of Software Project Management Process.
Following are the types of the feasibility study.
1. Technical Feasibility: In Technical Feasibility current resources both hardware
software along with required technology are analyzed/assessed to develop project.
2. Operational Feasibility: Evaluates how the project will integrate with existing
business processes and operations.
3. Economic Feasibility: In Economic Feasibility study cost and benefit of the project is
analyzed.
4. Legal Feasibility: In Legal Feasibility study project is analyzed in legality point of
view.
5. Schedule Feasibility: In Schedule Feasibility Study mainly timelines/deadlines is
analyzed for proposed project.
6. Resource Feasibility: This method evaluates if the resources needed to complete the
software project successfully are adequate and readily available.
Aim of Feasibility Study
 The overall objective of the organization are covered and contributed by the system
or not.
 The implementation of the system be done using current technology or not.
 Can the system be integrated with the other system which are already exist

Requirement Analysis
Requirement analysis is the process of identifying, analyzing and documenting the
requirements of a software product. It ensures that all stakeholders have a clear understanding
of what the system must do and lays the foundation for the design and development process.
Following are the types of Requirements analysis.
1. Functional Requirements
Define the features, behavior, and functionality of the system.
 Compiled By: (Jashmi Khadka) Computer
Engineer

2. Non-Functional Requirements
Describe system attributes such as performance, scalability, security, and usability.
3. Business Requirements
High-level goals of the system from the organization's perspective.
4. User Requirements
Requirements from the perspective of end users, often expressed in user stories.
5. System Requirements
Technical specifications for the software and hardware needed to implement the
solution.

Importance of Requirement Analysis

1. Understanding Stakeholder Needs: Ensures that the end product aligns with the needs
and goals of users and stakeholders.
2. Prevents Scope Creep: Clearly defined requirements help prevent unnecessary
features or changes during development.
3. Reduces Development Errors: Early identification of requirements minimizes
misunderstandings and rework later.
4. Improves Project Planning: Accurate requirements help estimate time, cost, and
resources more effectively.
5. Enhances Quality: Clearly defined and verified requirements lead to higher-quality
software.

2.2. Design (Algorithm and flowchart)

Program design is the process of planning and structuring a software application or
system before writing the actual code. It involves defining the objectives, architecture,
algorithms, and flow of the program to ensure it meets user requirements and functions
efficiently.
Algorithm and flowchart are mainly used for program design.
Algorithm Flowchart
Definition An Algorithm is step-by-step procedure or A Flowchart is diagrammatic
a set of instructions to solve a problem. representation of a process or workflow
using symbols to illustrate steps.
Format Written in textual form, often using Represented using symbols and shapes
pseudocode or structured language. (e.g., rectangles, diamonds, arrows).
Purpose To describe the logic or sequence of To visually represent the flow of a
actions needed to perform a task. process or system.
Readability Easier to understand for people with Easier for non-technical users to
programming knowledge. understand due to its visual nature.
Representation Linear and detailed; focuses on describing Graphical; shows relationships between
each step explicitly. steps and their sequence.
Significance/role/importance/ of the Algorithm and Flowchart in Programming (Why
Algorithm and Flowchart used)
 Problem-Solving and Planning
 Compiled By: (Jashmi Khadka) Computer
Engineer

 Improved Clarity and Understanding

 Reducing Errors and Debugging
 Efficient Program Design
 Communication and Collaboration
 Reusability and Scalability
 Foundation for Programming Concepts

Algorithm
An algorithm is a finite sequence of well-defined instructions that can be used to solve a
computational problem. It provides a step-by-step procedure that convert an input into a
desired output.
Algorithms typically follow a logical structure:
 Input: The algorithm receives input data.
 Processing: The algorithm performs a series of operations on the input data.
 Output: The algorithm produces the desired output
Advantages of Algorithms:
 It is easy to understand.
 An algorithm is a step-wise representation of a solution to a given problem.
 In an Algorithm the problem is broken down into smaller pieces or steps hence, it is
easier for the programmer to convert it into an actual program.
Disadvantages of Algorithms:
 Writing an algorithm takes a long time so it is time-consuming.
 Understanding complex logic through algorithms can be very difficult.
 Branching and Looping statements are difficult to show in Algorithms(imp).

Flowchart
Flowcharts are the visual representations of an algorithm or a process. Flowcharts use
symbols/shapes like arrows, rectangles, and diamonds to properly explain the sequence of
steps involved in the algorithm or process. Flowcharts have their use cases in various fields
such as software development, business process modeling, and engineering.
Symbols used in Flowchart Designs
1. Terminal/Terminator
 Compiled By: (Jashmi Khadka) Computer
Engineer

The oval symbol indicates Start, Stop and Halt in a program’s logic flow. A pause/halt is
generally used in a program logic under some error conditions. Terminal is the first and
last symbols in the flowchart.

Terminal/Terminator
2. Input/Output
A parallelogram denotes any function of input/output type. Program instructions that take
input from input devices and display output on output devices are indicated with
parallelogram in a flowchart.

Input/Output
3. Action/Process
A box represents arithmetic instructions, specific action or operation that occurs as a part
of the process. All arithmetic processes such as adding, subtracting, multiplication and
division are indicated by action/process symbol.

Action/Process
4. Decision
 Compiled By: (Jashmi Khadka) Computer
Engineer

Diamond symbol represents a decision point. Decision based operations such as yes/no
question or true/false are indicated by diamond in flowchart.

Decision
5. On-Page Connector/Reference
Whenever flowchart becomes complex or it spreads over more than one page, it is useful
to use connectors to avoid any confusions. On-Page Connector is represented by a small
circle

On-Page Connector/Reference
6. Flow lines
Flow lines indicate the exact sequence in which instructions are executed. Arrows represent
the direction of flow of control and relationship among different symbols of flowchart.

Flow lines
Rules For Creating a Flowchart
 Compiled By: (Jashmi Khadka) Computer
Engineer

A flowchart is a graphical representation of an algorithm. It should follow some rules while

creating a flowchart
 Rule 1: Flowchart opening statement must be ‘start’ keyword.
 Rule 2: Flowchart ending statement must be ‘end’ keyword.
 Rule 3: All symbols in the flowchart must be connected with an arrow line.
 Rule 4: Each decision point should have two or more distinct outcomes.
 Rule 5: Flow should generally move from top to bottom or left to right.
Advantages of using a Flowchart
 Flowcharts are a better way of communicating the logic of the system.
 Flowcharts act as a guide for blueprint during program designed.
 Flowcharts help in debugging process.
 With the help of flowcharts programs can be easily analyzed.
 They provide better documentation.
 Flowcharts serve as a good proper documentation.
Disadvantages of using a Flowchart
 It is difficult to draw flowcharts for large and complex programs.
 There is no standard to determine the amount of detail.
 It is very difficult to modify the Flowchart.
 Making a flowchart is costly.
 If changes are done in software, then the flowchart must be redrawn

2.3. Coding (Compilation and execution)

Coding, also known as programming, is the process of writing instructions in a
language that a computer can understand to perform specific tasks. These instructions
are written using programming languages such as Python, Java, C++, JavaScript, and
others. Coding translates human ideas into commands that computers execute.
Compilation Execution
Definition Compilation is the process of Execution is the process of
converting source code written in a running the compiled code on
high-level language into machine the computer to perform the
code (or bytecode). desired task.
Purpose Translates human-readable code Executes the instructions in the
into a format that the computer's compiled code to perform
operations or produce output.
 Compiled By: (Jashmi Khadka) Computer
Engineer

hardware or virtual machine can

understand.
Tools Used Requires a compiler (e.g., GCC for Requires an interpreter (for
C/C++, javac for Java). some languages) or an
executable file generated by
the compiler.
Output Produces a compiled file (e.g., .exe, Produces results or performs
.class, or binary). tasks as per the program logic.
Speed Slower, as it involves analyzing and Faster, as it directly runs the
translating the entire source code. machine code or pre-compiled
code.
Languages Used in compiled languages like C, Applies to all languages,
C++, Java (to bytecode), Go, etc. including both compiled and
interpreted languages (e.g.,
Python, JavaScript).
Errors Compilation errors (e.g., syntax Runtime errors (e.g., division
errors, missing semicolons) are by zero, null pointer) occur
detected during this phase. during execution.
Examples - Writing a C program and using a - Running the .exe file created
compiler to create an .exe file. during compilation to see the
program's output.
Dependency Must occur before execution in Depends on successful
compiled languages. compilation in compiled
languages.
2.4. Testing and debugging
Software testing is a process of identifying defects in the software product. It is
performed to validate the behavior of the software or the application compared to
requirements.
Each software or application needs to be tested before delivering to the clients and
checks whether the particular software or the application is working fine as per the
given requirements.
Debugging is the action where the development team or a developer implements after
receiving the test report related to the bugs in the software from the testing team.
In the software development process, debugging includes detecting and modifying
code errors in a software program.
In debugging process, the developer needs to identify the reason behind the particular
bug or defect, which is carried out by analyzing the coding rigorously.
[Link] Testing Debugging

It is the implementation of the software with the The process of fixing and resolving
1.
intent of identifying the defects the defects is known as debugging.
 Compiled By: (Jashmi Khadka) Computer
Engineer

Testing can be performed either manually or The debugging process cannot be

2.
with the help of some automation tools. automated.
A group of test engineers executes testing, and
Debugging is done by the developer
3. sometimes it can be performed by the
or the programmer.
developers.
The test engineers perform manual and
automated test cases on the application, and if The developers will find, evaluates,
4.
they detect any bug or error, they can report and removes the software errors.
back to the development team for fixing.

Without having an understanding of

Programming knowledge is not required to the programming language, we
5.
perform the testing process. cannot proceed with the debugging
process.

After the implementation of the test

Once the coding phase is done, we proceed with
6. case, we can start the Debugging
the testing process.
process.
Software Testing includes two or more Debugging tries to match indication
7. activities such as validation and verification of with cause, hence leading to the error
the software. correction.
It is built on different testing levels such as Unit It is built on different kinds of bugs
8. Testing, Integration Testing, System Testing, because there is no such level of
etc. debugging is possible.
9. Software testing is the presentation of defects. It is a logical procedure.
Software testing is the vital phase of SDLC It is not a part of SDLC because it
10.
(Software Development Life Cycle). occurs as a subset of testing.

2.5. Implementation, Evaluation and Maintenance of Computer programs

Implementation

This phase involves translating software design into executable code and preparing the system for
deployment. Following activities are including in implementation phase.

a. Coding

 Programming: Writing source code in a selected programming language based on the

system design.
 Integration: Combining different modules or components of the software to work together
seamlessly.
 Compiled By: (Jashmi Khadka) Computer
Engineer

 Version Control: Managing changes to the codebase using tools like Git to ensure
collaboration and traceability.

b. Testing

 Unit Testing: Testing individual components for correctness.

 Integration Testing: Ensuring that integrated modules function together as intended.
 System Testing: Validating the entire system against the requirements.
 Performance Testing: Assessing speed, scalability, and responsiveness.

c. Deployment

 Configuration: Setting up environments (e.g., development, staging, production) and

system configurations.
 Data Migration: Transferring data from old systems or formats into the new system.

Evaluation

This stage assesses the software's functionality, performance, and user satisfaction to ensure it
meets requirements. Following activities are taking in evalution.

a. Validation

 Ensuring the software behaves as expected based on functional and non-functional

requirements.

b. Verification

 Comparing the developed system with the initial specifications to confirm correctness.

c. User Acceptance Testing (UAT)

 Allowing end-users to test the software in real-world scenarios and provide feedback.

d. Performance Metrics

 Reliability: Measuring system uptime and error rates.

 Efficiency: Assessing resource usage and response times.
 Scalability: Evaluating how well the software handles increased loads.
 Usability: Ensuring the system is user-friendly and intuitive.

e. Feedback Collection

 Using surveys, feedback forms, or interviews to gather insights from end-users.

Maintenance
 Compiled By: (Jashmi Khadka) Computer
Engineer

After deployment, software requires ongoing maintenance to address bugs, adapt to changes, and
enhance functionality. Following are the types of the maintenance.

a. Corrective Maintenance

 Fixing bugs and issues reported by users or detected during operation.

b. Adaptive Maintenance

 Updating the software to adapt to changes in the environment, such as:

o Operating system upgrades.
o New hardware configurations.
o Regulatory or business requirements.

c. Perfective Maintenance

 Adding new features or enhancing existing functionalities based on user feedback or

market trends.

d. Preventive Maintenance

 Proactively identifying and resolving potential issues to ensure long-term reliability and
performance.
Implementation Evaluation Maintenance
Definition The process of building and The process of The ongoing process of
deploying a computer assessing whether the updating, debugging, and
program from design or program meets its optimizing a program after
specifications. intended purpose and deployment.
requirements.
Objective To convert requirements To determine the To ensure the program
and designs into a program's remains functional, relevant,
functional software effectiveness, and secure over time.
product. reliability, and
compliance with
requirements.
Activities Coding, integrating Performance analysis, Bug fixes, feature
Involved components, testing during usability testing, error enhancements, performance
development, and detection, and optimization, and adapting to
deploying the program. validation against new environments.
specifications.
Key Tools IDEs, version control Testing frameworks, Issue trackers, patch
systems, compilers, monitoring tools, management tools,
debugging tools. analytics, feedback performance monitoring
collection. systems.
 Compiled By: (Jashmi Khadka) Computer
Engineer

Team Developers, system

QA testers, end-users, Maintenance engineers,
Members architects, and quality project managers, and developers, customer support,
Involved assurance teams. analysts. and system administrators.
Challenges Translating requirementsIdentifying subtle Managing legacy code,
into efficient, error-free
issues, subjective user ensuring compatibility, and
code. feedback, and testing addressing evolving security
edge cases. threats.
Duration Finite and project-based Usually short-term Long-term and ongoing
(ends with deployment). (before or immediately (throughout the software
after deployment). lifecycle).
Examples Writing code for a new e- Conducting user Fixing bugs and adding new
commerce platform. acceptance testing for payment options after
the platform. deployment.
Importance Ensures the program is Validates the Keeps the software functional,
created and works as program’s success and secure, and aligned with user
intended initially. identifies areas for needs over time.
improvement.
2.6. Program Documentation
Program documentation refers to written descriptions and explanations that provide
information about a software program's functionality, structure, design, and usage. It is
an essential part of software development that ensures the program is understandable,
maintainable, and usable by developers, users, and other stakeholders.
Following are types of Program Documentation
1. Internal Documentation
o Written within the source code itself.
o Internal Documentation includes comments, code structure and annotations.
 Comments: Inline or block comments explaining the code logic.
 Code Structure: Meaningful variable names, function names, and
code formatting.
 Annotations: Used in modern programming languages to provide
metadata.
o It helps developers understand the code during maintenance or future
updates
2. External Documentation

o Written outside the source code.

o External Documentation includes user manuals, technical manuals and project
reports.
 Compiled By: (Jashmi Khadka) Computer
Engineer

 User Manuals: Guides for end-users to operate the software.

 Technical Manuals: Detailed information for developers about
system architecture, API usage, and program design.
 Project Reports: Summaries of project objectives, design
choices, and progress.

o It provides broader context and usage information for non-developers and

future developers.

Importance of Program Documentation

o Easy Maintenance
o Improves Collaboration
o Enhances Usability
o Simplifies learning
o Acts as a Reference

1. What do you mean by Algorithm and Flowchart? Explain the C compilation process in
brief. (2013 Spring)
2. Discuss the significance of Algorithm and Flow chart in programming. Draw a flow chart
for finding greatest digit for the supplied number by the user.(2014 Fall)
3. What is the importance of documentation in programming? Write an algorithm and draw
flowchart to find and output all the roots of a quadratic equation, for non-zero coefficients.
In case of errors program should report suitable error message. (2014 Spring)
Algorithm
Step 1: Start
Step 2: Read a, b, c values
Step 3: Compute d = b2- 4ac
Step 4: if d > 0 then
o r1 = -b+ sqrt (d)/(2*a)
o r2 = -b -sqrt(d)/(2*a)
o print r1,r2 values
Step 5: Otherwise if d = 0 then
o compute r1 = -b/2a, r2=-b/2a
o print r1,r2 values
Step 6: Otherwise if d < 0 then print roots are imaginary
Step 7: Stop
 Compiled By: (Jashmi Khadka) Computer
Engineer

4. What is a flowchart? Write an algorithm and draw a flowchart to display whether a number
is prime or not. (2015 Fall)
Answer in Question 5
5. Write the significance of algorithm and flowchart in programming. Draw a neat flowchart
to input a number and check it is prime number or not. (2015 Spring)
Algorithm
1. Start
2. Read Number n
3. Set the value of i=2 (Initialize variables)
4. If i<n then go to step 5 otherwise go to step 6
5. If n%i ==0 then go to step 6
 Else, Increment the value of I by 1 and go to step 4.
6. If i==n then
 Print “n is prime number”
 Else
 Print “n is not prime number”
7. Stop

FlowChart
 Compiled By: (Jashmi Khadka) Computer
Engineer

6. Define the role of flowchart in efficient program maintenance which its character. Also
develop a flowchart to print the even numbers between 150 -500. (2016 Fall)
Algorithm
Step 1: start
Step 2: Set Initial value of i=150 and n=150
Step 3: if (i%2==0)
 print value of I and go to step 4 else go to step 4
Step 4: Increment the Value of i=i+1 and go to step 5
Step 5: Check if(i<=500)
 Go to Step 4 else go to step 6
Step 6: Stop
 Compiled By: (Jashmi Khadka) Computer
Engineer

7. What is the significance of algorithm and flowchart in programming? Write an algorithm

and draw a neat flowchart to input a number and check it is palindrome number or not.
[Note: Palindrome number remains same after its reverse such as 989]. (2016 Spring)
Answer in Question 9
8. Define algorithm and flowchart. Draw a flowchart to read 3 numbers from the user and
find the smallest one. (2017 Fall)
9. What do you mean by algorithm and flowchart? Write an algorithm and flowchart to find
palindrome of given number. (2017 Spring)
Algorithm
Step 1: Start
Step 2: Read the input number from the user
Step 3: Declare and initialize the variable reverse=0, and assign input to a temp variable
tempNum=num
Step 4: Start the while loop until num !=0 becomes false
 rem = num % 10
 reverse*= 10 + rem
 num = num / 10
Step 5 : Check if reverse == tempNum
Step 6: If it’s true then the number is a palindrome
Step 7: If not, the number is NOT a palindrome
Step 8: Stop
FlowChart
 Compiled By: (Jashmi Khadka) Computer
Engineer

10. Write algorithm and flowchart to generate Fibonacci sequence of eight terms.(2018 Fall)
Algorithm
Step 1: START
Step 2: Declare variable n1, n2, sum, n=8, i
Step 2: Initialize variables: n1 = 0, n2 = 1, i = 2
Step 3: Read n
Step 4: Repeat this step until i <= n

 sum = n1 + n2
 print sum
 n1 = n2
 n2 = sum
 i=i+1
Step 5: STOP
 Compiled By: (Jashmi Khadka) Computer
Engineer

Flowchart

11. Define the role of flow chart in efficient program maintenance with its character. Also
develop a flow chart to print the Armstrong numbers (2018 Spring) 1³ + 5³ + 3³ = 153
Step 1: Start
Step 2: Declare Variable sum, temp, num
Step 3: Read num from User
Step 4: Initialize Variable sum=0 and temp=num
Step 5: Repeat Until num>
 Compiled By: (Jashmi Khadka) Computer
Engineer

.0
o sum=sum + cube of last digit[(num%10)*(num%10)*(num%10)]
o num=num/10
Step 6: IF sum==temp
Print "Armstrong Number"
ELSE
Print "Not Armstrong Number"
Step 7: Stop
Flowchart
 Compiled By: (Jashmi Khadka) Computer
Engineer

12. What is the role of algorithm in programming? Write down an algorithm to check if the
given numbers is prime or not. (2019 Fall)
Answer in Question 5

13. Differentiate between algorithm and flowchart. Write an algorithm and flowchart to find
the number given by user is divisible by 2,3 and 6 or not. (2019 Spring)
Algorithm
Step 1: Start
Step 2: Input: Read the number (num) from the user.
Step 3: Check divisibility by 2:

 If num % 2 == 0, proceed to the next check; otherwise, conclude that the

number is not divisible by 2, 3, and 6.

Step 4: Check divisibility by 3:

 If num % 3 == 0, proceed to the final check; otherwise, conclude that the

number is not divisible by 2, 3, and 6.

Step 5: Check divisibility by 6:

 If num % 6 == 0 conclude that the number is divisible by 2, 3, and 6.

otherwise, conclude that the number is not divisible by 2, 3, and 6.

Step 6: Output: Print the number is divisible by 2, 3, and 6 .

Step 7: End
14. Why algorithm and flowchart are used in programming? Draw a flowchart to find the sum
of numbers between 50 to 100.(2020 Fall)
Algorithm
Step 1: Start
Step 2: Set i=50, n=100 and Sum=0
Step 3: Check i<=n go to step 4 else go to step 6
Step 4: Calculate Sum=Sum+i and go to step 5
Step 5: i=i+1 go to step 3
Step 6: Stop
15. Judge efficiency of algorithm and flowcharting over program development process. Draw
a flowchart to find out the grade of student when the marks of four subject are given. The
method of assigning grade is as.(2020 Spring)
 Compiled By: (Jashmi Khadka) Computer
Engineer

Percentage Grade
More than or equal to 85 A
Less than 85 and more than or equal to 70 B
Less than 70 and more than or equal to 55 C
Less than 55 and more than or equal to 45 D
Less than 45 and more than or equal to 32 E
Less than 32 F
16. What are the different steps in problem solving using computer? Briefly explain each
step.(2021 Fall)