erp@@@@

1. INTRODUCTION Employees are the most valuable and dynamic assets of an organization. The Employee Information System is an extensive and comprehensive system that maintains and tracks information pertaining to all the employees in an organization. It captures comprehensive details pertaining to all the employees in the organization The proposed web application is supposed to record candidate’s performance at various levels during assessment. Once the candidate is registered for the required post according to his eligibility, his information is stored in the database and conduct test using PDF files, validate the test, generate result according the key, sort the applicants according to their result and display the status of the applicant whether selected or waiting or rejected. The four phases of online recruitment process are REGISTRATION: The applicant visits the site, looks for the available jobs. If any jobs are vacant, the applicant would apply for the post based on the eligibility criteria through the registration procedure provided in the website. GENERATE REGISTRATION ID: After the applicant registered successfully, the candidate is given with the date of online test and registration id which is generated by the combination of his date of birth, id proof number and some random numbers CONDUCTING ONLINE TEST: On the day of test, the applicant logs on to his account and take the test. The test consists of several psychometric, analytical and technical questions. SELECTION OF EMPLOYEES: After conducting examination for all the applied candidates, the applicants are sorted based on the results and names of the selected candidates and the status of the next top unselected candidates.

Various activities and steps involved in the procedure of recruiting the employees are as follows:

1.1 Efforts involved in recruiting the employees This module should let the Recruitment manager to record information about the recruitment efforts for a particular practice in the company. The recruitment effort involves recording of candidate’s resume, conducting assessment of candidate such as examination score, interview ratings etc.

1.2 Tracking the Database records of an employee The module should allow specifically to make tracking HR information such as personal data, test papers, results of the test, contact information, hiring checklists, and much more.

1.3 Storing the documents of registered employees The application should store certifications, Passport scan and relieving letters and more can be stored.

1.4 Activities involved in this process The following user access roles are required in the application: The Recruitment Manager is allowed to perform the following activities: ✔ Register Candidate: Add, Edit, Delete or List candidates. ✔ Interview: Add, Edit, Delete or list interview schedules. ✔ Result Management: Add, Edit, Delete or List results of interviews conducted with status ✔ Practice management: Create, Edit, Delete or List practices within the company (i.e. Various technologies expertise – Java/.Net/Testing) ✔ Evaluation Process: Add, Edit, Delete or List evaluation details of interviewed candidates.

1.5 Reports ✔ Interview schedules ✔ Search for a specific candidate’s interview result ✔ Search for interview result (i.e. conducted on a given date) ✔ Team-wise recruited persons ✔ Status of interviewed candidates ✔ Users list ✔ Login History ✔ Candidates who are registered, but not attended for interview ✔ Interview result ✔ Interview Schedules

1.6 Advantages: This project is completely secured and automated in order to make it easy for the users and the admin to access the information on a single mouse click. All information is stored in the database providing better user interface. Database can be entered only once and cannot be modified by providing more security to the information . Recruitment refers to the process of attracting, screening, and selecting qualified people for a job. For some components of the recruitment process, mid- and large-size organizations often retain professional recruiters or outsource some of the process to recruitment agencies. The recruitment industry has four main types of agencies: employment agencies, recruitment websites and job search engines, "headhunters" for executive and professional recruitment, and niche agencies which specialize in a particular area of staffing. Some organizations use employer branding strategy and in-house recruitment instead of agencies. Recruitment-related functions are generally carried out by an organization's human resources staff.

The stages in recruitment include sourcing candidates by advertising or other methods, screening potential candidates using tests and/or interviews, selecting candidates based on the results of the tests and/or interviews, and on-boarding to ensure the candidate is able to fulfill their new role effectively. The online software provided by those who specialize in online recruitment helps organizations attract, test, recruit, employ and retain quality staff with a minimal amount of administration. Online recruitment websites can be very helpful to find candidates that are very actively looking for work and post their resumes online, but they will not attract the "passive" candidates who might respond favorably to an opportunity that is presented to them through other means. Also, some candidates who are actively looking to change jobs are hesitant to put their resumes on the job boards, for fear that their companies, co-workers, customers or others might see their resumes. A vacancy arises. Sometimes this is due to the creation of a new job, on other occasions it may be because an existing member of staff has been promoted or is retiring. The job description is updated and an employee specification is written. The job description lists the duties of the job whilst the employee specification gives details of the experience, skills and abilities needed to carry out the job.

2. SYSTEM ANALYSIS

2.1 CURRENT SYSTEMS

✔ In the past organization systems lot of paper work was required to maintain the

records of the registered employees, the selected employees and the existing employees. ✔ Apart from paper work there is a lot of wastage of time and money. ✔ Planning and organizing the records in a systematic and planned manner are lacking

in the existing employee recruitment process. ✔ Also, manpower is not utilized in a proper way. The roles of Admin, HR and TM are

not clearly described and implemented. ✔ The database plays a very less role in present existing system. At present the general

recruitment procedure of the organization system is time consuming. ✔ Therefore there must be a very fast and easy to use system needed to perform the

organization recruitment system.

2.2 PROPOSED SYSTEMS

The disadvantages present in the existing manual systems can be overcome using the proposed systems.

✔ This system provides a simple and easy way for the users to feel comfortable to deal with this system. ✔ This software maintains a unique identification numbers for applicants information in order to provide convenience to them. ✔ It lets the applicants to view their profiles, interview schedules, results and about vacancies. ✔ Applicants can attend interview tests through online. ✔ Using this employee recruitment software an organization can manage the records of all the employees. ✔ With this software, the HR and Technical manager can record information about the

recruitment efforts for a particular practice in the company. ✔ It allows specifically to make tracking HR information such as personal data,

employee training, job responsibilities, benefits, contact information, hiring checklists, and much more. ✔ Administrator can perform the actions like create, edit, delete, list the roles of application, list users of the application and list the practices with in the company. ✔ HR Manager can list the registered candidates, list the interview schedules and list

results of interviews conducted with status. ✔ Team Manager can add, edit, delete or list evaluation details of interviewed candidates

