APTITUDE EXAMINER

SUBMITTED BY
Umera Pawar
Seat no :
Uzaira Sayyed
Seat no :

2010-2011
Under the guidance of Mrs. Anupama Bali

Submitted in partial fulfillment of the requirements for qualifying
B.Sc. (I.T.), Semester – VI Examination

Vivek College of Commerce
Vivek College Road, Siddharth Nagar,
Goregaon (West), MUMBAI - 400 062.

ACKNOWLEDGEMENT

Acknowledgement We would like to take this opportunity to express our deep regards towards all those who offered valuable guidelines in our hour of need.
We like to express our gratitude to, The Management of Vivek College of Commerce for its valuable co-operation and our respected Principle, Dr.Nandita Roy, for her continuous support and guidance which helped us to keep our focus and achieve excellence in our endeavor. We are greatly thankful to Vivek College Library for providing us with the required books and articles. Our sincere thanks to the librarian Mrs. Bindu Varma for being supportive and co-operative. We would also like to acknowledge the valuable support extended by Prof. Anupama Bali ( Head Of Department ), Prof. Aparna Padte, Prof. Maria Muthukumar, Prof. Mohnish Dukhande, Prof. Murugesh Chandran for their valuable suggestion rendered throughout the course of project. We would also like to take this opportunity to express our sincere gratitudeto Ms. Sayyed Humera our project guide for bestowing belief in our talent and providing us opportunity to partner in designing APTITUDE EXAMINER. We thank her for her valuable and timely guidance. Finally we would like to thank all those who were directly or indirectly associated with our project. Umera Pawar Uzaira Sayyed

Index

Index

Sr.no Contents Pg no 1. Synopsis of the Project ………………………………………………..6 2. Objectives of the project ………………………………………………8 3. Scope of the Project …………………………………………………..11 4. System study and analysis …………………………………………...14 * Problem Definitions ……………………………………………….15 * Feasibility Study …………………………………………………...17 * Existing System …………………………………………………….21 * Proposed System ………………………………………………….23 5. System Design …………………………………………………………..25 * Gantt Chart ………………………………………………………... 26 * E-R Diagram ………………………………………………………..28 * Data Flow Diagram ………………………………………………..30 * Use Case Diagram ………………………………………………...37 * Activity Diagram ……………………………………………………39 6. Database schema ………………………………………………………..42 7. Data dictionary …………………………………………………………...44 8. System Requirements …………………………………………………...49 9. Testing 10. Features of the S/W being Used for Development of the Project 11. Validations 12. Source code 13. Cost And Benefit Analysis 14. Refrences

Synopsis

Synopsis
The project is aimed at developing an Aptitude Testing System named 'APTITUDE EXAMINER'. The proposed system can be used to schedule, generate and conduct an examination for the desired candidate and view their performance. The Features of the Examiner System are as follows * Dynamic generation of question for the test. * Result generated as soon as the test is ended. * Reports generated that shows the marks obtained by the candidate and also how much he/she have performed in each sub category. * Reports can also be generated for each candidate and his/her test detail

OBJECTIVE OF THE PROJECT

OBJECTIVE OF THE PROJECT
The objective of this innovative system based software named 'Aptitude Examiner' is to provide the administrator of the organisation with a system that helps in maintaining the Examination details of the candidates
The major objectives of the Examination System 'Aptitude Examiner' are as follows * AUTOMATE THE MANUAL PROCEDURE OF STORING INFORMATION
The proposed system allows us to store the information thus decreasing the amount of time, human resources required to do the paper work. The system easily allows us to maintain the following details: * Slots Booked * Scheduled Tests. * Generated Tests. * Candidate Details * Test Details

* PRESENT THE DETAILS IN AN ORGANIZED WAYS * PRESENT AN OVERALL REPORT OF THE CANDIDATE
The report includes all the details of a particular candidate including * Tests attempted by the candidate.
When Using 'Aptitude Examiner', the administrator can view any information regarding Candidates in an efficient way. This information may include * Scheduled tests * Generated tests * Results * Feedbacks

* the test have been attempted. * Result of the test attempted. * Marks scored by the candidate.

* USER FRIENDLY SYSTEM
The 'Aptitude Examiner' system is completely PC based, providing the ultimate user friendly solution to the administrator. This system can be used by all the persons having the basic knowledge of computers. * FAST RETRIEVAL OF RECORDS

