Nothing going on here, move along…

Archive for the ‘Programming Concepts’ Category

Programming exam revision sheet

Program development life cycle

 

 

Also know as PDLC this process contains six main phases.

 

 

Define the problem

Design the solution

Code the programme

Test the programme

Document the programme – this should be done right the way through.

Implement the programme

Define, design, code, test, document, implement

Logic techniques

 

Brainstorming

 

Here are the steps to build a website with some organisation.

Show the basic layout. Draw a story board to show the general layout of the program.

Name different items using the naming standards. e.g. lblExample, btnTest. (these labels go in the name part of the properties and with the storyboard for reference.)

Logic. Explain what each item does.

Draw a flow chart

Create the interface and add naming standards to each item (physical)

Code each logical item starting with the easiest thing first. (physical)

Storyboard, naming standards, logic, flow chart, create interface and add naming standards, code logic items

 

Test plan example

A test plan contains columns for the following:

The test number

A description of the test

The test data

The expected output

Actual output

Suggestions

*Both the actual output and suggestions are filled in by someone else.

Test number, description, data, expected output, actual output, suggestions.

Checking the boundries

Check how the program performs when using numbers expected e.g. 1-100

Check the performance when using numbers outside the boundry e.g. 0 or 101

Check the performance when using special characters e.g. a-z

Naming standards

Uses the three letter acronym followed by the chosen naming standard which always starts with a capital letter.

e.g. btnFound

– What can be done to fix any problems- What actually happened in the test- What should happen in the test- The data which will be used to carry out the test- to explain what the program will be doing in the test

.

 

 

 

Not coding, used to help understand what the program should do. (On paper usu.)

 

Advertisements

Hint, hint!

PDLC – Program Development Life Cycle

*Plan, design, develop (logic), implement, test.

  • Define the problem,

What is the situation/requirements?

  • Design the solution (naming standards),

What should the program do?

  • Code the program
  • Test the program
  • Document the program
  • Implement the program

 

Types of program testing

  • Black box testing – User interface testing, using the program to pick out bugs
  • White box testing – Coding testing

Storyboard

  • design
  • naming standards
  • logic of items

Documentation

  • Program name
  • Authors name
  • Date
  • Program version
  • Explainations of each piece of code

Variables and and strings

Variable – A label which stands for something else.

DIM goes before the variable e.g.

DIM WHICH Horse as interger

‘DIM’ starts the code

‘WHIC H Horse’ is the variable

‘as interger’ is the string

WHICH Horse = Int(Rnd) * 2

Int= Interger

Rnd= Randomize

If two or more variables have the same string they can be put on the same DIM eg

DIM Last as interger, I as interger

Interger is an item, a string is a group of these items.

Skills learnt so far

Creating story boards

Hello program – Using a text box, creating buttons

Temperature converter – Horizontal scroll bars, linking to labels, formulas

Font program – Using check boxes, text boxes and system libraries

Whack-a-mole – Using multiple images/timers

Racing program – will be combining labels, using timers, if, else, endif, elseif, randomizing, backgrounds, images/pictures and buttons.

Encryption program – Using ascii to encrypt a message, opening files from the computer, saving files to the computer.

Program storyboard example

Items needed

  • Horizontal scroll
  • 3 Labels – Title, celsius, farenheit.
  • Exit button

 

 

lblTitle(add a title) – Show title

lblCelcius – Show celsius temp.

lblFaren – Show farenheit temp.

btnExit – Exit/close the program.

hsbDegree – Scroll left temperature decreases, scroll right temperature increases, links to celsius and farenheit, Conversion formula C=(F-32/9×5)

Steps for building a program

Brainstorming – Not coding, used to help understand what the program should do. (On paper usu.)

Here are the steps to build a website with some organisation.

  1. Show the basic layout. Draw a story board to show the general layout of the program.
  2. Name different items using the naming standards. e.g. lblExample, btnTest. (these labels go in the name part of the properties and with the storyboard for reference.)
  3. Logic. Explain what each item does.
  4. Draw a flow chart
  5. Create the interface and add naming standards to each item
  6. Code each logical item starting with the easiest thing first.

Coding codes

Some simple coding codes.

The exit/close button (double click on the exit button)

To exit a a program insert the following code between the subs:

close

 

To clear a text box

txtName.Text = ” ”

 

To insert text into a text box when a button (e.g. display) is clicked. (double click the ‘display’ button) 

Enter the following code between the subs:

txtHello.Text= “your text here”

*This connects the display button to the text box, in this example the text box is named ‘txtHello’ and the ‘Text’ part is the information which will appear in the box when the (‘display’) button is clicked*

 

To  connect a scroll bar to text (text changes when scrollbar is moved):

lblNamehere.Text= Format(hsbScrollname.value, “0.0”)
 
To enter a calculation (E,g. to change celcius to farenheit):
lblFaren.Text= Format(9/5* hsbDegree.Value + 32, “0.0”)

 

Tag Cloud