RECRUITMENT SYSTEM The aim of this project is to implement the on-campus recruitment system with a series of criteria to narrow

down to the best recruits. This enables ease of allocating jobs for application and fills concern vacancy position. A.1 Scope: This RECRUITMENT SYSTEM software is applicable to on-campus placements to any software or IT related company. It uses the commonly accepted tests and criteria to choose the recruits. This software eliminates the need for the company to test the individual one by one. It is effective in mass recruitment drives as it is very time saving and also very practical and maps to real world placements. A.1.1 Audience: The applicants to the job are the audience to this software. A.1.2 Organization: This recruiting company is the organization deploying the software. GLOSSARY: In its simplest form, the Glossary is a list of noteworthy terms and their definitions. It is surprisingly common that a term, often technical or particular to the domain, will be used in slightly different ways by different stakeholders; this needs to be resolved to reduce problems in communication and ambiguous requirements.

A.2 Software Requirement Specification: This software is used for an online registration, aptitude and technical tests for an on-campus interview. It posses the following requirements:

A.2.1 Problem statement: Poor recruitment and mis-profiling of individuals is one of the often repeated mistakes by the software organizations. This error in judgement proves to be very costly to the organization. There is a dire need to fix this problem with a regularized and standard recruitment system. The principle of the right person for the right job must be followed. Also, during on-campus interviews or off campus interviews, a large number of individuals apply. This proves to be a headache to the organization since it is a very time consuming process. Sometimes, the organization loses out on good talent owing to lack of time and resource. Due to the inability of the organizations behalf to test every candidate in an effective manner individually because of the time constraints, valuable human assets are lost. From the applicants view, an interview tends to be a tedious and long process. Applicants also suffer because of the lack of an organized recruitment system. Thus this software would be efficient for recruiting eligible candidates.

A.2.2 Gantt chart:

A.3 UML USE CASE MODEL A use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary, communication associations between actors and the use cases and generalization among use cases. Recruitment System use case diagram:

Login

Resume

<<include>>

Test <<extend>>

Applicant Checking <<extend>>

DBA

Interview

Result

Description of use case and actors: The recruitment system is used by the applicant/student. Actor name: Applicant/Student Description: The actor must be able to perform registration and undertake aptitude test.

Types of Actor: Primary Actor: This actor has user goals fulfilled through using services. Applicant is the primary actor in our project. Supporting Actor: This kind of actor provides a service. DBA is the supporting actor in our project. Offstage Actor: This type of actor has an interest in the behavior of the use case but is not primary or supporting actor. Government tax agency is the offstage actor in our project. Package name: Recruitment analysis system It includes the following use cases. Use Case Name: Data Base Administrator Description: The applicant inputs a given field of data that gets updated to the database. Use Case Name: Store Resume Description: The System receives the resume from the applicant and stores in DBA. Use Case Name: Conduct test Description: The use case allows the applicant to undertake test. Use Case Name: Verify answers Description: The use case allows the system to verify the correct answers and updates in the database. Use Case Name: Display result Description: The use case allows the actor to display the ids or name of the applicant who had cleared the test.

A.4 ACTIVITY DIAGRAM FOR A BUSINESS PROCESS An activity diagram is a variation or special case of state machine, in which the states are activities representing the performance of operations and transitions are triggered by the completion of the operations. An activity diagram models the entire business process.

Enter User_id

Register

Fill Resume Not cleared the test

Take a Test

cleared the test Attend Interview

Display Result

A.5UML CLASS DIAGRAMS A.5.1 Super class: The system is the super class of database entry and recruitment analysis classes. A.5.2Subclass: The following classes are subclasses of recruitment analysis class: Applicant A.5.3Conceptual Subclass and Super class: Since it is valuable to identify conceptual super- and subclasses, it is useful to clearly and precisely understand generalization, super classes, and subclasses in terms of class definition and class sets. A conceptual super class is more general or encompassing than a subclass. Conceptual subclasses and super classes are related in terms of set membership. All members of a conceptual subclass set are members of their super class set. In our project System is the conceptual super class and the remaining classes are conceptual subclass. System represents the validation of user details for recruitment of applicants and all other subclasses contain selection process and updation of results. A.5.4 Domain model: 1) Generalization:

Abstract Conceptual Class:

2) Association:

3) Composition:

CLASS DIAGRAM:

Applicant Name user_id depart_nam e provide_access() get_resum e() opname() send_ques()

System validate() user_id() pass_resume() send_result()

Login Resume accept_data() pass_data() user_id() password() get_resum e() pass_resume() Test send_ques() send_ans() Checking verify_ans() Interview analyse() Result disp_result()

DBA pass_data() store_resume() update_DB() store_result()

A.6 UML INTERACTION DIAGRAMS A.6.1 SEQUENCE DIAGRAM Sequence diagrams are an easy and intuitive way of describing the behavior of the system by viewing the interaction between the system and its environment. A sequence diagram shows the objects participating in a time sequence. It shows the objects participating in an \interaction by their lifelines and the messages they exchange, arranged in a time sequence.

SEQUENCE DIAGRAM:

A.6.2 COLLABORATION DIAGRAM A collaboration diagram represents a collaboration, which is a set of objects related in a particular context, and interaction, which is a set of objects within the collaboration, to achieve a desired outcome.

10: validate( )

: System 1: user_id( ) 4: pass_resume( ) 3: get_resume( ) 14: send_result( ) : Applicant 7: send_ans( ) : Test

6: send_ques( ) 13: send_result( ) 11: analyse( ) 8: verify_ans( ) : Result