The system enables fast retrieval of records pertaining to any query. This reduces the overheads of pulling the records from pillars of files.

* REDUCED OVERHEADS, SAVED TIME All the processes of maintaining details, generating reports are automated. This will reduce the overhead of maintaining details and generating report. This will dramatically reduce the time involved in the processes.

SCOPE OF THE PROJECT

SCOPE OF THE PROJECT
The scope of the this Examination System named 'Aptitude Examiner' is to automate all process involving maintaining data, managing slots, scheduling tests, generating tests, generating reports, giving feedbacks etc
The proposed system can be used by any organization that are into the activities of training people in any field and want to know their status. The system helps us in all the below processes * The system is designed to store the candidate and test details.

* The system basically automates the manual process of booking slots, scheduling tests, generating tests and giving feedbacks

* The system aims at reducing time and effort where ever possible

* The administrator is expected to provide the basic inputs to the system based on which the system is designed to perform various operations.

* The administrator of the system is expected to have some basic knowledge of the computer operations.

* The system is designed to be simple and easy to use.

* The system provides a security feature such as Access Codes & Passwords which helps in protecting the system & the stored data from unauthorized access.

* The Access Codes and Passwords are only known to the administrator of the system. The system also permits the administrator of the system to change the password and Access Codes

* The flexible reports generated by the system helps the organization to know the current status of a particular candidate.

SYSTEM STUDY AND ANALYSIS

DEFINITION OF THE PROBLEM

DEFINITION OF THE PROBLEM
In this technology driven world of today's,the computer has become the part of business. It is no longer related to data processing and other mundane tasks .As we enter 21st century the organization and its committees are breaking old barrier and entering new realm. The proposed system as conceived using this idea in mind
The proposed system addresses the problem maintaining the details of the candidate, tests taken by them, results of the test attempted and marks scored.
It also address the problem of keeping track of slots booked, tests scheduled and tests generated.
However the current system for maintaining all the details is manual. Following are the problems associated with the current system * Maintaining details of the Candidates, Tests etc.
All details are stored in some form of document even the candidate details and their attempted test details. Due to such a procedure all process has to be done manually. * Organizing the data
All the stored paperwork has to be organized in certain ways. All these processes have to be done manually. This may lead to wastage of time and also doing such a process is not easy.

FEASIBILITY STUDY

FEASIBILITY STUDY
The feasibility study plays an important role in the analysis of the system. The very decision of the system analyst, to design a particular system depends whether the system is feasible or not. Hence the feasibility study forms the very basis of the system. The Feasibility Study can be categorized as * Technical Feasibility. * Operational Feasibility. * Economic Feasibility.

* Economic Feasibility
The economic feasibility of the system is mainly concerned with its financial aspects. It determines whether the investment that goes into the implementation of the project is recoverable or not. The cost benefit analysis is a commonly used method in evaluating the effectiveness of the system.
The economic feasibility of the proposed system lies in the fact that it aims to be economical in terms of both cost and time. It automates most of the data storage and retrieval process thereby saving time and effort. Retrieving any data or reports is efficient and fast and the ability to print them provides a faster and organized way of presenting them.
The cost of developing this system currently includes the minimum hardware costs and the cost of software and plug-in needed to develop and run the system. The software costs include their licensing and other miscellaneous costs. * Operational Feasibility
The operational feasibility of the system lies in the fact that it is friendly, easy to use and has a simple user interface. The system promises to be quite user friendly by providing a simple system which requires no prior training for handling or using the system.
The system is easy to use and has no functions which require the user to provide any special system commands or write any code for accessing data or perform any function
The system has a simple user interface which provides one click access to almost all the functions. * Technical Feasibility
The technical feasibility of the software determines the software and hardware required for developing the system. The front end of the system is designed in VISUAL STUDIO 2005 which provides simple drag and drop controls that can be defined and used throughout the development of the system and the back end here is MICROSOFT ACCESS which provides comprehensive database facilities and supports the SQL standard.
The system is designed to run on standard or minimum system requirements and hence can work on standard desktops used in homes. It does not require any special software or plug-in to be installed. Installing and using the system is quite feasible.

EXISTING SYSTEM

EXISTING SYSTEM * The system is not an automated system. The current system is done manually where all the information is kept track of by an individual or a group of individual.

* There is a lot of paper work which consist of all the information about candidate, test detail, reports etc are all stored in different set files.

