| Unit name | Design Verification (Teaching Unit) |
|---|---|
| Unit code | COMS30026 |
| Credit points | 0 |
| Level of study | H/6 |
| Teaching block(s) |
Teaching Block 1 (weeks 1 - 12) |
| Unit director | Professor. Eder |
| Open unit status | Not open |
| Units you must take before you take this one (pre-requisite units) |
COMS10016 Imperative and Functional Programming and COMS10018 Object-Oriented Programming and Algorithms or equivalent. COMS20008 Computer Systems A or equivalent. Strong programming skills, software engineering skills and a basic understanding of computer architecture. |
| Units you must take alongside this one (co-requisite units) |
EITHER COMS30081 Topics in Computer Science (Examination assessment, 20 credits). OR COMS30086 Design Verification (20 credits). Please note: This unit is the Teaching only unit for the Design Verification option. Students taking this unit choose to be assessed by EITHER the MAJOR 20 credit unit (COMS30086) OR as part of the Topics in Computer Science MINOR 20 credit examination unit. Students select the form of assessment to be taken by enrolling on the appropriate co-requisite assessment unit. |
| Units you may not take alongside this one |
None. |
| School/department | School of Computer Science |
| Faculty | Faculty of Engineering |
Why is this unit important?
This unit familiarises students with the methods and techniques used in the design verification process, and gives them the technical background plus some of the practical skills (if assessed by coursework) expected from a design verification engineer. Almost all of what is taught is transferable into students’ professional software development or hardware design practice. Students will be exposed to a range of challenging final year project topics, some in collaboration with industrial partners. In addition, the unit content will open up various lucrative longer-term career opportunities, both within academia and industry.
How does this unit fit into your programme of study
This is an optional unit that can be taken in Year 3 for Computer Science students. It is mandatory for Year 3 BEng Computer Science and Electronics students. This positioning allows students to make use of fundamental skills and knowledge developed during the first two years of their study. This unit is also delivered around the time that students are selecting their final year project topics, so can have an influence on the nature of projects undertaken.
An overview of content
This unit introduces students to theoretical and practical aspects of design verification with examples from computer architecture and processor design. It starts with an overview of various verification techniques and explores their limits. We investigate two major topics: Simulation-based Testing (dynamic verification) and Property Checking (static verification). Simulation-based Testing includes the use of simulators, testbench components, collecting and measuring coverage, as well as assertion-based verification and requirements formalization. Property Checking investigates formal model checking techniques and features of state-of-the-art tools, the advantages and limitations of formal verification techniques and how simulation-based techniques can complement formal verification. The course also offers lectures on design and verification flow, including how to write a verification plan.
How will students, personally, be different as a result of the unit
The material delivered in this unit will fundamentally change students’ approach to system design; if you know you need to verify a system, you’ll design it differently. This unit aims to equip students with the knowledge and skills that enable them to see how to design a system for verification.
Learning Outcomes
On successful completion of this unit, ALL students will be able to:
1. Discuss the process of design verification, its complexities and limits.
2. Describe a variety of state-of-the-art verification techniques, including test-based and formal methods, their foundations, practical use, advantages and limits.
3. Set verification goals, select suitable verification methods and techniques to achieve these and assess the associated risks.
When the unit is taken with the associated 20 credit MAJOR option, students will also be able to:
4. Compile a verification plan, organise resources and perform a functional verification (as part of a small verification project).
5. Demonstrate a range of practical skills in the use of state-of-the-art professional verification tools and environments.
6. Document verification completion criteria, monitor progress, determine verification effectiveness and assess when the project can be signed off.
Teaching will be delivered through a combination of synchronous and asynchronous sessions, including lectures, practical activities supported by drop-in sessions, problem sheets and self-directed exercises.
Teaching will take place over Weeks 1-7, with coursework in Weeks 9-11 and for students assessed by examination, consolidation and revision sessions in Week 12.
If taken with coursework, the unit provides weekly coursework support sessions as required.
Tasks which help you learn and prepare you for summative tasks (formative):
Preparing for and attending the weekly lab sessions will help you turn the taught material into practical skills.
Teaching will take place over Weeks 1-7, with coursework support in Weeks 9-11 and for students assessed by examination, consolidation and revision sessions in Week 12.
Tasks which count towards your unit mark (summative):
For students taking this unit with the Topics in Computer Science (MINOR) examination unit, it will contribute 50% towards the 20CP Topics in Computer Science exam, (equivalent to 1 hour of exam time) that will be sat during the winter examination period. This closed-book exam will assess Learning Outcomes 1, 2, and 3.
For students taking this unit as a 20CP MAJOR choice, there will be two elements of assessment:
When assessment does not go to plan
Students will retake relevant assessments in a like-for-like fashion in accordance with the University rules and regulations.
If this unit has a Resource List, you will normally find a link to it in the Blackboard area for the unit. Sometimes there will be a separate link for each weekly topic.
If you are unable to access a list through Blackboard, you can also find it via the Resource Lists homepage. Search for the list by the unit name or code (e.g. COMS30026).
How much time the unit requires
Each credit equates to 10 hours of total student input. For example a 20 credit unit will take you 200 hours
of study to complete. Your total learning time is made up of contact time, directed learning tasks,
independent learning and assessment activity.
See the University Workload statement relating to this unit for more information.
Assessment
The Board of Examiners will consider all cases where students have failed or not completed the assessments required for credit.
The Board considers each student's outcomes across all the units which contribute to each year's programme of study. For appropriate assessments, if you have self-certificated your absence, you will normally be required to complete it the next time it runs (for assessments at the end of TB1 and TB2 this is usually in the next re-assessment period).
The Board of Examiners will take into account any exceptional circumstances and operates
within the Regulations and Code of Practice for Taught Programmes.
