|Semester 1 Credit Value:||10|
|CSC1025||Mathematics for Computer Science|
|CSC2023||Algorithm Design and Analysis|
To train students with practical aspects of formal modelling and verification technology as parts of a well-founded set of tools and techniques within software engineering.
1.1. The nature of software (SW) verification; verification principles (correctness, concurrency, abstraction, refinement, design decisions, documented assumptions, model-based testing)
1.2. Understanding expertise required and costs involved; identifying the right technique to the task at hand.
2. Modelling and Specification
2.1. From a requirements document and produce an initial abstract specification of the problem.
2.2. Elicit properties of interest from these requirements as formal consistency conditions, and make a specification of them that is amenable to analysis and verification.
2.3. Foundations of formal modelling: propositional and predicate logic, data types and invariants; state-based models; mathematical toolkits.
2.4. Propose design decisions as improved specifications; designs must be amenable to proof and consistency checking of desired properties;
2.5. Possibly propose code-level contracts from formal design.
3. Verification & Validation
3.1. Understand verification support systems able to discharge formal consistency conditions from modelling activities
3.2. Understand what it means for one specification to be a design refinement of another by establishing a link from the requirements to code-contracts
3.3. Study alternative (to formal) techniques aiming at understanding the costs and conditions under which to undertake a formal or rigorous development process.
3.4. Understand the importance of automated proof support and proof engineering (i.e. the process of mechanising a complex model)
3.5. Metrics for complexity, reliability, expertise, time costs
On successful completion of the module, students will be able to describe:
1. How abstraction can be used to capture informal requirements as a formal (mathematical) specification
2. One or more formal specification languages (i.e. modelling language, proof support system language).
3. What can be claimed about the system under design
4. A working knowledge of proof support systems
To be able to make an informed choice from a range of formal software engineering tools and techniques, and to apply them to the development of realistic software and systems.
|Graduate Skills Framework Applicable:||Yes|
|Scheduled Learning And Teaching Activities||Lecture||22||1:00||22:00||Background reading|
|Guided Independent Study||Assessment preparation and completion||28||0:30||14:00||Revision for end of Semester exam and exam duration|
|Guided Independent Study||Assessment preparation and completion||24||1:00||24:00||Lecture follow-up|
|Scheduled Learning And Teaching Activities||Lecture||24||1:00||24:00||Lectures|
|Scheduled Learning And Teaching Activities||Practical||8||1:00||8:00||Practicals|
|Guided Independent Study||Project work||8||1:00||8:00||Coursework|
Lectures provide the knowledge. Practicals to provide additional background.
The format of resits will be determined by the Board of Examiners
|Written Examination||90||1||A||60||Open book exam|
|Prob solv exercises||1||M||40||1 piece of coursework (15 hours)|
The open book exam will assess knowledge. Coursework to reinforce some of the lecture material.
N.B. This module has both “Exam Assessment” and “Other Assessment” (e.g. coursework). If the total mark for either assessment falls below 35%, the maximum mark returned for the module will normally be 35%.
Based on module CSC3304
Note: The Module Catalogue now reflects module information relating to academic year 14/15. Please contact your School Office if you require module information for a previous academic year.
Disclaimer: The University will use all reasonable endeavours to deliver modules in accordance with the descriptions set out in this catalogue. Every effort has been made to ensure the accuracy of the information, however, the University reserves the right to introduce changes to the information given including the addition, withdrawal or restructuring of modules if it considers such action to be necessary.