CHAPTER 1 INTRODUCTION 1.

1 ABOUT THE PROJECT

Recruitment refers to the process of attracting, screening, selecting, and on boarding a qualified person for a job. At the strategic level it may involve the development of an employer brand which includes an 'employee offering'. The stages of the recruitment process include: job analysis and developing a person specification; the sourcing of candidates by networking, advertising, or other search methods; matching candidates to job requirements and screening individuals using testing (skills or personality assessment) Assessment of candidates' motivations and their fit with organizational requirements by interviewing and other assessment techniques. The recruitment process also includes the making and finalizing of job offers and the induction and on boarding of new employees which is most toughest assignment for HR.

Chapter 2 deals with system analysis. Chapter 3 describes about system specification. Chapter 4 and 5 introduce the architecture of system and system designing. Chapter 6 explains about the system testing. Implementation is in Chapter 7. Chapter 8 concludes this project.

1.2 ABOUT THE ORGANISATION

Edserv is a software company that uses technology to efficiently synchronize manpower demand and supply in number and skills right from development to deployment. The size of India's addressable market, favourable demography, growing acceptance of technology-aided learning, and Edserv's innovative Human ware Education And Deployment System (HEADS) coupled with its trademarked content enable rapid growth. Its business model is scalable nationally and internationally. Edserv Softsystems Limited is incepted in Mar 2001 as Lambent Softsystems P Ltd., with an objective of providing niche training solutions, customised software solutions, and placement consulting on contract as well as permanent basis to both Corporate and Institutional clients. The company successfully provided staffing solutions to premier clients during 2002 to 2004 viz., TI Group, TVS Group, Office Tiger, KSB Pumps, Infosys Technologies, HCL Technologies, Shasun Chemicals, Hexaware Technologies, Ashok Leyland, Seshasayee Paper & Boards among others. Edserv acquired EDSERV EDUCATION, leading IT Training brand in the South in the year 2007 to move aggressively in Education & Training space. Edserv employs e-learning and has patented the education models which seamlessly control the complete learning life-cycle of a student from development to deployment in a web controlled framework. Edserv holds copyrighted e-contents covering over a dozen domains and verticals. Edserv is promoted by Mr. S.SundaraMoorthy, as senior technocrat of Indian IT space who is a pioneer in Job oriented education of 90's. He has over 2 decades of experience in Education. SundaraMoorthy later led EDSERV education brand and subsequently sold to Lambent and merged all the businesses under Edserv Edserv provides job linked next generation education through Integrated Learning Model (ILM). Edserv'sEdCenters, EdCampuses, and EdCademys are partner-led and in-campus online contact centers which are spread across India and South Asia providing education & placement throughILM

CHAPTER 2 SYSTEM ANALYSIS 2.1 EXISTING SYSTEM

HR plays an important role in recruitment and selecting apt person for the job and handling the project. HR will take decision based on the available data and user profile. Candidate profile consists of qualification details and performance in previous position. HR taking decision based on the history but it may indulge them to take decision within short period which may lead to uncomfortable decision.

Lead to HR allot and select candidate based on company Recruitment HR will go through candidate records for allot position This may had to improper decision HR may lead to wrong decision. HR not supported by proper records.

2.2 PROPOSED SYSTEM

This tool is automatic tool that can support decision making system for HR management system. HR is please with this tool to making perfect choice for performing the upcoming recruitment. This tool is supported with user profile and history of his projects. The HR can easily select an accurate person for position. HR makes automatic decision by user profile. Even if HR is new to concern he can make app decision. Advantage of HR: HR has been supported by well designed and developed tool. HR was supported by automatic decision system. He/She can flexibly make decision on the bases of project requirement. Avoid wrong decision. Provide proper tool with integrated system.

CHAPTER 3 SOFTWARE SPECIFICATION 3.1 HARDWARE SPECIFICATION Processor RAM Hard disk FDD Monitor Mouse CD Drive Keyboard : : : : : : : : Pentium IV 128 MB 20 GB 1.44MB 14 inch 3 Button scroll 52 X 108 keys

3.2 SOFTWARE SPECIFICATION Operating System Languages Backend : : : Windows 2000/xp/2007 VB.NET 2008 SQL SERVER