* All activities are done manually right from maintaining candidate and test details to booking slots scheduling tests, generating paper, checking paper and also giving results and feedbacks.

* The manual system lacks organization unless the user has been really careful about keeping track of all records.

* Also the system was not easy enough to keep track of each and every minute details

* Hence storing, maintaining and searching all records of candidate and their test details is a tedious job and results in wastage of time. There are also chances of losing the details, and error, might generate in calculating result of the test.

PROPOSED SYSTEM

PROPOSED SYSTEM
The proposed system is used to automate the process of maintaining all records including candidate, test details, booking slots scheduling tests, generating paper, checking paper and also giving results and feedbacks. * The functional requirements are

* The system should allow its administrator to add, view, edit and delete the information of the candidates and tests.

* The system should allow the administrator to book slots.

* The system should allow the administrator to schedule tests student wise and also batch wise based on slots booked.

* The system should allow the administrator to generate tests student wise and also batch wise based on scheduled tests.

* The system should allow administrator to import candidate details, test details and even question for a particular test from a *.CSV file or even a *.MDB file.

* The system should allow administrator to take backups of the database.

* The system should allow administrator to change database location and also passwords and access codes.

* The system should also generate reports and feedbacks.

SYSTEM DESIGN

GANTT CHART

E-R Diagram

E-R Diagram

DATA FLOW DIAGRAM

0 LEVEL DFD

0 LEVEL DFD

LEVEL 1 DFD

LEVEL 1 DFD

LEVEL 2 DFD

LEVEL 2 DFD

USE CASE DIAGRAM

USE CASE DIAGRAM

ACTIVITY DIAGRAM

Test Administrator

Test Engine

DATABASE SCHEMA

DATABASE SCHEMA

DATA DICTIONARY

Table Name: CandidateDetails
Description: Used to store Candidate Details FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | RegNo. | Text | Primary Key | - | Not Allowed | Candidate Name | Text | | - | Not Allowed | Batch | Text | | - | Not Allowed | Deleted | Text | | N | Not Allowed |

Table Name: Tests
Description: Used to store Test Details FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | TestName | Text | | - | Not Allowed | TimeLimit | Number | | - | Not Allowed | NumberOfQuestion | Number | | - | Not Allowed | Deleted | Text | | N | Not Allowed | Table Name: Slots
Description: Used to store Slot Details FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | SlotDate | Date/Time | | - | Not Allowed | SlotTime | Text | | - | Not Allowed | TotalSeats | Number | | - | Not Allowed | SeatsBooked | Number | | 0 | Not Allowed |

Table Name: ScheduledTests
Description: Used to store All Scheduled Test Details FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | RegNo | Text | Foreign Key | - | Not Allowed | TestID | Number | Foreign Key | - | Not Allowed | SlotID | Number | Foreign Key | - | Not Allowed | Status | Text | - | Scheduled | Not Allowed |

Table Name: TestReports
Description: Used to store Reports of the Test. FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | ScheduleID | Number | Foreign Key | - | Not Allowed | Marks | Number | - | - | Not Allowed | CorrectAns | Number | - | - | Not Allowed | WrongAns | Text | - | - | Not Allowed | Total | Number | - | - | Not Allowed |

Table Name:TestQuestions
Description: Used to store Question that will appear in Exam. FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | ScheduleID | Number | Foreign Key | - | Not Allowed | QuestionID | Number | Foreign Key | - | Not Allowed |

Table Name: ExamDetails
Description: Used to store Exam Details of the Test. FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | QuestionID | Number | Foreign Key | - | Not Allowed | ScheduleID | Number | - | - | Not Allowed | QuestionID | Number | - | - | Not Allowed | AnswerID | Number | - | - | Not Allowed | Attempted | Yes/No | - | No | Not Allowed | Bookmarked | Yes/No | - | No | Not Allowed |

Table Name: Questions
Description:Used to store Question Details of the Test FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | ID | Auto Number | Primary Key | - | Not Allowed | TestID | Number | Foreign Key | - | Not Allowed | Question | Memo | - | - | Not Allowed | Option1 | Memo | - | - | Not Allowed | Option2 | Memo | - | - | Not Allowed | Option3 | Memo | - | - | Not Allowed | Option4 | Memo | - | - | Not Allowed | CorrectAns | Number | - | - | Not Allowed | Deleted | Text | | N | Not Allowed |

