![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Real-Time Software Development Topic Summary: Created On: 23-Mar-2006 17:19 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Real-Time Software Development
University of North Texas Denton, TX USA Instructor: Dr. Hubert Bahr [email]hab@unt.edu[/email] Course Description: Specification of real-time system requirements, timing, synchronization and fault-tolerance issues, construction and validation of real-time software. Mathematical formalisms, design and analysis using real-time UML will also be emphasized. Prerequisites: CSCE 3610/4620. Text and Resources: RealTime Systems, Jane W.S. Liu, publisher Prentice Hall ISBN: 0130996513 2000 Software Engineering for RealTime Systems, Jim Cooling, Addison Wesley ISBN: 0201596203 2003 We will also be using I-Logix?s Rhapsody for modeling the realtime system. Grading: Homework: (Best 70% of assignments) 10 % Class Project 25 % Quizzes and Participation: (Best 70%) 15 % Midterm Exam 25 % Final: 25 % Policies: · ABSOLUTELY, NO LATE homework or projects will be graded, unless specific arrangements are made with the instructor in advance. · All homework will be turned in by midnight on the date due. Homework may only be submitted via email. · ALL requests for make-up exams and extensions on other assignments must be made prior to the due date or exam date, in person, and must be for a valid ?emergency? reason. In extreme circumstances, contact after the due date may be accepted if there is a COMPELLING reason. Normally makeups are not given. I have not found a valid reason to give a make up exam yet. · Attendance is at your option. However, you are responsible for all discussion, lecture and other information disseminated during the lecture period, regardless of whether you attend or not. Also note that there is a component of your grade that is for Quizzes and Participation. In general, quizzes will usually be unannounced prior to there occurrence, they are encouraged by light class attendance. They are subject to be given at any point during the class and more than one may be given in the same 1.5 hour block of instruction. · Lectures, Homework and Project assignments are not included in this syllabus. Typically quizzes are given over the reading assignment prior to the lecture on that topic, and homework is due after the completion of the last lecture on the topic. However, you should regularly check the class website, as well as take note of in-class announcements, for changes in the schedule or assignments. Collaboration and Cheating: Collaboration among students in class is most certainly encouraged, as it is my belief that it provides a better learning environment. For written homework I encourage collaboration as well, but make sure that each person can derive the correct result(s) by his or her self. Exam questions will often come directly from homework. On programming assignments, however, there should be no collaboration at all among students. No assignment-specific assistance should be given nor received on any programming assignment. Any outside help concerning the use of the computer facilities is acceptable. You may discuss the meaning or intent of an assignment, but not ways to program it. All work turned in must be completely your own. You must not share code or even outlines! Any and all use of programs from other texts or references must be explicitly stated as part of program documentation. And of course you need to do your own work on exams as well. |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.