CSE681 - Software Modeling and Analysis

Lecture #27 - Help with Project #5

Revised: 12/5/2010
Home Courses Code Handouts CoreTech Books Articles Math Research Masters Projects SWDev WebDev News OtherLinks SiteDesign Graduates AllPages Office Hours Notices Contents

CSE681-SWMAA CSE686-IP CSE687-OOD CSE775-DO CSE776-DP CSE778-AWP CSE784-SWS

Lecture #01 Lecture #02 Lecture #03 Lecture #04 Lecture #05 Lecture #06 Lecture #07
Lecture #08 Lecture #09 Lecture #10 Lecture #11 Lecture #12 Lecture #13 Lecture #14
Lecture #15 Lecture #16 Lecture #17 Lecture #18 Lecture #19 Lecture #20 Lecture #21
Lecture #22 Lecture #23 Lecture #24 Lecture #25 Lecture #26 Lecture #27 Lecture #28

Syllabus SG-SMA SG-OCD SG-Notes

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

Office Hours:Instructor & TAs

Content:

This lecture covers some Project #5 helper topics.
  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. Project #5
  3. Enterprise Architecture
  4. Questions concerning Project #5 ?
  5. Bonus Prototypes
    1. Repository manifest builder and scanner with tests showing how it works.
    2. Wizard to quickly build source code for test packages – inputs are name, name of production code package(s). Uses ITest and AbstractTest (see midterm solutions) and default TVG and Logger.
    3. Test Suite builder that uses csc to compile and build test libraries. Required to include timing, using high resolution timer, and timed results in a graph that shows time to compile versus lines of code.
    4. WPF Client GUI that mocks up client operation and illustrates how notification will work.
    5. Communication system with a service contract that has asynchronous PostMessage and streaming file download operation contracts, e.g., pushes messages and pulls files.
    6. Package authenticator that hashes a source file’s checksum, embeds it as a comment in the file, and authenticates by checking the hashed checksum with a computed checksum (after removing the comment). It is acceptable to substitute some other identifier for the checksum if you can think of a good one.
    7. Write code for a version manager that accepts an unversioned file and converts it to a versioned file. The manager should also accept a versioned file and increment its version number. You may version by name or by directory. However, the version manager should also insert a version number comment at the top of each accepted source file. Examine every file generated for a a) C# console application, and b) a C# WPF application. How might you manage versioning of the additional files you find? Do you need to do that?