Table Name: Access Codes
Description: Used to store Access Codes of the Administrator FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | Access_Code | Text | - | - | Not Allowed |

Table Name:Passwords
Description: Used to store Password Details . FIELD | DATATYPE | CONSTRAINT | DEFAULT | NULL VALUE | Passwords | Text | - | - | Not Allowed |

SYSTEM REQUIREMENTS

Hardware Requirements:

* Minimum Configuration

* Celeron or Pentium, 500 MHz

* 128MB RAM

* 500MB of free disk space after installation of all the required software.

* 800x600, "16-bit High Color" screen

* Any compatible Printer for printing.

* Recommended Configuration

* Pentium 3 or greater, 2.0GHz+ or AMD 2400xp+

* 512M RAM

* 2 GB of free disk space after installation of all the required software.

* 1280x1024, "32-bit True Color" screen

* Any Compatible Laser or Ink Jet printer.

Software Requirements: * Minimum Requirements

* Windows 98.

* .Net Framework 2.0

* MS Access * Recommended Requirements

* Windows XP.

* .Net Framework 2.0

* MS Office

Features of the S/W being Used for Development of the Project

MICROSOFT VISUAL STUDIO 2005
Microsoft Visual Studio is the main Integrated Development Environment (IDE) from Microsoft. It can be used to develop console and GUI applications along with Windows Forms applications, web sites, web applications, and web services in both native code as well as managed code for all platforms supported by Microsoft Windows, Windows Mobile, .NET Framework, .NET Compact Framework and Microsoft Silver light.
Microsoft .NET Framework - CLR 2.0
Version 2.0, the .NET Framework has extended the capabilities of developers by introducing significant enhancements across each of its functional areas. This release will give developers more efficient access to frequently used components such as printers, file system, and registry.
Features of Visual Studio 2005 * Refactoring
Making changes to your code like, "pulling a large stretch of inline code into its own method" or "converting a field to be a property." The Refactoring support makes this easy to do. * Edit and Continue
Visual Basic has always been about Rapid Application Development (RAD). One key feature is the ability to fix runtime errors on the fly. If you run into an exception at runtime, you get an exception helper that provides tips for fixing common errors, but more importantly, you can edit the code, select F5, and it continues right where you left off. Edit and Continue is VB .NET only feature. * Click once Click Once make it easy to install applications and provide ongoing updates (Self-Updating), rather than forcing to distribute new versions of application, can just deploy the portion of the application which has changed.

* Smart Tags

This provides access to information and common tasks without forcing you to constantly navigate away from your work area * Code Snippets
With code snippets, you can insert generic "template" code that requires only that you fill in the blanks.
MICROSOFT MS ACCESS 2007
Advantages of using MS-Access as database are as follows * Relational database management :
A relational database management system uses only its relational capabilities to manage the information stored in its database. * Information Representation
All information stored in a RDBMS is represented only by data item values, which are stored in the tables that make up the database. * Logical accessibility
Every data item value stared in a relational database is accessible by stating the name of the table stored in, the name of the column under which it is stored and the value of the primary key that defines the row in which it is stored. * Representation of null values
The database management system has a consistent method for representing null values. For Example, null values for the numeric value and for the character data it must be different from a string of blanks or any other character values. * Catalog facility
The logical description of the relational database management system is represented in the same manner as ordinary data. * Data language:
A relational database management system may support many types of languages for description data and accessing the database. However, there must be at least one language that uses ordinary character strings to support the definition of data, definition of views, manipulation of data etc. * View updating:
Any view that can be defined using combination of base tables that are theoretically updateable is capable of being updated by RDMS. * Insert update delete:
Any operand that describes, the results of a single retrieval operation is capable of being applied to an insert, update or delete operation as well. * Physical data independence:
Changes made to physical storage representation or access methods do not require change to be made to application programs. * Logical data independence:
Changes made to the table's, that do not modify any stored in that tables, do not require change to be a made to application program. * Integrity constraints:
Constraints that apply to entity integrity and referential integrity are specifiable by the data language implemented by the database management system and not by the statement coded in the application program. * Database distribution:
The data language implement by the relational database management system supports the ability to distribute the database without requiring changes to the application program. * Not subversion:
If the relational database management support facilities that allow application program to operate on the table's row at a time, an application program using this type of database access is prevented from bypassing entity integrity or referential integrity.

TESTING

