Faculty Kit

[attachment=16408]

Evaluation Strategy/Tips for the different milestones of the project

Objective

These guidelines are meant for the assesor of the project to check the progress and health of the project. Given below are some tips for evaluation at each of the important milestones of the project. These are in addition to the evaluation process that you may have in assessing the project.

Requirements Specification

Some key points that need to be evaluated on the Requirements Specification document are:

1. Clarity of the specification document
2. Validity of the assumptions made
3. Understanding of the same by all the team-members
4. Quality of the presentation

Technology Familiarization

The evaluation of this milestone can be done through a presentation by the team on the technologies that are going to be used in implementing this project. This can be followed by a quiz on those topics to evaluate the team’s understanding.

Database Creation

A small write-up on the database, giving the fields, explaining each field etc should be written. This write-up can be evaluated on the following points.

1. Clarity and conciseness of the database design. Like, whether key is defined, whether any redundant fields are there etc.
2. Whether data-storage calculations are made, and if so, whether they are done properly etc.
3. Whether any data-backup/recovery mechanism is discussed or being thought of.


Front-end implementation

A demo of the front-end can be given by the team for evaluation. Features like mail notification, actual updation of the database etc come in the next stage. This stage is for the front-end only.

Evaluation can be based on parameters like,

1. The look-and-feel of the user interface, like whether there are too many boxes/links in one page, whether any sound-effects are there (for successful/unsuccessful logins, for example) etc
2. The quality of help available for the user, like whether the help instructions match the actual implementation, whether they are simple to understand etc
3. The intuitive-ness of the design, like whether you are able to use the application without spending too much time in reading help screens etc
4. Appropriate, meaningful and non-confusing error messages where applicable etc