Programming Concepts

Click to add text

Francis Densil Raj V
Department of Big Data Analytics
St. Joseph’s College
Bengaluru
Introduction
• Programs are developed to
solve real-life problems
• Tend to be huge and
complex
• Programming Methodology is
an approach
• To analyze complex problems
• Planning the software
development
• Controlling the
development process
Types of Programming Methodologies

Types

Object-
Procedural Functional Logical
oriented
Programming  Programming Programming
Programming

Top-down Bottom-up
approach approach
 Procedural Programming
• Problem is broken down
into procedures
• Blocks of code
• Perform one task All
together form the
Program
• Suitable for problems
with low complexity
Eg: Calculator
 Object-oriented Programming

• Entities or Objects 
• Entity - something that has
a real existence
• Object - Object is a real-
world entity
• how to store data related to
the entities
• how the entities behave
• how they interact with each
other
Eg: Student
 Functional Programming

• Broken down into

functional units
• Each unit performs its own
task
• These units joined to form
the complete solution
 Logical Programming

• Broken down into

logical units
• Top-down approach
• Bottom-up approach
Top-down or Modular Approach

• Broken down into

smaller units
• Further smaller units can
be done
• Each unit is called
a module
• Eg:
• Payroll Processing
 Bottom-up Approach

• System design starts with

the lowest level of
components
• Interconnected to get
higher level components
• Hierarchy of all system
components is generated
• Eg: Car System
Understanding the Problem
Requirement
gathering

Problem
Maintenance
definition

Training and
support SDLC System design

Documentation Implementation

Testing
 Requirement Gathering
• Clients • Understanding the Needs
• Not able to clearly define
problems
• Just have vague idea what
they want
• Developers
• Gather Client Requirements
• 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?
Techniques Document Failure
• Interviews • Create clear and concise • Incomplete problem
• Need thorough definition
• Questionnaires requirements document in
order to identify • Incorrect program goals
• Studying existing system
documents • SMART • Re-work to deliver
• Specific required outcome to
• Analyzing business data client
• Measurable
• agreed upon • Increased costs
• realistic and time-based • Delayed delivery
requirements
 Problem Definition

• Unambiguously state what

problem or problems need to
be solved
• Define project scope
• Keep the team focused
• Keep the project on track
• Validate that desired outcome
was achieved at the end of
project
 Identifying the Solution

• Coding is to be the most essential Designing a system

part  • Initially we come up with more
• A part of the process than one solutions
• Before the system can be • But only one solution is required
designed, a solution must be • Unique solution can be obtained
identified based on detailed requirements.
• Flowcharts, data flow diagrams,
entity relationship diagrams
 Flowcharting

• Process of illustrating workflows and data flows in a system through

symbols and diagrams
• Helps identifying a solution to the problem
• Depicts the components of the system visually
• 1. The Oval
• An End or a Beginning
• 2. The Rectangle
• A Step in the Flowcharting Process

• 3. The Arrow
• Indicate Directional Flow
• 4. The Diamond
• Indicate a Decision
Flowchart
Symbols
 Guidelines for Developing Flowcharts

• 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