CT5002 User
Support Systems
Development
Module Guide
Last revision: 28/06/2012 23:46
2 0 1 2 / 2 0 1 3
T h i s
p a g e
i s
i n t e n d e d
t o
b e
b l a n k
Table of Contents
Learning Outcomes ..................................................................................................................................... 5
Teaching and Learning ................................................................................................................................ 5
Books.......................................................................................................................................................... 6
Assessment ................................................................................................................................................. 8
Assignment Teams and Group Assignment Registration Forms (GARFs) ..................................................................9
Advice on Group Work......................................................................................................................................... 10
Staff Involved............................................................................................................................................. 11
PDP statement ........................................................................................................................................... 11
Student Activities ....................................................................................................................................... 11
Feedback from tutors ................................................................................................................................. 11
Scheme of Work – weekly schedule ............................................................................................................ 12
Assessment Specifications .......................................................................................................................... 14
Microsoft Excel Practical Assessment (40% weighting)................................................................................ 16
Microsoft Access Assessment (60% weighting) ........................................................................................... 17
Practical Element (50% of this assessment point) ................................................................................................. 17
Documentation Element (50% of this assessment point) ....................................................................................... 18
Additional Information Regarding Assessments.......................................................................................... 19
Penalties for Late Submission .............................................................................................................................. 19
Students with Disabilities .................................................................................................................................... 19
Assessment Regulations ............................................................................................................................. 20
Plagiarism ........................................................................................................................................................... 20
Writing style .............................................................................................................................................. 21
Using references and citations ................................................................................................................... 21
Appendix 2: CT5002 Microsoft Excel Practical – Marking Sheets ................................................................. 22
Stage 1: TASK 1a Data Sheet Validation Checklist.................................................................................................. 22
Stage 2: TASK 1a Data Validation via Coding Checklist .......................................................................................... 23
Stage 3: TASK 1b .................................................................................................................................................. 24
Stage 4: TASK 2 (2a plus either 2b or 2c) ............................................................................................................... 25
Appendix 2: CT5002 Microsoft Access Practical – Mark Sheets ................................................................... 26
Appendix 3: ICT Assessment Criteria Grid .................................................................................................... 29
Appendix 4: Specimen GARF ....................................................................................................................... 30
T h i s
p a g e
i s
i n t e n d e d
t o
b e
b l a n k
CT5002 User Support Systems Development - Module Guide
Module CT5002 - User Support Systems Development
Learning Outcomes
By the end of the module, students will be able to demonstrate that they can :
1) identify the main facilities that exist within Access and Excel that can enhance
the usability of these packages
2) explain the need for customisation and when it is appropriate
3) create, test and amend macros/procedures that carry out application
functionality and facilitate invoking these via appropriate triggers in order to build
a customised application system.
4) explain the role of a help desk in a technical support environment
5) evaluate the various forms of help desk technology
6) plan the hardware and software aspects of security relevant to IT User Support
When you are asked to complete a module evaluation at the end of the module you should
be able to tell us to what extent you feel your learning experience has enable you to
achieve these outcomes.
Teaching and Learning
A typical week will consist of 3 hours class contact in a computer lab with up to one hour
lecture time and two hours practical time. Delivery may be flexible in that the hour or so
lecture time may be split across the 3 hour session so attendance across the entire
session is essential in order to achieve the module objectives and pass the module. In
addition, it is expected that you should spend up to a further 3 to 5 hours each week
completing any exercises or set work, which you start and perhaps complete during the
practical sessions as appropriate.
For the Excel part, you will be expected to use the module workbook. You can choose to
work from either an electronic copy or a hard copy. The electronic copy will be made
available on the information server (see later note) or you can buy a hard copy (from the
online shop) and collect it from the Assignment Room. Substantial reference will be made
to these notes in this workbook and it contains weekly exercises that will form the
foundation for the module assessment work. Other supporting material including this guide
5
CT5002 User Support Systems Development - Module Guide
will be supplied during the lectures and/or made available on the Information Server as
necessary. This guide will also be made available on Moodle.
There is no requirement for you to buy a book covering the Access or Excel elements of
the course although you would, of course, be able to enhance and consolidate your skills
by making use of additional materials.
It is assumed that, for the purposes of this module, you are already familiar with the basic
features of both Access and Excel (either via school/work experience or by having
attended BT110).
Books
Excel
Internal publication (essential):
CT5002 User Support Systems Development - Module Workbook – Excel Macros
Generally available at shelf number: 005.369 EXC/WAL and some via MyiLibrary and/or Safari books
Walkenbach J (2010) Excel 2010 VBA Programming for Dummies. 2nd ed. USA: Wiley &
Sons (Recommended)
Jelen B, Syrstad T (2010) VBA and macros :Microsoft Excel 2010. Indianapolis: Que
Publications (My Library)
Walkenbach J, (2010) Excel 2010 Power Programming with VBA (Mr. Spreadsheets
Bookshelf) USA: Wiley & Sons
Walkenbach J, (2011) Excel 2010 Bible. USA: Wiley & Sons
Bullen S, Bovey R, Green J (2009) Professional Excel development [electronic resource
via MyiLibrary] : the definitive guide to developing applications using Microsoft Excel, VBA,
and .NET, 2nd ed., Upper Saddle River, NJ : Addison-Wesley
Kelly, J (2005) Master Visually Excel 2003 VBA Programming, USA: Wiley & Sons
6
CT5002 User Support Systems Development - Module Guide
Access
Generally available at shelf number 005.7565 ACC/GRO and some via MyiLibrary and/or Safari books
Groh, M R (2010) Access 2010 Bible. USA: Wiley & Sons
Shepherd, R. (2011) Microsoft Access 2010 VBA Macro Programming. New York :
McGraw-Hill
MacDonald, M. (2010). Access 2010 : the missing manual. Sebastopol, CA : Pogue Press,
O’Reilly
User Support 004.068
Bruton N (2002) How to Manage the IT Helpdesk: A Guide for User Support and Call
Center (Computer Weekly Professional). Oxford Butterworth-Heinemann
Czegel B (1998) Running an Effective Helpdesk 2nd Edition Chichester, John Wiley & Sons
Wooten B (2001) Building and Managing a World Class IT Helpdesk. London: Osborne
Google book
Gerbyshak, P (2009) Help desk manager's crash course. [S.l.] : Booksurge Llc, 2009
7
CT5002 User Support Systems Development - Module Guide
Assessment
There are two assessment points for this module to be undertaken in groups of 2 or 3.
Note that, for simplicity, week numbers relate to the scheme of work as presented later in
this document (and not the global timetabling system).
Assessment
Point
Assessment
Weighting
Demos of Excel work stages
(pre Final)
1
2
Submission of Excel
Customisation (Stages 3 & 4)
Demo
Deadline
See Scheme of
Work1
Submission
Deadline
x
x
Wednesday
week 82
Demonstration of Excel
Customisation (Stages 3 & 4)
Lab session
Week 8
x
Demos of Access features
(pre Final)
See Scheme of
Work
x
Final Demonstration of
Access
Lab session
Week 20
x
x
Wednesday
week 31
(hard copy & electronic evidence)
Submission of Access
Customisation
(hard copy & electronic evidence)
& User Support
Documentation
40%
60%
The first assessment point is based on the completion of the Excel workbook exercises
(demonstration and hard copy evidence) which involves the customisation of Microsoft
Excel and is weighted 40% of the overall module mark. The second assessment point
involves the customisation of Microsoft Access and requires demonstration of completed
tasks, hard copy evidence and documentation from a user support perspective. Further
details of requirements are provided later in this document and during time-tabled
sessions.
Minor adjustment may be made to the requirements or mark distribution within each of
these assessments according to any unforeseen developments to ensure that you are not
disadvantaged.
You will develop skills during the practical sessions that will enable you to complete the
assessments. There are milestones in the schedule (see previous table) when you have
1
Failure to meet deadlines may result in a maximum of 40% of the marks being awarded
Note that submission of hard copy evidence for PRACTICAL elements is due BEFORE demonstration of
work in lab
2
8
CT5002 User Support Systems Development - Module Guide
the opportunity to demonstrate your achievements to date. If you elect not to take these
opportunities then you will need to demonstrate them on a later occasion (on or before the
final demonstration) and you may be awarded up to a maximum of 40% of the marks that
could otherwise be achieved for that element.
You will be given a provisional mark for your work at each demonstration. This mark is
subject to change based on the quality of your hard copy submission which documents
that practical work. You are required to submit hard copy evidence to the
Assignment Room and supply a virus-free electronic copy of your work on for
moderation and external scrutiny purposes. For Excel, this is to be no later than the
Wednesday of the week that the final demonstration takes place and for Access this
corresponds to the user documentation deadline. Electronic copies need to be
submitted to tutors via email (Excel) or Dropbox (Access) by the same Wednesday
deadline. You need to ensure you keep a copy of the submitted work not least because
you need to demonstrate it after submission. Dropbox and how to use it will be explained
during the module sessions.
Assignment Teams and Group Assignment Registration Forms (GARFs)
You will be working in groups of two or three for each of the assignments. You
need to establish your group members as early as possible. This will allow time for the
group to gel as a team and make for good group dynamics. Once your group members
have been determined, you need to complete a Group Assignment Registration Form
(GARF). This form is available from the information server and should be emailed to
[email protected] when complete. It is important to note that, once you have
agreed to be a member of a group you can only switch to another group in exceptional
circumstances and with permission of the module tutor.
It is important that, immediately after you agree your group, you all exchange contact
details (name, phone number and email address) and agree the main method of
communication that you’ll all use. At the same time elect one member of the group to
email those details to the module tutor. Each member should therefore have contact
details of all other group members. Email addresses may be particularly critical for parttime students who may wish to use this method to communicate within the group.
You are expected to work as a team within these groups where each member makes an
equal contribution and it is the responsibility of the team to ensure that this happens. You
9
CT5002 User Support Systems Development - Module Guide
should you work together on all aspects of the assignment. You must NOT split up
the work into individual tasks and then combine solutions. If you do this, our experience is
that it results in chaos (due to the nature of the work) and there are always some
individuals do not do the agreed work in time for others to do theirs; thus causing major
group problems. If everyone contributes to the entire assignment, you all will achieve an
optimal learning experience and hence gain the maximum benefit from doing the work.
Splitting the work reduces your learning experience which may result in part coverage of
the learning outcomes and almost always leads to group problems. Always make sure
that you individually retain a copy of any shared group work as it develops.
The GARF registers your intent to work within a particular group and does not
automatically entitle you to the same mark or even to be included in the group upon
submission if you have not contributed to the work. The formal and final declaration of
group membership is taken from the cover sheet that is submitted with your work. It is
therefore imperative that each group member is present when the assignment is
submitted to ensure that full and correct details are entered on the cover sheet and also
that each member submits any individual elements.
Advice on Group Work
Working as a group can be very beneficial but any difficulties with the
group are for you to resolve. If you work in a group it is your responsibility
to organise the group, maintain copies of the work and ensure your group
members all contribute equally. Staff will not get involved in setting up
groups or resolving any problems.
Group problems will not be accepted as excuses for late or incomplete submission.
If, after completion of the assignment, a group member considers that not all group
members have made an equal contribution, the difference in contributions is considered to
be significant and you are able to produce evidence of this then they must complete a
Peer Group Assessment Form and email this to me, Mo Clutterbuck, copied to all team
members, and by the assignment deadline. The remaining team members must then also
email a completed form to me. If this procedure is not followed then the work will not
attract any different treatment during marking. The form itself together with further details
for completion can be emailed to you on request. You should note that all emails and
evidence will be made public to all the individuals concerned in order to resolve the
situation fairly.
10
CT5002 User Support Systems Development - Module Guide
Please note that the assignment work for this module is strictly group work. Reasons for
setting the tasks as group tasks include the requirement to enable you to experience and
develop your team working skills and to help you to adjust to studying at University. It is
not essentially on the basis of workload and it is possible, with permission from the module
tutor to complete some work individually provided there are very good reasons.
Permission MUST be granted prior to undertaking the work. Any assignment submitted
from an individual, for any reason and without prior permission, may receive a
maximum of 30%.
Any groups larger than 3 will have their marks reduced according to the group size
i.e. the group mark will be multiplied by 3/(size of group), so a group of 4, for
example, will have their mark multiplied by 0.75.
N.B. Group composition can be different for each of the assignments and it is
considered that a change of group might be healthy in many cases.
Staff Involved
Name (Academics)
Mo Clutterbuck
Kevin Walter
Room
Owen002
Owen002
Phone Number
(01242) 714314
(01242) 714315
Email Address
[email protected]
[email protected]
PDP statement
By the end of the module students will achieve a high level of skills in the use of
information technology and be confident in the application of a range of software. In
addition they will gain a broad understanding of the use and application of information
technology.
Student Activities
Weekly student activities are indicated by the following Scheme of Work.
Feedback from tutors
All students are entitled to both formative and summative feedback during the module.
Formative feedback is designed to enable you to improve your work/performance and
takes many forms. Students will have several opportunities to receive feedback on their
progress, e.g. during lab sessions, tutorials or seminars; as part of general feedback in
lectures; and where appropriate, one to one sessions with their Academic Review Tutors.
Summative feedback is received when your submitted coursework has been marked. As a
minimum this will comprise constructive comments from the tutor and a grade.
11
CT5002 User Support Systems Development - Module Guide
Scheme of Work – weekly schedule
CT5002 2012/13
Tutors: Maureen Clutterbuck and Kevin Walter
Sessions: Thursday 5.15 - 8.15 in LC114
T/T
Date
Topic(s)
Week
Thu
Sem1
Week
1
27
Sep
1
Creating and running a simple macro in Excel
Recording modes. Methods for running macros.
2
04
Oct
2
Building a simple Excel system –
Custom screens, event-triggered macro; data validation.
3
11
Oct
3
4
18
Oct
4
Building a simple Excel system Transferring data: message boxes, screen navigation
5
25
Oct
5
Building a simple Excel system Finishing touches
6
01
Nov
6
7
08
Nov
7
Assessment Workshop
8
15
Nov
8
Demo of Excel Work Stages 3 & 4 ( Final): all remaining aspects
9
22
Nov
9
Nature and Background of the Help Desk.
10
29
Nov
10
Documentation
11
06
Dec
11
Personal/ Customer Communications
12
13
Dec
12
Help Desk Processes and Procedures
Building a simple Excel system –
Transferring data: conditions, loops & testing
Demo of Excel Work Stage 1: validation via worksheet3
Demo of Excel Work Stage 2: validation via macros
Christmas vacation
3
Failure to meet deadlines may result in a maximum of 40% of the marks being awarded
12
CT5002 User Support Systems Development - Module Guide
T/T
4
Date
Topic(s)
Thu
Sem2
week
#
17
17
Jan
1
Access VBA: Form Synchronisation and Event Triggers
18
24
Jan
2
Access VBA: Embedding SQL, Buttons and Controlling System
Messages
19
31
Jan
3
20
07
Feb
4
21
14
Feb
5
22
21
Feb
6
23
28
Feb
7
24
07
Mar
8
Demo of Access Work (Final)
25
14
Mar
9
Documenting the Final System: Independent work
26
21
Mar
10
Internet and Network Support
30
18
Apr
11
Help Desk Management
31
25
Apr
12
Problem Solving & Help Desk Metrics. Module Review
Week
Demo work target: ‘Go To Product’4
Access VBA : More Functionality on Buttons and Control of
System Messages
Access VBA: User-defined Functions
Demo work target: ‘Add to Order’
Access VBA: Controlling user input & Debugging code
Demo work target: ‘Validate Date’
Customised Access System Final Requirements
Demo work target: ‘Orders Last Month’
Customised Access System Workshop
Demo work target: ‘Orders for Period’
Failure to meet deadlines may result in a maximum of 40% of the marks being awarded
13
CT5002 User Support Systems Development - Module Guide
Assessment Specifications
1. Module code and title
CT5002 User Support Systems Development
2. Module tutor
Mo Clutterbuck
3. Tutor with responsibility
for this Assessment
Mo Clutterbuck
4. Assignment
001: 40% Coursework: Excel (1600 words or
equivalent). You will be penalised according to the
Academic Regulations for Taught Provision if
you exceed the size limit.
5. Submission deadline
Your attention is drawn to the
penalties for late submission;
see Undergraduate Modular
Handbook.
14 Nov 2012
Your attention is drawn to the penalties for late
submission; see Academic Regulations for
Taught Provision.
6. Arrangements for
submission
Park Assignment Room
7. Date and location for
return of work
Written feedback and provisional mark will be
within 20 working days of submission
Alternative assessment arrangements may be
made, where appropriate, for students with
disabilities. However, these will only be
implemented upon the advice of the Disability
Advisor. Students wishing to be considered for
alternative assessment arrangements must give
notification of the disability (with evidence) to the
Disability Advisor by the published deadlines.
All assessments are subject to the Academic
Regulations for Taught Provision. These include
regulations relating to Errors of Attribution and
Assessment Offences. In exercising their
judgement, Examiners may penalise any work
where the standard of English, numeracy or
presentation adversely affects the quality of the
work, or where the work submitted exceeds the
published size or time limits, or where the work fails
to follow normal academic conventions for
acknowledging sources.
8. Students with
Disabilities
9. University Regulations
for Assessment
10. The requirements for assessment 1
See the section Microsoft Excel Practical Assessment (40% weighting)
11. Special instructions
None
12. Assessment 1 criteria
See Appendix 1
Assesses learning outcomes (1) (2) (3)
14
CT5002 User Support Systems Development - Module Guide
1. Module code and title
CT5002 User Support Systems Development
2. Module tutor
Mo Clutterbuck
3. Tutor with responsibility
for this Assessment
Kevin Walter
4. Assignment
002: 60% Coursework: Excel (2400 words or
equivalent). You will be penalised according to the
Academic Regulations for Taught Provision if
you exceed the size limit.
5. Submission deadline
Your attention is drawn to the
penalties for late submission;
see Undergraduate Modular
Handbook.
24 April 2013
Your attention is drawn to the penalties for late
submission; see Academic Regulations for
Taught Provision.
6. Arrangements for
submission
Park Assignment Room
7. Date and location for
return of work
Written feedback and provisional mark will be
within 20 working days of submission
Alternative assessment arrangements may be
made, where appropriate, for students with
disabilities. However, these will only be
implemented upon the advice of the Disability
Advisor. Students wishing to be considered for
alternative assessment arrangements must give
notification of the disability (with evidence) to the
Disability Advisor by the published deadlines.
All assessments are subject to the Academic
Regulations for Taught Provision. These include
regulations relating to Errors of Attribution and
Assessment Offences. In exercising their
judgement, Examiners may penalise any work
where the standard of English, numeracy or
presentation adversely affects the quality of the
work, or where the work submitted exceeds the
published size or time limits, or where the work fails
to follow normal academic conventions for
acknowledging sources.
8. Students with
Disabilities
9. University Regulations
for Assessment
10. The requirements for assessment 2
See the section Microsoft Access Practical Assessment (60% weighting) (both elements)
11. Special instructions
None
12. Assessment 2 criteria
See Appendix 2 and Appendix 3
Assesses learning outcomes (1) - (6)
15
CT5002 User Support Systems Development - Module Guide
Microsoft Excel Practical Assessment (40% weighting)
Supplied Workbook: None
Learning Outcomes: (1) – (3)
Tutor Responsible: M Clutterbuck
TASK 1. For a Maximum mark of 70
a. Before the transfer process in part b takes place the data must be
validated. Validate the worksheet cells for card number, wine types
and wine quantities. You should first use the standard worksheet
validation (available via Data Validation) then and more
importantly via macro coding to capture the same errors and
additional errors as appropriate.
Validation aspects you should consider are whether the input is:
non-empty, text/numeric, in the valid range, of valid length and, in
the case of numeric values, required to be an integer value.
Incorporate this validation into the main flow of execution
(30 marks)
b. Implement the SilverToad system as per the weekly exercises in the
workbook to transfer records from the OrderForm to the OrderData
worksheet. NB Inputs MUST use the same cells as the workbook.
(40 marks)
TASK 2. For a mark higher than 70
In addition to completing all the requirements in TASK 1, implement TASK 2(a) and either
TASK 2(b) or TASK 2(c) below:
a. Fully validate the expiry date cell considering aspects such as those
listed above and more e.g. valid composition of input (2 digits,
slash, 2 digits).
AND EITHER
b. Fully validate the offer and gift choice cells including checking that
the offer cell is non-empty, that if offer is No then there is no entry
for gift choice and that if offer cell is Yes then one of the valid
entries for gift choice has been entered.
OR
c. Implement a further validation of wine types and quantities such that
i. each wine type is only used once and
ii. inputs can only be made in pairs.
This part must be implemented using a general reference method to
examine the content of each input pair together with a looping
construct.
(18 marks)
(12 marks)
(12 marks)
NOTE:
Completion of TASK 1 does not guarantee a mark of 70 and Completion of TASK 2 does not guarantee a mark greater than 70
16
CT5002 User Support Systems Development - Module Guide
Microsoft Access Assessment (60% weighting)
Practical Element (50% of this assessment point)
Supplied database: CT5002_assessment.accdb
Learning Outcomes: (1) – (3)
Tutor Responsible: K Walter
TASK 1, Compulsory. For a potential mark up to and including 70
a. Orders form (supplied); implement the following requirements:
 Add a Products Browser, which must contain:
