Cyberspace and Society

home >> projects >> project schedule

CIS 4309 Project Schedule and Weights

Project Submission

At the end of each project are the following submission instructions: 

Send an e-mail message with your name and account (c4309ssuu) to the TA, James Joseph,  at james.joseph@temple.edu stating that you have finished the project.  He will send you a receipt. 

Each assignment has a deadline, shown in the Due Date column of the Project Schedule.    Submission policy is that an assignment turned in by the Due Date gets the full letter grade.  It can be turned in up to one week late but will be downgraded by 1 letter grade.  It will not be accepted after the Late Date. 

The project Setup instructions discuss the creation of a Table of Contents to your projects in the VS.NET IDE Structure.  You must add each lab project to this Table of Contents before submitting to the TA.  He can then run your project from the Table of Contents.  He can also examine your website directly for examination of your source files, if necessary.

Projects are graded on 3 major factors:

1.   Functional correctness and completeness

This will be graded by running your project. The TA will expect to run your project from the Table of Contents, so without it, your project cannot be graded.  The project statements will specify various functions to be performed.  All functions are to be correctly implemented.  You should thoroughly test your project before turning it in for all combinations of inputs, because a crash or an incorrect result for any input may cause significant loss of points for a particular functionality.  A crash at an entry point to the system may cause loss of all points, in the event that the project cannot be run at all.

2.   Code examination

Sometimes the project description will specify a particular method of  implementation or the way in which you code should be structured.  In this case, we will examine your code to determine that you have implemented it correctly.

3.   Design

Good design includes the following:
(1)  Maximizing the effectiveness of user inputs.  For example, if the user enter a product which already exists in a database, then the existing list of products should be displayed in a dropdown or dynamic table rather than requiring the user to enter a product name or number into a text box.  Furthermore, the product name rather than the number should probably be displayed, because it would be more recognizable to the user.

(2)  Good navigation among pages.  Requiring the user to use the Browser Back and Forward buttons is extremely poor design.  On each page, the user should have every logical page transfer option.

(3) Appropriate Client and Server side validation, with precedence being given to client side wherever possible.  Also, the correct data that a user has entered should be redisplayed, so that he/she does not have to enter it again.

(4)  Page design

• Pages should be attractive, though not gaudy or too tightly packed with information, which usually causes confusion.
• Page layout, labeling and instructions of what the user is to do should be clear. 
  
• Make use of the visibility attribute to cause various form controls to appear and disappear when redisplaying a page for different phases of a particular transaction.