Projects

Development of a feature-rich, practical online on-request courses coordination system (ORS)

 

Title of the project

 

Development of a feature-rich, practical online on-request courses coordination system (ORS)

 

Abstract of the project

 

This project is aimed at developing an online on-request courses coordination system that is of importance to an IT organization which has a training department of its own. The online on-request courses coordination system (ORS) is an Intranet based application that can be accessed throughout the organization or a specified group/Dept. This system can be used to automate the workflow of the requests that come from various departments for project specific trainings and their approvals. The training department has to cater to the training of the fresh recruits. It has a regular calendar and schedule to train the Freshers. In addition to this it has to handle the project specific training requests coming from various departments. For this the department has appointed one person as the on-request coordinator, who will be able to service the requests with help of ORS. The whole process starting from logging the request by a dept to servicing the request is automated. There are features like logging the request, to check the existing training calendar and checking the availability of respective faculties for the course, allocating the faculty for the course, if an internal faculty is not free during that period getting faculties from outside, report generators etc in this system.

 

Keywords

 

Generic Technology keywords

 

Databases, Network and middleware, Programming

 

Specific Technology keywords

 

MS-SQL server, Visual basic 6.0

 

Project type keywords

 

Analysis, Design, Implementation, Testing, User Interface

 

Functional components of the project

 

Following is a list of functionalities of the system. More functionalities that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed.

 

An IT organization has a training department of its own. The main job of the training department is to train the fresh recruits. It has a regular calendar and schedule to train the Freshers. In addition to this it has to handle the project specific training requests coming from various departments in the organization. To handle the on-request courses the department has appointed one person as the on-request coordinator, who takes care of servicing the requests.  He/she has to collect the requests from various departments. Then he/she will check in the existing fresher training calendar whether a similar course is scheduled there in the given dates. If not he/she has to schedule it looking at the availability of faculties. If none of the internal faculties are free at that time, then he/she has to take the approval of the concerned department to get a faculty from outside.

 

  1. A person from any department should be able to

 

  • login to the system through the first page of the application using the guest login

 

  • Enter the details of the course required in the form available. This form also captures the details like, name of the course, number of days, number participants, and background of the participants, dates on which the course needs to be conducted, mail id and name of the requestor. In addition, this form also takes a confirmation from the department whether it is ready to go for external faculties if none of the internal faculties are free. If a department accepts this then it has bear the cost to be paid to the external faculty.

 

  • If any fresher level course with the same course contents is scheduled during the same time he/she will be shown with details of those courses

 

  • He/She can opt to send his team for this course or if his/her request is very specific then he/she can submit his/her request.

 

  • Withdraw his/her course request (which has not been serviced yet)

 

  • Cancel his/her course request (which has been already been planned).

 

  • Get help about the system on how to use the different features of the system

 

  1. As soon as a course request /withdrawal /cancellation is made by the person, an automatic email should be sent to the on-request coordinator giving details about the course request

 

  1. The on-request coordinator has to log on to ORS using the admin id and check the list of courses which are to be serviced. Then he/she has to check the availability of faculties who can handle the specific course during the requested period. If a faculty is free during the period then he/she can be allocated to the course and a mail is sent to the faculty as well as the requestor regarding the course schedule. The status of the course is now set to “planned”. Once course is delivered to the required dept then the status is set to “serviced”
  2. If none of the faculties are free during the period and if the department is willing, then the on-request coordinator can go ahead and arrange for external faculty.

 

  1. A list of all the external faculties(Vendors) is available in the database, along with their contact details, courses offered previously , the feedback got  etc., the on-request coordinator can refer to this list and schedule the course after getting in touch with the vendor.

 

Steps to start-off the project

 

The system is developed using Visual Basic as the front end and SQL Server as the back end.

 

The following steps will be helpful to start off the project.

 

  1. Study and be comfortable with technologies such as
    1. Visual Basic and SQL server.

 

            Some links to these technologies are given in the ‘Guidelines and References’ 

            Section of this document

 

  1. Make a database of course, faculties and the courses they can handle. Also maintain the latest schedule for fresher training in the database. In addition the details of the vendors also needs to be maintained in the database

 

  1. Have two logins to the system, the admin and guest. The admin login is used only by the on-request coordinator. Guest login is used by all the people in the organization to log the requests to ORS

 

  1. Create the front-page of the ORS  giving a brief description about the system and a login box

 

  1. Create the help-pages of the system in the form of Q&A. This will help you also when implementing the system

 

  1. Create other sub-systems like automatic notification, screens for various functions (like logging the request, to check the existing training calendar and checking the availability of respective faculties for the course, allocating the faculty for the course, if an internal faculty is not free during that period getting faculties from outside, report generators etc)

 

Requirements

 

Hardware requirements

 

Number

Description

Alternatives (If available)

1

PC with 2 GB hard-disk and 256 MB RAM

Not-Applicable

2

 

 

 

Software requirements

 

Number

Description

Alternatives (If available)

1

Windows 95/98/XP with MS-office

Not Applicable

2

MS-SQL server

MS-Access

3

Visual Studio

Not Applicable

 

 

Manpower requirements

 

2 to 3 students can complete this in 4 – 5 months if they work fulltime on it.

 

Milestones and Timelines

 

Number

Milestone Name

Milestone Description

 

 

Timeline

 

Week no. 

from the start

of the project

Remarks

 

 

1

Requirements Specification

Complete specification of the system (with appropriate assumptions).

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 functionalities other than those that are listed in this document.

2

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 theoretical perspective.

3

Database creation

Make a database of courses, faculties and the courses they can handle. Also maintain the latest schedule for fresher training in the database. In addition the details of the vendors also needs to be maintained in the database

 

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.

4

High-level and Detailed  Design

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario.

7-9

The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).

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 request form, list of courses scheduled 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 when new scenarios come to mind.

6

Integrating the front-end with the database

The front-end developed in the earlier milestone will now be able to update the database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing.

12-13

 

7

Integration Testing

The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).

14-15

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

8

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

16-18

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)

 

Guidelines and References

 

 http://www.programmingtutorials.com/vb6.aspx(VB 6.0 tutorial)

 

http://www.functionx.com/sqlserver/(SQL-server tutorial)



Tags :
0
Your rating: None