Hindustan Aeronautics Limited (HAL), a Navratna Central Public Sector Undertaking, is a premier Aeronautical industry of South East Asia,

with 20 Production / Overhaul / Service Divisions and 10 co-located Research & Design Centres spread across the country. HALs spectrum of expertise encompasses design, development, manufacture, repair, overhaul and upgrade of Aircraft, Helicopters, Aero-engines, Industrial & Marine Gas Turbines, Accessories, Avionics & Systems and structural components for Satellites & Launch Vehicles. HAL, over the last seven decades, has grown progressively into an integrated aerospace organization with the indigenous design & development of the Advanced Light Helicopter (ALH-Dhruv), Intermediate Jet Trainer (IJT) & Light Combat Aircraft (LCA-Tejas). The ongoing major projects & programmes include ALH (both Military & Civil roles), IJT, LCA, Pilotless Target Aircraft (PTA), SU-30 MKI, Hawk (Advanced Jet Trainer) & Dornier 228 (Light Transport Aircraft). Aligning with the emerging future requirements, HAL has conceptualized the indigenous development of Light Combat Helicopter (LCH), Basic Turboprop Trainer Aircraft (HTT-40), Light Utility Helicopter (LUH) & Indian Multi-Role Helicopter (IMRH). HAL will co-design & co-develop the Fifth Generation Fighter Aircraft & Multi Role Transport Aircraft, with foreign partners. To fuel its ambitious growth plan, HAL is looking for young, energetic & result oriented Graduate Engineers and Marketing / HR / Legal Professionals with brilliant academic record for the post of Management Trainees for its various Production, Overhaul & Service Divisions / Research & Design Centres / Offices, at Bangalore, Hyderabad, Kasaragod, Nasik, Koraput (Orissa), Lucknow, Kanpur, Korwa (Uttar Pradesh), Barrackpore (West Bengal).

NUMBER OF VACANCIES:
Post Category-wise Vacancies ST SC OBC (Non Creamy layer) UR Total Management Trainee (Technical) 15 30 54 101 200 Management Trainee (Integrated Materials Management) 4 5 9 17 35 Management Trainee (Marketing) 1 2 4 8 15

2
Post Category-wise Vacancies ST SC OBC (Non Creamy layer) UR Total Management Trainee (Human Resources) 1 2 4 8 15 Management Trainee (Legal) 1 1 3 5 10 Management Trainee (Civil) 0 1 2 4 7 Management Trainee (Architecture) 0 1 1 1 3

RESERVATION OF VACANCIES FOR PERSONS WITH DISABILITIES:

Persons with Disabilities (PWDs) suffering from not less than 40% of the relevant disability shall be eligible for the benefit of reservation. Candidate who wants to avail the benefit of reservation is required to submit a disability certificate issued by the Competent Authority in the prescribed format. The vacancies in respect of PWDs will be distributed among all the categories i.e, ST, SC, OBC & UR. The vacancies reserved for PWDs are as given below. Sl. No. Post Discipline Type of Disability No. of vacancies earmarked for PWDs
1

Management Trainee (Technical)

Aeronautical (i) One Leg affected (Right or Left) (ii) One Arm affected (Right or Left) 13 Computer Science (i) Partially Deaf (ii) One Leg affected (Right or Left) (iii) One Arm affected (Right or Left) (iv) Both Legs affected but not arms Electrical (i) Partially Deaf (ii) One Leg affected (Right or Left) Electronics (i) Partially Deaf (ii) One Leg affected (Right or Left) Mechanical (i) One Leg affected (Right or Left) Metallurgy (i) One Leg affected (Right or Left) Production (i) One Leg affected (Right or Left) (ii) One Arm affected (Right or Left) 2 Management Trainee

(IMM)
(i) Partially Deaf (ii) Low Vision (iii) One Leg affected (Right or Left) (iv) One Arm affected (Right or Left) (v) Both Legs affected but not arms 1 3 Management Trainee

