Software Development Process Powerpoints

There were some excellent Software development Powerpoints. I have taken some screenshots of the best ones:

If yours is featured I owe you a Merit refferal (see me if you want to collect it).

Maintenance

If everything went to plan today (without me) then you should have learned about the three different types of maintenance that can occur after a program has been released.

These are:

Perfective – adding new features to improve the software (e.g. Sims updates!)

Corrective – fixing problems in the software that should have been taken care of during development!

Adaptive – altering the software to work on new computer systems or in new environments

All of these occur after the software has been released.

Powerpoint from lesson:

Documentation and Evaluation

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:

Testing

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.

Software Development Process – Analysis

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:

Analysis

Design

Implmentation

Testing

Documentation

Evaluation

Maintenance

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

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 diagram – A 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