3.3 ABOUT THE SOFTWARE .NET Framework Now that you are familiar with the major goals of the .NET Framework, let's briefly examine its architecture. As you can see in Figure 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) .NET Framework 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.

 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 deProjectging Cross-language exception handling Full suspport 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. Figure shows where the common language runtime fits into the .NET Framework.

The common language runtime. Code written using a .NET language is known as managed code. Code that uses anything but the common language runtime is known as unmanaged code. The common language runtime provides a managed execution environment for .NET code, whereas the individual runtimes of non-.NET languages provide an unmanaged execution environment. Inside the Common Language Runtime The common language runtime enables code running in its execution environment to have features such as security, versioning, memory management and exception handling because of the way .NET code actually executes. When you compiled Visual Basic 6 forms applications, you had the ability to compile down to native node or p-code.

Visual Basic 6 compiler options dialog. When you compile your applications in .NET, you aren't creating anything in native code. When you compile in .NET, you're converting your
8

codeno matter what .NET language you're usinginto an assembly made up of an intermediate language called Microsoft Intermediate Language. standard format for processor-specific execution. The file format for the IL is known as PE (portable executable) format, which is a When a user or another component executes your code, a process occur called just-in-time (JIT) compilation, and it's at this point that the IL is converted into the specific machine language of the processor it's executing on. This makes it very easy to port a .NET application to any type of operating system on any type of processor because the IL is simply waiting to be consumed by a JIT compiler. When the IL code is JITted into machine-specific language, it does so on an asneeded basis. If your assembly is 10MB and the user is only using a fraction of that 10MB, only the required IL and its dependencies are compiled to machine language. This makes for a very efficient execution process. But during this execution, how does the common language runtime make sure that the IL is correct? Because the compiler for each language creates its own IL, there must be a process that makes sure what's compiling won't corrupt the system. The process that validates the IL is known as verification. Figure demonstrates the process the IL goes through before the code actually executes.

(Fig) The JIT process and verification When code is JIT compiled, the common language runtime checks to make sure that the IL is correct. The rules that the common language runtime

uses for verification are set forth in the Common Language Specification (CLS) and the Common Type System (CTS). The .NET Framework Class Library The second most important piece of the .NET Framework is the .NET Framework class library (FCL). As you've seen, the common language runtime handles the dirty work of actually running the code you write. But to write the code, you need a foundation of available classes to access the resources of the operating system, database server, or file server. The FCL is made up of a hierarchy of namespaces that expose classes, structures, interfaces, enumerations, and delegates that give you access to these resources. The Structure of a .NET Application To understand how the common language runtime manages code execution, you must examine the structure of a .NET application. The primary unit of a .NET application is the assembly. An assembly is a self-describing collection of code, resources, and metadata. The assembly manifest contains information about what is contained within the assembly. The assembly manifest provides:

Identity information, such as the assemblys name and version number A list of all types exposed by the assembly A list of other assemblies required by the assembly A list of code access security instructions, including permissions required by the assembly and permissions to be denied the assembly Each assembly has one and only one assembly manifest, and it contains

all the description information for the assembly. However, the assembly

10

manifest can be contained in its own file or within one of the assemblys modules. Compilation and Execution of a .NET Application When you compile a .NET application, it is not compiled to binary machine code; rather, it is converted to IL. This is the form that your deployed application takesone or more assemblies consisting of executable files and DLL files in IL form. At least one of these assemblies will contain an executable file that has been designated as the entry point for the application. When execution of your program begins, the first assembly is loaded into memory. At this point, the common language runtime examines the assembly manifest and determines the requirements to run the program. It examines security permissions requested by the assembly and compares them with the systems security policy. If the systems security policy does not allow the requested permissions, the application will not run. If the application passes the systems security policy, the common language runtime executes the code. It creates a process for the application to run in and begins application execution. The .NET Framework base class library contains the base classes that provide many of the services and objects you need when writing your applications. The class library is organized into namespaces. A namespace is a logical grouping of types that perform related functions. Namespaces are logical groupings of related classes. The namespaces in the .NET base class library are organized hierarchically. The root of the .NET Framework is the System namespace. Other namespaces can be accessed with the period operator. A typical namespace construction appears as follows: System System.Data System.Data.SQLClient
11