: Checking

2: pass_data( ) 5: store_resume( ) 15: update_DB( ) : Interview

9: update_DB( ) 12: update_DB( )

: DBA

A.7 STATE CHART DIAGRAM: State chart diagram is one of the five UML diagrams used to model dynamic nature of a system. They define different states of an object during its lifetime. And these states are changed by events. So State chart diagrams are useful to model reactive systems. Reactive systems can be defined as a system that responds to external or internal events. State chart diagram describes the flow of control from one state to another state. States are defined as a condition in which an object exists and it changes when some event is triggered. So the most important purpose of State chart diagram is to model life time of an object from creation to termination. State chart diagrams are also used for forward and reverse engineering of a system. But the main purpose is to model reactive system. Following are the main purposes of using State chart diagrams:

To model dynamic aspect of a system. To model life time of a reactive system. To describe different states of an object during its life time. Define a state machine to model states of an object.

Prov ide user_id

Registration

Attend Test

Interview

Display Result

A.8 LOGICAL VIEW OF LAYERED ARCHITECTURE DIAGRAM:

A.8.1 LOGICAL ARCHITECTURE DIAGRAM:

A.8.3 PACKAGE DIAGRAM A package is a group of modeling elements. It may contain both subordinate packages and ordinary model elements. The entire system can be thought of as a single high-level package, with all the UML diagrams organized within it. It is used to designate the logical, physical and also the use case groups.
R C U MN S SE E RI E T Y TM T

ap a p lic

ss m y te

ap at p lic n d ta e ils

s r u e d ta toe s r a a dr s lt n eu

lo in g a c p a dp s c et n as u e d ta sr a

r sm eu e

ps r s m a s eu e

te t s s n qe ad ed us n as n

c ek hc

c e kc re t h c or c as n

in r w tev

r s lt eu

DA B

aa s ue n ly e s r d ta e ils

d p yin r ie is la tev w r s lt eu

u d tea d pa n s r a r s lts toe ll e u

A.9 USER INTERFACE LAYER: This layer provides the user interface (UI) within a composite application. To increase user productivity, user interfaces should support easy adoption. The limitations on the UI design resulting from the capabilities of the underlying components should not be seen as constraints, but rather as some help to provide consistent UIs. User interfaces consume Web services either from the business logic layer or the back-end layer to retrieve and update data. They do not contain any business logic. UI and business logic decoupling is implemented by using services of the business logic layer only. User interfaces are integrated in the overall composite process by being wrapped into a callable object.

A.10 DOMAIN LAYER: A domain layer also known as the business logic layer (BLL) is a software engineering practice of compartmentalizing. The business logic layer is usually one of the tiers in a multitier architecture. It separates the business logic from other modules, such as the data access layer and user interface. By doing this, the business logic of an application can often withstand modifications or replacements of other tiers. For example, in an application with a properly separated business logic layer and data access layer, the data access layer could be rewritten to retrieve data from a different database, without affecting any of the business logic. This practice allows software application development to be more effectively split into teams, with each team working on a different tier simultaneously.

A.11 TECHNICAL SERVICES LAYER: The Infrastructure Layer may be partitioned into different levels (high-level or low-level technical services). Though, it is not unusual that developers only consider the persistence (data access) and therefore only talk about the Persistence Layer or the Data

Access Layer (instead of an Infrastructure Layer or Technical services Layer). In other words, the other kind of technical services are not always being explicitly thought of as being part of any particular layer.

A.12.1 COMPONENT DIAGRAM: A component diagram depicts how components are wired together to form larger components and or software systems. They are used to illustrate the structure of arbitrarily complex systems.Components are wired together by using an assembly connector to connect the required interface of one component with the provided interface of another component. This illustrates the service consumer - service provider relationship between the two components.

A.12.2 DEPLOYMENT DIAGRAM: Deployment diagrams are used to visualize the topology of the physical components of a system where the software components are deployed. So deployment diagrams are used to describe the static deployment view of a system. Deployment diagrams consist of nodes and their relationships.

A.13 TESTING A.13.1 TEST CASES 1. The system when entered into by the applicant displays a unique id for them. 2. The applicant must have some technical skills about the languages mentioned in registration form. 3. If applicant details are edited then the dependent record should also be updated automatically. 4. The data updated in the front end must be reflected in the database also. 5. The total number of applicant has to include the category of student. 6. The system should display result of the applicants based on their registration id. A.13.1.1 USABILITY TEST CASE SCENARIOS Scenario 1: Display the unique id to the applicants while entering into system. Scenario 2: Store the resume of the applicant to the database with their given details. Scenario 3: Display the test result based on applicant id. A.13.1.2 USER SATISFACTION TESTING The following attributes have been selected for measuring user satisfaction. Easy to operate. Efficient to use. Visually pleasing. Provides easy recovery from errors.

SCREENSHOTS: REGISTRATION FORM:

APTITUDE ROUND :

CALL LETTER:

REPORT 1:

REPORT 2:

CONCLUSION:Computerization of Recruitment System does effectively reduce the manual work involved in recruiting applicants for the concerned firm. It saves time and gives easy access for already stored information. It enables the administrator in providing faster services to the applicants. The system is completely menu driven and extremely user friendly since it is developed in an efficient front end tool Visual Basic. Appropriate error messages are also provided to guide the user in a proper and user friendly manner. The system has effective management of records which holds all the information about the candidates. Even if all the details of the applicant are not sustained, reports are generated and sent to the applicant. Finally, after passing all the confirmation requirements the unique registration number is issued to the candidate.