Unit testing
In this kind of testing each unit is checked for its proper functionality. Till the functionality of the code is achieved it is modified, rewritten and tested. Here we check for the conditions, loops and the error in the each unit of code then the errors are noted and rectified until the objective of the code is fulfilled. Code is subject to extreme values in the loop: the conditions for either side are tested for. It also includes checking for the user interfaces .Which implies the user friendliness of the system us also looked for in unit testing. Only once a particular code has cleared this testing is being appended/included to the system code. Then the next code is tested for with this testing methodology. Black Box Testing In black box testing the software is tested by the user of the system or someone who is not related to development of software. In this kind of testing the system developed is subject to various kinds of input data generated randomly by the user. The user also gets to check for the extreme values of the system. This kind of testing is done to check whether the system can give accurate response to all kinds of queries and mistakes done by the user while using the system. This kind of testing is usually done at the user end. All the errors generated during the testing are noted and documented. These errors are later rectified before being finally implemented at the user end. Generally the errors that remain at the end of this testing are often very less and can be neglected. The error so generalized is called residual errors. White Box Testing The white box testing is carried out at the developers end. The system is subject to various kinds of input data and the extreme conditions are checked for. In this testing the entire system is thoroughly checked and tested. All the loops, condition and error statement are checked for. All the methods are tested for their functionality and scope. The faults in the system are documented at the end of testing and then are rectified.

Validations

SOURCE CODE
Parent Form
Imports System.Windows.Forms

Public Class MDIParent1 Private Sub CascadeToolStripMenuItem_Click(ByVal sender As Object, ByVal e As EventArgs) Handles CascadeToolStripMenuItem.Click Me.LayoutMdi(MdiLayout.Cascade) End Sub

Private Sub TileVerticleToolStripMenuItem_Click(ByVal sender As Object, ByVal e As EventArgs) Handles TileVerticalToolStripMenuItem.Click Me.LayoutMdi(MdiLayout.TileVertical) End Sub

Private Sub TileHorizontalToolStripMenuItem_Click(ByVal sender As Object, ByVal e As EventArgs) Handles TileHorizontalToolStripMenuItem.Click Me.LayoutMdi(MdiLayout.TileHorizontal) End Sub

Private Sub ArrangeIconsToolStripMenuItem_Click(ByVal sender As Object, ByVal e As EventArgs) Handles ArrangeIconsToolStripMenuItem.Click Me.LayoutMdi(MdiLayout.ArrangeIcons) End Sub

Private Sub CloseAllToolStripMenuItem_Click(ByVal sender As Object, ByVal e As EventArgs) Handles CloseAllToolStripMenuItem.Click ' Close all child forms of the parent. For Each ChildForm As Form In Me.MdiChildren ChildForm.Close() Next End Sub

Private m_ChildFormNumber As Integer = 0 Private Sub TestToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TestToolStripMenuItem1.Click If (TestToolStripMenuItem1.Checked = False) Then ImportTest.MdiParent = Me ImportTest.StartPosition = FormStartPosition.CenterScreen ImportTest.Label1.Text = "Select Associated Access File or a CSV File for Importing" ImportTest.Show() TestToolStripMenuItem1.Checked = True Else ImportTest.Activate() End If End Sub

Private Sub CandidateToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CandidateToolStripMenuItem.Click If (CandidateToolStripMenuItem.Checked = False) Then Candidate.MdiParent = Me Candidate.StartPosition = FormStartPosition.CenterScreen Candidate.Show() CandidateToolStripMenuItem.Checked = True Else Candidate.Activate() End If End Sub Private Sub TestToolStripMenuItem2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TestToolStripMenuItem2.Click If (TestToolStripMenuItem2.Checked = False) Then Test.MdiParent = Me Test.StartPosition = FormStartPosition.CenterScreen Test.Show() TestToolStripMenuItem2.Checked = True Else Test.Activate() End If End Sub Private Sub AboutTestAdministratorToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles AboutToolStripMenuItem.Click If (AboutToolStripMenuItem.Checked = False) Then AboutBox1.MdiParent = Me AboutBox1.StartPosition = FormStartPosition.CenterScreen AboutBox1.Show() AboutToolStripMenuItem.Checked = True Else AboutBox1.Activate() End If End Sub Private Sub ExitToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ExitToolStripMenuItem.Click End End Sub Private Sub LockToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles LockToolStripMenuItem.Click Dim obj As New LockScreen obj.StartPosition = FormStartPosition.CenterScreen obj.ShowDialog() End Sub

