Real-time Software Engineering

Identify techniques used in the analysis and prediction of the timing behavior of a system based on detailed design. Specify examples of using such techniques for assessing design trade offs and troubleshooting the system timing behavior.

Identify tasks and techniques used for software verification and validation at the early stages of the software life-cycle.

Topics

• Introduction to Real-time Systems
  
• Notes: Chapter 1
• Lecture Slides 1
• Introduction to Software Engineering and the Software Life Cycle
  
• Notes: Chapter 2
• Lecture Slides 2 on system and software engineering development process
• Lecture Slides 3 on software development standards, and ICASE environments
• Project Requirements
  
• System and Software Requirements Analysis 
• Notes: Chapter 3, Section1, the SRS document pdf file
• Structured Analysis for Real-time Systems. 
• Notes: Chapter 3 Section 2, SART notation pdf file
• Lecture Slides 4, The SRS document, and SART Notation
• Project Requirements Analysis Review
  
• High-level Design 
• Notes: Chapter 4
• Lecture Slides 5, Software Design Document and Design Criteria
• Lectures Slides 6, Structured Design Techniques
• Project: High-level Design Review
  
• Lecture Slides 7, Detailed Design, Implementation, and Testing
  
• More on Testing, Testing Strategies, Lecture Slides 8
  
• Testing Techniques, Lecture Slides 9
  
• Project: Detailed Design and Testing Review
  
• Computer Usage: Students will be required to use graphical tools to support the SART/SD notation such MS Visio or Smart Draw.
  

Grading

• Attendance: 5%
  
• Mid-term Exam: 25%
  
• Project
  
• Analysis: 25%
• Design: 20%
• Detailed Design & Coding
• Testing & Verification: 15%
• Project Final Report: 10%

The project will be conducted by groups of two-three students. Reports on projects will be required from each group after each phase. The final report should summarize the whole project and show the testing results, and give a section on problems encountered and lessons learned during the software development process. It is expected that students will participate equally in the work of the group. Group meetings minutes specifying the attendees should be included, and the contribution of each student must be documented in each report.