2.3 FEASIBILITY STUDY Feasibility study or feasibility analysis is a vital step in the system development life cycle. The main aim of the feasibility study activity is to determine whether it would be financially

and technically feasible to develop the product. The feasibility study activity involves the analysis of the problem and collection of all relevant information relating to the product such as the different data items which would be input to the system, the processing required to be carried out on these data, the output data required to be produced by the system, as well as various constrains on the behavior of the system.

2.3.1 Technical Feasibility ✔ This software allows to view any employee’s current status working in the organization. ✔ Can have a brief view about all the projects i.e. which are under developing and which are already developed. ✔ It lets us to know about the dead ends of a project. ✔ Employees who are related to a particular project can be identified without much effort. ✔ Technologies used for developing a projects can also be known. 2.3.2 Operational Feasibility The ability, desire, and willingness of the stakeholders to use, support, and operate the proposed computer information system. The stakeholders include management, employees, customers, and suppliers. The stakeholders are interested in systems that are easy to operate, make few, if any, errors, produce the desired information, and fall within the objectives of the organization. This project can be very easily used in the process of decision making in new recruitments, and also ERP allows very easy way to job providers to maintain the information about employees. And finally ERP will reduce the amount of time required to complete the recruitment process of any organization. ERP also provides an advanced search facilities.

2.3.3 Economic Feasibility

This feasibility study present tangible and intangible benefits from the project by comparing the development and operational cost. The technique of cost benefit analysis is often used as a basis for assessing economic feasibility. This system needs some more initial investment than the existing system, but it can be justifiable that it will improve quality of service. Thus feasibility study should center along the following points: Improvement resulting over the existing method in terms of ✔ Accuracy ✔ Timeliness. ✔ Cost comparison ✔ Estimate on the life expectancy of the hardware. ✔ Overall objective. Our project is economically feasible. It does not require much cost to be involved in the overall process. The overall objective is in easing out the recruitment processes.

3. SYSTEM REQUIREMENTS SPECIFICATION

3.1 Functional Requirements ✔ This system should provide an intuitive graphical user interface to all the users. ✔ Databases must be maintained to store the details of all the employees, images, ID proofs, scores of the individual candidates in the test and short listed candidates. ✔ The database manager has the complete control over the database. He controls all user accounts by storing all usernames and passwords. Every user has to login in order to use the system. ✔ New users can register and they can create their own user id and password which are stored in database and used every time for authentication purpose. Cases are assigned to doctor based on in and out times specified by him. ✔ In case a registered patient forgets the ID, some mechanism must be provided to retrieve his data. ✔ The doctor can view the list of patients assigned to him and their details. ✔ The doctor is provided with an interface to enter the remarks of diagnosis for a patient and prescribed medicines. He can also specify if any tests are to be performed. ✔ In case a patient needs to be admitted or operated, the doctor enters the concerned details through the interface. ✔ The test reports for a patient are entered into the database by the lab technician though the interface provided to him. ✔ If the expiry date of drug is reached the store keeper should remove the medicine entry from the database.

3.2 Non Functional Requirements In systems engineering and requirements engineering, a non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a

system, rather than specific behaviors. Non-functional requirements are often called qualities of a system. Other terms for non-functional requirements are "constraints", "quality attributes", "quality goals" and "quality of service requirements," and "non-behavioral requirements." Qualities, that is, non-functional requirements, can be divided into two main categories: ✔ Execution qualities, such as security and usability, which are observable at run time. ✔ Evolution qualities, such as testability, maintainability, extensibility and scalability, which are embodied in the static structure of the software system. 3.3 System Requirement Analysis Introduction: To be used efficiently, all computer software needs certain hardware components or other software resources to be present on a computer. These pre-requisites are known as (computer) system requirements and are often used as a guideline as opposed to an absolute rule. Processing Environment: This mini project is developed on the following hardware and software specifications. 3.3.1 Hardware requirements The most common set of requirements defined by any operating system or software application is the physical computer resources, also known as hardware, A hardware requirements list is often accompanied by a hardware compatibility list. Key Board

: Key Board with 104 keys

VDU

: Monitor/ LCD TFT / Projector

Processor

: Pentium Dual Core

Monitor

: 15” Color Monitor

Hard Disk

: Capacity 250GB

RAM

: 2GB

Clock

: 2.6GHz

3.3.2 Software requirements: Software Requirements deal with defining software resource requirements and prerequisites that need to be installed on a computer to provide optimal functioning of an application. These requirements or pre-requisites are generally not included in the software installation package and need to be installed separately before the software is installed. Operating System

: Windows XP

Environment

: MS.net 2008

Language

: C# 3.5

Framework

: asp.net 3.5

Database

: SQL Server2008

4. DESIGN & IMPLEMENTATION

4.1 SYTSTEM ARCHITECTURE System design develops the architectural detail required to build a system or product. The system design process encompasses the following activities. Partition the analysis model into subsystem, Identify concurrency that is dictated by the problem, Allocate subsystems to processors and tasks, Develop a design for the user interface, Choose a basic strategy for implementing data management, Identify global resources and the control mechanisms required to access them. The design of a system is a plan for solution such that if plan is implemented system will satisfy the requirements of the system. The goal of the design process is to find the best possible design. Some of the essential components involved in the design of application software are: Abstraction is used to construct solutions to problem without having to take account of the intricate details of the various component subprograms. Modularity is concerned with decomposing of main module into well-defined, manageable units with well-defined interfaces among the units. Verification is a fundamental concept in software design. A design is verification if it can be demonstrated that the design will result in an implementation that satisfied the customer’s requirements. Sql Server database have several layers in its architecture in which every layer plays its role. They are application, driver managers, DSN configuration, connector/odbc and finally the database. The following figure gives us the clear view…

Fig 4.1 Description: Overall view of .NET Connection with SQL SERVER

