. Microsoft platform: the system is developed using Active Server Pages as the
Front end and SQL Server as the back end.
B. Unix-based platform: HTML or even Shell scripting, C programming, any
Relational database (e.g. Postgress or Oracle or even flat files), and tools in
UNIX
The following steps will be helpful to start off the project.

Section of this document
Decide on a Time table policy and other related aspects.
Make a database of people whosoever login. Decide on the various details of the people that would be stored in the database (like name, age group, address, location, system-login, password in cryptic form, etc).
Create the front-page of the Time table system giving

Create the help-pages of the system in the form of Q&A. This will help you also w n implementing the system.
Create other sub-systems like automatic notification, screens for various functions (like selecting a course, cancelling the selection etc)

Requirements Specification
Complete specification of the system (with appropriate assumptions) including the framing of timetable policy etc constitutes this milestone. A document detailing the same should be written and a presentation on that be made.
2-3
Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Technology familiarization
Understanding of the technology needed to implement the project.
4-5
The presentation should be from the point of view of being able to apply it to the project, rather than from a the theoretical perspective.

Database creation
A database should be created. As per the rules taken for the purpose of maintenance of the records.
5-7
It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.

5
Implementation of the front-end of the system
Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options (course-selection form, courses-listing form etc).
10-12
During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and w n new scenarios come to mind.