Archive for the ‘COURSE-WORK’ Category

Peer Grades

December 27, 2011 Leave a comment

Peer grades are to be sent until January,6. The ones who do not send will loose grades. Keep in mind that the grades will be kept private. The grading range is between 0-10. Attach brief comments related to your gradings for your group members.


Project Grading Criteria

December 27, 2011 Leave a comment

In general, you will be graded according to your design(%35), analysis(%25) and implementation(%20). You can organize your project and demo by checking the criteria given in ProjectGradingCriteria form.



Project System Designs Report Content

November 20, 2011 Leave a comment

Internal Documentation is a means for communicating ideas between different parts of a development team, especially during the design phase as well as for proper maintenance of a software system. Considering the fact that people responsible for maintenance might not be the same people who have designed and implemented the software, it should be self-explanatory and complete.  This means just about anything used during analysis and design such as reasoning and rationale of key design decisions, design procedures (e.g. top-down decomposition of the system and specific architectural style used), and UML diagrams should be part of this document. Proper commenting of source code, of course, is an essential part of internal documentation.

Again there is no single way to organize such a report, a sample follows:

  1. Introduction
    1.1 Purpose of the system
    1.2 Design goals
    1.3 Definitions, acronyms, and abbreviations
    1.4 References
    1.5 Overview
  2. Software architecture
    2.1 Overview
    2.2 Subsystem decomposition
    2.3 Hardware/software mapping
    2.4 Persistent data management
    2.5 Access control and security
    2.6 Boundary conditions
  3. Subsystem services
  4. Glossary

You are required to use CASE tools and UML during all phases of software development.

Source: Description

Categories: PROJECT

How to Submit Project

October 23, 2011 Leave a comment
  1. Write “Bilkent CS 319- Project/HW- Your Name” to the subject of your e-mails.
    • eg.  Bilkent CS 319- Project – Burcu Dal
    • eg. Bilkent CS 319- HW1- Burcu Dal
  2. Your e-mails should include your signature that is your name, student ID and e-mail address.
  3. Send the project (as RAR or ZIP file) and the runnable version of the project (Executable JAR) to the instructor, the TA and the all group members.
  4. Submit the program as a sheet of paper printed on.(Do not print out the automatically generated code, just  your own parts)
  5. Final submission should include all your reports, source code, executable jar file and be named as “group name.rar” (eg. “3f.rar”).
Categories: SUBMISSION

Late Submisson Policy

October 23, 2011 Leave a comment

Marks are deducted for a late submission based on the following penalty marks formula:

  • Work submitted after deadline up to 1 day, 10 points out of 100
  • Work submitted after 1 day up to 2 days,  5 points out of 100
  • Work submitted after 2 days,  for each day 1 point
Instructor has the right to change these rules.
Categories: SUBMISSION