4.2 DATABASE DESIGN A properly designed database provides you with access to up-to-date, accurate information. Because a correct design is essential to achieving your goals in working with a database, investing the time required to learn the principles of good design makes sense. In the end, you are much more likely to end up with a database that meets your needs and can easily accommodate change. Logical Database Design: A Database is a collection of interrelated data stored with a minimum of redundancy to serve many applications. The database design is used to group data into a number of tables and minimizes the artificiality embedded in using separate files.

✔ Reduced duplication of data. ✔ Simplify functions like adding, deleting, modifying data etc.., ✔ Retrieving data ✔ Clarity and ease of use ✔ More information at low cost

Use of Primary Key: Here we use a concept of primary key where we can set this type of constraint to only one column of the table. It is mainly used to reduce the duplication of data entry in that column. Normalization: Normalization is built around the concept of normal forms. A relation is said to be in a particular normal form if it satisfies a certain specified set of constraints on the kind of functional dependencies that could be associated with the relation. The normal forms are used to ensure that various types of anomalies and inconsistencies are not introduced into the database. First Normal Form A relation R is in first normal form if and only if all underlying domains contained atomic values only. Second Normal Form A relation R is said to be in second normal form if and only if it is first normal form and every non-key attribute is fully dependent on the primary key. Third Normal Form A relation R is said to be in third normal form if and only if it is in second normal form and every non key attribute is non-transitively depend on the primary key.

REGISTRATION DATA TABLE:

This table stores information about the applicants who registered for a particular post.the table consists of attributes name, e-mail id, marks of tenth, intermediate, graduation.

Tab 4.1

ER Diagrams ER diagrams are used to represent the design of the database. An entity-relationship (ER) diagram is a specialized graphic that illustrates the relationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.

For an example lets us consider a diagram for the above table.

Applies

candiadt es

Vacant posts

Fig 4.2 Description: ER diagram showing that candidates applies for vacant posts

Phone num

DOB

Percentage Email Organization database Name

Address

Fig 4.2.1 Description: Attributes of the databse

4.3 DATA FLOW DIAGRAMS A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes that change or transform data throughout a system. It’s a structured analysis and design tool that can be used for flowcharting in place of, or in association with, information oriented and process oriented system flowcharts. When analysts prepare the Data Flow Diagram, they specify the user needs at a level of detail that virtually determines the information flow into and out of the system and the required data resources. This network is constructed by using a set of symbols that do not imply a physical implementation. The Data Flow Diagram reviews

the current physical system, prepares input and output specification, specifies the implementation plan etc. Four basic symbols are used to construct data flow diagrams. They are symbols that represent data source, data flows, and data transformations and data storage. The points at which data are transformed are represented by enclosed figures, usually circles, which are called nodes

4.4 UML DIAGRAMS Introduction to Unified Modeling Language: This mapping permits forward engineering: The generation of code from a UML model into a programming language. The reverse is also possible: You can reconstruct a model from an implementation back into the UML. Reverse engineering is not magic. Unless you encode that information in the implementation, information is lost when moving forward from models to code. Reverse engineering thus requires tool support with human intervention. Combining these two paths of forward code generation and reverse engineering yields round-trip engineering, meaning the ability to work in either a graphical or a textual view, while tools keep the two views consistent. In addition to this direct mapping, the UML is sufficiently expressive and unambiguous to permit the direct execution of models, the simulation of systems, and the instrumentation of running systems.

4.4.1 SEQUENCE DIAGRAM A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a Message Sequence Chart. Sequence diagram is one type of interaction diagram. Sequence diagram is having two important features. They are: 1) Focus of control

2) Objects lifeline

Modeling techniques: 1) Modeling flow of control by time ordering.

2) Sequence diagram has following modeling technique

SEQUENCE DIAGRAM1 : Sequence diagram for applicant: This sequence diagram explains how the candidate will fill the registration form and perform the required changes for online registration.

Fig 4.4.1 Description: Sequence digram showing registering process

SEQUENCE DIAGRAM2: Sequence diagram for applicant: This sequence diagram explains about the online registration, generation of a unique registration id , performing online test and evaluation of results.

Fig 4.4.2 Description: This shows registration, taking online test and displaying results

4.4.2 COLLABORATION DIAGRAM Definition: A collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects that send and receive messages. Sequence diagrams and collaboration diagrams are isomorphic, meaning that you can take one and transform it into the other. Collaboration diagram is one of the type of interaction diagram. It has two important features. They are: ✔ Path ✔ Sequence number

Modeling technique: The modeling technique for collaboration diagram is Modeling flow of control by organization

Collaboration diagram for recruiting manager: This collaboration diagram explains how the recruiting manager updates vacancies, conducts interview test for the applicants and generates results. 1: updating vacancies 3: storing details 5: conduct test 7: update selected candidates list recruiting manager

website 2: updated 4: stored 6: sucess 8: updated

Fig 4.4.3 Description: Storing, updating the database

Collaboration diagram for applicant: This collaboration diagram explains how the applicant registers in the website and gets the interview schedule. It also explains how he gets selected to the job. 1: view website 3: job search 5: register to the post 7: take test 9: view result user

website 2: display website 4: result 6: registration id 8: sucess 10: selected/not selected

Fig 4.4.4 Description: How user interacts with website

Collaboration diagram for applicant: This sequence diagram explains how the applicant registers for the interview.

1: clicks on onlinepage 3: views form 4: fills form 5: upload 6: submit 8: logout user

website 2: displays 7: sucess

Fig 4.4.5 Description: Showing how user registers with site

4.4.3 CLASS DIAGRAM Definition: A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics. Graphically, a class is rendered as a rectangle. Contents: Class diagram commonly contains the following things: ✔ Classes ✔ Interfaces ✔ Collaborations ✔ Dependency, generalization, and association relationships

Modeling techniques: There are three modeling techniques. They are: ✔ Modeling simple collaboration ✔ Modeling logical database schema ✔ Modeling vocabulary of system

4.4.4 Class diagram: This class diagram represents all the classes and their relationships. The classes are the user, recruiting manager and the database. The recruiting manager can update the database.

recruiting manager registration id name id proof number

user username registration id id proof user date of birth

update vacancy() maintain database() view applications() conduct test() view result()