The first example refers to the System namespace. The second refers to the System.Data namespace. The third example refers to the System.Data.SQLClient namespace. Table 1.1 introduces some of the more commonly used .NET base class namespaces. Introduction to Object-Oriented Programming Programming in the .NET Framework environment is done with objects. Objects are programmatic constructs that represent packages of related data and functionality. Objects are self-contained and expose specific functionality to the rest of the application environment without detailing the inner workings of the object itself. Objects are created from a template called a class. The .NET base class library provides a set of classes from which you can create objects in your applications. You also can use the Microsoft Visual Studio programming environment to create your own classes. This lesson introduces you to the concepts associated with object-oriented programming. Objects, Members, and Abstraction An object is a programmatic construct that represents something. In the real world, objects are cars, bicycles, laptop computers, and so on. Each of these items exposes specific functionality and has specific properties. In your application, an object might be a form, a control such as a button, a database connection, or any of a number of other constructs. Each object is a complete functional unit, and contains all of the data and exposes all of the functionality required to fulfill its purpose. The ability of programmatic objects to represent real-world objects is called abstraction. Classes Are Templates for Objects Classes were discussed in Chapter 1 and represent user-defined reference types. Classes can be thought of as blueprints for objects: they define all of the members of an object, define the behavior of an object, and set initial
12

values for data when appropriate. When a class is instantiated, an in-memory instance of that class is created. This instance is called an object. To review, a class is instantiated using the New (new) keyword as follows: Visual Basic .NET ' Declares a variable of the Widget type Dim myWidget As Widget ' Instantiates a new Widget object and assigns it to the myWidget ' variable myWidget = New Widget() When an instance of a class is created, a copy of the instance data defined by that class is created in memory and assigned to the reference variable. Individual instances of a class are independent of one another and represent separate programmatic constructs. There is generally no limit to how many copies of a single class can be instantiated at any time. To use a real-world analogy, if a car is an object, the plans for the car are the class. The plans can be used to make any number of cars, and changes to a single car do not, for the most part, affect any other cars. Objects and Members Objects are composed of members. Members are properties, fields, methods, and events, and they represent the data and functionality that comprise the object. Fields and properties represent data members of an object. Methods are actions the object can perform, and events are notifications an object receives from or sends to other objects when activity happens in the application. Object Models Simple objects might consist of only a few properties, methods, and perhaps an event or two. More complex objects might require numerous
13

properties and methods and possibly even subordinate objects. Objects can contain and expose other objects as members. Similarly, every instance of the Form class contains and exposes a Controls collection that comprises all of the controls contained by the form. The object model defines the hierarchy of contained objects that form the structure of an object. Encapsulation Encapsulation is the concept that implementation of an object is independent of its interface. Put another way, an application interacts with an object through its interface, which consists of its public properties and methods. As long as this interface remains constant, the application can continue to interact with the component, even if implementation of the interface was completely rewritten between versions. Polymorphism Polymorphism is the ability of different classes to provide different implementations of the same public interfaces. In other words, polymorphism allows methods and properties of an object to be called without regard for the particular implementation of those members. There are two principal ways through which polymorphism can be provided: interface polymorphism and inheritance polymorphism. Interface Polymorphism An interface is a contract for behavior. Essentially, it defines the members a class should implement, but states nothing at all about the details of that implementation. An object can implement many different interfaces, and many diverse classes can implement the same interface. All objects

14

implementing the same interface are capable of interacting with other objects through that interface. Inheritance Polymorphism Inheritance allows you to incorporate the functionality of a previously defined class into a new class and implement different members as needed. A class that inherits another class is said to derive from that class, or to inherit from that class. A class can directly inherit from only one class, which is called the base class. The new class has the same members as the base class, and additional members can be added as needed. Additionally, the implementation of base members can be changed in the new class by overriding the base class implementation. Inherited classes retain all the characteristics of the base class and can interact with other objects as though they were instances of the base class. Microsoft Visual Basic.Net With its release for the .NET platform, the Visual Basic language has undergone dramatic changes. For example: 1. The language itself is now fully object-oriented. 2. Applications and components written in Visual Basic .NET have full access to the .NET Framework, an extensive class library that provides system and application services. 3. All applications developed using Visual Basic .NET run within a managed runtime environment, the .NET common language runtime. 3.3.1 MICROSOFT OFFICE ACCESS The previously known as Microsoft Access, is a DBMS that combines the relational with a and software-development tools. It is a member of the suite of applications, included in the Professional and higher editions or sold
15

