CLASS GUIDELINES
Cpe 684
Advanced Real-Time Systems Development
Fall semester of every year
Instructor: Prof. Dr. Hany H. Ammar, email: hammar@wvu.edu,
Office: 246 AER, Phone: 293-9682. Office Hours: Tuesdays: 10:30 -11:45 am,
Wednesdays 10:30 am 12:00 noon, Thursdays 10:00 11:00 am
Prerequisites: CS 415, Intr. To Object-Oriented Programming, CpE 484, Intr. to Real-Time Systems Development, or instructor consent.
Recommended Text: Pattern-Oriented Analysis and Design: Composing Patterns to Design Software Systems by Sherif M. Yacoub, Hany H. Ammar, Addison-Wesley, 2004, ISBN: 0201776405
References:
Course Description and Objectives: This is a project-based course focused on systems development with an emphasis on analysis and design of real-time systems. The course starts by introducing the Unified Modeling Language (UML) for real-time systems and describing their characteristics and unique attributes of real-time safety critical systems. The object-oriented development process for embedded systems is described. The analysis and design phases of development are then covered by describing object modeling techniques and design patterns and frameworks. The Course concentrates on Pattern-Oriented Analysis and Design (POAD). The POAD process and its application to several case studies will be addressed.
A computer-aided software engineering (CASE) tool is used throughout the course. A term project, in-class exercises, and a mid-term examination are used to assess the students learning process. The term project is to be done in teams of 3 or 4 students. Project Presentations and reviews will be conducted in class..
Expected Learning Outcomes:
Upon successful completion of this course students will be able to:
Topics:.(Lecture Slides).................................................................................................# of Weeks
· Review of Real-Time Systems Attributes and Characteristics 1/2
· Introduction to Object-Oriented Analysis and Design and The Unified Modeling Language (UML) 1/2
Case study: The Digital Sound recorder
·
Requirements
Engineering, and Object Oriented Analysis (OOA) 2
o The UML Requirements Model Use Case Diagrams, Sequence Diagrams,
o The UML Object Model Class Diagrams, State Charts
Grading:
The project will be conducted by groups of 3 or 4 students. Project Reviews and Reports will be required from each group. The final report should summarize the whole project and document problems encountered and lessons learned during the software analysis and design 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.
Grading Policy : No make-up exams except by prior arrangement with instructor
Late assignment = no assignment
Exam grading appeals in writing on the day the exam is returned.