రామచంద్రాపురం మండలం కొల్లూరు వద్ద ఔటర్ రింగ్ రోడ్డుపై జరిగిన
కారు ప్రమాదంలో మాజీ మంత్రి కోమటిరెడ్డి వెంకటరెడ్డి ఏకైక కుమారుడు
ప్రతీక్ రెడ్డి మృతి చెందారు. ఈ ప్రమాదంలో మొత్తం ముగ్గురు విద్యార్థులు
మృతి చెందారు. వీరు ముగ్గురూ సిబిఐటిలో ఇంజనీరింగ్ చదువుతున్నారు. మిగిలిన
ఇద్దరిని సుచిత్ రెడ్డి చంద్రారెడ్డిగా గుర్తించారు. కారు డివైడర్ ను
ఢీకొనడం వల్ల ఈ ప్రమాదం జరిగింది. గొర్రెలను తప్పించబోయి డివైడర్ కు
ఢీకొట్టారు. ఈ ప్రమాదంలో కారు నుజ్జునుజ్జు అయింది. సంఘటనా స్థలంలోనే
ముగ్గురు మృతి చెందారు. మరో విద్యార్థి ఆరో రెడ్డి తీవ్రంగా గాయపడ్డారు.
ఆస్పత్రిలో చికిత్స పొందుతున్న అతని పరిస్థితి విషమంగా ఉంది. మృతదేహాలను
గాంధీ ఆస్పత్రికి తరలించే అవకాశం ఉంది.
ప్రతీక్ రెడ్డి మృతితో నల్గొండ జిల్లాలో విషాదచాయలు అలముకున్నాయి. కొడుకు
మరణవార్త విని వెంకటరెడ్డి సోదరులు ఢిల్లీ నుంచి హుటాహుటీన హైదరాబాద్
బయలుదేరారు. రాత్రి 10 గంటలకు వారు హైదరాబాద్ చేరుకునే అవకాశం ఉంది. వెంకట
రెడ్డికి ఒక్కడే కుమారుడు. ఒక కుమార్తె ఉన్నారు.
Tuesday, 20 December 2011
Friday, 9 December 2011
PHP and Webdesign Jobs
We have urjent reqirement on PHP and WEBDESIGNER jobs , if anybody
knows plz send resumes to ramakrishna@unicornsoftwaresolutions.com ,
hr@unicornsoftwaresolutions.com .I can refer to uuuuu
Ramakrishna , 9247988101
knows plz send resumes to ramakrishna@unicornsoftwaresolutions.com ,
hr@unicornsoftwaresolutions.com .I can refer to uuuuu
Ramakrishna , 9247988101
Friday, 2 December 2011
gOOD jOBS
ARMY :
Indian Army Technical Graduate Course 115th July 2012
ARTICLE JOBS :
Make This Summer Memorable - Using Holidays- Part 1
Punjab and Sind Bank Financial Inclusion Coordinator vacancies Recruitment 2012
CORPORATE JOBS :
Parle Mumbai 2011 - Production Executives Jobs
ICICI Bank Recruitment for CAs, Managers, Business Analysts 2011
ICICI Walk Ins for Senior Development Officers 201 in AP
ENGINEERING JOBS :
Indian Army Technical Graduate Course 115th July 2012
SCTIMST Recruitment 59 Various Vacancies 2012
MCEME Engineering Faculty Jobs Secunderabad November 2011-12
AP Panchayat Secretaries Assistant Engineers in DPO and RWS Jobs 2011-12
PSTCL Asst jr Engineers Officers UDC SSO Accountant Job November 2011
BEL (Bharat Electronics Limited) Bangalore Walk Ins for Graduate Apprentices Recruitment 2011
BHEL (Bharat Heavy Electricals Limited) Experienced Engineers Recruitment 2011
IOCL-Indian Oil Recruitment of Graduate Engineers 2012 through GATE
ONGC 150 A1 ,A2 Level jobs – Oil & Natural Gas Corporation Ltd & 162 Field Operator jobs
BHEL Engineer Trainee Recruitment for GATE Candidates 2012
AP-Latest Recruitments for D.Sc, SI, Engineering, Excise, Health and Revenue Posts 2011-2012
NTPC Graduate Engineers Recruitment 2011 for GATE Candidates 2012
BEL Bharat Electronics Limited Walk Ins at Pune for Data Base Administrators 2011
BEL Ghaziabad Engineering Assistants,Clerk And Technician Jobs 2011
ALIMCO Kanpur - Accounts Officers,Engineers,Trainees Jobs 2011
unior Engineers in MPPKVVCL - Madhya Pradesh Paschim Kshetra Vidyut Vitaran Company Ltd.
IOCL Bioler Engineers, QC and Medical Officers Jobs 2011
SKU(Sri Krishnadevaraya University) Anantapur Walk ins for Faculty and Lab Assistants 2011
Rani Channamma University Belagavi 2011-2012 Teaching Jobs
TTD (tirumala tirupathi devasthanam) Ayurvedic College Walk Ins for Faculty Jobs 2011-2012
Mahatma Gandhi University -2011 Teaching and Non Teachng Posts
IIM Indore Academic Resource Persons 2011 Recruitment
Faculty Jobs 2011 in OUAT Orissa University of Agriculture and Technology College of Forestry, Orissa.
New Delhi ESIC Medical Faculty Recruitment 2011
CDAC Global Openings Technical Faculty 2011
Jobs In Faculty Villa Marie Education Society 2011-12
ICICI Bank Recruitment for CAs, Managers, Business Analysts 2011
RMSA-SSA Haryana Recruitment for Library Manager, Lab Attendant and Accountants 2011
APCOB Assistant Managers, Clerks Jobs | AP Co-Operative Bank - IBPS Notification 2011
AP Animal Husbandry Dept 2011 - Veterinary Assistant Surgeons Jobs
Gautam Buddha University Recruitment Medical Officer September 2011-12 uttra pradesh
New Delhi ESIC Medical Faculty Recruitment 2011
IOCL Bioler Engineers, QC and Medical Officers Jobs 2011
HAL Koraput - Assistant Engineers, Officers Recruitment 2011
Para Medical Posts in South Central Railway Walk Ins for 2011
East Coast Railway Various Recruitment sports quota Vacancies 2011 –2012
RRB Assistant Loco Pilot Exam Syllabus,Important Topics, Exam Structure
RRB Assistant Loco Pilot Model Questions,Previous Papers,Books and Material
RRB Assistant Loco Pilot Recruitment | Centralised Employment Notice 2011
RRB Secunderabad Assistant Loco Pilot 2011 Recruitment
RESULTS :
JNTUH MBA 1,2,3,4 Sem (NR,R07,R09) & MCA 1,2,3,4,5 Sem (R09,R06,NR) Regular/Supple Exams Results (July/Aug-2011)
AP Police SI 201 Results
IOB Results of Probationary Officers in JMG Scale-I and Clerical Staff 2011
Canara bank Results of Specialist Officers in JMG Scale I, MMG Scale II
IBPS Key and Results - POs,Clerks,Management Trainees CWE Answers 2011
sCIENTIST :
NCL Pune Scientists and Technical Jobs 2011 -2012
NPL - CSIR New Delhi Scientists 2011 Recruitment
NBRI Lucknow Scientists 2011 Recruitment
ICFRE Dehradun Scientists-B 2011 Recruitment
TECHNICAL:
Indian Army Technical Graduate Course 115th July 2012
SCTIMST Recruitment 59 Various Vacancies 2012
SAIL (Steel Authority of India Limited ) Bhilai Steel Plant Attendant Cum Technician Jobs - October 2011
NCL Pune Scientists and Technical Jobs 2011 -2012
ISRO Recruitment Technicians Jobs 2011
ONGC 150 A1 ,A2 Level jobs – Oil & Natural Gas Corporation Ltd & 162 Field Operator jobs
Indian Army 27th 10+2 Technical Entry Scheme - TES Session july 2011
AIATSL Junior Executives And Technical Recruitment 2011
BEL Ghaziabad Engineering Assistants,Clerk And Technician Jobs 2011
VSSC Thiruvananthapuram Graduate and Apprentices Technician Recruitment 2011
WALKINS:
Para Medical Posts in South Central Railway Walk Ins for 2011
Careers Cross Tab 2011
SCTIMST Recruitment 59 Various Vacancies 2012
NIRD TOT Project Coordinators Walk Ins November 2011-12
BEL (Bharat Electronics Limited) Bangalore Walk Ins for Graduate Apprentices Recruitment 2011
CMET (Centre for Materials for Electronics Technology) Hyderabad Walk Ins for Project Staff - October 2011-12
MG University Nalgonda - Walk Ins for Academic 2011 Consultants
BEL Bharat Electronics Limited Walk Ins at Pune for Data Base Administrators 2011
BEL Ghaziabad Engineering Assistants,Clerk And Technician Jobs 2011
Do u Need JOB?
This site guides u? may be it will use for u
Just check and get job i wish u all the best to ur bright feature
student2jobs.blogspot.com/search/label/AP%20Jobs
Friday, 25 November 2011
Car Info
After months of speculation and spy shots, Maranello has finally revealed the mid-engined V8 replacement for the Ferrari F430. The all-new Ferrari 458 Italia won't be shown in public until September's Frankfurt Motor Show, but the official details were released early this morning. A new direct-injected 4.5-liter V8 ups the ante underhood, pumping out 562 horsepower and 398 lb-ft of torque. The redline? A screaming 9,000 rpm. Eighty percent of the F458 Italia's torque is now available at a low 3,250 rpm, thanks in all likelihood to the new engine's 12.5:1 compression ratio.
As with last year's California, the Ferrari 458 gets a seven-speed dual clutch gearbox that directs power to the rear axle. Much has been done to reduce internal friction within the new V8, in addition aerodynamic drag improvements. As a result, the Ferrari 458 Italia's gas mileage improves to a combined 17.1 mpg (US) on the EU test cycle. As this is a Ferrari, talk of fuel consumption really does seem somewhat pointless, anyway. No mention of incorporating any type of KERS hybrid system has been made thus far. The KERS idea, you'll remember, had taken several spins around the rumormill over the last year or so; maybe that'll materialize at a later date.
Like its predecessor, the Ferrari 458 Italia's aluminum structure helps keep weight under control -- it tips the scales at just 3,042 pounds dry. So, we know you're wondering: How quick is it? Based on specs at least, this new coupe does't disappoint. Acceleration to 100 km/h (62 mph) takes just 3.4 seconds, and this will be the first volume production Ferrari V8 to top the 200 mph barrier, with a top whack of 202 mph. Is it still too early to head to the airport for our flight to Frankfurt in September?
[Source: Ferrari]
ITALIA - Ferrari's innovative new V8
The 458 Italia is the latest incarnation of the mid-rear engined berlinetta and will be unveiled at the next Frankfurt Motor Show
Maranello, July 28th 2009 – While it's true that every Ferrari is innovative by definition, it's equally true that in the course of the Prancing Horse's history, certain cars have marked a genuine departure from the current range. This is very much the case with the Ferrari 458 Italia, which is a massive leap forward from the company's previous mid-rear engined sports cars.
The new model is a synthesis of style, creative flair, passion and cutting-edge technology, characteristics for which Italy as a nation is well-known. For this reason Ferrari chose to add the name of its homeland to the traditional figure representing the displacement and number of cylinders.
The Ferrari 458 Italia is a completely new car from every point of view: engine, design, aerodynamics, handling, instrumentation and ergonomics, just to name a few.
A two-seater berlinetta, the Ferrari 458 Italia, as is now traditional for all Ferrari's road-going cars, benefits hugely from the company's Formula 1 experience. This is particularly evident in the speed and precision with which the car responds to driver inputs and in the attention focused on reducing internal friction in the engine for lower fuel consumption than the F430, despite the fact that both overall displacement and power have increased. However, Ferrari's track experience makes its presence felt in the 458 Italia not only in terms of pure technological transfer but also on a more emotional level, because of the strong emphasis on creating an almost symbiotic relationship between driver and car. The 458 Italia features an innovative driving environment with a new kind of steering wheel and dashboard that is the direct result of racing practice. Once again input from Michael Schumacher - who was involved from the very start of the 458 Italia project - played an invaluable part.
The Ferrari 458 Italia's Pininfarina design provides further evidence of the complete departure from the past that this new car hails. The Ferrari 458 Italia has a compact, aerodynamic shape, underscoring the concepts of simplicity, efficiency and lightness that inspired the project. As with every Ferrari, the car's styling has been very heavily influenced by the requirements for aerodynamic efficiency, as can be seen from the downforce of 140 kg at 200km/h generated by the new model. The front features a single opening for the front grille and side air intakes, with aerodynamic sections and profiles designed to direct air to the coolant radiators and the new flat underbody. The nose also sports small aeroelastic winglets which generate downforce and, as speed rises, deform to reduce the section of the radiator inlets and cut drag.
The new 4499 cc V8 is the first Ferrari direct injection engine to be mid-rear mounted. It has a very low piston compression height typical of racing engines which contributed to achieving its compression ratio of 12.5:1. Equipped with the traditional flat-plane crankshaft, the engine delivers 570 CV at 9000 rpm and, with an outstanding power output of 127 CV/litre, sets a new benchmark not only for the whole Ferrari range and the history of company, but also for the entire market segment. Maximum torque is 540 Nm at 6000 rpm, over 80 per cent of which is available from 3250 rpm. Specific torque is a record 120 Nm/litre. However, what is truly extraordinary is the amount of torque available while still maintaining high levels of power at low revs.
The car's soundtrack is also typical Ferrari, with an exciting, powerful growl emerging from the engine before it channels through to the exhaust's three rear tailpipes.
The 458 Italia is equipped with the seven-speed dual-clutch transmission which increases performance whilst providing very smooth shifts even at full throttle. The engineers have developed specific, sportier gear ratios to match the power and torque curves of the new V8, guaranteeing high torque even at lower engine speeds and allowing the car to reach its maximum speed in top gear.
This new Ferrari is also a major leap forward when it comes to cutting emissions. Despite the fact that the new engine is significantly more powerful than the V8s that preceded it, the Ferrari 458 Italia produces just 320 g/km of CO2 and fuel consumption is 13.7 l/100 km (combined cycle), the best in the entire segment.
The engineers also focused on weight reduction during the design phase for similar reasons. Consequently, the Ferrari 458 Italia has a dry weight of 1380 kg with a power-to-weight ratio of 2.42 kg/CV. Weight distribution is also optimal with 58 per cent over the rear axle. The result of the engineers' endeavours can be summed up in to two simple statistics which together perfectly encapsulate the Ferrari 458 Italia's exceptional performance: 0-100 km/h acceleration in under 3.4 seconds and a maximum speed in excess of 325 km/h.
For the new chassis, once more in aluminium, Maranello's engineers incorporated various types of advanced alloys along with aerospace industry-derived manufacturing and bonding techniques.
With regard to vehicle dynamics, the Ferrari 458 Italia's suspension features twin wishbones at the front and a multi-link set-up at the rear tuned for maximum roadholding and superlative handling. Along with a more direct steering ratio, the 458 Italia thus offers extremely rapid turn-in and body control whilst maintaining superior ride comfort.
The integration of the E-Diff and F1-Trac (now controlled by the same ECU) and their respective mappings is even greater, resulting in a 32 per cent increase in longitudinal acceleration out of corners compared to previous models. The evolution of the control logic, with even faster and more accurate calculation of levels of grip, ensures even greater roadholding, better handling and ease of control on the limit.
The same ECU also governs the high-performance ABS, providing even more precise control over the logic threshold and greater efficiency. The brakes also feature a prefill function whereby the pistons in the callipers move the pads into contact with the discs on lift off to minimise delay in the brakes being applied. This combined with the ABS has cut the 100-0 km/h braking distance to a mere 32.5 metres.
The Ferrari 458 Italia's interior is another area of the car that exalts its sporty personality. The driver is welcomed by a new layout and a revolutionary ergonomic interface where the main controls are all clustered on the steering wheel.
With the Ferrari 458 Italia, Maranello has brought a highly distinctive new car to its 8-cylinder range. The company now offers two models that share a common, race-derived DNA, both exceptionally sporty and fun to drive in true Ferrari tradition, but aimed at two very different kinds of client. While the Ferrari California was created for owners requiring a more versatile sports car with a practical edge, the 458 Italia is designed for owners for whom the priority is uncompromising on-road performance with occasional track day capability, but who still demand a car that is useable in day-to-day driving like all Ferrari's recent models.
Ferrari 458 Italia – Technical specifications
Dimensions
Length 4527 mm (178.2 in.)
Width 1937 mm (76.3 in.)
Height 1213 mm (47.8 in.)
Wheelbase 2650 mm (104.3 in.)
Dry weight 1380 kg (3042 lbs)*
Weight/power ratio 2,42 kg/CV (7.16 lbs/kW)
Weight distribution fr/r 42%/58%
Engine
Type V8 – 90°
Displacement 4499 cc (274.5 cu in.)
Maximum power 570 CV (425 kW)** @ 9000 rpm
Maximum torque 540 Nm (398 lbs/ft) @ 6000 rpm
Specific power output 127 CV/l
Compression ratio 12.5:1
Tyres
Front 235/35 ZR20 8.5"
Rear 295/35 ZR20 10.5"
Performance
Maximum speed >325 km/h (>202 mph)
0-100 km/h
Fuel consumption + emissions
Fuel consumption*** 13.7 l/100 km
Emissions*** 320 g CO2/km
Gearbox
Dual-clutch, 7-speed F1
Electronics
E-Diff3, F1-Trac, high-performance ABS
* With forged wheels and Racing seats
** Including 5 CV of ram effect
*** Combined cycle (ECE+EUDC)
As with last year's California, the Ferrari 458 gets a seven-speed dual clutch gearbox that directs power to the rear axle. Much has been done to reduce internal friction within the new V8, in addition aerodynamic drag improvements. As a result, the Ferrari 458 Italia's gas mileage improves to a combined 17.1 mpg (US) on the EU test cycle. As this is a Ferrari, talk of fuel consumption really does seem somewhat pointless, anyway. No mention of incorporating any type of KERS hybrid system has been made thus far. The KERS idea, you'll remember, had taken several spins around the rumormill over the last year or so; maybe that'll materialize at a later date.
Like its predecessor, the Ferrari 458 Italia's aluminum structure helps keep weight under control -- it tips the scales at just 3,042 pounds dry. So, we know you're wondering: How quick is it? Based on specs at least, this new coupe does't disappoint. Acceleration to 100 km/h (62 mph) takes just 3.4 seconds, and this will be the first volume production Ferrari V8 to top the 200 mph barrier, with a top whack of 202 mph. Is it still too early to head to the airport for our flight to Frankfurt in September?
[Source: Ferrari]
ITALIA - Ferrari's innovative new V8
The 458 Italia is the latest incarnation of the mid-rear engined berlinetta and will be unveiled at the next Frankfurt Motor Show
Maranello, July 28th 2009 – While it's true that every Ferrari is innovative by definition, it's equally true that in the course of the Prancing Horse's history, certain cars have marked a genuine departure from the current range. This is very much the case with the Ferrari 458 Italia, which is a massive leap forward from the company's previous mid-rear engined sports cars.
The new model is a synthesis of style, creative flair, passion and cutting-edge technology, characteristics for which Italy as a nation is well-known. For this reason Ferrari chose to add the name of its homeland to the traditional figure representing the displacement and number of cylinders.
The Ferrari 458 Italia is a completely new car from every point of view: engine, design, aerodynamics, handling, instrumentation and ergonomics, just to name a few.
A two-seater berlinetta, the Ferrari 458 Italia, as is now traditional for all Ferrari's road-going cars, benefits hugely from the company's Formula 1 experience. This is particularly evident in the speed and precision with which the car responds to driver inputs and in the attention focused on reducing internal friction in the engine for lower fuel consumption than the F430, despite the fact that both overall displacement and power have increased. However, Ferrari's track experience makes its presence felt in the 458 Italia not only in terms of pure technological transfer but also on a more emotional level, because of the strong emphasis on creating an almost symbiotic relationship between driver and car. The 458 Italia features an innovative driving environment with a new kind of steering wheel and dashboard that is the direct result of racing practice. Once again input from Michael Schumacher - who was involved from the very start of the 458 Italia project - played an invaluable part.
The Ferrari 458 Italia's Pininfarina design provides further evidence of the complete departure from the past that this new car hails. The Ferrari 458 Italia has a compact, aerodynamic shape, underscoring the concepts of simplicity, efficiency and lightness that inspired the project. As with every Ferrari, the car's styling has been very heavily influenced by the requirements for aerodynamic efficiency, as can be seen from the downforce of 140 kg at 200km/h generated by the new model. The front features a single opening for the front grille and side air intakes, with aerodynamic sections and profiles designed to direct air to the coolant radiators and the new flat underbody. The nose also sports small aeroelastic winglets which generate downforce and, as speed rises, deform to reduce the section of the radiator inlets and cut drag.
The new 4499 cc V8 is the first Ferrari direct injection engine to be mid-rear mounted. It has a very low piston compression height typical of racing engines which contributed to achieving its compression ratio of 12.5:1. Equipped with the traditional flat-plane crankshaft, the engine delivers 570 CV at 9000 rpm and, with an outstanding power output of 127 CV/litre, sets a new benchmark not only for the whole Ferrari range and the history of company, but also for the entire market segment. Maximum torque is 540 Nm at 6000 rpm, over 80 per cent of which is available from 3250 rpm. Specific torque is a record 120 Nm/litre. However, what is truly extraordinary is the amount of torque available while still maintaining high levels of power at low revs.
The car's soundtrack is also typical Ferrari, with an exciting, powerful growl emerging from the engine before it channels through to the exhaust's three rear tailpipes.
The 458 Italia is equipped with the seven-speed dual-clutch transmission which increases performance whilst providing very smooth shifts even at full throttle. The engineers have developed specific, sportier gear ratios to match the power and torque curves of the new V8, guaranteeing high torque even at lower engine speeds and allowing the car to reach its maximum speed in top gear.
This new Ferrari is also a major leap forward when it comes to cutting emissions. Despite the fact that the new engine is significantly more powerful than the V8s that preceded it, the Ferrari 458 Italia produces just 320 g/km of CO2 and fuel consumption is 13.7 l/100 km (combined cycle), the best in the entire segment.
The engineers also focused on weight reduction during the design phase for similar reasons. Consequently, the Ferrari 458 Italia has a dry weight of 1380 kg with a power-to-weight ratio of 2.42 kg/CV. Weight distribution is also optimal with 58 per cent over the rear axle. The result of the engineers' endeavours can be summed up in to two simple statistics which together perfectly encapsulate the Ferrari 458 Italia's exceptional performance: 0-100 km/h acceleration in under 3.4 seconds and a maximum speed in excess of 325 km/h.
For the new chassis, once more in aluminium, Maranello's engineers incorporated various types of advanced alloys along with aerospace industry-derived manufacturing and bonding techniques.
With regard to vehicle dynamics, the Ferrari 458 Italia's suspension features twin wishbones at the front and a multi-link set-up at the rear tuned for maximum roadholding and superlative handling. Along with a more direct steering ratio, the 458 Italia thus offers extremely rapid turn-in and body control whilst maintaining superior ride comfort.
The integration of the E-Diff and F1-Trac (now controlled by the same ECU) and their respective mappings is even greater, resulting in a 32 per cent increase in longitudinal acceleration out of corners compared to previous models. The evolution of the control logic, with even faster and more accurate calculation of levels of grip, ensures even greater roadholding, better handling and ease of control on the limit.
The same ECU also governs the high-performance ABS, providing even more precise control over the logic threshold and greater efficiency. The brakes also feature a prefill function whereby the pistons in the callipers move the pads into contact with the discs on lift off to minimise delay in the brakes being applied. This combined with the ABS has cut the 100-0 km/h braking distance to a mere 32.5 metres.
The Ferrari 458 Italia's interior is another area of the car that exalts its sporty personality. The driver is welcomed by a new layout and a revolutionary ergonomic interface where the main controls are all clustered on the steering wheel.
With the Ferrari 458 Italia, Maranello has brought a highly distinctive new car to its 8-cylinder range. The company now offers two models that share a common, race-derived DNA, both exceptionally sporty and fun to drive in true Ferrari tradition, but aimed at two very different kinds of client. While the Ferrari California was created for owners requiring a more versatile sports car with a practical edge, the 458 Italia is designed for owners for whom the priority is uncompromising on-road performance with occasional track day capability, but who still demand a car that is useable in day-to-day driving like all Ferrari's recent models.
Ferrari 458 Italia – Technical specifications
Dimensions
Length 4527 mm (178.2 in.)
Width 1937 mm (76.3 in.)
Height 1213 mm (47.8 in.)
Wheelbase 2650 mm (104.3 in.)
Dry weight 1380 kg (3042 lbs)*
Weight/power ratio 2,42 kg/CV (7.16 lbs/kW)
Weight distribution fr/r 42%/58%
Engine
Type V8 – 90°
Displacement 4499 cc (274.5 cu in.)
Maximum power 570 CV (425 kW)** @ 9000 rpm
Maximum torque 540 Nm (398 lbs/ft) @ 6000 rpm
Specific power output 127 CV/l
Compression ratio 12.5:1
Tyres
Front 235/35 ZR20 8.5"
Rear 295/35 ZR20 10.5"
Performance
Maximum speed >325 km/h (>202 mph)
0-100 km/h
Fuel consumption + emissions
Fuel consumption*** 13.7 l/100 km
Emissions*** 320 g CO2/km
Gearbox
Dual-clutch, 7-speed F1
Electronics
E-Diff3, F1-Trac, high-performance ABS
* With forged wheels and Racing seats
** Including 5 CV of ram effect
*** Combined cycle (ECE+EUDC)
Monday, 14 November 2011
Mercury Interview Questions
Q1. What is Software Testing?
Ans. Operation of a system or application under controlled conditions and evaluating the results. The controlled conditions must include both normal and abnormal conditions. It is oriented to detection.
Q2. What is Software Quality Assurance?
Ans. Software QA involves the monitoring and improving the entire software development process, making sure that any agreed-upon standards and procedures are followed. It is oriented to prevention.
Q 3. What are the qualities of a good test engineer?
Ans.
A good test engineer has a test to break attitude.
An ability to take the point of view of the customer
a strong desire for quality
Tactful and diplomatic
Good communication skills
Previous software development experience can be helpful as it provides a deeper understanding of the software development process
Good judgment skills
Q4. What are the qualities of a good QA engineer?
Ans.
The same qualities a good tester
Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization.
In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed.
An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.
Q5. What are the qualities of a good QA or Test manager?
Ans.
Must be familiar with the software development process
able to maintain enthusiasm of their team and promote a positive atmosphere
always looking for preventing problems
able to promote teamwork to increase productivity
able to promote cooperation between software, test, and QA engineers
have the skills needed to promote improvements in QA processes
have the ability to say 'no' to other managers when quality is insufficient or QA processes are not being adhered
have people judgement skills for hiring and keeping skilled personnel
be able to run meetings and keep them focused
Q6. What is the 'software life cycle'?
Ans. The life cycle begins when an application is first conceived and ends when it is no longer in use.
Q7. Tell us about some world famous bugs
Ans. 1. In December of 2007 an error occurred in a new ERP payroll system for a large urban school system. More than one third of employees had received incorrect paychecks that results in overpayments of $53 million. Inadequate testing reportedly contributed to the problems
2. A software error reportedly resulted in overbilling to 11,000 customers of a major telecommunications company in June of 2006. Making the corrections in the bills took a long time.
3. In March of 2002 it was reported that software bugs in Britain's national tax system resulted in more than 100,000 erroneous tax overcharges.
Q8. What are the common problems in the software development process?
Ans.
Poor requirements
Unrealistic schedule
Inadequate testing
A request to pile on new features after development is unnderway.
Miscommunication
Q9. What are the common solutions to software development problems?
Ans.
Solid requirements
Realistic schedules
Adequate testing
stick to initial requirements where feasible
require walkthroughs and inspections when appropriate
Q10. What is a Quality Software?
Ans. Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and / or expectations, and is maintainable.
Q11. What is good code?
Ans. Good code is code that works, is reasonably bug free, and is readable and maintainable.
Q12. What is good design?
Ans. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable. It should also be robust with sufficient error-handling and status logging capability and work correctly when implemented. And, good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements.
Q13. What's the role of documentation in QA?
Ans. QA practices must be documented to enhance their repeatability. There should be a system for easily finding and obtaining information and determining what documentation will have a particular piece of information.
Q14. Which projects may not need independent test staff?
Ans. It depends on the size & nature of the project. Then, it depends on business risks, development methodology, the skills and experience of the developers.
Q15. Why does software have bugs?
Ans.
miscommunication or no communication
software complexity
programming errors
changing requirements
time pressures
poorly documented code
software development tools
egos - people prefer to say things like:
• 'no problem'
• 'piece of cake'
• 'I can whip that out in a few hours'
Ans. Operation of a system or application under controlled conditions and evaluating the results. The controlled conditions must include both normal and abnormal conditions. It is oriented to detection.
Q2. What is Software Quality Assurance?
Ans. Software QA involves the monitoring and improving the entire software development process, making sure that any agreed-upon standards and procedures are followed. It is oriented to prevention.
Q 3. What are the qualities of a good test engineer?
Ans.
A good test engineer has a test to break attitude.
An ability to take the point of view of the customer
a strong desire for quality
Tactful and diplomatic
Good communication skills
Previous software development experience can be helpful as it provides a deeper understanding of the software development process
Good judgment skills
Q4. What are the qualities of a good QA engineer?
Ans.
The same qualities a good tester
Additionally, they must be able to understand the entire software development process and how it can fit into the business approach and goals of the organization.
In organizations in the early stages of implementing QA processes, patience and diplomacy are especially needed.
An ability to find problems as well as to see 'what's missing' is important for inspections and reviews.
Q5. What are the qualities of a good QA or Test manager?
Ans.
Must be familiar with the software development process
able to maintain enthusiasm of their team and promote a positive atmosphere
always looking for preventing problems
able to promote teamwork to increase productivity
able to promote cooperation between software, test, and QA engineers
have the skills needed to promote improvements in QA processes
have the ability to say 'no' to other managers when quality is insufficient or QA processes are not being adhered
have people judgement skills for hiring and keeping skilled personnel
be able to run meetings and keep them focused
Q6. What is the 'software life cycle'?
Ans. The life cycle begins when an application is first conceived and ends when it is no longer in use.
Q7. Tell us about some world famous bugs
Ans. 1. In December of 2007 an error occurred in a new ERP payroll system for a large urban school system. More than one third of employees had received incorrect paychecks that results in overpayments of $53 million. Inadequate testing reportedly contributed to the problems
2. A software error reportedly resulted in overbilling to 11,000 customers of a major telecommunications company in June of 2006. Making the corrections in the bills took a long time.
3. In March of 2002 it was reported that software bugs in Britain's national tax system resulted in more than 100,000 erroneous tax overcharges.
Q8. What are the common problems in the software development process?
Ans.
Poor requirements
Unrealistic schedule
Inadequate testing
A request to pile on new features after development is unnderway.
Miscommunication
Q9. What are the common solutions to software development problems?
Ans.
Solid requirements
Realistic schedules
Adequate testing
stick to initial requirements where feasible
require walkthroughs and inspections when appropriate
Q10. What is a Quality Software?
Ans. Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and / or expectations, and is maintainable.
Q11. What is good code?
Ans. Good code is code that works, is reasonably bug free, and is readable and maintainable.
Q12. What is good design?
Ans. Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable. It should also be robust with sufficient error-handling and status logging capability and work correctly when implemented. And, good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements.
Q13. What's the role of documentation in QA?
Ans. QA practices must be documented to enhance their repeatability. There should be a system for easily finding and obtaining information and determining what documentation will have a particular piece of information.
Q14. Which projects may not need independent test staff?
Ans. It depends on the size & nature of the project. Then, it depends on business risks, development methodology, the skills and experience of the developers.
Q15. Why does software have bugs?
Ans.
miscommunication or no communication
software complexity
programming errors
changing requirements
time pressures
poorly documented code
software development tools
egos - people prefer to say things like:
• 'no problem'
• 'piece of cake'
• 'I can whip that out in a few hours'
QC questions
Mercury Quality Centre is a web-based test management tool. It gives you a centralized control over the entire testing life cycle. It gives an easy interface to manage and organize activities like Requirements coverage, Test Case Management, Test Execution Reporting, Defect Management, and Test Automation. All these activities are provided from a single tool, which is web-based and can be accessed from any where. Hence, making the task of the testers and managers easy.
Mercury Quality Centre can be divided into two parts:
- Site Administrator Bin
- Quality Centre Bin
Site Administration Bin: It is the starting point for the usage of Mercury Quality Centre. This part is used for all the administrative activities. Password for site admin is defined during the installation so make sure that you remember the password during installation. From this part of Mercury Quality Centre, we generally do the following activities:
- Creating the projects
- Assigning users to the projects
- Creating specific roles
- Configuring QTP or Winrunner scripts to use from Mercury Quality Centre
- Configuring the mail servers
- Verifying licensing information
- Information about database
Note: If you are using Winrunner, you need to make sure that backward compatibility property of the application to true.
Quality Center Bin: This part of Mercury Quality Centre gives functionality of almost everything that as a tester or test manager you need to do in your day to day activity apart from execution. This is the most common interface used by the customers or users. In this part, we generally do the following activities:
- Creating test plans
- Defining requirements
- Creating test cases
- Creating test labs
- Associating requirements with defects in essence
Mercury Quality Centre is installed as a service in Microsoft windows environment. Before start working on it, make sure that Mercury Quality Centre service is running.
As soon as you access the application, the first screen is a login screen where you need to provide administrator credentials which were used during the installation of Mercury Quality Centre. Once you are logged on to the SABin, you can perform all the administrative tasks mentioned above.
Note: If Mercury Quality Centre is listening to default port, then you can access the application using the following URL:
http://%7Byourmachinename%7D:8080/sabin/SiteAdmin.htm
Define your projects in SABin. Mercury Quality Center provides the role based accessed to the Projects. For example, A Test Manager can create projects and Test Lead can prepare test plans and tester can write the test cases. This role based access makes it very easy to control access to various artifacts of the project and also distribution of responsibility among team members. Following four things can be managed in Mercury Quality Centre:
- Requirements
- Test Plan
- Test Lab
- Defects
Once you have created a project in SABin, Now log on to QCBin by providing your credentials and access the project that you have created. Here, you will notice different tabs for Requirements, TestPlan, TestLab and Defects.
Under Requirements Tab, you can organize the project requirements. You can also create folder hierarchy to represent various features in your project. This can be accomplished by just right-clicking and choosing appropriate options. After creating requirements, move on to next tab Test Plan.
Test Plan Tab will have information about the test cases. These test cases can also be mapped to requirements created in the earlier steps, thus makes foundation for the traceability metrics. Each requirement can be mapped to one or more than one test cases.
After creating new test case you will see in the left hand pane. The right hand pane will have tabs for writing the steps, mapping to requirements, description, expected result etc. Every test case will have steps and for every step you can specify the expected behavior.
The test cases written here, can also be linked to the QTP or Winrunner Scripts. This way, it is providing you better management for the automation and capability of executing automation scripts from Mercury Quality Centre itself. Once you are done with Test Plan preparation, move on to the next tab Test Lab.
To manage test execution for a specific release, you have to create a Test Lab. Test Labs can be created, specific to the release and execution of test cases specific to release can be managed very easily using this concept. In the Test Lab you can identify the set of test cases already written under test plan to include for execution.
If the test cases are already linked to the requirements, then after each test cycle the management will be able to trace what requirements have been tested.
When you choose the option of manual test execution, a window will open up containing the steps to execute. These steps are executed and after every step you can specify whether it is passed or not. Mercury Quality Center also allows parameterized manual test execution, where some of the default parameters like username, password etc. can automatically be read during the manual execution. If you encounter any defects during the failure of any of the steps, it will be automatically logged in to the defect tracking system of Mercury Quality Centre. Once you are done with Test Execution move on to next tab, Defects.
Report generation is one of the most important part of the test management process. Once you are done with planning and execution, its REPORTING time. Mercury Quality Centre provides a very good reporting feature by providing certain pre-defined reports and also capability to create your own reports.
Mercury Quality Centre can be divided into two parts:
- Site Administrator Bin
- Quality Centre Bin
Site Administration Bin: It is the starting point for the usage of Mercury Quality Centre. This part is used for all the administrative activities. Password for site admin is defined during the installation so make sure that you remember the password during installation. From this part of Mercury Quality Centre, we generally do the following activities:
- Creating the projects
- Assigning users to the projects
- Creating specific roles
- Configuring QTP or Winrunner scripts to use from Mercury Quality Centre
- Configuring the mail servers
- Verifying licensing information
- Information about database
Note: If you are using Winrunner, you need to make sure that backward compatibility property of the application to true.
Quality Center Bin: This part of Mercury Quality Centre gives functionality of almost everything that as a tester or test manager you need to do in your day to day activity apart from execution. This is the most common interface used by the customers or users. In this part, we generally do the following activities:
- Creating test plans
- Defining requirements
- Creating test cases
- Creating test labs
- Associating requirements with defects in essence
Mercury Quality Centre is installed as a service in Microsoft windows environment. Before start working on it, make sure that Mercury Quality Centre service is running.
As soon as you access the application, the first screen is a login screen where you need to provide administrator credentials which were used during the installation of Mercury Quality Centre. Once you are logged on to the SABin, you can perform all the administrative tasks mentioned above.
Note: If Mercury Quality Centre is listening to default port, then you can access the application using the following URL:
http://%7Byourmachinename%7D:8080/sabin/SiteAdmin.htm
Define your projects in SABin. Mercury Quality Center provides the role based accessed to the Projects. For example, A Test Manager can create projects and Test Lead can prepare test plans and tester can write the test cases. This role based access makes it very easy to control access to various artifacts of the project and also distribution of responsibility among team members. Following four things can be managed in Mercury Quality Centre:
- Requirements
- Test Plan
- Test Lab
- Defects
Once you have created a project in SABin, Now log on to QCBin by providing your credentials and access the project that you have created. Here, you will notice different tabs for Requirements, TestPlan, TestLab and Defects.
Under Requirements Tab, you can organize the project requirements. You can also create folder hierarchy to represent various features in your project. This can be accomplished by just right-clicking and choosing appropriate options. After creating requirements, move on to next tab Test Plan.
Test Plan Tab will have information about the test cases. These test cases can also be mapped to requirements created in the earlier steps, thus makes foundation for the traceability metrics. Each requirement can be mapped to one or more than one test cases.
After creating new test case you will see in the left hand pane. The right hand pane will have tabs for writing the steps, mapping to requirements, description, expected result etc. Every test case will have steps and for every step you can specify the expected behavior.
The test cases written here, can also be linked to the QTP or Winrunner Scripts. This way, it is providing you better management for the automation and capability of executing automation scripts from Mercury Quality Centre itself. Once you are done with Test Plan preparation, move on to the next tab Test Lab.
To manage test execution for a specific release, you have to create a Test Lab. Test Labs can be created, specific to the release and execution of test cases specific to release can be managed very easily using this concept. In the Test Lab you can identify the set of test cases already written under test plan to include for execution.
If the test cases are already linked to the requirements, then after each test cycle the management will be able to trace what requirements have been tested.
When you choose the option of manual test execution, a window will open up containing the steps to execute. These steps are executed and after every step you can specify whether it is passed or not. Mercury Quality Center also allows parameterized manual test execution, where some of the default parameters like username, password etc. can automatically be read during the manual execution. If you encounter any defects during the failure of any of the steps, it will be automatically logged in to the defect tracking system of Mercury Quality Centre. Once you are done with Test Execution move on to next tab, Defects.
Report generation is one of the most important part of the test management process. Once you are done with planning and execution, its REPORTING time. Mercury Quality Centre provides a very good reporting feature by providing certain pre-defined reports and also capability to create your own reports.
Subscribe to:
Posts (Atom)