C C T B H P N

Lecture #19 - Midterm Review

Web Resources:

UML XML, HTML Code Project Microsoft Developer's Network DevelopMentor XML Sells Brothers Windows Developer's Journal WindowsClient.net DotNetJunkies dotnet quickstart tutorials C# Corner Mono Project Performance Counters

Today we review for the Midterm that you will take on Monday.
  1. The Syllabus describes topics to be covered, reading material for you to digest before coming to class, and due dates for the assigned projects.
  2. Exam Notes

    The exam is closed book. You may bring in one sheet of notes, written with text as small as you like, on both sides if you wish. You may bring in and use a magnifing glass. You may not share notes with someone else during the exam. If you bring in more than one page I will take all but one from you - my choice which ones. The exam will start promptly at the beginning of the class period and end promptly at the end of the class period. If you come late you will not be given more time at the end. I strongly recommend you hand write your notes rather than copy parts of the class notes. Organizing them and writting them yourself will help you remember their contents.
  3. Midterm Exam

    Study materials:

    Delegates, Threads, Tasks, Blocking Queue, Wait For Event, WPF Dispatcher Invoke Demo, Lambda Capture, Lambda Demo, Reflection
    Parameter passing Note: the Tasks link contains a demo of async await in a WPF application. Topics for Midterm, doc

    Make sure you look at:
    • Project #1, Project #2, Project #3, Project #4
    • Project #1
      Uses and users, impact on design, structure, critical issues
    • Project #2
      Use of classes, interfaces, inheritance, and C# object model
    • Project #3
      • How did you use data structures to store type and dependency information?
      • What is the processing flow used for analysis?
    • Project #4
      • How will we use Message-Passing-Comm to support sending files and messages? What messages are required?
        What will the code analyzer and client be required to do?
      • Look at use of threads in Sender, Receiver, and WpfClient.
      • Look at service and data contracts.
      • Look at Activity and Package Diagrams here.
    • delegates, lambdas, threads, and Tasks
    • WCF contracts, instancing, bindings
    • LINQ and XDocument
    • .Net Object model and simple reflection
    • UML, e.g., package, activity, and class diagrams
    • .Net Collections and Generic.Collections