view website() apply() attend test() view results() updates

updates

catalogue no of employees emp name emp id emp age emp salary emp designation test scores generate reg id() generate score() generate selected candidates()

Fig 4.4.6 Description: Class diagram showing user, catalogue and recruiting manager

4.4.5 USE CASE DIAGRAM Use case diagrams are one of the five diagrams in the UML for modeling the dynamic aspects of systems(activity diagrams, statechartdigrams,sequence diagrams, and collaboration diagrams are four other kinds of diagrams in the UML for modeling the dynamic aspects of systems). Use case diagrams are central to modeling the behavior of a system, a subsystem, or a class. Each one shows a set of use cases and actors and their relationship.

Use case diagram for the entire project: Use case diagram describes various use cases like login, attend interview, conduct test,select candidatesand get results.

Fig 4.4.7 Description: Actors-User, Admin; interacting with system

4.4.6 ACTIVITY DIAGRAM: An activity diagram shows the flow from activity to activity. These are one of the five diagrams in the UML for modeling the dynamic aspects of system. Graphically an activity diagram is a collection of vertices and arcs CONTENTS: The contents of activity diagram are: ✔ Transitions ✔ Objects ✔ Activity states and Action state

MODELING TECHNIQUES: To model a workflow To model an operation.

ACTIVITY DIAGRAM FOR THE ACTORS: It specifies the activities of user,recruiting manager and the website.

:user

:w ebsite

visit site

:recruiting manager

displays details

search for vacancies if available

view post

no

yes

displays instructions

if eligible

apply and register

no

yes give resgistration id and test details

download paper attend test

conduct test validate test display result

view result

Fig 4.4.8 Description: It shows all the steps involved in the recruiting process

4.4.7 STATE CHART DIAGRAM State chart diagrams are one of the five diagrams in the UML for modeling the dynamic aspects of systems. A state chart diagram shows a state machine, emphasizing the flow of control from state to state.

A state machine is a behavior that specifies the sequences of states an object goes through during its lifetime in response to events, together with its responses to those events. Graphically, a state chart diagram is a collection of vertices and arcs. State chart diagram describing the activities of DB Admin: In this state chart diagram, it shows recruiting updates vacancies,conducts tests and generates results.

update vacancy list

view applicants

update notifications

conduct test

display shortlisted candidates

Fig 4.4.9 Description: State chart diagram showing the activities of DB Admin

State chart diagram for applicant: In this stare chart diagram, the applicant visits the site registers for the interview and attends the test.

view site

apply for job & register

view notification

take test

view shortlisted candidates

Fig 4.4.10 Description: Activity diagram showing how a candidates registers applies and take the tests

4.4.8 COMPONENT DIAGRAM: Component: A Component is physical and replaceable part of a system that conforms to and provides the realization of set of interfaces. Graphically, a component is rendered as a rectangle with tabs. Component diagrams are not only important for visualizing, specifying, and documenting component-based systems, but also for constructing executable systems through forward and reverse engineering. Component diagram for employee recruitment project: This component diagram describes all the physical and replaceable part of the system and also provides set of interfaces.

employee recuitment.exec

login.aps x

registrati on.aspx

online test.apsx

results.a psx

Fig 4.4.11 Description: Component diagram of recruiting process

4.4.9 DEPLOYMENT DIAGRAM: Deployment: - A node is a physical element that exists at run time and represents a computational resource, generally having at least some memory and, often, processing capability. Graphically, a node is rendered as a cube. Deployment diagrams are not only important for visualizing, specifying, and documenting embedded, client/server, and distributed systems, but also for managing executable systems through forward and reverse engineering. Deployment diagram for employee recruitment process project: This deployment diagram describes abouthow the user and the recruitment manager console systems are connected to regional servers and the main server.

server user console

recruitor console

Fig 4.4.12 Description: Deployment diagram of employement recruitment process

5. CODING

5.1 Introduction to technology This section explains the various technologies and tools used for development of the system. INTRODUCTION TO .NET 5.1.1 What is .NET? When .NET was announced in late 1999, Microsoft positioned the technology as a platform for building and consuming Extensible Markup Language (XML) Web services. XML Web services allow any type of application, be it a Windows- or browser-based application running on any type of computer system, to consume data from any type of server over the Internet. The reason this idea is so great is the way in which the XML messages are transferred: over established standard protocols that exist today. Using protocols such as SOAP, HTTP, and SMTP, XML Web services make it possible to expose data over the wire with little or no modifications to your existing code. Since the initial announcement of the .NET Framework, it's taken on many new and different meanings to different people. To a developer, .NET means a great environment for creating robust distributed applications. To an IT manager, .NET means simpler deployment of applications to end users, tighter security, and simpler management. To a CTO or CIO, .NET means happier developers using state-of-theart development technologies and a smaller bottom line. To understand why all these statements are true, you need to get a grip on what the .NET

Framework consists of, and how it's truly a revolutionary step forward for application architecture, development, and deployment.

5.1.2 .NET Framework Now that you are familiar with the major goals of the .NET Framework, let's briefly examine its architecture. The .NET Framework sits on top of the operating system, which can be a few different flavors of Windows and consists of a number of components .NET is essentially a system application that runs on Windows.

Fig 5.1.1 Description: Framework of .net

Conceptually, the CLR and the JVM are similar in that they are both runtime infrastructures that abstract the underlying platform differences. However, while the JVM officially supports only the Java language, the CLR supports any language that can be represented in its Common Intermediate Language (CIL). The JVM executes byte code, so it can, in principle, support many languages, too.

