Driving Test Log Book
IMAT1604 Visual Web Development
This log book must be handed in at the end of the academic year along with a CD containing your work over the year.
This is an official record of your driving tests. Keep it in a safe place.
Your Name ______
P Number ______
Course ______
Tutor ______
Driving test 1 ______/10 marks tutor’s signature:
Driving test 2 ______/10 marks tutor’s signature:
Driving test 3 ______/10 marks tutor’s signature:
Driving test 4 ______/10 marks tutor’s signature:
Driving Test Schedule and Marks Awarded 1
Assignment Introduction 2
Overview 4
Submitting your Log Book 4
The Driving Test Process 5
Three Strikes and you are out! 5
Your Tutor Will Not Help you during the Driving Test 6
Your Tutor is a Very Busy Person 6
The Longer you take the Lower your Grade 6
Test Resetting 6
Banked Grades 7
Points Your Tutor will Check 7
Plagiarism 8
Getting Started on the Driving Tests 9
Driving Test 1 – Delete a Record in a Database 11
Driving Test 1 Skills 11
The Programming Problem 12
Driving Test 2 – Creating a List 13
Driving Test 2 Skills 13
The Programming Problem 14
Driving Test 3 – Insert and Update 15
Driving Test 3 Skills 15
The Programming Problem 16
Driving Test 4 – Linking the Pages 17
Driving Test 4 Skills 17
The Programming Problem 18
Driving Test Schedule and Marks Awarded
Week no / Driving Test 1 / Driving Test 2 / Driving Test 3 / Driving Test 41 / 10 / 10 / 10 / 10
2 / 10 / 10 / 10 / 10
3 / 10 / 10 / 10 / 10
4 / 10 / 10 / 10 / 10
5 / 10 / 10 / 10 / 10
6 / University employability week
7 / 10 / 10 / 10 / 10
8 / 10 / 10 / 10 / 10
9 / 9 / 10 / 10 / 10
10 / 8 / 10 / 10 / 10
11 / 7 / 10 / 10 / 10
12-14 Xmas break
15 / Phase Test 1
16 / 6 / 10 / 10 / 10
17 / 5 / 10 / 10 / 10
18 / 4 / 9 / 10 / 10
19 / 3 / 8 / 10 / 10
20 / 2 / 7 / 10 / 10
21 / 1 / 6 / 10 / 10
22 / University reading week
23 / 0 / 5 / 10 / 10
24 / 4 / 10 / 10
25 / Easter Break
26 / Easter Break
27 / Easter Break
28 / 3 / 9 / 10
29 / 2 / 8 / 10
30 / Phase Test 2
Assignment Introduction
Module name: / Visual Web DevelopmentModule code: / IMAT1604
Title of the Assignment: / Driving Tests
This coursework item is: (delete as appropriate) / Summative / Formative
This summative coursework will be marked anonymously / No
The learning outcomes that are assessed by this coursework are:
· Produce code based solutions to simple problems generating suitable documentation
· Comprehend and explain programming concepts
· Adapt existing code
· Apply good practice in code design/testing and interface design
· Find answers using various resources such as MSDN
This coursework is: (delete as appropriate) / Individual
This coursework constitutes 40% to the overall module mark.
Date Set: / Week 1
Date & Time Due: / By the end of the module (see schedule)
Your marked coursework and feedback will be available to you on:
If for any reason this is not forthcoming by the due date your module leader will let you know why and when it can be expected. The Head of Studies ( ) should be informed of any issues relating to the return of marked coursework and feedback.
Note that you should normally receive feedback on your coursework by no later than four working weeks after the formal hand-in date, provided that you met the submission deadline. / Continuous assessment
When completed you are required to submit your coursework to:
Hand in log book to FOTAC at the end of the module for moderation
Late submission of coursework policy: Late submissions will be processed in accordance with current University regulations which state:
“the time period during which a student may submit a piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar days after the original submission date will receive a mark of 0%. These regulations apply to a student’s first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a previously failed piece of coursework will always receive a mark of 0%.”
Academic Offences and Bad Academic Practices:
These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor referencing or the passing off of somebody else's ideas as your own. If you are in any doubt about what constitutes an academic offence or bad academic practice you must check with your tutor. Further information and details of how DSU can support you, if needed, is available at:
http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academic-offences.aspx and
http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/bad-academic-practice.aspx
Tasks to be undertaken: See below
Deliverables to be submitted for assessment: See below
How the work will be marked: See below
Module leader/tutor name: / Matthew Dean
Contact details: /
Overview
This log book is the official record of your driving test. Keep this book safe!
Submitting your Log Book
At the end of the year you will submit your log book to student services, you will need to hand in:
· A signed cover sheet
· The log book
· A CD containing your code and testing
The Driving Test Process
Step 1: Each driving test involves the completion of a part of the main system you are developing.
Step 2: Once you are happy you understand the code you need to ask your fellow students to question you about your work.
Step 3: Once you are happy you know what you are talking about you may approach your tutor to be formally tested.
During the formal test, your tutor will ask you questions about your code to make sure that you have a clear idea of what the code is doing.
Three Strikes and you are out!
The driving test process is not just about your ability to know and do, but also your ability to find out answers and solutions. If during the driving test there is any aspect of your program which you do not fully understand your tutor will halt the test and you must find out the answer working with your class mates. If you fail to answer three questions during the driving test on the third question you will be deemed to have failed. This means that you must wait until next week to be reassessed picking up where you left off.
Your Tutor Will Not Help you during the Driving Test
In these driving tests, you are encouraged to find answers for yourself. Your tutor will not help you during the test itself, nor should they give you any hints. The answers to the questions that arise may be found in the following places:
· Teaching Materials
· The Internet
· Your fellow students
If you have any specific questions to ask your tutor, they must be asked outside of the formal test.
Your Tutor is a Very Busy Person
Remember you are not the only student wishing to see your tutor.
You may only be tested during the timetabled sessions as and when it is convenient for your tutor. Also note that you may only be tested once in a given week.
The Longer you take the Lower your Grade
A successful driving test will mean that you are awarded a grade based on which week you pass the test in. It is very much in your interest to pass your driving tests as soon as possible. Don’t be shy, you may find you know more than you think, and even if you fail you will still find out what you need to know in order to pass on the next attempt.
Test Resetting
You may decide to reset a driving test to full marks. What this means is that you may decide to reset driving test 1 at full marks. In resetting a test in this way you will sacrifice later tests. For example resetting test 1 would sacrifice test 4. Resetting test 2 would sacrifice test 3 & 4. There is no option to reset tests 3 or 4.
Banked Grades
As you progress through each test you have the option to bank your grades. What this means is that you may claim the grade for that week having answered specified questions.
For example in driving test should you answer questions 1 and 2 correctly in week 8 (10 out of 10) you will be awarded full marks for those two questions even if you complete the test the following week when it drops to 9 out of 10.
Points Your Tutor will Check
· Your code for suitable comments
· Your code and controls for correct use of the naming convention
· Your variable /object names
· The structure of your code (For example unwieldy or inefficient IF statements)
· The testing, by asking you to run through tests in your plan
· Your program, by running it to see if it works
· Your comprehension, by asking you questions on how your code works
· Your skill, by asking you to change / correct something
If you answer all questions clearly and correctly you will be awarded the grade for the week in which you pass the test, e.g. a pass in week one will give you 10 out of 10, a pass in week sixteen 6 out of 10. You must pass all questions asked by your tutor.
Plagiarism
In preparing for the driving tests, you are all encouraged to work together. This will inevitably result in people producing similar solutions.
You must make an effort to personalise your own code. If your code is the same as another student’s you will automatically fail the test for that week.
Getting Started on the Driving Tests
You have been provided with a file on the module web site called “Address Book Finished.Zip”. You will need to download and try out the sample web site.
Having looked at the sample program you need to decide on an overall topic for your four driving tests. This topic may be anything that you like (but not an address book). You could perhaps decide you are setting up an on-line shop selling a product of some sort that you find interesting, e.g. mobile phones, DVDs or holidays.
Once you have decided on your topic you must get it approved by your tutor.
No two students in the same lab group may be working on identical topics!
Once you have decided on your topic you will need to document your design so that it is clear what you plan to achieve.
You will need to create the following diagrams
Class diagram
Use Case Diagram
Entity Relationship Diagram
(To do this you may copy and adapt the documents provided in week 2)
Once you have created the documented your design you will need to create an SQL server database to store the data for your site. At this stage you will need to create two tables.
Table 1 will contain the primary data for your database e.g. tblAddress in the address book.
This table must contain
· A primary key set up as identity
· Text fields of suitable size
· At least one numeric field
· At least one date field
· At least one Boolean field
Keep the number of fields to a sensible minimum otherwise you will be creating too much work for yourself.
Table 2 will contain secondary data for your database e.g. tblCounty in the address book example.
This table must contain
· A primary key set up as identity
· A text field of suitable size
Driving Test 1 – Delete a Record in a Database
Driving Test 1 Skills
Please do not write on this page
You are able to / Signed1. Present the plans for your design (class diagram, use case diagram and entity relationship diagram)
2. Write meaningful comments
3. Explain variables, naming conventions, values and data types
4. Explain the use of the assignment operator
5. Explain objects and classes, their purpose and relationship to each other
6. Explain the difference between methods and properties
7. Demonstrate simple validation and error messages
8. Give examples of sequence
9. Explain events and handlers
10. Demonstrate the correct use and purpose of naming conventions for controls
11. Create a simple three layer application explaining one of the benefits
12. Explain how parameters work
Banked Grades
1, 2 Wk grade ______x .4 ______
3-6 Wk grade ______x .3 ______
7-12 Wk grade ______x .3 ______
The Programming Problem
You need to set up Visual Studio to support your three layer architecture such that your database is in the App_Data folder, the DataConnection class is in the App_Code folder and a web form called Delete.aspx is in the root of the site.
When you run the program you should be able to enter the value of a primary key into a text box. Upon pressing a suitable button the value of the primary key should be passed to the middle layer and the corresponding record in the data layer should be deleted.
If the user enters a value that is not a number the program should show an error message to let them know. The program does not need to deal with attempts to delete primary key values that do not exist in the database.
Driving Test 2 – Creating a List
Driving Test 2 Skills
Please do not write on this page