| TDDC05 | Embedded Systems Simulation and Verification, 7,5 ECTS credits. /Projektkurs i Inbyggda systems simulering och verifiering, CDIO/ |
||
Prel. scheduled
hours: 64 |
|||
|
Area of Education: Technology Subject area: Computer Science/Computer Engineering |
|||
| Advancement level
(A-D): C
|
|||
| Aim: The project is carried out in accordance with industrial professional practice, and it is aimed to develop and pinpoint competence in the following areas: - To Analyse and structure a problem, -To seek and obtain complementary knowledge, -To write and follow up project plan and time plan, -Active contribution as a team member in a group, -Apply knowledge learnt in earlier courses, - Take initiative and find creative solutions, -Report on the results verbally and in writing, -To get basic knowledge in industrial development methods for systems with embedded software, -To get an understanding for the importance of requirements management for a system,in particular, systems that include other components (mechanics, electronics, hydraulics) than software. -To learn the use of tools for tracing the requirements to different subsystems at design and verification stages, -To get familiar with specifying systems using discrete modeling tools like finite automata,functional blocks and logic,-To learn how specifications can be used to verify that a design satisfies the functional and performance requirements, - To use models for automatic generation of code, and for future updates and evolution of the system. The results of the project shall: -be of a high technical quality and based on modern methods in system construction, -be documented in the form of a project plan and time plan, as well as a technical report, -be presented orally, -be followed up in a post-analysis repport. |
|||
| Prerequisites: (valid for students admitted to programmes within which the course is offered) Real-time systems (eg. TDDC47, TDDB47) and basic course in automatic control, basic set theory. Note: Admission requirements for non-programme students usually also include admission requirements for the programme and threshhold requirements for progression within the programme, or corresponding. |
|||
| Organisation: There will be lectures providing an overview of the theory of system development, as well as lectures covering fundamental notions in formal specification and verification. There are resource sessions available for questions about practical handling of tools. The student's work also includes individual exercises to obtain deeper knowledge. The course is spread over two periods (the whole spring term). The work is carried out in project form in groups of 4-5 persons from different educational programs.For students outside the Y program there will be a lecture on orientation in CDIO and the LIPS templates. Every group has a supervisor that helps with practical problems around tools and management of the group process. There is a possibility of booking time with an "expert" (consultant) to discuss design issues and experiences from similar projects. Every group agrees on its requirements specification with a customer. Before the work starts the group draws up a project plan and a time plan. These documents are recorded in accordance with the LIPS templates. This applies also to the reflection document (the post analysis report). |
|||
| Course contents: Lectures: Development of systems with embedded software. Different phases of systems engineering process and standards, and the relation to software engineering. Tools for modelling systems: Finite automata, data flow diagrams and specification languages - discrete as well as hybrid (discrete/continuous). Orientation on component based modelling and recent development approaches (e.g. Model Driven Architecture, standards like UML). Use of logic to prove system properties. Resource sessions: Questions around the tools to be used in the project, for example: requirements management in CORE, design specification in UML or other tools (e.g. Scade), and logik-based verification tools (e.g. Prover plugin). The work in the project consists of capturing requirements, design, implementation, and verification documents for a laser guided vehicle that moves in a printing area and finds its way in a number of rooms, lifts and moves paper rolls and places them in special areas. The robot should function in a correct and safe way in relation to other objects, operators, fire doors, and so on, that should be verified using simulations and formal verification. |
|||
| Course literature: Systems Engineering: Coping with complexity. R. Stevens, K. Jackson, P. Brook, S. Arnold, Prentice Hall, 1998. Handouts and supplementary books. |
|||
| Examination: | |||
| Planning and follow-up of project, Requirements management and specification, Design specification and verification for a high-level design, code generation and adaptation (Group assignment). Home assigments in Logic (Individual). |
4 p 1 p |
||
| The work in the project is graded based on satisfaction of course goals. Six partial goals that are each graded as pass/fail are included. These are: Requirement capture and specification, Design specification, verification of high level properties, Code generation and adjustment, Written documentation, Oral presentation and LIPS docuemnts. The LIPS documents should at least include project plan, time plan, and the post analysis report. To pass the project part all the partial goals for the course should be achieved. Grades are given as �?~Fail�?T or �?~Pass�?T. | |||
Course language is Swedish. Department offering the course: IDA. Director of Studies: sas-sr @ ida.liu.se Examiner: Simin Nadjm-Tehrani Link to the course homepage at the department Course Syllabus in Swedish |
|||
|
|
 |
|||||
| ||||||