- a ‘Go to Product’ feature;
(10 Marks)
- an ‘Add to Order’ button; this button should report an error when an attempt is made to
duplicate a Product already present in an order.
(10 Marks)
 Use a function written in a module to validate the ‘Date Required’ field so that a
required date earlier than the date of the Order will generate an error.
(10 Marks)
b. Main Menu (supplied); provide the functionality for the supplied buttons:
 ‘Orders Last Month’: you must use functions written in a module.
 ‘Orders for Period’ : Either using pop-up input boxes; (4 marks max)
: OR using a separate date-entry form. (8 marks)
(10 marks)
(8 marks)
c. An additional feature of your own choosing, which must involve writing code within an
event handler, a function, or both.
(10 marks)
Important note. Implement one additional feature only – just one will be marked.
Suggestions
In the Orders Form (implement one only of the following three bullet points)

Either: add Delete buttons so that both individual whole orders and individual order
items can be deleted – users must be given an opportunity to cancel deletion;

OR: add a ‘New Customer’ feature that facilitates the adding of a new customer to the
database – the new customer must appear in the Customer combo box;

OR: add a ‘Go to Order’ feature – users should be given a list showing Customer
Name, Order date, and OrderID, sorted by Customer Name;
OR

Add a suitable feature of your own choosing, not necessarily in the Orders Form
- you are advised to check the suitability of your feature with a tutor;
d. Ease of Use and Clarity (the end-user interface)
(12 marks)
All features that you add should be designed to avoid (naïve) end-user confusion.
TASK 2, Optional. For a potential mark greater than 70
In addition to completing all the requirements in TASK 1:
Build an Invoice in the form of a Report that replicates an Order, but WITHOUT the products
browser, and WITH Customer details. For this task, you will need a query that uses the
current order number to supply data for the Invoice. The invoice must be activated from
within the orders form using a suitable method.
(30 marks)
NOTE:
Completion of TASK 1 does not guarantee a mark of 70 and Completion of TASK 2 does not guarantee a mark greater than 70
17
CT5002 User Support Systems Development - Module Guide
Documentation Element (50% of this assessment point)
As an experienced and literate member of the Help Desk team, you are tasked to produce
a user guide / training document containing hints, techniques, and guidance for ICT users
within your organisation.
You must produce this documentation for the access database developed in the first part
of this assessment. The user guide documentation must cover the following aspects:





