Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 38

PROGRAMMING CONCEPTS

PROGRAM
• A set of instruction needed in order for the
computer to produce desired results.
• Tells the computer how to interact with the
user, interact with computer peripherals
and devices, and to process data
PROGRAMMING LANGUAGE
• Formalized notations which use command
instruction in order to produce the desired
function of a program.
First Generation of Programming
Language
• MACHINE LANGUAGE
▫ Combination of binary digits (0 and 1) is used to
represent a command.
Second Generation of Programming
Language
• ASSEMBLY LANGUAGE
▫ Uses symbolic codes called “Mnemonics” to
represent a command.
▫ This language is still used nowadays because it is
the nearest to the machine language.
MNEMONICS
Third Generation Language (3GL)
• Represented using “English-like structures”
• Ex: BASIC, PASCAL
Fourth Generation Language (4GL)
• Allow and use objects aside from the usual
“English-like” structure of codes.
• Better programs are created.
• Programming was easier because programming
languages are became user-friendly.
• Forms are readily available in order to design a
GUI type of application.
• Web pages also become interactive because of
the availability of better languages.
from 3GL to 4GL
• HIGH LEVEL LANGUAGES
Compilers
• Translates the high level instruction that
programmers have written into a machine
language.
• Ex: Python, C language, C++, JAVA, C#,
COBOL, FORTRAN etc
Interpreter
• Translates the program written by programmers
as the program is running.
• Ex: Basic, Visual basic, Python etc
Systems Programming
• Systems Analyst
▫ person who uses analysis and design techniques
to solve business problems using information
technology.
• The System Analyst must analyze the problem
well in order to provide a good plan of how the
program work
PROBLEM
CREATING SOLVING
A PROGRAM

CRITICAL
THINKING
SYSTEMS DEVELOPMENT LIFE CYCLE
• PROGRAMMERS
• DESIGNERS SOFTWARE
• SYSTEM ANALYSTS DEVELOPMENT
• TEAM
TEST GROUPS
SYSTEMS DEVELOPMENT LIFE CYCLE
PLANNING PHASE
• Is there a need to develop a system?
• Planning focuses on studying if a system is
feasible thereby investigation is done.
ANALYSIS PHASE
• Will allow one to gather necessary requirements
such as business processes and policies.
• Documents are carefully analyzed in order to be
transformed into diagrams that will serve as
guide in the design of the system.
DESIGN PHASE
• Preparation of diagrams and program code.
• FLOWCHART
• DATABASE design
• Coding starts based on the diagrams prepared.
IMPLEMENTATION PHASE
• Where the system is put into place
• Testing is done in order to check whether it
conforms to system requirement and to validate
how efficient the system is.
• Training for end-users
MAINTENANCE PHASE
• Person-in-charge continuously monitors and
maintains the system’s performance and
efficiency.
• A feedback must be done in order to look into
some problems of the system thereby
improvement is done.
SOFTWARE ENGINEERING
• Roger Pressman: Application of a systematic,
disciplined, quantifiable approach to the
development, operation and maintenance of
software.
• Systems Analysis and Design (SAD) is one of
the activities in Software Engineering
3 Technologies in order to have Quality
Product
• PROCESS: defines a framework that must be
established for effective delivery of software
Engineering Technology.
• METHOD: provides the technical “how to’s” for
building the software. It needs variety of tasks
such as communication, analysis, design,
modeling, program coding, testing and support.
• TOOLS: provide automated and semi-
automated support for the process and the
methods.
Generic Process Frameworks in
Software Engineering
• Communication: An activity where collaboration
with customer is done in order to gather
necessary requirements in the analysis and
design of the software.
Generic Process Frameworks in
Software Engineering
• Planning: It describes the technical tasks, risks,
work products and work schedule for the
Software Development.
Generic Process Frameworks in
Software Engineering
• Modeling: Creation of Models that allow
developers & customers to better understand
software requirements and the design.
• Flowcharts, Data flow diagrams, entity-
relationship diagrams are some of the models
that can be created.
Generic Process Frameworks in
Software Engineering
• Construction: the creation of program code and
testing in order to debug the errors present in
the program.
Generic Process Frameworks in
Software Engineering
• Deployment: delivery of the software. Evaluation
is also done by the customer in order to provide
feedback. Feedback is very necessary in
Software Engineering since it will make the
software better.
Common Process Models in Software
Engineering
• Waterfall Model
• Incremental Model
• Rapid Application Development (RAD)
• AGILE Development
2 Models of Programming
• Structured Programming
▫ Consists of blocks of program statements (codes)
that computer executes one after the other
• Object-oriented Programming
▫ Data are contained in objects and are accessed
using special method that is specific to the type of
data.
Structure of Structured Program
• Statements to establish the start of the program
• Variables needed are declared
• Program statements or the block of codes are
written
Elements of a Program
• DATA which maybe in a form of constants and
variables.
• INPUT is the reading of values from any input
devices, more specifically the keyboard.
• OUTPUT is the information that is displayed or
produced to any output device.
• OPERATIONS like comparing, assigning and
combining values. These maybe mathematical
formulas, logical and relational operators.
Elements of a Program
• CONDITIONS/SELECTIONS. If…statements or
case…statements needed to provide selections.
• LOOPS AND ITERATION. Codes that allow
certain instructions to be repeated. For statement,
while statement are looping and iteration
statements that can be used to repeat program
codes.
• SUBROUTINES. Functions or procedures that
can be called anywhere in the program in order to
do its function.
Program Development flow
• First, Identify the program requirements
Program Development flow
• Second, prepare the algorithm of the program.
• A pseudocode or flowchart can be used to
prepare the algorithm.
Program Development flow
• Third, write the code.
• In writing the code, use the algorithm (or
flowchart) as a basis.
Program Development flow
• Fourth, translate the program into a machine
language. Translating maybe done by compiling
the program.
• Remember that in compiling, once the program
encounters an error, the program cannot be
executed.
Program Development flow
• Fifth, if the program code contains syntax error
then debug the program code and go back to
compiling after checking the error.
• Syntax Error
▫ An error in the use of a program statement,
basically, in the format.
• Debug
▫ Means check the error
Program Development flow
• Sixth, run the program. While running the
program, check if there are logical errors.
• Logical error
▫ An error that may cause a problem on the flow of
the program or on the formulas used; thereby
producing incorrect results.
▫ Logical error is sometimes difficult to trace than a
syntax error because you need to test the
program by passing through different set of data
in order to check the logic of a program.

You might also like