Unlike Java's byte code, though, CIL is never interpreted. Another conceptual difference between the two infrastructures is that Java code runs on any platform with a JVM, whereas .NET code runs only on platforms that support the CLR. In April 2003, the International Organization for Standardization and the International Electro technical Committee (ISO/IEC) recognized a functional subset of the CLR, known as the Common Language Interface (CLI), as an international standard. This development, initiated by Microsoft and developed by ECMA International, a European standards organization, opens the way for third parties to implement their own versions of the CLR on other platforms, such as Linux or Mac OS X. For information on third-party and open source projects working to implement the ISO/IEC CLI and C# specifications. The layer on top of the CLR is a set of framework base classes. This set of classes is similar to the set of classes found in STL, MFC, ATL, or Java. These classes support rudimentary input and output functionality, string manipulation, security management, network communications, thread management, text management, reflection functionality, collections functionality, as well as other functions. On top of the framework base classes is a set of classes that extend the base classes to support data management and XML manipulation. These classes, called ADO.NET, support persistent data management—data that is stored on backend databases. Alongside the data classes, the .NET Framework supports a number of classes to let you manipulate XML data and perform XML searching and XML translations. Classes in three different technologies (including web services, Web Forms, and Windows Forms) extend the framework base classes and the data and XML classes. Web services include a number of classes that support the development of lightweight distributed components, which work even in the face of firewalls and NAT software. These components support plug-and-play across the Internet, because web services employ standard HTTP and SOAP.

Web Forms, the key technology behind ASP.NET, include a number of classes that allow you to rapidly develop web Graphical User Interface (GUI) applications. If you're currently

developing web applications with Visual Interdev, you can think of Web Forms as a facility that allows you to develop web GUIs using the same drag-and-drop approach as if you were developing the GUIs in Visual Basic. Simply drag-and-drop controls onto your Web Form, double-click on a control, and write the code to respond to the associated event. Windows Forms support a set of classes that allow you to develop native Windows GUI applications. You can think of these classes collectively as a muchbetter version of the MFC in C++ because they support easier and more powerfulGUI development and provide a common, consistent interface that can be used in all languages. 5.1.3 Features of the Common Language Runtime The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime. With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means that a managed component might or might not be able to perform file-access operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application. The runtime also enforces code robustness by implementing a strict type- and codeverification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety. Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure

enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting.

5.1.4 The Common Language Runtime At the heart of the .NET Framework is the common language runtime. The common language runtime is responsible for providing the execution environment that code written in a .NET language runs under. The common language runtime can be compared to the Visual Basic 6 runtime, except that the common language runtime is designed to handle all .NET languages, not just one, as the Visual Basic 6 runtime did for Visual Basic 6. The following list describes some of the benefits the common language runtime gives you: ✔

Automatic memory management

✔

Cross-language debugging

✔

Cross-language exception handling

✔

Full support for component versioning

✔

Access to legacy COM components

✔

XCOPY deployment

✔

Robust security model

You might expect all those features, but this has never been possible using Microsoft development tools. The common language runtime fits into the .NET Framework.

5.1.5 The common language runtime and the .NET Framework

Fig 5.1.2 Description: CLR & framework of .net language

5.1.6 ADO.NET Overview ADO.NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. It was designed specifically for the web with scalability, statelessness, and XML in mind. ADO.NET uses some ADO objects, such as the Connection and Command objects, and also introduces new objects. Key new ADO.NET objects include the Dataset, Data Reader, and Data Adapter. The important distinction between this evolved stage of ADO.NET and previous data architectures is that there exists an object -- the Dataset -- that is separate and distinct from any data stores. Because of that, the Dataset functions as a standalone entity. You can think of the Dataset as an always disconnected recordset that knows nothing about the source or destination of the data it contains. Inside a DataSet, much

like in a database, there are tables, columns, relationships, constraints, views, and so forth. A Data Adapter is the object that connects to the database to fill the DataSet. Then, it connects back to the database to update the data there, based on operations performed while the Data Set held the data. In the past, data processing has been primarily connection-based. Now, in an effort to make multi-tiered apps more

efficient, data processing is turning to a message-based approach that revolves around chunks of information. At the center of this approach is the DataAdapter, which provides a bridge to retrieve and save data between a DataSet and its source data store. It accomplishes this by means of requests to the appropriate SQL commands made against the data store. The following sections will introduce you to some objects that have evolved, and some that are new. These objects are: ✔

Connections For connection to and managing transactions against a database.

✔

Commands

✔

DataReaders For reading a forward-only stream of data records from a SQL

For issuing SQL commands against a database.

Server data source. ✔

DataSets For storing, remoting and programming against flat data, XML data

and relational data. ✔

DataAdapters For pushing data into a DataSet, and reconciling data against a

database. ○ Connections Connections are used to 'talk to' databases, and are represented by provider-specific classes such as SQLConnection. Commands travel over connections and result sets are returned in the form of streams which can be read by a DataReader object, or pushed into a DataSet object.

○ Commands Commands contain the information that is submitted to a database, and are represented by provider-specific classes such as SQL Command. A command can be a stored procedure call, an UPDATE statement, or a statement that returns results. You can also use input and output parameters, and return values as part of your command syntax. The example below shows how to issue an INSERT statement against the North wind database.

○ DataReaders The Data Reader object is somewhat synonymous with a read-only/forward-only cursor over data. The DataReader API supports flat as well as hierarchical data. A DataReader object is returned after executing a command against a database. The format of the returned DataReader object is different from a recordset. For example, you might use the DataReader to show the results of a search list in a web page.

5.1.7 ASP.NET Server Application Development: Server-side applications in the managed world are implemented through runtime hosts. Unmanaged applications host the common language runtime, which allows your custom managed code to control the behavior of the server. This model provides you with all the features of the common language runtime and class library while gaining the performance and scalability of the host server.

Server-side managed code: ASP.NET is the hosting environment that enables developers to use the .NET Framework to target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete architecture for developing Web sites and Internetdistributed objects using managed code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing mechanism for applications, and both have a collection of supporting classes in the .NET Framework. Finally, like Web Forms pages in the managed environment, your XML Web service will run with the speed of native machine language using the scalable communication of IIS(Internet Information Service)

5.1.8 DATABASE - SQL SERVER A database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update and extract information from their database.

A database is a structured collection of data. Data refers to the characteristics of people, things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields relating to a particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a number of fields. No two fields in a record can have the same field name. During an SQL Server Database design project, the analysis of your business needs identifies all the fields or attributes of interest. If your business needs change over time, you define any additional fields or change the definition of existing fields.