An overview of what the database does and how to use it effectively
Structure of the database
Key file and data names
Relationships between tables and forms.
The code for the control buttons needs to be documented in a way that would
enable a maintainer to debug and/or improve the efficiency of the database.
You must refer to the guidance given on how to write documentation as detailed in the
papers supplied on the Infoserver.
Marks for this element will be awarded according to clarity and standard of the submission.
The standard of the submission will be assessed by



appropriateness of the level
clarity of instructions and writing style
Appropriateness of the level may be judged by factors such as:



source of material e.g. screen dumps, database dumps etc.
use of appendices.
Adequate but not excessive amount of detail
Clarity of instructions may be judged by factors such as




correct use of English
correct spelling
lack of jargon
conciseness and clarity of explanation
The ICT assessment grid will be used to mark this element of the assessment
18
CT5002 User Support Systems Development - Module Guide
Additional Information Regarding Assessments
The following general information also applies to assignments in this module.
Penalties for Late Submission
Your attention is drawn to the penalties for late submission; seethe regulations on the
University website at
http://resources.glos.ac.uk/currentstudents/undergraduate/umshbkcontents.cfm
Students with Disabilities
Alternative assessment arrangements may be made, where appropriate, for students with
disabilities. However, these will only be implemented upon the advice of the Disability
Advisor. Please see the University regulations for advice.
19
CT5002 User Support Systems Development - Module Guide
Assessment Regulations
Plagiarism
All assessments are subject to the University Regulations for Assessment which at the
time of writing can be found at
http://resources.glos.ac.uk/currentstudents/undergraduate/umshbkcontents.cfm.
These include regulations relating to Errors of Attribution, Poor Academic Practice, and
Breach of the University Regulations for Assessment. In exercising their judgement,
Examiners may penalise any work where the standard of English, numeracy or
presentation adversely affects the quality of the work, or where the work submitted
exceeds the published size or time limits. You should pay particular attention to regulations
on the University website.
For this module, it is particularly vital that you understand this rule and you are advised to
take the following precautions:
1.
Always keep up-to-date with your work and familiarise yourself with the assignment
brief early on, this will leave you time to think through the problem carefully and
allow to see the relevance of exercises to the assignment as you go.
2.
Do not discuss the assignment with your fellow students other than on a conceptual
level. If discussion is necessary, make use of your workbook exercises as
illustrative examples to indicate your view of solutions to problems. Discussion of
the actual assignment will almost certainly lead to some similarity in your work. Any
similarity is likely to lead tutors to suspect collusion (working together) or
syndication (sharing out then amalgamation of work), which has the same penalties
as plagiarism (plagiarism is often defined as direct copying of someone else’s work
- published or otherwise, and is a term which is often used to cover collusion and
syndication). There is an online tutorial and guide for the avoidance of plagiarism,
see http://ist.glos.ac.uk/referencing/plagiarism
3.
Keep your work secure. Never leave any of your work on a University machine. If
you use the hard disk to copy disks, ALWAYS clear your work off the hard disk. If
someone else finds your work and uses it, YOU could be accused of plagiarism.
4.
NEVER let anyone have a copy of a file, or see the detail of your assignment. You
would not be doing them any favours since they are unlikely to learn from simply
copying your work and YOU could be accused of plagiarism.
Note: The assessments for this module are set as tasks for individual completion. Thus,
the work you submit must be your own and yours alone.
20
CT5002 User Support Systems Development - Module Guide
Writing style
All written work should be written in a formal, impersonal, style from the point of view of the
passive researcher or observer and not from a personal point of view. This improves the
tone for technical documents. For example: "I carried out the interviews in a quiet room…"
is poor style; "The interviews were carried out in quiet room …" is better.
Abbreviations or acronyms can be used, and in some cases have become standard.
However, in all cases the first time a word or phrase is used it should be presented in full,
with the acronym given in parentheses; the appropriate acronym can then be used
throughout the document. For example: "The questionnaire was published on the Internet
though the World Wide Web (WWW) …", "The British computer Society (BCS) have stated
…", "… currently automatic speech recognition (ASR) technology is available at a
relatively small cost …".
Using references and citations
For all academic work it is essential that any sources are correctly acknowledged. This
means that the source should be list in the reference list at the end of the work and cited
within the body of the document where information from the source has been
incorporated.. Full and accurate citing of sources is important for the following reasons:

