2 - Lectures Note Week3
2 - Lectures Note Week3
2
Introduction to
Programming
Overview of Programming
Language
Problem Solving Strategy
Software Development Life Cycle
(SDLC)
3
Design of
Algorithms
A person must translate an algorithm into a
computer program.
4
Overview of
Programming
A language is a system of communication. Humans
communicate with one another in some language, like
English, German or in many other languages.
In order to make computers work for us, some sort of
instructions must be stored in a some kind of language.
And that language is called a Programming
Language.
5
Programming
To tell a computer to do something
Programming is writing computer code to create a
program, to solve a problem.
Programs consist of a series of instructions to tell a
computer exactly what to do and how to do it.
Programs are created to implement algorithms.
Algorithms can be represented as pseudocode or
a flowchart, and programming is the translation of
these into a computer program.
• Fast
development
• Assembly • Use developer
2n
• Similar to
• Machine Code Language environments
spoken
d
• Machine
• Machine phrases code
independent • Machine
dependent • Machine
• E.g., JAVA
dependent independent
• E.g., SQL and
SPSS
7
Programming
Language
1st GL- Machine Languages (ML): Use binary coded instructions
instructions
4th GL- 4GL are also known as very high level languages. They
8
Scripting languages such as SQL, Applescript, VBScript
s
1GL:
The first generation program language is pure
machine code, which is called machine language.
The main drawbacks of machine language that
the code cannot be exported to other systems and
has to be rewritten, code is difficult to edit and
update.
2GL:
The second-generation program language is
assembly language.
The main problem of assembly language is that it
requires extensive knowledge of programming
and consumes a lot of time when writing a big 9
program.
s
3GL:
The third-generation language is called “high-
level" programming language.
Third-generation programming languages
brought many programmer-friendly features to
code such as loops, conditionals, classes etc.
This means that one line of 3GL generation code
can produce many lines of object (machine)
code, saving a lot of time when writing programs.
Third generation languages can be platform
independent, meaning that code written for one
system will work on another.
To convert a third generation program into
machine language requires a Compiler or an 10
Interpreter.
s
4GL:
The fourth-generation language is designed to be
closer to natural human language than other high-
level languages.
They are accessible to people without formal
training as programmers.
They allow multiple common operations to be
performed with a single programmer-entered
command.
They are intended to be easier for users.
All 4GLs are designed to reduce programming
effort, the time it takes to develop software, and
the cost of software development.
Some 4G languages are: FoxPro, LINC, FOCUS etc.
4G languages also use Complier or an Interpreter to 11
13
s
1st 4th
Machine Code Fast development
Zeros and Ones Use developer environments that help
Machine dependent generate the code
2nd Machine independent
Assembly Language High Level Language
Used some English User friendly, Similar to natural
like phrases languages
Machine dependent Platform independent
3rd Easy to write or remember
Similar to spoken Easy to learn and work
languages While execution: translated into
Machine assembly language then to machine
independent language.
Slow in execution but is efficient for
14
developing programs.
Programming
Language
A programming language is a set of written symbols that
details.
15
Programming
Language
The language is made up of series of statements that fit
16
Programming
Language
There are many different programming languages, some
more complicated and complex than others.
Among the most popular languages are:
Python
Java
C++
BASIC
Scratch
17
Programming Language
Cont’d
Different languages work in different ways.
For example, in Python all instructions are written in
lowercase, but in BASIC they tend to be written in
uppercase.
Programming languages are designed to be easy for a
human to understand and write in. However, a
computer cannot run programs written in these
languages directly.
Most programming languages must be translated
into machine code before the computer
18
20
Program
Program s a sequence of instructions that a computer
follows to solve a problem. A program is written in a
computer language.
Most of the languages have been created to fit particular
classes of problems.
The process of collecting requirements, analyzing a
problem and designing its solution as well as
writing and maintaining a computer program is
called software development
Programs are made up of statements that the
programming language knows and understands.
21
22
Software
Development
Programming: Needed to take ideas or business
Technology infrastructure.
25
SDLC
SDLC is a systematic approach which explicitly breaks down the
work into phases that are required to implement either new or
modified System. It is used by analysts to develop a system.
Phases:-
1. Preliminary Analysis
2. Systems Analysis
3. Systems Design
4. Programming
5. Testing
6. Implementation
7. Maintenance
Some project managers will combine, split, or omit steps,
depending on the project’s scope.
These are the core components recommended for all software
26
development projects.
SDLC
27
Phases
1. Preliminary Analysis:– requests are reviewed
Deliverable - feasibility analysis document
2. Systems Analysis – if approved, determine the system
requirements for new system
Deliverable – systems requirement document
3. Systems Design:– converts system analysis requirements into
system design document deliverable
4. Programming:– coding commences using design documents
5. Testing:– ensures that the code functions according to
requirements
6. Implementation:- converting from old system to new system
28
29
Models
Here, are some important phases of SDLC life
cycle:
Waterfall Model
RAD Model
Spiral Model
V-Model
Incremental Model
Agile Model
Iterative Model
Big bang Model 30
Study
Study the following:
SDLC Phases
SDLC Models: Advantages and
Disadvantages, and Applications
31
Python
Python is a Scripting programming language known for both
its simplicity and wide breadth of applications. For this
reason it is considered one of the best languages for
beginners.
Python is a powerful and flexible programming language.
It uses concise and easy-to-learn syntax which enables
programmers to write more codes and develop more
complex programs in a much shorter time.
Used for everything from Web Development to Scientific
Computing
Python is referred to as a “general purpose” language by
32
33
Next Lecture:
Week4
Concept & properties of Algorithm, Role of
Algorithm in problem solving process, Design
of Algorithms, Pseudocode, Flowcharting
34
Model
Requirements – defines
needed information,
function, behavior,
performance and
interfaces.
Design – data structures,
software architecture,
interface representations,
algorithmic details.
Implementation – source
code, database, user
documentation, testing.
Waterfall
Strengths
Easy to understand, easy to use
Provides structure to inexperienced staff
Milestones are well understood
Sets requirements stability
Good for management control (plan, staff, track)
Works well when quality is more important than
cost or schedule
Waterfall
Deficiencies
All requirements must be known upfront
Deliverables created for each phase are considered frozen –
inhibits flexibility
Can give a false impression of progress
Does not reflect problem-solving nature of software
development – iterations of phases
Integration is one big bang at the end
Little opportunity for customer to preview the system (until
it may be too late)
When to use the
Waterfall Model
Requirements are very well known
Technology is understood
Architecture or High-Level
Design – defines how software Integration and Testing –
functions fulfill the design check that modules
interconnect correctly
Detailed Design – develop
algorithms for each Unit testing – check that each
architectural component module acts as expected
Coding – transform
algorithms into software
V-Shaped Strengths
Emphasize planning for verification and
validation of the product in early stages of
product development
Each deliverable must be testable
Project management can track progress by
milestones
Easy to use
V-Shaped Weaknesses
Does not easily handle concurrent events
Does not handle iterations or phases
Does not easily handle dynamic changes
in requirements
Does not contain risk analysis activities
When to use the V-Shaped
Model
Excellent choice for systems requiring high
reliability – hospital patient control
applications
All requirements are known up-front
When it can be modified to handle
changing requirements beyond analysis
phase
Solution and technology are known
Structured Evolutionary
Prototyping Model
Developers build a prototype during the
requirements phase
Prototype is evaluated by end users
Users give corrective feedback
Developers further refine the prototype
When the user is satisfied, the prototype
code is brought up to the standards
needed for a final product.
Structured Evolutionary
Prototyping Steps
A preliminary project plan is developed
An partial high-level paper model is created
The model is source for a partial requirements
specification
A prototype is built with basic and critical
attributes
The designer builds
the database
user interface
algorithmic functions
The designer demonstrates the prototype, the
user evaluates for problems and suggests
improvements.
This loop continues until the user is satisfied
Structured Evolutionary
Prototyping Strengths
Customers can “see” the system
requirements as they are being gathered
Developers learn from customers
A more accurate end product
Unexpected requirements accommodated
Allows for flexible design and development
Steady, visible signs of progress produced
Interaction with the prototype stimulates
awareness of additional needed
functionality
Structured Evolutionary
Prototyping Weaknesses
Tendency to abandon structured program development
for “code-and-fix” development
Bad reputation for “quick-and-dirty” methods
Overall maintainability may be overlooked
The customer may want the prototype delivered.
Process may continue forever (scope creep)
When to use
Structured Evolutionary
Prototyping
Requirements are unstable or have to be
clarified
As the requirements clarification stage of a
waterfall model
Develop user interfaces
Short-lived demonstrations
New, original development
With the analysis and design portions of
object-oriented development.
Rapid Application Model
(RAD)
Requirements planning phase (a workshop utilizing
structured discussion of business problems)
User description phase – automated tools capture
information from users
Construction phase – productivity tools, such as code
generators, screen generators, etc. inside a time-box.
(“Do until done”)
Cutover phase -- installation of the system, user
acceptance testing and user training
RAD Strengths
Reduced cycle time and improved productivity with
fewer people means lower costs
Time-box approach mitigates cost and schedule risk
Customer involved throughout the complete cycle
minimizes risk of not achieving customer satisfaction
and business needs
Focus moves from documentation to code (WYSIWYG).
Uses modeling concepts to capture information about
business, data, and processes.
RAD Weaknesses
Accelerated development process must
give quick responses to the user
Risk of never achieving closure
Hard to use with legacy systems
Requires a system that can be
modularized
Developers and customers must be
committed to rapid-fire activities in an
abbreviated time frame.
When to use RAD
Reasonably well-known requirements
User involved throughout the life cycle
Project can be time-boxed
Functionality delivered in increments
High performance not required
Low technical risks
System can be modularized
Incremental SDLC
Model
Construct a partial
implementation of a total
system
Then slowly add
increased functionality
The incremental model
prioritizes requirements
of the system and then
implements them in
groups.
Each subsequent release
of the system adds
function to the previous
release, until all designed
functionality has been
implemented.
Incremental Model
Strengths
Develop high-risk or major functions first
Each release delivers an operational
product
Customer can respond to each build
Uses “divide and conquer” breakdown of
tasks
Lowers initial delivery cost
Initial product delivery is faster
Customers get important functionality
early
Risk of changing requirements is reduced
Incremental Model
Weaknesses
Requires good planning and design
Requires early definition of a complete and
fully functional system to allow for the
definition of increments
Well-defined module interfaces are
required (some will be developed long
before others)
Total cost of the complete system is not
lower
When to use the Incremental
Model
Risk, funding, schedule, program
complexity, or need for early realization of
benefits.
Most of the requirements are known up-
front but are expected to evolve over time
A need to get basic functionality to the
market early
On projects which have lengthy
development schedules
On a project with new technology
Spiral SDLC Model
Adds risk analysis,
and 4gl RAD
prototyping to the
waterfall model
Each cycle involves
the same sequence
of steps as the
waterfall process
model
Spiral Quadrant
Determine objectives, alternatives and
constraints
http://www.nebulon.com/articles/index.html
Dynamic Systems Development
Method (DSDM)
Applies a framework for RAD and short time
frames