Private Sub StudentDetailsToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles StudentDetailsToolStripMenuItem1.Click If (StudentDetailsToolStripMenuItem1.Checked = False) Then ImportCandidate.MdiParent = Me ImportCandidate.Label1.Text = "Select Associated Access File or a CSV File for Importing" ImportCandidate.StartPosition = FormStartPosition.CenterScreen ImportCandidate.Show() StudentDetailsToolStripMenuItem1.Checked = True Else ImportCandidate.Activate() End If End Sub

Private Sub QuestionsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles QuestionsToolStripMenuItem.Click If (QuestionsToolStripMenuItem.Checked = False) Then ImportQuestion.MdiParent = Me ImportQuestion.StartPosition = FormStartPosition.CenterScreen ImportQuestion.Label1.Text = "Select Associated Access File or a CSV File for Importing" ImportQuestion.Show() QuestionsToolStripMenuItem.Checked = True Else ImportQuestion.Activate() End If End Sub

Private Sub SlotManagementToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles SlotManagementToolStripMenuItem.Click If (SlotManagementToolStripMenuItem.Checked = False) Then SlotManagement.MdiParent = Me SlotManagement.StartPosition = FormStartPosition.CenterScreen SlotManagement.Show() SlotManagementToolStripMenuItem.Checked = True Else SlotManagement.Activate() End If End Sub Private Sub schBatchWiseToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles schBatchWiseToolStripMenuItem.Click If (schBatchWiseToolStripMenuItem.Checked = False) Then SchdTest_Batch.MdiParent = Me SchdTest_Batch.StartPosition = FormStartPosition.CenterScreen SchdTest_Batch.Show() schBatchWiseToolStripMenuItem.Checked = True Else SchdTest_Batch.Activate() End If End Sub

Private Sub schCandidateWiseToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles schCandidateWiseToolStripMenuItem.Click If (schCandidateWiseToolStripMenuItem.Checked = False) Then SchdTest_Candidate.MdiParent = Me SchdTest_Candidate.StartPosition = FormStartPosition.CenterScreen SchdTest_Candidate.Show() schCandidateWiseToolStripMenuItem.Checked = True Else SchdTest_Candidate.Activate() End If End Sub Private Sub genBatchWiseToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles genBatchWiseToolStripMenuItem1.Click If (genBatchWiseToolStripMenuItem1.Checked = False) Then GenTest_Batch.MdiParent = Me GenTest_Batch.StartPosition = FormStartPosition.CenterScreen GenTest_Batch.Show() genBatchWiseToolStripMenuItem1.Checked = True Else GenTest_Batch.Activate() End If End Sub