SQL Server Tables: SQL Server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database.

Data Abstraction: A major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels. ✔ Physical level: This is the lowest level of abstraction at which one describes how the data are actually stored. ✔ Conceptual Level: At this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them. ✔ View level: This is the highest level of abstraction at which one describes only part of the database.

5.2 SAMPLE CODE

5.2.1 Code to validate the login details with deatils already in database.

namespace WebApplication1 { public partial class WebForm13 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["onlinetest"].Equals("completed")) { Panel4.Visible = false; Panel2.Visible = true; } if (Session["registration"].Equals("success")) { Panel4.Visible = false; Panel3.Visible = true; Label1.Text = Session["regid"].ToString(); } } protected void LinkButton9_Click(object sender, EventArgs e) { Response.Redirect("~//WebForm1.aspx"); } protected void LinkButton10_Click(object sender, EventArgs e) {

Response.Redirect("~//WebForm1.aspx"); } } }

5.2.2 To generate id number for the registered candidates.

protected void Button8_Click(object sender, EventArgs e) { int count1 = 0; Random randNum = new Random(); randNum.Next(); string regid = cell.Text.ToString(); regid = regid.Substring(7) + randNum.Next(); Session["regid"] = regid; SqlCommand cmd = new SqlCommand("insert into registration values('" + name.Text + "','" + email.Text + "','" + dob.Text + "','" + cell.Text + "','" + tenth.Text + "','" + tenyr.Text + "','" + tenper.Text + "','" + graduation.Text + "','" + gradyr.Text + "','" + gradper.Text + "','" + pg.Text + "','" + pgyr.Text + "','" + pgper.Text + "','" + exporg.Text + "','" + expyrs.Text + "','" + position.Text + "','" + null + "','" + null + "','" + twelve.Text + "','" + twelveyr.Text + "','" + twelveper.Text + "','" + regid + "','" + Session["post"] + "','" + idpf.Text + "')", cn); cmd.ExecuteNonQuery(); SqlCommand c23 = new SqlCommand("select * from registration ", cn); SqlDataReader dr23 = c23.ExecuteReader(); while (dr23.Read())

{ count1++; } dr23.Close();

int c = (int)count1 % 3; if (c==0)

c = 3; string qpapername = Session["post"].ToString() + c; //TextBox2.Text = c.ToString(); cmd = new SqlCommand("insert into questionpaper values('" + regid + "','" + Session["post"].ToString() + "','" + qpapername + "')", cn); cmd.ExecuteNonQuery(); Panel4.Visible = true; }

5.2.3 Validating the login page of the registered employee

public partial class WebForm12 : System.Web.UI.Page { string cs; SqlConnection cn; protected void Page_Load(object sender, EventArgs e) { cs = ConfigurationManager.ConnectionStrings["regConnectionString1"].ConnectionString; cn = new SqlConnection(cs);

cn.Open(); } protected void Button1_Click(object sender, EventArgs e) { Session["c"] = "0"; Session["login"] = "invalid";

SqlCommand c = new SqlCommand("select * from registration where regid='" +regid.Text+"' ", cn); SqlDataReader dr = c.ExecuteReader(); string name = name1.Text; string idprof = idpf.Text; string dobb = dob.Text; while (dr.Read()) { if (name.Equals(dr["name"].ToString())) { if (idprof.Equals(dr["idpf"].ToString())) { if (dobb.Equals(dr["dob"].ToString())) Session["regidtest"] = regid.Text; Session["login"]="valid"; Session["idpftest"] = idprof; } Session["nametest"] = name; Session["C"] = "1"; //Response.Redirect("~//WebForm9.aspx");

} } dr.Close(); if (Session["login"].Equals("valid")) { Panel2.Visible = false;

Panel3.Visible = true; SqlCommand c1 = new SqlCommand("select * from registration where regid='" + Session["regidtest"].ToString() + "' ", cn); SqlDataReader dr1 = c1.ExecuteReader(); while (dr1.Read()) { namee.Text = dr1["name"].ToString(); regide.Text = dr1["regid"].ToString(); poste.Text = dr1["post"].ToString(); Image2.ImageUrl = "~/ShowImage.ashx?id=" + Session["nametest"].ToString(); } } if (Session["c"].Equals("0")) { Label1.Text = "enter valid details"; } } protected void Button2_Click(object sender, EventArgs e) {

Response.Redirect("~//WebForm16.aspx"); } } }

5.2.4 Code to validate the answer sheet with already provided key

public partial class WebForm9 : System.Web.UI.Page { char[] answers = new char[20]; char[] key = {'c','c','c','c','a','d','a','a','d','b','b','d','d','b','c','d','c','a','a','a'}; int i = 0 , score=0; string cs; SqlConnection cn; protected void Page_Load(object sender, EventArgs e) { cs = ConfigurationManager.ConnectionStrings["regConnectionString1"].ConnectionString; cn = new SqlConnection(cs); cn.Open(); } protected void Timer1_Tick1(object sender, EventArgs e) { /* Label1.Text = DateTime.Now.ToLongTimeString(); if (ViewState["tickcount"] != null) {

int tickcount = 0;

tickcount = (int)ViewState["tickcount"]; } tickcount++; if (tickcount > 0)

ViewState["tickcount"]=tickcount; { Response.Redirect("~//WebForm2.aspx"); } */

int seconds = int.Parse(Label1.Text); if (seconds > 0) Label1.Text = (seconds - 1).ToString(); else { Timer1.Enabled = false; Button1_Click2(sender,e); }

}

protected string look(string a) { if (a.Equals("")) a = "o"; return a; }

protected void Button1_Click2(object sender, EventArgs e) { string s = T1.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T2.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T3.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T4.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T5.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T6.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T7.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T8.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0];

s = T9.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T10.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T11.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T12.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T13.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0];

s = T14.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T15.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T16.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T17.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T18.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T19.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0]; s = T20.Text.ToString(); s.ToLower(); s = look(s); answers[i++] = s[0];

