Image /home/gaius/text/Glamorgan/macros/UoG.eps.png

UNIVERSITY OF GLAMORGAN

Assessment Cover Sheet and Feedback Form

All of the relevant sections of Part A and Part B MUST be completed by the student and the form submitted with the assignment on or by the required submission date.
Please note that you should always keep a copy of your assigment

PART A: RECORD OF SUBMISSION

Record of Submission and Plagiarism Declaration:

I declare that this assignment is my own work and that the sources of information and material I have used (including the internet) have been fully identified and properly acknowledged as required in the referencing guidelines provided.

You are required to acknowledge that you have read the above statement by writing your student number(s) here:
Student Number:

Module Code:
SY2S21
Module Title:

NAD & SEC
Lecturer:

Gaius Mulley

Assessment Title: Summarising web server log files

Please see the page following PART D of the assessment for the full description of this coursework.

Assignment No. 1

No. of pages submitted in
total including this page:

Word Count:

Date Set: 21 11 2007
Submission Date:
23 01 2008
Return Date:
27 02 2008

Details of Submission:

- All coursework should be submitted in accordance with the date indicated on the front cover sheet. Hand in during lecture.

- IT IS YOUR RESPONSIBILITY TO KEEP A RECORD OF ALL WORK SUBMITTED.

- An electronic copy of your work should be deposited in the ’Drop Box’ within the relevant module in Blackboard. This provides you with an electronic receipt of the submission.

- However you must only submit pdf versions to the ’Drop Box’ all other file formats will be ignored by the lecturer. One method to generate a pdf version is to open up a MS Word document in OpenOffice and export as pdf.

- Work should also be submitted to the member of academic staff responsible for setting your work (Hand in during lecture).

- Work not submitted to the lecturer responsible may, exceptionally, be submitted to the reception of the Faculty Office which is on the 2nd Floor of the Rhondda Building (G221) where a receipt will be issued.

Please note that assignments may only be submitted at the following specific times

10.00-12.00 and 14.00-16.00 hrs Monday to Thursday
and
10.00-12.00 and 14.00-15.30 hrs Friday

Please note that no marks will be awarded if the assignment is submitted after the submission date.

This assignment will be marked out of 100%

This assignment contributes to 25% of the total module marks.

This is a non bonded assignment i.e. it is not linked to a particular learning outcome.

Mitigating Circumstances: If there are any exceptional circumstances which may have affescted your ability to undertake or submit this assignment, please make sure you contact the Faculty Advice Shop on 01443 482540 (G221).

PART B: MARKING & ASSESSMENT

Learning Outcomes
This assignment addresses the following learning outcomes of
the module:

(1) Design, develop and maintain scripts

Hours of Work
Number of Hours
1. Number of hours of work that this assignment should take:

20
2. Please indicate the number of hours actually taken:

Marking Scheme

Marks
Available
Marks
Awarded

Implementation
60
Additions and docs
40

ASSESSMENT CRITERIA

Performance Level
Criteria

Fail
(<40%)

A fail grade will be awarded for an answer which contains major errors and shows little understanding of the issues involved

Pass
(40%-49%)

A pass grade will be awarded for an answer which addresses the majority of points with few errors or omissions.

Pass
(50%-59%)

An average grade will be awarded for answers which contain no major errors or omissions.

Merit
(60%-69%)

A higher mark can be achieved if the work contains no major errors and also contains an analytical answer.

Distinction
(70%+)

A high grade will be awarded for work which includes the earlier criteria and contains a high quality analysis of issues from a range of source materials and makes some original contribution on the subject.

PART C: FOR COMPLETION BY THE STUDENT

Proof Reading

Please indicate that you have checked the:

Spelling (inc. spell-checking)
Y/N
Punctuation
(inc. correct use of
apostrophies)
Y/N

Paragraphs (NB: one sentance is not a
paragraph)
Y/N

Citations and References (do they
correspond?)
Y/N

Esthetically pleasing typography.
(Use of fonts, no widows or orphans etc.)
Y/N
P LEASE ASSESS ASPECTS OF YOUR WORK

For each of the marking criteria, you are required to assess
whether you feel that you have completed it:
Very well
Well
Adequately
Poorly
Very Poorly

Implementation
Additions and docs
D O YOU CONSIDER YOUR W ORK WORTH:
70 or more
60-69
50-59
40-49
39 or less

PART D: MARKER’S FEEDBACK

Lecturer’s Comments:

A REAS TO CONCENTRATE ON NEXT TIME:

English
Spelling
Grammar
Punctuation
Paragraphs/Sentances
Layout

Titles
Subtitles
Blank Spaces
Typography
Technical

Citation
Referencing
Lecture’s signature:
Date:
Mark awarded:

All marks are subject to confirmation by the Board of Examiners

It is common for web servers to generate logging information about which files are downloaded and the address of the client performing the download. These log files can become large over time and difficult to analyse by hand. You have two tasks. Firstly produce a python program which will summarise an apache web server log file. Your program should report the total number of successful web server accesses and, if the -p projectname option is given then your program should report the number of accesses (in total and as a percentage) under this project. Your program should also include a help summary option and use a -f option to indicate which web server log file is to be summarised. For example a system administrator might use your program in the following way:

$ ./webscan.py -h

some help information is emitted

$ ./webscan.py -f access.data

indicates that the total number of accesses as logged in access.data will be displayed.

$ ./webscan.py -f access.data -p /pipermail

indicates that the total number of web server accesses are displayed together with the number of web server accesses in the pipermail folder.

For example if the apache web server log file contained the following contents then the output from your script would report the following details:

$ ./webscan.py -f access.data
Total number of accesses: 6
$ ./webscan.py -f access.data -p /pipermail
Total number of accesses: 6
Number of accesses in pipermail: 3 (50%)
Number of successful accesses to pipermail: 1 (16%)

You should test your script using the tiny example above. For a more extensive test you can use this example apache web log file.

For the second component of this coursework you must provide documentation for your script and describe any additions you might consider useful. The script documentation should be a detailed commentry of your program. You should also provide testing evidence. The total commentry and improvement discussion should not exceed 1500 words.