it helps the reader distinguish between your own ideas and findings from those
ideas quoted or obtained from other sources; failing to do this suggests deliberate
plagiarism;

it helps your arguments by showing the extent to which independent theoretical and
empirical sources support them (though this depends on the quality and
appropriateness of those sources);

it enables readers to check and follow up those original sources for themselves;

it gives credit to authors of original work (therefore, where possible, cite the original
author, not the secondary source).
The general standard for referencing at the University is based on the Harvard Citation
system which uses the author family name (surname) and year of publication. For further
information and assistance, see http://ist.glos.ac.uk/referencing/harvard
21
CT5002 User Support Systems Development - Module Guide
Appendix 1: CT5002 Microsoft Excel Practical – Marking Sheets
These sheets will be used to mark your practical work
This is a guide for markers only and does not necessarily represent the definitive basis for an
allocated mark
Student
Number
Overtype with
your numbers
Student Name Overtype with your names then print
Maximum marks = 6, minimum mark = 0. Marks will be deducted for
each error, omission or inconsistency.
Stage 1: TASK 1a Data Sheet Validation Checklist
IM = Input Message, should fully describe input constraints to user and any user
action required
SCE = Settings Capture Error(s) to ensure violation of constraints is captured,
and
EAM = Error Alert Message, informative message to user with appropriate action,
Each aspect needs to be addressed and both correct and appropriate.
Category
Card Number
Wine types
Wine Quantities
When...... Comment (if appropriate)
IM
SCE
EAM
(/) (/) (/)
....is non-numeric or
wrong length
..are other than
Red/White/Mixed
...are non-numeric
...are non-integer
...are not in range
6 marks available, marks deducted for each error/omission/inconsistency
Stage 1 Marks:
Marker Signature:
Date:
Please note only 40% of these marks may be available if the work is
demonstrated after the session as scheduled in the Scheme of Work
22
/6
CT5002 User Support Systems Development - Module Guide
This is a guide for markers only and does not necessarily represent the definitive basis for an
allocated mark
Student
Number
Overtype with your
student numbers
Student Name Overtype with your names then print
Marks will be deducted for each error/omission/inconsistency.
Stage 2: TASK 1a Data Validation via Coding Checklist
EC= Error Captured, AMD=Appropriate Message Displayed & AAT= Appropriate
Action Taken e.g. clear cell, position cursor and exit validation routine.
Category
When......
....is non-numeric
Card Number
....is empty
2_1
Card Number
...is numeric but
wrong length
2_2
..are other than
Red/White/Mixed
Wine types
..are all empty
AMD
AAT
(/) (/) (/)
2_0 There are no marks allocated for correct inclusion but
marks will be deducted for omission of or incorrect code
Card Number
Wine types
EC
Comment (if appropriate)
-
-
-
2_3a, 2_3b, 2_3c
2_4
Quantities
...are non-numeric
2_5a, 2_5b, 2_5c
Quantities
...are non-integer
2_6a, 2_6b, 2_6c
Quantities
...are not in range
2_7a, 2_7b,2_7c
Quantities
...are all empty
2_8
Stage 2 Marks:
/24
Marker Signature:
Date:
All marks are subject to exam board ratification
Please note only 40% of these marks may be available if the work is
demonstrated after the session as scheduled in the Scheme of Work.
23
CT5002 User Support Systems Development - Module Guide
This is a guide for markers only and does not necessarily represent the definitive basis for an
allocated mark
Student
Number
Overtype with your
numbers
Student Name Overtype with your names then print
Stage 3: TASK 1b
Category
Feature
Sub Feature
(Mark Breakdown if applicable)
Displays Main Menu and Order Form OK
Silver Toad
Basics
5
Data Transfer Works for empty database (5)
5
Data Transfer Any order wine type OK e.g. WRM (5
5
Data Transfer Order Ref generation OK (5)
5
Prompts
Control and other logic
Validation code calls Transfer
Clears form OK for next order
5
Print required? includes Order Ref No
Another order?
5
Menu navigation – auto and manual OK
Generally robust
5
Stage 3 Marks
Marker Signature:
Date:
Mark
awarded
5
Data Transfer Works with dummy rec & RWM order (5)
Control and other logic
24
Mark
Available
/40
CT5002 User Support Systems Development - Module Guide
Student
Number
Overtype with your
numbers
Student Name Overtype with your names then print
Stage 4: TASK 2 (2a plus either 2b or 2c)
Each aspect needs to Capture Error, give an Appropriate Message & Take Action
When......
2a
Expiry Date
When......
Comment (if
appropriate)
Error
....is empty
1
2
...is wrong length
2
2
..has non-numeric month or year
3a,3b
4
Month not in range 1 - 12
4a,4b
4
Year<current year
5
2
Month < current, if this year
6
2
Separator not “/”
7
2
Comment (if
appropriate)
Error
...offer is empty or illegal
2b
Offer & Gift
...offer is N, Gift is not empty
...offer is Y, Gift is empty or
illegal
When......
2c
combined
Wine types &
quantities
Mark
Available
1a,1b
4
2
4
3a,3b
4
Comment (if
appropriate)
Error
...wine types are duplicated
...wine type missing when
quantity set
... quantity missing when wine
type set
Mark
Available
Mark
Available
1a,1b,1c
4
2a,2b,2c
4
3a,3b,3c
4
Mark
awarded
Mark
awarded
Mark
awarded
All marks are subject to exam board ratification
Stage 4 Marks
/30
Marker Signature:
Date:
25
CT5002 User Support Systems Development - Module Guide
Appendix 2: CT5002 Microsoft Access Practical – Mark Sheets
This is a guide for markers only and does not necessarily represent the definitive basis for an
allocated mark
Student
Number
Overtype with your
numbers
Student Name Overtype with your names
TASK 1
Category
Feature Approx Mark Breakdown
Product
Browser
GoTo Product
Product
Browser
Add To Order
button
Orders
Form
Validate ‘Date
Required’
Orders
Last
Month
Date functions
Orders
for Period
Additional
feature
Date Entry
e.g. Delete buttons
Single form subform &synchronised
combo (4)
Multiple fields via concatenation(2)
Includes stock level (2)
User instructions[click drop-down](2)
New record in table (5)
New record displayed in subform (2)
Check & message re. for dup prod(5)
Works but not coded as function (4)
Coded as Function (3)
Clears control & cursor stays there(3)
LastOfLastMonth() OK (4)
FirstOfLastMonth() OK (4)
Functions used in query criteria (2)
Pop-up boxes/parameter OK (2 max)
Or
Correct operation of input form with
date picker (4)
Dates validated OK
[date inputs&compared](4)
ONE Nominated working option
e.g.
delete buttons on main and subform (6)
Mark
Mark
Available awarded
10
12
10
10
8
10
with clear message checks (4)
Ease of
Use
Clarity,
& Robustness
Smooth operation & robust (4)
Plus 2 others
(±3 each, max 6)
Overtype this text to list 2 or 3 other aspects you
consider worthy of consideration in terms of
establishing a professional-looking application
10
Marks can also be deducted for
aspects that are considered lacking in
some respect according to the
severity
TOTAL MARKS for TASK 1(max 70)
All marks are subject to exam board ratification
26
CT5002 User Support Systems Development - Module Guide
This is a guide for markers only and does not necessarily represent the definitive basis for an
allocated mark
Student
Number
Overtype with your
numbers
Student Name Overtype with your names
TASK 2
Mark
Mark
Available awarded
Single Order Report
Unsynchronised report (max 15)
– multiple order
– parameter query
– hard-wired single order
OR
Synchronised report (max 25)
– full syntax ref to OrderID on form
–OrderID obtained via function
30
and
Totals (max 5)
Total Cost
VAT
Total Order Value
TOTAL MARKS for TASK 2
c/f TOTAL MARKS for TASK 1 (overleaf)
TOTAL MARKS AWARDED
Marker:
Mo Clutterbuck
Kevin Walter
Signature:
Date:
All marks are subject to exam board ratification
27
CT5002 User Support Systems Development - Module Guide
28
CT5002 User Support Systems Development - Module Guide
Appendix 3: ICT Assessment Criteria Grid
Mark
%
0
Grade &
Characteristics
Fail
1-9
10-29
Fail
Fail
30-39
Reassess:
inadequate but
recoverable with
limited effort
4049:
3rd, D
Pass: Sufficient for
award of credit
adequate mainly
descriptive approach,
fair, limited conceptual
or theoretical ability
50-59
2ii, C
BTEC Merit - 53-59
BTEC Pass - 50-52
Satisfactory
Satisfactory with some
conceptual ability but
lacks good evaluation
or synthesis of ideas
2i, B
BTEC Merit -60-65
BTEC Distinction -6669
Good.
Good analysis,
evaluation, synthesis,
integration &
argument.
60-69
70-79
first class, A,
Excellent.
BTEC Distinction
as above but also
stronger evidence of
excellent, original,
innovative, articulate
work
80-89
Outstanding.
BTEC Distinction
as above but also
authoritative,
superlative,
creative
Faultless
BTEC Distinction
90100
Theory &
Academic Approach
plagiarism, collusion, non-pres., name
only
no understanding, very short, inadequate
factual but little interpretation, lacks
coherence, short, errors, misconceptions
coherent but mechanical notes, basic
task OK but limited - partial - rudimentary
answer, limited interpretation, lack of
knowledge of topic, weak English but
some appropriate use of language of
topic
adequate response, demonstration of
basic knowledge, relevant content, clear
intention communicated, evidence of
reading, acceptable minimum level of
English for business presentation but
may lack precision, some limited analysis
/ application of knowledge / theory /
weighting of evidence, inconsistent
good response to task, collates info,
satisfactory analysis & judgement,
constructs generalisations based on
evidence & opinion, argues clearly,
logically & constructs a case, some
limited ability to state a personal position,
correct English with few imprecise
statements
evaluates info. & synthesises
generalisations, good ability to state &
defend personal position, good analysis
& judgement, applies knowledge to new
situations, sound on theory, critical,
understands limitations of methods,
selective coherent & logical approach,
well written with clear, correct and
precise English
very strong ability to state & defend
position, uses criteria & weighting in
judgements, wide knowledge and
theoretical ability, full understanding of
possibilities and limitations of methods &
theories, 75+ more original, innovative
approach, command of critical positions,
lively articulate writing, excellent grasp of
material - synthesis of ideas
as above but also :seen all possibilities in task, gone
beyond accepted conceptual/critical
positions, evidence of creative,
intelligent, innovative approach
consistently & forcefully expressed
as for 80-89 but also :all work superlative & without fault
Practice &
Deliverables
as theory
no effective deliverables
requirements not met; not
recoverable
deliverables partially complete, not
all requirements met, limited
response to brief.
deliverables meet basic
requirement correctly but limited,
just adequate but not innovative,
interesting or exciting, for higher
marks, 45+ just exceeds minimum
specification, might be good in
some areas but not consistent
good deliverables, some evidence
of good design or execution,
coherent and organised product,
some limited evidence of self
criticism concerning deliverable,
some independence, initiative,
autonomy, appropriate techniques,
integration of knowledge for task
all criteria met to good standard,
evidence of good design or
execution, good integration of
academic & practical issues, solid
evidence of self critique/evaluation
of deliverables, products well
organised - documented coherent. Evidence of
independence, initiative, autonomy,
creativity, adaptability,
resourcefulness. Integration of
knowledge,
most criteria met to high standard,
strong evidence of evaluation of
deliverables, 75+: deliverables
excellent - all criteria met in clear
and definite manner, evidence of
excellent design or execution,
elegance, innovation, very good
evaluation of deliverables,
as above but also :all aspects of deliverables
superlative
beyond 80% emphasis on theory
rather than practice/deliverables
as for 80-89
29
BT230 User Support Systems Development - Module Guide
Appendix 4: Specimen GARF
CT5002
Group Assignment Registration Form
To be completed by one group member and emailed to [email protected] and all other group members
Group Name:
Agreed method of
communication:
Group Members
Student Number
30
Forename
Surname
Contact Phone #
UoG  Version No.: 16
Email (if different from
University)