Programming Theory

Mr Arthur

Aims of the Lesson 1

Today’s Lesson1. Intro to Computing theory

The Software Development Process

The Analysis Stage Read Chapter 12 up to half

past Finish questions on Forum Continue with revision

slideshow

The Software Development Process

All competent programmers use the SDP process to solve problems and create effective software

A Analysis Dance Design In Implementation The Testing Dark Documentation Every Evaluation Monday Maintenance

Analysis Stage

The Analysis stage involves reading and understanding a problem

Most programmers split their analysis of the problem into

Input = What user input is going into the software?

Process = What exactly has the software to do?

Output = What output does the user get?

Aims of the Lesson 2

Last Lesson1. Intro to Computing

theory The Software

Development Process The Analysis Stage

Read Chapter 12 up to half past

Finish questions on Forum

Continue with revision slideshow

Today’s Lesson

2. The Design stage Structure Diagrams Algorithm

Implementation Stage Testing Stage

Design Stage

At this stage of the SD process, the programmer needs to break the problem down into manageable steps

Pseudocode This uses plain language ,

breaking the problem down into main steps

Structure Diagram This diagram uses shaped

boxes to show loops, decisions, procedures etc

Implementation

Implementation is where the programmer develops the design into programming instructions (code).

Readability The code should have clear

comments telling the user what each part is doing

Testing

Normal Where the input into the

program is within the correct range

Extreme Where the input into the

program is at the limits of the range

Exceptional Where the input into the

program is outwith the correct range

Aims of the Lesson 3

Last Lesson1. Intro to Computing

theory1. The Software

Development Process

2. The Analysis Stage

3. The Design stage Structure Diagrams Algorithm

Implementation Stage Testing Stage

Today’s Lesson

2. Documentation

3. Evaluation

4. Maintenance

Documentation

Documentation can be of 2 types: User Guide = gives instructions on how

to use the program, it may include FAQs and tutorials

Technical Guide = this document shows the system requirements of the software i.e RAM and processor required

Evaluation

The Evaluation stage is where you review your solution against what the program was meant to do at the start

You may evaluate the following factors The HCI How much RAM does the software use Can the program cope with wrong

input??

Maintenance

Maintenance is the final step and is where you may make changes to the software in an effort to improve it Add new features Fix problems Make changes to allow it to work

on a different computer