Projects

Development of a feature-rich, practical Online Survey Tool (OST)

 

Title of the project

 

Development of a feature-rich, practical Online Survey Tool (OST)

 

Abstract of the project

 

This project is aimed at developing an online Survey Tool that is of importance to either an organisation or a college . The Online Survey Tool System (OST) is an Intranet based application that can be accessed throughout the organisation or a specified group/Dept. This system can be used to launch surveys (such as Hostel Feedback, Library Usage ) and record user responses. The surveys responses report is to be automated. There are features like email notifications of surveys, publishing of survey results, report generators etc in this system.

 

Keywords

 

Generic Technlogy keywords

 

Databases, Open Source PHP Survey Tool, Programming

 

Specific Technology keywords

 

MS-SQL server, HTML, PHP , ASP

 

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 a functionality is not adequate, you can make appropriate assumptions and proceed.

 

All the employee/requestor of the organisation are legally the users of the OST System. Some of the users are admins and are approvers for launching a survey and publishing results. An approver can also be a requestor. In an organization, Surveys could be at the Organization level, Department level, Project/Individual level  etc. For each of these, there has to be a provision where the  end-users name or roll-no/emp-no. may or may not have to be captured. The approvers would be HRs , Dept HRs respectively, The approver is only a role, It could be granted to anybody.

 

  1. A person should be able to

 

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

 

  • change the user  details after logging into the system

 

  • see the list of surveys for the Org/Dept respectively.

 

  • see the results of survey, which he is supposed to see

 

  • see the list of surveys history he/she has launched.

 

  • create and submit a survey to the approver for launching

 

  • user can withdraw his/her survey application (which has not been approved yet)

 

  • cancel his/her survey (which has been already approved). This will need to be approved by his/her Superior

 

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

 

  1. As soon as a survey request in application /cancellation request /withdrawal /approval /rejection / is made by the person, an automatic email should be sent to the person and the approver giving details about the action

 

  1. The number of days for a survey to be open can be set and e-mail notification regarding the same be sent to the target audience automatically.

 

  1. A summary report of the survey results can be generated (eg in excel or word, or text)

 

  1. Surveys will have any no of questions.

 

  1. Answers to each of the question can be in a radio button or a checkbox but not both.

 

  1. A calender giving the surveys of the organization/college should be available on the system

 

Steps to start-off the project

 

There are couple of alternatives to implement such a system.

 

A.     Microsoft platform: The system is developed using Active Server Pages /PHP

as the front end and SQL Server as the back end.

 

B.     Unix-based platform: HTML/PHP and  Mysql or Postgress database

 

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

 

  1. Study and be comfortable with technologies such as
    1. Active Server Pages/HTML/PHP and SQL server.
    2. Unix commands, Shell programming, C Programming, Tools like AWK etc.

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

            section of this document

 

  1. PHP Survey Tool is open source project. It can be downloaded for free.

Same project can be used to customise.And meet the requirements.

Please read through the licensing terms.

 

  1. Make a database of people at different levels with their roles and form a hirearchy of them, like which role reports to which particular role. Decide on the various details of the people and their roles that would be stored in the database (like employee/registeration-number, name, grade, location, system-login, password in cryptic form, etc)

 

  1. Assign a mail-admin who will create mail-ids for the people in the intranet. These mail-ids will be used for sending automatic notifications and reports. The mail-admin will also take care of assigning the logins to the users of the OST system

 

  1. Since the real-time project needs to be tested in real-time, you can take ‘hours’ as ‘days’ for testing the system. However, the display will still be in ‘days’ only.

 

  1. Create the front-page of the OST system 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 apply,reject,cancel,withdraw etc)

 

9.    Maintain a administration section for the System.

 

Requirements

 

Hardware requirements

 

Number

Description

Alternatives (If available)

1

PC with 2 GB hard-disk and 256 MB RAM

Not-Applicable

 

 

 

 

Software requirements

 

Number

Description

Alternatives (If available)

1

Windows 95/98/XP with MS-office

Not Applicable

2

MS-SQL server

MySql

3

Linux

Not Applicable

4

Oracle database system

POSTgres

 

Manpower requirements

 

2 to 3 students can complete this in 4 – 6 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) including the framing of Surveys and questions corresponding etc constitutes this milestone. A document detailing the same should be written and a presentation on that be made.

2

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

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

A database of atleast 100 entries of employees of all grades should be created. The number of mail-ids to be created need not be 100. It can be around 10 to 20.

6

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 (like survey, approval, rejection, cancellation, automatic credit etc) and then coming up with flow-charts or pseudocode to handle the scenario.

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 (application form, cancellation form, reports page etc).

13

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 employee leave database. Other features like mail notification etc should be functional at this stage. In short, the system should be ready for integration testing.

15

 

7

Integration Testing

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

16

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.

17

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://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnasp/html/asptutorial.asp (ASP tutorial)

 

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

 

http://heather.cs.ucdavis.edu/~matloff/UnixAndC/Unix/CShellII.html (Shell script introduction)

 

http://www.sourceforge.net



Tags :
3
Your rating: None Average: 3 (2 votes)