Private Sub genCandidateWiseToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles genCandidateWiseToolStripMenuItem1.Click If (genCandidateWiseToolStripMenuItem1.Checked = False) Then GenTest_Candidate.MdiParent = Me GenTest_Candidate.StartPosition = FormStartPosition.CenterScreen GenTest_Candidate.Show() genCandidateWiseToolStripMenuItem1.Checked = True Else GenTest_Candidate.Activate() End If End Sub Private Sub MDIParent1_Disposed(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Disposed End End Sub Private Sub MDIParent1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load HelpProvider1.SetShowHelp(Me, True) HelpProvider1.HelpNamespace = "help.chm" End Sub Private Sub PrintFeedbackToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles PrintFeedbackToolStripMenuItem.Click If (PrintFeedbackToolStripMenuItem.Checked = False) Then frmCandidateFeedback.MdiParent = Me frmCandidateFeedback.StartPosition = FormStartPosition.CenterScreen frmCandidateFeedback.Show() PrintFeedbackToolStripMenuItem.Checked = True Else frmCandidateFeedback.Activate() End If End Sub

Private Sub StudentDetailToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles StudentDetailToolStripMenuItem.Click If (StudentDetailToolStripMenuItem.Checked = False) Then CandidatePerformance.MdiParent = Me CandidatePerformance.StartPosition = FormStartPosition.CenterScreen CandidatePerformance.Show() StudentDetailToolStripMenuItem.Checked = True Else CandidatePerformance.Activate() End If End Sub

Private Sub AccessCodeToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles AccessCodeToolStripMenuItem.Click If (AccessCodeToolStripMenuItem.Checked = False) Then frmChangeAccess.MdiParent = Me frmChangeAccess.StartPosition = FormStartPosition.CenterScreen frmChangeAccess.Show() AccessCodeToolStripMenuItem.Checked = True Else frmChangeAccess.Activate() End If End Sub

Private Sub PasswordToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles PasswordToolStripMenuItem.Click If (PasswordToolStripMenuItem.Checked = False) Then frmChangePassword.MdiParent = Me frmChangePassword.StartPosition = FormStartPosition.CenterScreen frmChangePassword.Show() PasswordToolStripMenuItem.Checked = True Else frmChangePassword.Activate() End If End Sub

Private Sub DatabaseLocationToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles DatabaseLocationToolStripMenuItem.Click If (DatabaseLocationToolStripMenuItem.Checked = False) Then Database.MdiParent = Me Database.StartPosition = FormStartPosition.CenterScreen Database.Show() DatabaseLocationToolStripMenuItem.Checked = True Else Database.Activate() End If End Sub

Private Sub LogsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles LogsToolStripMenuItem.Click If (LogsToolStripMenuItem.Checked = False) Then Logs.MdiParent = Me Logs.StartPosition = FormStartPosition.CenterScreen Logs.Show() LogsToolStripMenuItem.Checked = True Else Logs.Activate() End If End Sub

Private Sub TerminateTestToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TerminateTestToolStripMenuItem.Click If (TerminateTestToolStripMenuItem.Checked = False) Then TerminateTest.MdiParent = Me TerminateTest.StartPosition = FormStartPosition.CenterScreen TerminateTest.Show() TerminateTestToolStripMenuItem.Checked = True Else TerminateTest.Activate() End If End Sub

Private Sub RestartTestToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles RestartTestToolStripMenuItem.Click If (RestartTestToolStripMenuItem.Checked = False) Then RestartTest.MdiParent = Me RestartTest.StartPosition = FormStartPosition.CenterScreen RestartTest.Show() RestartTestToolStripMenuItem.Checked = True Else RestartTest.Activate() End If End Sub

Private Sub WindowsMenu_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles WindowsMenu.Click

End Sub
End Class

COST BENEFITS

COST BENEFIT AND ANALYSIS Cost benefit analysis involves the balance project expenditure and returns from simple implementations. It must be noted that any software implementations involves initial investments and benefits are usually long term. System implementations time may vary for different organizations, and may also take some time for the employees of the different organizations to get adjusted with the system. Thorough analysis of the system was undertaken by keeping in the cost benefit ratio, details of which are as follows: COSTS
The cost involved in the development of the system is categorized as under: * Hardware costs
The current System is considered to be manual system; hence the necessary hardware as specified earlier needs to be purchased. The exact cost depends on the size of the organization using the software and the task force, which will use the system. * Software costs
The major software requirement for the system is MS Windows XP or higher version of an O.S. The software costs can be estimated for MS Office and for VISUAL STUDIO 2005 is around 10,000. * Development Costs
The software's involved in the development are VISUAL STUDIO 2005 and MS-Office 2007. The only related costs are software license costs. Hence no major expenses were involved in developing the software.

Cost of Software
Management and end user time for discussions. * Testing and verification costs = Rs. 1000/-.

* Data Collection Costs = Rs. 1000/-

* Documentation Cost = Rs. 1000/-

* Total = Rs. 3000/- (a)
Developer Cost
(No. OF Days) * (Cost per Developer) * 2 = 60 * 50 *2 = Rs.6000(b)
Developing Cost a + b = 3000+ 6000 = Rs.9000/-

BENEFITS

Benefits can be categorized as * Tangible Benefits * Intangible Benefits

The tangible and intangible benefits provided by the software implementation with regard to different perspective are listed below: * Tangible Benefits
The tangible benefits of developing the system are * The profits generate by selling the system.

* Return of investments made in development of the system which includes the costs of the hardware & software used for developing the system.

* Increase in the revenue inflow of the organization due to the selling and implementing the system.
The tangible benefits of the system from the user's point of view : * Easy storage and retrieval of customer's and nominees details.

* Ability to provide various reports format.

* Backing up important details which can help in recovering data.

* Intangible Benefits
The intangible benefits of developing the system are. * Customer satisfaction.

* Reputation of the organization.

REFERENCES

* Bibliography

* VB.NET 2005

* VISUAL STUDIO 2005 MSDN

* Website Reference

* www.google.com

* www.microsoft.com

* www.wikipedia.org