TDTS07 System Design and Methodology

Laboratory

Rules

Before you read the information on this Web page and before you register for the labs, please spend some time to read the

rules (this is a link)

that we apply to conduct the laboratory work in this course. In addition to what you just read by following the abovementioned link,

• a lab group consists of 1 or 2 students (preferably 2!),
• the members in a lab group must work together during the whole course, and
• a lab group is not allowed to work on more than one computer during the scheduled lab sessions.

If you have any questions, or if you are not sure about the exact meaning of any of the rules, you must consult the course leader or the lab assistants before you start working with the labs.

Lessons

The two lessons give an introduction to the labs and an opportunity for the students to further clarify issues regarding the labs. Please read the lessons page for more information regarding contents and schedule.

Lab sessions

We have 10 scheduled lab sessions (2 hours each). You are expected to read and prepare the material related to the lab before going to the supervised lab sessions.

Lab registration

You must choose your lab partner and sign up for the labs through a Web interface. The deadline for lab registration is January 27, 2012.

Deadline

The (firm) deadline for the lab assignments is March 16, 2012. The results (i.e., the students that have passed the laboratory part of the course) will be registered in LADOK on Monday morning, March 19, 2012. Note that all reports that are handed in after the lab deadline will be corrected when your assistant has time. The next corresponding LADOK registration will be end of June.

Assignments and their examination

The laboratory part of this course comprises three separate labs. To prepare for a lab, study its tutorial by following the corresponding link below, and try the presented examples. The assignments for a lab are found in the tutorial.

• 1. Modeling and simulation with SystemC

  Examination: To pass this lab, you must hand in a written report that explains your solution.

• 2. Formal verification with UPPAAL

  Examination: To pass this lab, you must hand in a written report that explains your solution.

• 3. Design space exploration with an MPARM simulator

  Examination: To pass this lab, you must hand in a written report that explains your solution.

Useful links

• SystemC tutorials
• Short UPPAAL tutorial [pdf]
• Long UPPAAL tutorial [pdf]