for (i = 0; i < 20; i++) { if (key[i].Equals(answers[i])) score++; } Session["score"] = score.ToString(); SqlCommand c = new SqlCommand("select * from registration where regid='" + Session["regidtest"].ToString() + "' ", cn); SqlDataReader dr = c.ExecuteReader(); string post = ""; while (dr.Read()) { post = dr["post"].ToString();

} dr.Close(); Session["onlinetest"] = "completed"; Session["regidonline"] = Session["regidtest"].ToString();

SqlCommand cmd = new SqlCommand("insert into results values('" + Session["regidtest"].ToString() + "','" + Session["nametest"] + "','" + post + "','" + Session["score"].ToString() + "','" + null + "')", cn); cmd.ExecuteNonQuery(); Session["registration"] = "no"; Response.Redirect("~//WebForm13.aspx"); } } }

5.2.5 Code to direct to home page after online test

namespace WebApplication1 { public partial class WebForm13 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["onlinetest"].Equals("completed")) {

Panel4.Visible = false; Panel2.Visible = true; } if (Session["registration"].Equals("success"))

{ Panel4.Visible = false; Panel3.Visible = true; Label1.Text = Session["regid"].ToString(); } } protected void LinkButton9_Click(object sender, EventArgs e) { Response.Redirect("~//WebForm1.aspx"); } protected void LinkButton10_Click(object sender, EventArgs e) { Response.Redirect("~//WebForm1.aspx"); } } }

5.2.6 Code to open question paper (pdf files) and to test count down tym

public partial class WebForm16 : System.Web.UI.Page { string cs; SqlConnection cn; protected void Page_Load(object sender, EventArgs e) { cs = ConfigurationManager.ConnectionStrings["regConnectionString1"].ConnectionString; cn = new SqlConnection(cs); cn.Open(); SqlCommand c = new SqlCommand("select * from questionpaper where regidq='" + Session["regidtest"].ToString() + "' ", cn); SqlDataReader dr = c.ExecuteReader(); while (dr.Read()) { string u = "http://localhost:3099/files/" + dr["qname"].ToString()+".pdf"; HyperLink1.Text = u; HyperLink1.NavigateUrl=u; } } protected void Timer1_Tick(object sender, EventArgs e) {

int seconds = int.Parse(Label1.Text); if (seconds > 0)

Label1.Text = (seconds - 1).ToString(); else { Timer1.Enabled = false; Button1_Click(sender, e); } } protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("~//WebForm9.aspx"); } }

5.2.7 To connect with SQL database:

partial class WebForm11 : System.Web.UI.Page { string cs; SqlConnection cn; protected void Page_Load(object sender, EventArgs e) {

cs = ConfigurationManager.ConnectionStrings["regConnectionString1"].ConnectionStri ng; cn = new SqlConnection(cs);

cn.Open(); }

5.2.7 To upload image:

protected void Button9_Click(object sender, EventArgs e) { string ext = System.IO.Path.GetExtension(FileUpload1.PostedFile.FileName); ext = ext.ToLower(); if (ext.Equals(".jpg") ext.Equals(".png"))

||

ext.Equals(".jpeg")

||

ext.Equals(".gif")

||

{ try { byte[] myimage = new byte[FileUpload1.PostedFile.ContentLength]; HttpPostedFile Image = FileUpload1.PostedFile; Image.InputStream.Read(myimage, (int)FileUpload1.PostedFile.ContentLength);

0,

//cn = new SqlConnection(cs); // cn.Open(); Session["user"] = name.Text.ToString(); SqlCommand storeimage = new SqlCommand("Update registration photo=(@k) where name='" + Session["user"].ToString() + "'", cn); storeimage.Parameters.AddWithValue("@k", myimage);

set

storeimage.ExecuteNonQuery(); upstatus.Visible = true; upstatus.Text = " photo sucessfully updated"; //Response.Redirect("~//Default.aspx");

} catch (Exception ex) { upstatus.Text = ex.Message; } } Else { upstatus.Text = "file format not supported upload only jpg,gif,png files"; } }

6.TESTING

Testing is the process of finding differences between the expected behavior specified by system models and the observed behavior of the system. Unit testing finds differences between the object design model and its corresponding component. Structural testing finds differences between the system design model and a subset of integrated subsystems. Functional testing finds differences between the use case model and the system. Finally, performance testing finds differences between nonfunctional requirements and actual system performance. When differences are found, developers identify the defect causing the observed failure and modify the system to correct it. In other cases, the system model is identified as the cause of the difference, and the model is updated to reflect the state of the system. From a modeling point of view, testing is the attempt of falsification of the system with respect to the system models. The goal of testing is to design tests that exercise defects in the system and to reveal problems. Testing, however, is aimed at breaking the system. Consequently, testing is usually accomplished by developers that were not involved with the construction of the system. Software testing can also be stated as the process of validating and verifying that a software program/application/product:

✔ Meets the business and technical requirements that guided its design and development. ✔ Works as expected and can be implemented with the same characteristics.

6.1 TESTING STRATEGY Testing methods The box approach Software testing methods are traditionally divided into white- and black-box testing. These two approaches are used to describe the point of view that a test engineer takes when designing test cases. 8.1.1 White box testing White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these. Types of white box testing The following types of white box testing exist: API testing (application programming interface) - testing of the application using public and private APIs Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once) Fault injection methods - improving the coverage of a test by introducing faults to test code pat Mutation testing methods Static testing - White box testing includes all static testing.

Test coverage White box testing methods can also be used to evaluate the completeness of a test suite that was created with black box testing methods. This allows the software team to examine parts of a system that are rarely tested and ensures that the most important function points have been tested. 6.1.2 Black box testing Black box testing treats the software as a "black box"—without any knowledge of internal implementation. Black box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing. Specification-based testing is necessary, but it is insufficient to guard against certain risks. Specification-based testing aims to test the functionality of software according to the applicable requirements. Advantages and disadvantages: The black box tester has no "bonds" with the code, and a tester's perception is very simple: a code must have bugs. Black box testing has the advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of "blind exploring," on the other.