(Marketing)
(i) Low Vision (ii) One Leg affected (Right or Left) (iii) One Arm affected (Right or Left) 1 4 Management Trainee (HR) (i) Partially Deaf (ii) Low Vision (iii) One Leg affected (Right or Left) (iv) One Arm affected (Right or Left) (v) Both Legs affected but not arms (vi) One Arm & one Leg affected 2

Pure integrity

Pure integrity of data refers to the property which determines that data, once stored, has not been altered in an unauthorised way -- either by a person, or by the malfunctioning of hardware. An example is used to illustrate the point. Suppose your name is stored on some computer somewhere as "Harry Hacker", and either by the hand of a hacker, or a disgruntled employee, your name is changed to "Harry Hawker"; data integrity has been compromised. To answer the second portion of the question, we merely have to consider if "Harry Hacker" would really be a legitimate name for someone to have. Data validity thus has to do with determining if the data itself is valid - context here plays a critical role. For example, one would not expect a phone number to contain the characters #, @, or %. It can be said with reasonable safety that such a phone number is invalid (thus no data validity). In some instances it is possible for data validity and integrity to fail on the same piece of data. For example, because of a hard disk crash, a person's phone number is changed in such a way that it now contains the character '%'. Thus the integrity has been compromised, and the validity as well.

Answer-- Data Integrity Important data stored in the database include the catalog pricing shipping tables tax tables order database and customer information. Testing must verify the correctness of the stored data. Therefore testing should be performed on a regular basis because data changes over time. Examples of data integrity tests Test the creation modification and deletion of data in tables as specified in the functionality Test to make sure that sets of radio buttons represent a fixed set of values. Check what happens when a blank value is retrieved from the database. Test that when a particular set of data is saved to the database each value gets saved fully. In other words the truncation of strings and rounding of numeric value does not occur. Test whether default values are saved in the database if the user input is not specified. Test the compatibility with old data. In addition old hardware versions of the operating system and interfaces with other software need to be tested. Data Validity Errors caused due to incorrect data entry called data validity errors are probably the most common datarelated errors. These errors are also the most difficult to detect in the system. These errors are typically caused when a large volume of data is entered in a short time frame. For example $67 can be entered as $76 by mistake. The data entered time frame. For example $67 can be entered as $76 by mistake. The data entered is therefore invalid. You can reduce data validity errors. Use the data validation rules in the data fields. For example the date field in a database uses the MM/DD/YYYY format. A developer can incorporate a data validation rule such that MM does not exceed 12 DD does not exceed 31.In many cases simple field validation rules are unable to detect data validity errors. Here queries can be used to validate data fields. For example a query can be written to compare the sum of the numbers in the database data field with the original sum of numbers from the source. A difference between the figures indicates an error in at least one data element.

Exception Testing
I guess is, to test if the application is showing the error messages appropriately and is recovering from the errors to continue running the application. There is a concept called Exception Handling in S/W Programming. It is carried out as one of the phases of SDLC. Here, the expected errors in the s/w application are handled so that, the correct and complete error message is displayed to the user, rightly recovered, execution status is updated and the error is logged for future reference. Exception Testing may be all about testing to see if such development techniques are followed or not. For Testing perspective Exception Testing means tester needs to verify the error messages or exceptions which developers mentioned during coding or mentioned in requirement docs for different-2 scenarios like.. Server down, payment down, applications error, system errors etc.

Functional testing & System testing

Functional testing aims to figure out whether given functionality works as specified. System testing aims to figure out whether the whole system fulfils the requirements given to it. So in functional testing you test that given part of the whole system functions in a specified way. And in system testing you test the system as a whole fulfills the requirements given to it. For example testing that 1+1=2 tests the plus function and sum function. And thus is a functional test. Testing whether user can calculate correct amount of tip using the calculator or not, is a system test, since it tests a requirement (calculate tip), but not a specific function of the application. And non-functional testing includes stuff like usability and performance.