separately. On May 12 2010, the current version of Microsoft Access 2010 was released by Microsoft in Office 2010; Microsoft Office Access 2007 was the prior version. MS Access stores data in its own format based on the Access Jet Database Engine. It can also import or link directly to store in other applications and databases. and can use Microsoft Access to develop, and " can use it to build software applications. Like other, Access is supported by, an programming language that can reference a variety of objects including DAO (Data Access Objects), Data Objects, and many other ActiveX components. Visual objects used in forms and reports expose their methods and properties in the VBA programming environment, and VBA code modules may declare and call Windows functions. 1992: Microsoft released Access version 1.0 on 13 November 1992, and an Access 1.1 release in May 1993 to improve compatibility with other Microsoft products and to include the Access Basic programming language. 1993: Microsoft specified the minimum hardware requirements for Access v2.0 as: Microsoft Windows v3.1 with 4 MB of required, 6 MB RAM recommended; 8 MB of available space required, 14 MB hard disk space recommended. The product shipped on seven 1.44 MB diskettes. The manual shows a 1993 copyright date. Originally, the software worked well with relatively small databases but testing showed that some circumstances caused. For example, file sizes over 10 MB proved problematic (note that most hard disks held less than 500 MB at the time this was in wide use), and the Getting Started manual warns about a number of circumstances where obsolete or incorrect configurations can cause. With the phasing out of Windows 95, 98 and ME, improved network reliability, and Microsoft having released 8 for the Jet, the reliability of Access databases has improved and it supports both more data and a larger number of users.

16

With Office 95, Microsoft Access 7.0 (a.k.a "Access 95") became part of the Microsoft Office Professional Suite, joining Microsoft Excel, Word, and PowerPoint and transitioning from Access Basic to Visual Basic for Applications (VBA). Since then, Microsoft has released new versions of Microsoft Access with each release of Microsoft Office. This includes Access 97 (version 8.0), Access 2000 (version 9.0), Access 2002 (version 10.0), Access 2003 (version 11.5), Access 2007 (version 12.0), and Access 2010 (version 14.0).Versions 3.0 and 3.5 of database engine (used by Access 7.0 and the later-released Access 97 respectively) had a critical issue which made these versions of Access unusable on a computer with more than 1 GB of memory. While Microsoft fixed this problem for Jet 3.5/Access 97 post-release, it never fixed the issue with Jet 3.0/Access 95. The native Access database format (the Jet MDB Database) has also evolved over the years. Formats include Access 1.0, 1.1, 2.0, 7.0, 97, 2000, 2002, 2007, and 2010. The most significant transition was from the Access 97 to the Access 2000 format; which is not with earlier versions of Access. As of 2011 all newer versions of Access support the Access 2000 format. New features were added to the Access 2002 format which can be used by Access 2002, 2003, 2007, and 2010.MS Access 2007 introduced a new database format:. ACCDB supports complex such as multivalve and attachment fields. These new field types are essentially record sets in fields and allow the storage of multiple values in one field. With Access 2010, a new version of the ACCDB format supports hosting on a SharePoint 2010 server for exposure to the web. Prior to the introduction of Access, and Fox dominated the desktop database market. Microsoft Access was the first mass-market database program for Windows. With Microsoft's purchase of FoxPro in 1992 and the incorporation of Fox's Rushmore routines into Access, Microsoft Access quickly became the dominant database for Windows - effectively eliminating the competition which failed to transition from the world.

17