6.1.3 Grey box testing Grey box testing (American spelling: gray box testing) involves having knowledge of internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level. Manipulating input data and formatting output do not qualify as grey box, because the input and output are clearly outside of the "black-box" that we are calling the system under test. This distinction is particularly important when conducting

integration testing between two modules of code written by two different developers, where only the interfaces are exposed for test.

6.1.4 Testing levels Tests are frequently grouped by where they are added in the software development process, or by the level of specificity of the test.

Unit testing Unit testing refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors These type of tests are usually written by developers as they work on code (white-box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather is used to assure that the building blocks the software uses work independently of each other. Integration testing Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together ("big bang"). Normally the former is considered a better practice since it allows interface issues to be localized more quickly and fixed.

Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

System testing System testing tests a completely integrated system to verify that it meets its requirements.

System integration testing System integration testing verifies that a system is integrated to any external or third party systems defined in the system requirements.

Regression testing Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, or old bugs that have come back. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code.

Non-functional testing Special methods exist to test non-functional aspects of software. In contrast to functional testing, which establishes the correct operation of the software (correct in that it matches the expected behavior defined in the design requirements), non-functional testing verifies that the software functions properly even when it receives invalid or unexpected

inputs. Software fault injection, in the form of fuzzing, is an example of non-functional testing. Non-functional testing, especially for software, is designed to establish whether the device under test can tolerate invalid or unexpected inputs, thereby establishing the robustness of input validation routines as well as error-handling routines.

Software performance testing and load testing Performance testing is executed to determine how fast a system or sub-system performs under a particular workload. It can also serve to validate and verify otherquality attributes of the system, such as scalability, reliability and resource usage. Load testing is primarily concerned with testing that can continue to operate under a specific load, whether that be large quantities of data or a large number of users.

Stability testing Stability testing checks to see if the software can continuously function well in or above an acceptable period. This activity of non-functional software testing is often referred to as load (or endurance) testing. Security testing Security testing is essential for software that processes confidential data to prevent system intrusion by hackers. Destructive testing Destructive testing attempts to cause the software or a sub-system to fail, in order to test its robustness.

6.2 TEST CASES

Error Report: S.No 1.

Error Invalid mail id

Cause Giving wrong mail id without including “@”

2.

Invalid marks

Giving marks without specifying precision values

3.

Uploading errors

Uploading files other than .jpeg, .jpg, .png etc.,

5.

Already exists

Entering Existing details

5.

Does not exist

Deletion/ updating the non existed details

6.

Enter the details

Entering invalid registration id

Table 6.2.1 Description: warning messages shown when invalid details are eneterd

Test Plan for applicant: Test

Test Case

Expected Output

Actual Output

Result

Valid Log In Test:

The Text Screen

The Text Screen

Passed

By providing Valid for accepting the

for accepting the

ID to user

text to be shown

text is shown

Valid Register

The Text Screen

The Text Screen

Test: By providing

for accepting the

for accepting the

not existed

text to be shown

text is shown

Valid Status: By

The asp accept the

The asp accepting

providing existed

accepting text to

text to be shown

record information

be shown

Valid Id

The asp accept the

The asp accepting

information:

accepting text to

text to be shown

No. 1.

2.

Passed

information

3.

4.

By providing existed Id information for take the details

be shown

Passed

Passed

Table 6.2.2 Description: test cases describing phases and its corresponding outputs

Screen shot describing a test case:

Fig 6.2 Description: it shows to enter the valid details when wrong id is enetred

7. RESULTS AND DISCUSSIONS

About us:

Fig 7.1 Description: The above page displays overall view of the company

Locations:

Fig 7.2 Description: The above page displays information about the places all over the world where the company is established and situated. Dial us:

Fig 7.3 Description:The above page displays information to contact people of SYMBIOSYS Clients:

Fig 7.4 Description: The above page displays the various clients of the company

Vaccancies

Fig 7.5 Description: shows available posts in the company

Application Form:

Fig 7.6 Description: The above page displays the application form of the candidates who will be registering in the website.

Notifications:

fig 7.7 Description: The above page displays the notifications for the applied candidates.

Eligibility criteria for post software engineer:

Fig 7.8 Description: The above page displays the eligibility criteria for the post2

Registartion form :

Fi 7.9 Description: The above page displays theapplication form after registration

Data base:

Fig 7.10 Description: The above page displays the data of the applicants that is stored

Question paper:

Fig 7.11 Description: This is the question paper that is generated by Recruitment manager

Results:

Fig 7.12 Description: The above page displays the results of the test

Selected candidates list:

Fig 7.13 Description:The above page shows the list of shortlisted candidates list.

8. CONCLUSION

The goal of the system is achieved and problems are solved. The package is developed in a manner that it is user friendly, with a nice user interface and required help is provided at different levels. The project can be easily used in the process of recruiting candidates. The online recruiting process tests the basic prerequisites like candidates interest on the job the way he handles the situation, the way he operates the system, time management and skills in c, c++, java, quantative. Hence the project successfully recruits the highly talented professionals through online. The conclusion is that you cannot leave your employee recruiting to chance. Plan your activities, measure the results and have an on-going strategy to keep the candidate pool full.

9. BIBLIOGRAPHY

[1] ssRoger S. Pressman “Software Engineering , A Practioner’sApporach” Tata Mc-Graw Hill International Edition: Pages 81-83. [2] Raghu Ramakrishnan , Johannes Gehrke “Database Management Systems” Mc-Graw Hill International Edition: Pages 26-36 , 132-165. [3] Chris Bates “Web Programming Building Internet Applications” Winley India Edition: Pages 15-47 , 98-176. [4] Stephen Holzner “C#.net Black book” Second edition: pages 9-50, 89-189 [5] Mathew Macdonald and Mari Szpuszta “Pro asp.net 3.5 in C# 2008” Third edition: pages 20-69, 156-220 [6] Jain “ SQL for professionals” Tata Mc-Graw Hill Third edition.