Category Archives: Coursework

Task 3 – Adding Graphics

Images make your pages more stimulating to browse. Most people like the colorful graphics. On the other hand, pages that have very large graphics, or too many graphics, take longer to load, particularly for users connecting to the Internet by modem. The trick is to strike a balance that will make your pages stimulating but will not make them take 5 minutes to load!

Graphics are not actually part of a web page; they are stored as separate files on the web server and sent to the browser to be displayed in the approriate part of the page.

What is put into the web page (which is a text document, remember) is a hypertext link which tells the browser where the image is and what it’s name is. The browser can then collect the image and display it.

The hypertext link which collects and display a graphic looks like this…

<IMG SRC=”image_URL “>

The part of the HTML tag displayed in red above, image_URL, is the part you will change to load a specific graphic.

Right, enough theory. Let’s do it!

Step 1 . Inside the webschool folder on your hard disc is a file called construction.gif. The graphic shows some construction items and can be used to illustrate the fact that the page which displays it is still under construction. The graphic is in GIF format (more about this later).

Move this so that it is in the same folder as the web page that you want to display it.

You can search the internet for a suitable web construction graphic if you want.

Step 2. In your web page, at the point where you want the image displayed, put this HTML tag; <IMG SRC=”construction.gif”>

Step 3. Preview your page. Bet you’re not satisfied, right? There are different ways of aligning graphics, that’s why. So you might want to change this in Step 4.

Step 4. You can configure the graphic to be aligned in many different places. You can use the <CENTER> and </CENTER> to CENTER your graphic. See below for 4 other ways to align your graphic.

<IMG SRC=”construction.gif” ALIGN=”CENTER”>
Click here to see an example using this tag.<IMG SRC=”construction.gif” ALIGN=”TOP”>
Click here to see an example using this tag.

<IMG SRC=”construction.gif” ALIGN=”BOTTOM”>
Click here to see an example using this tag.

<IMG SRC=”construction.gif” ALIGN=”LEFT”>
Click here to see an example using this tag.

<IMG SRC=”construction.gif” ALIGN=”RIGHT”>
Click here to see an example using this tag.

Above you’ll notice that it doesn’t close off at the .gif”> but continues on saying align=”CENTER”>. The “>” is moved over and ends later in the command.

Step 5. One of the best sources of web compatible graphics is the web itself.
I have put some graphics on your floppy disk, ask your tutor how you load them..

Topic 8 Real World Programming

today we started the topic 8 notes, so far we have been learning the programming side to the software development, but topic 8 is all about the other stages.

The stages of the software development cycle are as follows:

Analysis:-the main purpose of this stage is to be absolutely clear about what the program is supposed to do. We must turn a rough idea of what we want the program to do into a detailed description of how it will behave, by asking questions on what the I/O are, and what type of computer it will run on etc. Through this we create the software specification, agreed on by both the client and the developer. This is a very important document and it is a basis of a contract between the client and the developer. It sets out exactly what the client is paying the developer to produce. It can be used at the end of development to resolve any disputes.

Design:- a lot of people just jump into implementation when giving a task. But you MUST not do this, you need to design the program your going to create. Designing the program before implementaion will make is easier. Create Structured Diagrams, or Pseudocode to make it easier to see what steps are needed to make the program work. In real-world programming a test plan is created before implementation begins. The test plan is based on the software specification.

Implementation:- This is where you change the program design into a programming language. This is done by a team of programmers, a team approach is possible if the code used modular program design. Modular programming allows you to re-use section of pre-tested code.

Advantages of modular programming are:

  • it allows programmers to work indepentandly on different sections of the software.
  • Any modules developed with me well documented for inclusion into a module library for future use.
  • and Sections of the overall software can be tested independantly as their developed, this making tracking and destroying bugs easier.

Testing:- Testing is a vital part of any development process.

their are two types of testing. Systematic and Comprehensive.

Systematic Testing: this means that the testing is planned and structured, rather than just random tests. A test plan is developed during the design stage.

Comprehensive Testing: this means that everything is tested. Every part of every module, and aswell as the whole program. Comprehensive testing inclused testing under Normal, Extreme and Exceptional circumstances. The criteria for passing the test stage will have been laid down in detail in the software specification

Testing Normal Conditions: Making sure the program does what i should do when used “normally”. E.g. a program where you enter a number between 1 and 10. Entering numbers such as 4,5,6 are testing it normally.

Testing Extreme Conditions: Making sure the program can handle situations that are at the edge of what would be considered normal. E.g. the same example above, numbers such as 1 and 10 would be testing the extreme conditions.

Testing Exceptional conditions: making sure it can handle unexpected situations of inputs that its not designed to cope with. E.g. The same example as above, numbers such as 15, -98, 11 are all testing the exceptional conditions.

Documentation:- When you buy a peice of software, their are usually two peices of documentation inside. The user guide, and the technical guide.

The user guide tells you how to use the product, and might also include a tutorial, taking you through the uses of it step by step.

the Technical guide gives you technical information of the product. E.g. The software requirements how much RAM the software needs to run, the OS that it works on and how fast the processor needs to be. It should also contain instructions on how to install the software.

Evaluation:- Evaluation involves reviewing the software under 8 headings. These headings are:

1. Is the program fit for purpose?
2. Is the user interface good to use?
3. Is the program code readable
4. Is the program robust?
5. Is the program reliable?
6. Is the program portable?
7. Is the program efficient?
8. Is the program maintainable?

The definition of all the words in Itallic are all in the software development glossary that you were given out. If you do not have this glossary you can find it here.

THIS IS VERY IMPORTANT FOR THE COURSEWORK!

Coursework – good and bad

The lesson today was the first in over 2 weeks. We have had very bad snow in Scotland and this has resulted in a lot of missed work. The class were reminded about Scholar, Glow and other resources.

The class was sorted into friendship pairs and I issued sample coursework to the pairs. One half of the room had candidate 2 and the other candidate 3. The pairs were to discuss the coursework given out and look at the example to find out if it was a good or poor candidate. Both example students had passed the coursework task when it was given but one had scrapped a pass and the other had achieved 58/60. We swapped sheets and took notes about what is expected during the coursework.

The class has had some problems with glow so we undertook a sample homework assessment to make sure that the class could submit the homework for Tuesday on time. Scott Brown scored full marks in the sample homework.

Homework will be posted in Glow tonight.

Coursework Tasks

I have added a new page to the Glow group that has previous coursework tasks. It was my intention last week to start looking at previous coursework tasks and evaluate what is good and bad.

Obviously the snow has kinda got in the way a big bit so, I would like to to try one of the tasks here. You should find the Computer Systems section straight forward enough but the software development side will be a lot harder. Make sure you stick to the main plan. I have uploaded the unedited PDFs from these years so you can see how the marking schemes are applied. If you do not have VB at home then this link should help.

I have also uploaded some new software development notes into the group.

Please share this message with as many pupils as you can in the class.