All project demonstrations and evaluations will be on 3 January 2008, Thursday (CENG 401) and 4 January 2008, Friday (BILM 401), between 9:00 and 16:00.

The project team demonstrations will be scheduled according the CENG 401 projects list (6 projects) and BILM 401 projects list (6 projects).

There will be 3 projects (at 9, 10 and 11) in the morning, and 3 projects (at 13, 14, and 15) in the afternoon on Thursday (CENG 401 Projects) and Friday (BILM 401 Projects).

A project demo duration will be 30-45 minutes depending on the project.

All team members must be ready to answer questions about your project in the lab at your presentation time.

When evaluating a project team in their time, other teams will not be in the lab.

You should come at least 30-45 minutes before your demo time, your team may be called earlier depending on the project presentation before your time. 

Upload all your project work to your project web site before your demo time.

You should have submitted your printed documents, updated Project Proposal, RAD, SAD, and UM, to your instructor before your demonstration.

Your running program, UML modeling and development tools (Borland JBuilder 2007) must be ready before you show your final work.

Your program must be running without your development tool! That is you should have deployed and put all your class files into a JAR file and run it using only a Java Run Time Environment (JRE). In short, it should be a product, not a developing application in a development environment!

You should also bring your Project Contribution Report. Prepare it using this template.

When evaluating your project, I'll use this project organization document for your project organization and this grading policy document for grading all artifacts and activities of your project.

During the demo, first of all, you have to show your software architecture and working prototype based on PCMEF meta architecture using Together and your implementation tool (Eclipse or JBuilder).

You have to show your packages, their dependencies, class diagrams, your updated functional model (Use Case model and companion HTML documents), updated some dynamic views (sequence, activity, state diagrams depending on your project) using Together.

Your User Manual (UM), Coding and Product (CP) will be graded this last week. Your Process and Communication (PC) have being graded for some time...

The grading criteria for Coding and Product (CP):

Software Architecture and Development Techniques   (35)
  Architecture and Project Difficulty (Subsystem decomposition based on PCMEF, packages, classes, inheritance, ...) (20)
  Applying UML and Patterns (15)

Coding and Implementation (35)
  Coding Style and Coding API Documentation (15)
    (Java coding style and documentation - generated Javadoc HTML API showing packages, classes and their explanations )
  Testing Process (10)
  Audits and Metrics for Source Code (10)

Product (30)
  Final Product for Naive End User: Working Software (Functionality, usability, user friendliness, …) (30)

The announcements on this page may be updated depending on your questions and some new needs. So please check this page for a while ...