Access's initial codename was Cirrus; the forms engine was called Ruby. This was before saw the prototypes and decided that the language component should be co-developed as a separate expandable application, a project called Thunder. The two projects were developed separately as the underlying forms engines were incompatible with each other; however, these were merged together again after. Access was also the name of a communications program from Microsoft, meant to compete with and other programs. This proved a failure and was dropped. MS SQL Microsoft SQL Server is a relational database management system developed by Microsoft. As a database, it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for different workloads (ranging from small applications that store and retrieve data on the same computer, to millions of users and computers that access huge amounts of data from the Internet at the same time). Its primary query languages are T-SQL and ANSI SQL. Introduction Security is becoming increasingly important as more networks are connected together. Your organizations assets must be protected, particularly its databases, which contain your companys valuable information. Security is one of the critical features of a database engine, protecting the enterprise against myriad threats. The new security features of Microsoft SQL Server 2005 are designed to make it more secure and to make security more approachable and understandable to those who are responsible for data protection. During the past few years, the world has developed a far more mature understanding of what a secure, computer-based system must be. Microsoft has been in the forefront of this development, and SQL Server is one of the first
18

server products that fully implements that understanding. It enables the important principle of least privilege so you do not have to grant users more permissions than are necessary for them to do their jobs. It provides in-depth tools for defense so that you can implement measures to frustrate even the most skillful attackers. FEATURES OF SQL-SERVER The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server 2000 Analysis Services. The term OLAP Services has been replaced with the term Analysis Services. Analysis Services also includes a new data mining component. The Repository component available in SQL Server version 7.0 is now called Microsoft SQL Server 2000 Meta Data Services. References to the component now use the term Meta Data Services. The term repository is used only in reference to the repository engine within Meta Data Services SQL-SERVER database consist of six type of objects, They are, 1. TABLE 2. QUERY 3. FORM 4. REPORT 5. MACRO

