[ Home | Syllabus |Course Notes]
|Title||Windows NT Systems Programming|
|Lectures||Tuesday/Thursday 11:00-12:15 PM|
|Office||Education Room TBA|
|Office Hours||Tues/Thurs 10:00-11:00 AM 4:00-5:15 PM or by appointment|
|Textbooks||Win32 Systems Services, 2nd edition,
Marshall Brain, Prentice Hall PTR, 1996, ISBN
Programming Windows 95 with MFC, Jeff Prosise, Microsoft Press, 1996, ISBN 1-55615-902-1
Objectives: Gain a basic understanding of systems programming for the Windows NT and 95 platforms. Emphasis will be placed on network application programming. This course will cover the architecture of the windows NT programming environment. Two major areas of study will be the WIN32 API service layer and GUI programming using the Microsoft Foundation Classes (MFC) of Visual C++. This course will provide a practical application of material from operating systems, computer networks, data structures and object oriented design.
PreRequisites: Strong Background in C++ and Operating Systems. Network and Communications concepts would also be useful. Because of the importance of MFC in windows programming, you should be comfortable with the principles of object oriented programming and their implementation in C++. You should be able to read the C++ constructs in the these examples.
|WIN 32 API||GUI in MFC|
|File Handling||Windows Message System|
|Process and Thread Management||User Events (keyboard and mouse)|
|Remote Procedure Calls (DCOM)||Document/View Architecture|
Attendance: Attendance at classes is not generally required, but students are responsible for all material covered and announcements made in class. Consequently, if you are going to miss class, be sure to get notes, handouts, etc., from another class member. Class notes and other information will be available at the following WebSite: http://www.cs.odu.edu/~wild/windowsNT.
During the first two weeks of class, please notify the instructor if you will be missing two or more classes in a row, as it will otherwise be assumed that you have dropped the class.
Cheating: Everything turned in for grading in this course must be your own work. The instructor reserves the right to to question a student orally or in writing and to use his evaluation of the student's understanding of the assignment and of the submitted solution as evidence of cheating. Violations will be reported to the Honor Council for consideration for punitive action. However, it is entirely appropriate seek and give assistance on procedural matters (such as how to send e-mail, how to run the debugger, how to send files from a home PC to a UNIX workstations). If there is any question on whether a particular behavior is appropriate, the student is encouraged to seek guidance from the instructor.