Archive for the ‘Software Development’ Category

Documentation and Evaluation

November 5, 2007

I handed out a load of games today! I was trying to make a point about the different documents that should come with finished software. The two you need to remember are:

User guide – explains how the software should be used

Technical guide – details system requirements, how to install the software etc.

We also looked at Evaluation.  An evaluation report must detail if the software is fit for purpose.

Here are the arrangements for the software development process part of the course:




November 5, 2007

There are 3 kinds of test data that you need to know about. You should also be able to give examples of data for a piece of code shown:

Normal – data within the expected range for a program (e.g. 45 for a program expecting a mark between 1 and 100)

Boundary – data on the edge of the expected range (e.g. 1 or 100)

Out of Range – data not expected by the program (e.g. “fifteen”, -1)

Apart from that we discussed the terms comprehensive and systematic. See powerpoint for details. testing.jpg

Implementation – Procedural, Event Driven and Declarative Languages

November 1, 2007

We wrote down notes from a powerpoint today that explained the difference between procedural languages, event driven and declarative.

For the exam: you need to be able to give an example language for each of these categories (COMAL for procedural, Visual Basic for Event driven, Prolog for declarative).


In the screen shot below it shows the declarative language example. I wrote some facts and rules in (about people with blond hair and cleverness levels) for example purposes only. Not being hairist.


We also did an image quiz (see below)covering most of the features of good software:

  • Robust
  • Readable
  • Reliable
  • Correct
  • Easily Maintained
  • Portable
  • Efficient


Software Development Process – Analysis

October 29, 2007

Today we started looking at the theory of the second unit of Higher Computing, Software Development, and started the stages of the software development process. There are 7 stages the you need to remember:








The acrostic I offered to remember them by was:

A Dance In The Dark Every Monday

The one you guys came up with is unpublishable…

We also disucussed some of the people involved during analysis (client – who requests the software, Systems analyst – helps plan a piece of software based on the client’s needs), aswell as the document that is created then (the software specification).


Software Development Process – Design

October 29, 2007

Today we looked at the different methods that can be used to design your program. These include:

Flow Chart A representation of the program showing the direction in which a user can proceed

Block diagramA representation of the parts of the program in a diagram

Pseudocode A version of the program written not quite in progrmaming code but not quite in normal English either