SQL Server 2005 (code named Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational databases. For this purpose, it defined an xml data

19

type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP Protocol requests. When the data is accessed over web services, results are returned as XML. SQL Server 2005 has also been enhanced with new indexing algorithms and better error recovery systems. Data pages are Check summed for better error resiliency, and optimistic concurrency support has been added for better performance. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. Architecture of SQL Server 2005 Protocol layer - implements the external interface to SQL Server. All operations that can be invoked on SQL Server are communicated to it via a Microsoft-defined format, called Tabular Data Stream (TDS). TDS is an application layer protocol, used to transfer data between a database server and a client. Initially designed and developed by Sybase Inc. for their Sybase SQL Server relational database engine in 1984, and later by Microsoft in Microsoft SQL Server, TDS packets can be encased in other physical transport dependent protocols,including TCP/IP, Named pipes, and Shared memory. Consequently, access to SQL Server is available over these protocols. In addition, the SQL Server API is also exposed over band web services. Data storage - The main unit of data storage is a database, which is a collection of tables with typed columns. SQL Server supports different data types, including primary types such as Integer, Float, Decimal, Char (including character strings), Varchar (variable length character strings), binary (for unstructured blobs of data), Text (for textual data) among others. It also allows user-defined composite types (UDTs) to be defined and used. SQL Server also makes server statistics

20

available as virtual tables and views (called Dynamic Management Views or DMVs). A database can also contain other objects including views, stored procedures, indexes and constraints, in addition to tables, along with a transaction log. Buffer management - SQL Server buffers pages in RAM to minimize disc I/O. The amount of memory available to SQL Server decides how many pages will be cached in memory. The buffer cache is managed by the Buffer Manager. Subsequent reads or writes are redirected to the inmemory copy, rather than the on-disc version. The page is updated on the disc by the Buffer Manager only if the in-memory cache has not been referenced for some time.While writing pages back to disc, asynchronous I/O is used whereby the I/O operation is done in a background thread so that other operations do not have to wait for the I/O operation to complete. Data retrieval - The main mode of retrieving data from an SQL Server database is querying for it. The query declaratively specifies what is to be retrieved. It will be necessary to retrieve the requested data. The sequence of actions necessary to execute a query is called a query plan. There might be multiple ways to process the same query. In such case, SQL Server chooses the plan that is supposed to yield the results in the shortest possible time. This is called query optimization and is performed by the query processor itself. SQL Server includes a cost-based query optimizer which tries to optimize on the cost, in terms of the resources it will take to execute the query. Given a query, the query optimizer looks at the database schema, the database, which sequence to execute the operations and what access method to be used to access the tables Server also allows stored procedures to be defined. Stored procedures are parameterized T-SQL queries that are stored in the server itself. Stored procedures can accept values sent by the client as input parameters, and send back results as output parameters. Distributed Databases As more and more applications are used on an enterprise wide basis or beyond, the ability of a single, centralized database to support dozens of major applications and thousands of concurrent users will continue to erode. Instead,

21

major corporate databases will become more and more distributed, with dedicated databases supporting the major applications and functional areas of the corporation. To meet the higher service levels required of enterprise wide or Internetbased applications, data must be distributed; but to ensure the integrity of business decisions and operations, the operation of these distributed databases must be tightly coordinated. Roles and permissions For a sense of the number of permissions available in SQL Server you can invoke the fn_builtin_permissions system function: SELECT * FROM sys.fn_builtin_permissions(default) Here are the new permission types in SQL Server 2005: CONTROL. Confers owner-like permissions that effectively grant all defined permissions to the object and all objects in its scope, including the ability to grant other grantees any permissions. CONTROL SERVER grants the equivalent of sysadmin privileges. ALTER. Confers permission to alter any of the properties of the securable objects except to change ownership. Inherently confers permissions to ALTER, CREATE, or DROP securable objects within the same scope. For example, granting ALTER permissions on a database includes permission to change its tables. ALTER ANY <securable object>. Confers permission to change any securable object of the type specified. For example, granting ALTER ANY ASSEMBLY allows changing any .NET assembly in the database, while at the server level granting ALTER ANY LOGIN lets the user change any login on that server. IMPERSONATE ON <login or user>. Confers permission to impersonate the specified user or login. As you'll see later in this article, this permission

22

is necessary to switch execution contexts for stored procedures. You also need this permission when doing impersonating in a batch. TAKE OWNERSHIP. Confers the permission to the grantee to take ownership of the securable, using the ALTER AUTHORIZATION statement. SQL Server 2005 still uses the familiar GRANT, DENY, and REVOKE scheme for assigning or refusing permissions on a securable object to a principal. The GRANT statement is expanded to cover all of the new permission options, such as the scope of the grant and whether the principal is able to grant the permission to other principals. Cross-database permissions are not allowed. To grant such permissions, you create a duplicate user in each database and separately assign each database's user the permission. Like earlier versions of SQL Server, activating an application role suspends other permissions for the duration that the role is active. However, new in SQL Server 2005, is the ability to unset an application role. Another difference between SQL Server 2000 and 2005 is that when activating an application role, the role also suspends any server privilege, including public. For example, if VIEW ANY DEFINITION is granted to public, the application role wont honor it. This is most noticeable when accessing server-level metadata under an application role context. Functional Requirements: Functional requirements specify which output file should be produced from the given file they describe the relationship between the input and output of the system, for each functional requirement a detailed description of all data inputs and their source and the range of valid inputs must be specified. Non Functional Requirements: Describe user-visible aspects of the system that are not directly related with the functional behavior of the system. Non-Functional requirements include quantitative constraints, such as response time (i.e. how fast the

23

system reacts to user commands.) or accuracy ((.e. how precise are the systems numerical answers.) Pseudo Requirements: The client that restricts the implementation of the system imposes these requirements. Typical pseudo requirements are the implementation language and the platform on which the system is to be implemented. These have usually no direct effect on the users view of the system.

CHAPTER 4 SOFTWARE ARCHITECTURE

4.1 MODULE

HR Management Candidate Details Recruitment Interface Automatic Filtering and ranking Communication Interface

4.2 MODULE DESCRIPTION

24

HR Management This module is used to manage employee detail and project description. It is used to explanation over the recruitment more accurately.HR management provides and support huge database for maintaining their records.

Candidate Details This is to manage candidate details. it has full detail about each register candidates. Their personal and professional detail of the candidate. Recruitment Interface This module allows HR to detailing his recruitment for selecting a suitable person for the post. This module can automate the recruitment system by providing various information and history about employee performance and previous project records. This is one of the major factors handled by HR in IT or non-IT concerns.

Automatic Filtering and ranking After receiving the detail from HR this tool will automatically filter and rank candidate suitable for HR description based on user profile analysis. Initially it will gather project details, platform, programming language and application details from HR and compare with available data record of employee. This module can make decision automatically and ranked list.

Communication Interface

25

This window allow user to know and communicate with automatic mail sender for the sorted list. It provides GUI based mail sending service. This provides flexibility for using the common mail service such as Gmail.

CHAPTER 5 SYSTEM DESIGN 5.1 DATABASE DESIGN DATABASE NAME: SQLDB

TABLE NAME: EMPLOYEE_DE FIELD NAME Empid Empnam Qual Datb Skil Gen Addr Cnt Datj Exp Pas DATA TYPE Text Text Text Text Text Text Text Text Text Text Text DESCRIPTION Employee id Employee name Qualification Date of birth Skills Gender Address Contact no Date of joining Experience Password

26

Java C Cpp Dotnet Web mailid

Text Text Text Text Text Text

Java C Cpp Dotnet Web designing mailid

TABLE NAME: EMP_DETAILS FIELD NAME Empid Empnam Skills Grade Exp Status DATA TYPE Text Text Text Text Text Text DESCRIPTION Employee id Employee name Skills Grade Experience Status

TABLE NAME: HRM_DET FIELD NAME Empid Empnam Qual Datb Skil Gen Addr Cnt Datj Exp Pas Mailed Connam Addrs Phn DATA TYPE Text Text Text Text Text Text Text Text Text Text Text Text Text Text Text DESCRIPTION Hr id Hr name Qualification Date of birth Skill Gender Address Contact no Date of joining experience Password Mailed Concern name Concern address phone no

27

TABLE NAME: PROJECTDET FIELD NAME Projid Appnam Projdesc Lan1 Lan2 Lan3 Lan4 Lan5 Plat leve DATA TYPE Text Text Text Text Text Text Text Text Text Text DESCRIPTION Project id Application name Project description Language1 Language2 Language3 Language4 Language5 Platform Level

TABLE NAME: EMPDB FIELD NAME Empid Java C Cpp dotnet Web Plt grd DATA TYPE Text Text Text Text Text Text Text Text DESCRIPTION Employee id Java C Cpp dotnet Web designing Platform Grade

TABLE NAME: RESULT FIELD NAME Empid Count DATA TYPE Text Text DESCRIPTION Employee id Count

TABLE NAME: SELCAN

28

FIELD NAME Prjid Appnam Prodes Emid Nam Star

DATA TYPE Text Text Text Text Text Text

DESCRIPTION Project id Application name Project description Emailed Name Star

TABLE NAME: HRMAIL FIELD NAME Hrid Projnam Dat listedusr DATA TYPE Text Text Text Text DSCRIPTION Hr id Project name Date Listed user

TABLE NAME: HRMAIL

FIELD NAME To From Subj Con Det

DATA TYPE Text Text Text Text Text

DSCRIPTION To From Subject Content date

29

5.2 DATA FLOW DIAGRAM

30

CHAPTER 6

31

SYSTEM TESTING 6.1 TESTING INTRODUCTION: After finishing the development of any computer based application, the next complicated time consuming process is testing. During the time of testing only the development company knows that, how far the user requirements have been met. The testing methods applied to our project are as follows. 6. 1 Unit Testing 6. 2 Integration Testing 6. 3 Validation Testing 6. 4 Output Testing 6. 5 Acceptance Testing 6.2 TESTING METHODOLOGY 6.2.1 UNIT TESTING: This testing involve in checking each direct input and its units. Major inputs of this project are text and numbers so there are minimal unit validation handled in this project. In unit testing each module is tested individually. It focuses the verification efforts on the smallest unit of software in the module. This is known as module testing. In the project all the modules are tested separately. For our project testing is performed at programming stage itself. In this testing each module project is found to work satisfactorily with regard to the expected output from the module. There are some validations for fields. The unit testing is performed now and then whenever a patch is delivered for each module. This makes our project standard. Unit testing comprises the set of tests performed by an individual programmer Prior to integration of the unit in to larger system. A program unit is usually small enough that the programmer who developed it can test it in a great detail. In

32

unit testing the modules are independent of one another are tested, the test data for unit testing should follow each condition and option this testing helps to find out the errors in coding and option.

6.2.2 INTEGRATION TESTING: Integration testing is the phase of software testing in which individual software modules are combined and tested as a group. In this project the parts of a module are tested first and then it will test some of its parts, integration testing is done successfully. This project tool is used by HR and candidate so thoroughly binded based on user login.each form are incorporated based on user type.

6.2.3 VALIDATION TESTING: It begins after the integration testing is successfully assembled. Validation succeeds when the software functions in a manner that can be reasonably accepted by the client. In this project, the majority of the validation is done during the data entry operation where there is a maximum possibility of entering wrong data. Other validation will be performed in all process where correct details and data should be entered to get the required results. This module validate each input provide in each module. Each module has to be individually validated because each sub module has various runtime inputs such as date, number, string and use various controls.

6.2.4 OUTPUT TESTING: After performing the validation testing, the next step is output testing of the proposed system since no application would be termed as useful until it produces the required output in the specified format. This project has been run in various environment and tested with runtime input and outputs.

CHAPTER 7

33

SYSTEM IMPLEMENTATION IMPLEMENTATION PHASE

This project has been successfully create and implemented for monitoring in the concern. Under the monitoring period it had satisfy each user category. Implementation refers to post-sales process of guiding a client from

purchase to use of the software or hardware that was purchased. This includes Requirements Analysis, Scope Analysis, Customizations, Systems Integrations, User Policies, User Training and Delivery. These steps are often overseen by a Project Manager using Project Management Methodologies set forth in the Project Management Body of Knowledge. Software Implementations involve several professionals that are relatively new to the knowledge based economy such as Business Analysts, Technical Analysts, Solutions Architect, and Project Managers. The implementation is the final and important phase. It involves HR training, employee interface system testing and successful running of the developed system. The users test the developed system when changes are made according to the needs. The testing phase involves the testing of the developed system using various kinds of data. An elaborate testing of data is prepared and system is tested using the tests data. Implementation is the stage where theoretical design turned into a working system. Implementation is planed carefully to propose system to avoid unanticipated problems. Many preparations involved before and during the implementation of proposed system. The system needed to be plugged in to the organizations network then it could be accessed from anywhere, after a user logins into the portal. The tasks that had to be done to implement the system were to create the database tables in the organization database domain. Then the administrator was granted his role so that the system could be accessed.

34

The next phase in the implementation was to educate the system. A demonstration of all the functions that can be carried out by the system was given to examination department person, who will make extensive use of the system.

Technical analysis In finance, technical analysis is security analysis discipline for forecasting the direction of prices through the study of past market data, primarily price and volume. The efficacy of both technical and fundamental analysis is disputed by efficientmarket hypothesis which states that stock market prices are essentially unpredictable.

Social Analysis The role title has a wider meaning in relation to solving problems, but is more often used in the narrower domain of Technical architecture - the context for the remainder of this definition. In this context, the Solutions Architect is a very experienced architect with cross-domain, cross-functional and cross-industry expertise. He/she outlines solution architecture descriptions, then monitors and governs their implementation.

CHAPTER 8

35

8.1 CONCLUSION
Thus this project has been successfully implemented and run under HR description and user circumstance. This project can support both hr and candidate. It can automatically filter and validate based on hr description. This project has the capable of producing list with auto ranking system. Hr can flexible use it for recurring apt candidate for HR. This project provide flexible communication between register users.

8.2 FUTURE ENHANCEMENT

This project can be redesign as web page ,that why candidate can register from anywhere . This can be made as mobile based application for accessing it through mobile .Now a days mobile has been grown enormously and various os development provide feel free environment for users. So it can be implementing as android tool.

CHAPTER 9 REFERENCE

36

1.

BOOKS REFERENCE 1. MATTHEW MACDONALD, MICROSOFT VISUAL BASIC.NET PROGRAMMERS COOKBOOK -TATA McGraw HILL EDITION Reference Page Nos:

2. WEBSITE REFERENCE WWW.3SCHOOL.COM www.hrworkindia.com

APPENDIX SCREEN SHOT

37

Login form:

HRM Main Form:

38

New HRM Registration:

39

HR Details View:

HR View Candidate Details:

40

HR Password Change:

Project Recruitments:
41

Filter:

42

43

View Result based on Ranking:

44

HR Inbox:

45

HR View Candidate Details

46

Candidate Main Form:

47

New Candidate Registration:

48

Candidate Professional Details:

49

Candidate Password Change:

50

Candidate Inbox:

51

52