Custom Search

How Bank works

Posted byPrashanthNaik at 8:37 PM 0 comments  

Basic Linux Commands

TIP 1:
All of these commands should work from your command prompt (regardless which shell you're using). Just in case some folks were not aware, you MUST press enter to invoke the command

TIP 2:
For this summary, please note that the EX: stands for example and is not part of the command. Commands are denoted in courier type font.

TIP 3:
If you need help understanding what the options are, or how to use a command, try adding this to the end of your command: --help

For example, for better understanding of the df command's options, type:
df --help

Command Summary Use
Use cd to change directories Type cd followed by the name of a directory to access that directory.
Keep in mind that you are always in a directory and allowed access to any directories hierarchically above or below. Ex:
cd games

If the directory games is not located hierarchically below the current directory, then the complete path must be written out. Ex:
cd /usr/games

To move up one directory, use the shortcut command. Ex:
cd ..
Use clear to clear the command prompt Type clear to clean up your command prompt window.
This is especially helpful when you are typing lots of commands and need a clean window to help you focus.Ex:
clear

This is also useful when you are getting ready to type a rather long command and do not wish to become confused by other details on the screen.
Use date to set your server's date and time Type date followed by the two digit month, the two digit date, the two digit time, and two digit minutes. The syntax is easy enough and resembles this: MMDDhhmm
This command is helpful but must be used when superuser or logged in as root. Otherwise you will get an "Operation not permitted" reply.As root user you can use the command such as:
date 11081300

The above command will set the server date and time to the 11th month (November), the 8th day, at 1:00pm.
Use df to check disk space Typing df provides a very quick check of your file system disk space.
Type df -h to get a more easily readable version of the output. Notice that this command will include all applicable storage such as your hard disk/s (hda, hdb etc.) and your server SWAP file (shm). To list disk space including filesystem type:
df -h -T
Use finger to see who's on the system Typing finger allows you to see who else is on the system or get detailed information about a person who has access to the system.
Type finger followed by the name of a user's account to get information about that user. Or, type finger and press enter to see who's on the system and what they are doing. Ex:
finger johndoe
Use logout to quit using the system Yep, you guessed it, typing logout will log your account out of the system.
Type logout at the prompt to disconnect from your Linux machine or to logout a particular user session from the system. Keep in mind that although rudimentary, leaving your critical account logged on may be a security concern. We always recommend promptly using logout when you are finished using your root account! Ex:
logout
Use ls to list files and directories Type ls to see a list of the files and directories located in the current directory. If you’re in the directory named games and you type ls, a list will appear that contains files in the games directory and sub-directories in the games directory. Examples:
ls Mail
ls /usr/bin

Type ls -alt to see a list of all files (including .rc files) and all directories located in the current directory. The listing will include detailed, often useful information. Examples:
ls -alt
ls -alt /usr/bin
If the screen flies by and you miss seeing a number of files, try using the |more at the end like:
ls -alt |more

* In Bash (Linux shell) often the abbreviated command L is available. To get a verbose listing of files and directories you could therefore simply type: l

Use man to pull up information about a Linux command Type man followed by a command to get detailed information about how to use the command. Ex:
man ls

Type man -k followed by a word to list all of the commands and descriptions that contain the word you specified. Ex:
man -k finger
Use more to read the contents of a file Type more followed by the name of a text file to read the file’s contents. Why do we exmphasize using this on a "text" file? Because most other types of files will look like garbage! Ex:
more testfile.txt
Use nano to start a text editor Typing nano will start a basic text editor on most Linux systems.
Type nano followed by the filename you wish to edit. This basic editor is quick and easy to use for beginners. However, it is very important that you also learn about other text editors available on Linux and UNIX systems. Click on this link to learn about others like emacs, vi, and pico. Ex:
nano /etc/security/access.conf
Use passwd to change your current password Type passwd and press enter. You'll see the message Changing password for yourname.
At the Old password: prompt, type in your old password .
Then, at the Enter new password: prompt, type in your new password .
The system double checks your new password. Beside the Verify: prompt, type the new password and press again.

Create a secure password that combines parts of words and numbers. For instance, your dog's name may be Rufus. He may have been born in 1980. Create a password that uses parts of both the name and date of birth, such as 80rufuS. Note the use of at least one capital letter. This is a fairly secure password and easy to remember.
Use pwd to list the name of your current directory Type pwd and hit enter. You'll see the full name of the directory you are currently in. This is your directory path and is very handy. This is especially handy when you forget which directory you’ve changed to and are trying to run other commands.

Posted byPrashanthNaik at 1:00 AM 0 comments  

Sky Smiled At ...............................

On December 02 2008 Sky Smiled at me!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Posted byPrashanthNaik at 3:58 AM 0 comments  

Nice Ad.......

Posted byPrashanthNaik at 2:54 AM 0 comments  

HOW TO BE POPULAR

What do all popular people have in common? Do they all wear the same clothes? Have the same hair? Say the same things? Of course not. There are popular people all over the world, enjoying their social status at school, work, and wherever they go. They don't all look or act like each other--but they do all share one very crucial characteristic: people skills. Maybe they were born with them, or maybe they learned them from their family; however they got them, they have them. Here's how to develop your people skills.

Be willing to step out of your comfort zone. If you're not popular, it's because you're not comfortable doing the things that popular people tend to do--making conversation, cracking jokes, flirting, and in general, engaging people. You might be introspective, shy, or quiet, but in order to get what you want, you need to change how you interact with people. At first, that might feel like you're being shallow or fake, but remember that being yourself is, at its core, all about knowing what you truly want out of life. There's nothing wrong with wanting to be on good terms with most people (which is what popularity really is). To be popular, you're going to need to take a few chances (on a social level) that normally feel uncomfortable (perhaps terrifying) to you. So be prepared to be bold.


Be friendly. Popular people are on friendly terms with pretty much everyone--not only their peers, but also the teachers, the supervisors, the grocery store clerk, the janitor, the parents, the kids, and generally anyone who's even the tiniest bit nice. (The only people they're not friends with are the ones who are practically impossible to get along with.) They're on good enough terms that they can hold a short, friendly conversation with anyone in the room. There's no reason you can't do that, too.

Be polite. Respect people's privacy; don't pry. Learn to read body language so you can see when your questions are starting to make them feel uncomfortable. Don't invite yourself anywhere, don't brag, and don't interrupt. In other words, don't be annoying.

Stop thinking about yourself. People will think you're self-centered, and not many people like that kind.Of all the people skills that popular individuals have, the one that none of them can do without is empathy. How well do you relate to other people? If you're so caught up in how they perceive you that you don't consider how they feel, then you're being self-absorbed--not in that cocky, obnoxious sort of way, but still, your thoughts are revolving around you. Stop worrying so much about how you look, how you sound, how you compare, and start thinking about how other people are doing. Don't try to act interesting to get other people's attention; act interested in them. Ask them how work or school is going, how their family is doing, how that situation they mentioned a while back turned out, and so on. Then relate. Talk to them about how you or someone you know had something similar happen to them, and how they dealt with it. Find common ground.

Give a helping hand.Popular people don't just know everyone--they're on good terms with everyone. They establish those terms by helping people out, and they don't do it in particularly noticeable ways (they're not the martyrs or saints of society). They do little things to establish rapport (in addition to some big things, like volunteering). They offer someone a pencil when they need it. They close the neighbor's gate when it opens after a strong wind. They hold the door open and wait for the person behind them. But most often, they listen to people when they talk, and they offer to help somehow. If you truly empathize with people, you'll want things to work out for them. If there's nothing you can do to help then, at the very least, let them know that you're hoping the best for them. Here are some phrases that you'll often hear popular people saying:
• "Well, I hope things work out. If you need anything, call me, OK?"
• "Whoa. That's crazy. I can't believe he did that. Do you want me to talk to him for you?"
• "Yeah! I definitely want to go check that out. Do you want to go there together? We can split the gas that way."

Be yourself. It may sound trite, but popular people live out this popular phrase. You might think that in order to be popular, you need to be attractive and talented, but--while it's true that those qualities are more likely to make you a hit with people--there are extremely popular people who are otherwise quite average, and there are extremely good-looking and talented people who are anything BUT popular. Remember, the only thing you need in order to be popular is a good set of people skills--the remainder is all yours to mold as you see fit, regardless of what anyone else thinks. have fun and still remember to be yourself cuz thats important too.

Posted byPrashanthNaik at 2:42 AM 0 comments  

Job market in 2009 ---Too Good..

Watch This Video........

Posted byPrashanthNaik at 12:29 AM 0 comments  

Abraham Lincoln's creative touch

Posted byPrashanthNaik at 9:49 PM 0 comments  

You have low self esteem and you feel rejected??

It might help you to lift your morale..Copied it from rediff question and Answer section..But its worth reading...

No one will manufacture a lock without a key.
Similarly God won't give problems without solutions. Life laughs at you when you are unhappy... Life smiles at you when you are happy...
Life salutes you when you make others happy...
Every successful person has a painful story. Every painful story has a successful ending. Accept the pain and get ready for success.
Easy is to judge the mistakes of others. Difficult is to recognize our own mistakes.
It is easier to protect your feet with slippers than to cover the earth with carpet. No one can go back and change a bad beginning; But anyone can start now and create a successful ending.
If a problem can be solved, no need to worry about it. If a problem cannot be solved what is the use of worrying?
If you miss an opportunity don't fill the eyes with tears. It will hide another better opportunity in front of you "Changing the Face" can change nothing. But "Facing the Change" can change everything.
Don't complain about others; Change yourself if you want peace.
Mistakes are painful when they happen. But year's later collection of mistakes is called experience, which leads to success. B
e bold when you loose and be calm when you win.
Heated gold becomes ornament. Beaten copper becomes wires. Depleted stone becomes statue. So the more pain you get in life you become more valuable.

Posted byPrashanthNaik at 4:09 AM 0 comments  

Global Imbalance - An imminent Dollar Crisis

Watch the speech by venkatesh,Economist on Global Imbalance ....

http://video.google.com/videoplay?docid=4343898391323537541&hl=en

Posted byPrashanthNaik at 3:13 AM 0 comments  

Bulls Revenge....

Posted byPrashanthNaik at 1:14 AM 0 comments  

Deer Hunter.............

Posted byPrashanthNaik at 1:10 AM 0 comments  

How women rule the wolrd????????

Here is the Answer.......... :-)

Posted byPrashanthNaik at 9:19 PM 0 comments  

Different ways to be a happy employee

When an employee is under-productive he or she will be the first target when companies look for opportunities to give pink slips.Being happy is always in your hands. A happy employee is more productive and gives more than an unhappy employee. So let's look at some ways to up the happiness factor.

1. Plan your week on Sunday night
Look at your work calendar and plan your week on Sunday night or Monday morning. This would include important meetings, deliverables, a brief summary of things that are pending from last week and any tasks to be achieved during the week. Though this might look like a time management tip, at the end of the week, on Friday night when you re-visit what you have achieved over the last five days, the satisfaction is immense.

2. Undertake activities that you are passionate about even though it might not be in your job profile
Start an initiative that you would love to do irrespective of whether it is required for you to do or not.

  • Send a daily newsletter to your team on the topics that most of them will be interested.
  • Do a presentation on the topic that you are passionate about.
  • Organise a small sports event for your team.
  • Call everyone in your team for a team coffee, breakfast or lunch break
  • Appreciate colleagues in your team or in a cross-functional team who did a great job
  • Write a poem on your team's achievements
  • Arrange a potluck lunch

3. Do not indulge in the blame game
If something goes wrong do not blame others blindly. If you commit a mistake, do not hesitate to accept it. As Gauthama Buddha said, there are three things we can't hide for long: the sun, earth and the truth. Accepting your mistake gracefully will only make you look like a true professional and also give you the satisfaction of not cheating.

4. Communicate more often in person
Utilise all the opportunities where you can speak to an individual in person rather than e-mail or phone. But be aware of the other person's time and availability. Listening to a positive answer from a person will give you more happiness than if it is done over the phone or via e-mail.

5. Know what is happening at your workplace
Will this make a person happy? Truly, yes! Imagine a cricket team that doesn't know how many runs to score to win a match? More than losing the game, the player will never be interested or motivated to play well.

Attend all meetings that are addressed by the CEO to your immediate manager to know what is going to happen around you. It could be the company's growth plan or your department's next big project. Jack Welch mentions in his book Winning "every employee, not just the senior people, should know how a company is doing."

You will also get an extra edge if you are in a position to answer queries raised by your peers or juniors. This is not just for the good reasons, but bad reasons as well. You do not want to be the last employee to know if your company is laying off employees (in the worst case, if you are the one who is on that list).

6. Participate in organisation-level activities
This could be as simple as spending one weekend for a corporate social responsibility activity or attending a recruitment drive to help your HR team or arranging a technical/sports event at the organisational level. Most of these events will be successful as people do come on their own to contribute.

7. Have a hobby that keeps you busy and happy
Many people say their hobby is watching TV or listening to music or reading the newspaper. These aren't hobbies, they are just ways of passing the time. Some hobbies are evergreen and will keep you evergreen as well: dancing, painting, writing short stories, poems, blogs and sharing your experiences.

8. Take up a sport
While choosing a sport make sure that there is physical activity. There is the danger of becoming addicted to sports where there is less physical activity (like computer games, chess, cards etc). Physical activity keeps a person healthy and happy. If you pick up one sport well, you can represent your organisation in corporate sports event too.

9. Keep yourself away from office politics
Politics, as a practice, whatever its profession, has always been the systematic organization of hatreds. -- Henry Brooks Adams

Politics is everywhere and the office is no exception. Playing politics might be beneficial but only for the short term. So the best thing to do is play fair.

10. Wish and smile
More often than not, there are fair chances that the other person will smile back. This could be your security guard at the gate, your receptionist, your office boy, your CEO or your manager -- never forget to wish them and smile.

11. Volunteer for some activity

"The value of a man resides in what he gives and not in what he is capable of receiving." by Albert Einstein

Do at least one activity without expecting anything in return. There is no set frequency for this. This could be once in a day or once in a week or thrice in a week. It could be as simple as making tea at the office for your colleague, helping a colleague who is working in another department by using your skills, dropping your colleague at his door step in your car, going to your manager or colleague to ask if there is any help you can extend, contributing to technical or knowledge management communities in your organisation etc.

This article has been picked from www.rediffmail.com (http://in.rediff.com/getahead/2008/oct/29career.htm)

Posted byPrashanthNaik at 2:33 AM 0 comments  

Who is telling tulu doesn't have script???

Tulu language is one of the five Dravidian languages of South India (Pancha- Bhasha, others are Tamil, Telugu, Kannada and Malayalam). The four major languages spoken today are dominantly spoken in their respective states (Tamilnadu, Andhra Pradesh, Karnataka and Kerala), whereas Tulu is spoken in a small niche, mainly in coastal Karnataka and Northern Karala (Kasaragod district). About 2.5 million people speak Tulu and call it their mother tongue. Tulu nadu is a region where many languages are spoken. While Kannada is the official state language, different ethnic communities in Tulu Nadu speak different languages. Tulu, derived from proto-Dravidian is the predominant language spoken by Hindus of various castes and by the Jains of Tulu Nadu. Konkanasthas and Catholics speak two variants of Konkani. Muslims speak a language of their own that is derived from Tulu as well as Malayalam.

For More Info Please Visit the Site: http://www.boloji.com/places/0020.htm

Posted byPrashanthNaik at 6:12 PM 0 comments  

Dell Recruiting 2007 & 2008 Freshers

Hi all please forward your 2007 & 2008 passed out resumes to below

mentioned emails.


Dell is planning to recruit more than 1000 new graduates for their new

web mail development, in various locations. This is Great Opportunity

for Fresh Graduates to work with Dell


Qualification:


ØBE / B. Tech. - 2008 pass outs (Computer Science, Information

Technology, Electronics and all Electronics, Electronics &

Telecommunication, Electronics & Instrumentation etc.) Ø MCA / M.Sc.

-2007/08: Only Computer Science & Information Technology Branch Ø

B.Sc./BCA - 2007/08: Computer Science, Information Technology,

Physics, Mathematics, Chemistry, Statistics, Electronics


Eligibility Criteria:


ØGraduation 60% and Above


Ø 10th/12th: 60% and above


Ø No Gap in education


Ø Willingness to work in shifts, any platform & any location Ø No

Supplementary (un-cleared) subjects as on date Ø Good Communication

Skills


If you have resumes meeting the above criteria you can send it to:


Bangalore: offcampus.bangalore @dellmail. com


Chennai: offcampus.chennai@ dellmail. com


Hyderabad : offcampus.hyderabad @dellmail. com


It will be great if you could forward this message to any of your

acquaintances who are keen in participating in this test. Please note

that as per our regular hiring norms, the students clearing this test

with go thru the various levels of Interviews before being made the

FTE offers.


Posted byPrashanthNaik at 6:38 PM 0 comments  

Cool Meanings of some of the Words!!!!

Cigarette:

A pinch of tobacco rolled in paper with fire at one end & a fool at the other.
***********

Love affairs :

Something like cricket where one-day internationals are more popular than a five-day test.
***********

Marriage :

It's an agreement in which a man loses his bachelor degree and a woman gains her master
***********

Divorce:

Future tense of marriage
***********

Lecture:

An art of transferring information from the notes of the lecturer to the notes of the students without passing through the minds of either.
***********

Conference:

The confusion of one man multiplied by the number present.
***********

Compromise :

The art of dividing a cake in such a way that everybody believes he got the biggest piece.
***********

Tears:

The hydraulic force by which masculine will power is defeated by feminine waterpower.. .
***********

Dictionary:

A place where divorce comes before marriage.
***********

Conference Room:

A place where everybody talks, nobody listens & everybody disagrees later on.
***********

Ecstasy:

A feeling when you feel you are going to feel a feeling you have never felt before.
***********

Classic:

A book which people praise, but do not read.
***********

Smile:

A curve that can set a lot of things straight.
***********

Office :

A place where you can relax after your strenuous home life.
***********

Yawn:

The only time some married men ever get to open their mouth.
***********

Etc:

A sign to make others believe that you know more than you actually do.
***********

Committee:

Individuals who can do nothing individually and sit to decide that nothing can be done together.
***********

Experience :

The name men give to their mistakes.
***********

Atom Bomb:

An invention to end all inventions.
***********

Philosopher :

A fool who torments himself during life, to be spoken of when dead.
***********

Diplomat:

A person who tells you to go to hell in such a way that you actually look forward to the trip.
***********

Opportunist:

A person who starts taking bath if he accidentally falls into a river.
***********

Optimist :

A person who while falling from Eiffel Tower says in midway See I am not injured yet.
***********

Pessimist:

A person who says that O is the last letter in ZERO, Instead of the first letter in word OPPORTUNITY
***********

Miser:

A person who lives poor so that he can die rich.
***********

Father:

A banker provided by nature.
***********

Criminal:

A guy no different from the rest... Except that he got caught.
***********

Boss:

Someone who is early when you are late and late when you are early.
***********

Politician:

One who shakes your hand before elections and your Confidence after.
***********

Doctor:

A person who kills your ills by pills, and kills you with his bills .

***********

Posted byPrashanthNaik at 1:30 AM 0 comments  

Creative Ads...Watch This...

Posted byPrashanthNaik at 1:30 AM 0 comments  

BEST JOKE COMPETITION

A Chinese walks into a bar in America late one night and he saw Steven Spielberg.
As he was a great fan of his movies,he rushes over to him, and asks for his autograph.


Instead, Spielberg gives him a slap and says,
"You Chinese people bombed our Pearl Habour, get outta here."


The astonished Chinese man replied,
"It was not the Chinese who bombed your Pearl Harbour,
it was the Japanese".


"Chinese, Japanese, Taiwanese, you're all the same," replied Spielberg.


In return, the Chinese gives Spielberg a slap and says,
"You sank the Titanic, my forefathers were on that ship."
Shocked, Spielberg replies, "It was the iceberg that sank the ship, not me."


The Chinese replies,
"Iceberg, Spielberg, Carlsberg, you're all the same."

Posted byPrashanthNaik at 1:30 AM 0 comments  

What is Love???

A group of 4 to 8 year-olds was asked, "What does love mean?"
The answers they gave were broader and deeper than anyone could have
imagined.


--"When my grandmother got arthritis, she couldn't bend
over and paint her toe nails anymore. So my grandfather does it for her all
the time, even when his hands got arthritis too. That's love." (Rebecca -
age 8)


--"When someone loves you, the way they say your name is
different. You know that your name is safe in their mouth." (Billy - age 4)



--"Love is when you go out to eat and give somebody most of
your French fries without making them give you any of theirs." (Chrissy -
age 6 )



--"Love is what makes you smile when you're tired." ( Terri - age 4 )

--"Love is when my mommy makes coffee for my daddy and she
takes a sip before giving it to him, to make sure the taste is OK." (Danny
- age 7)


--"Love is when you tell a guy you like his shirt, then he
wears it everyday" (Tina - age 7)


--"Love is like a little old woman and a little old man who
are still friends even after they know each other so well." (Tommy - age 6
)



--"During my piano recital, I was on a stage and scared. I
looked at all the people watching me and saw my daddy waving and smiling!
He was the only one doing that. I wasn't scared anymore. That's love"
(Cindy -age 8)


--"My mommy loves me more than anybody. You don't see anyone
else kissing me to sleep at night." (Clare - Age 5)



--"Love is when mommy gives daddy the best piece of
chicken." (Elaine - age 5)

--"Love is when your puppy licks your face even after you
left him alone all day." (Mary Ann - age 4 )


Smile and spread some love today.........

Posted byPrashanthNaik at 1:00 AM 0 comments  

How you can bring back the joy in your job

Here's how you can bring back the joy in your job

Feeling trapped in your job? Well, in that case, stop fretting, for here are few ways to help you fall back in love with work.

Psychologist Dr Timothy Sharp, who calls himself ''Mr Happy'' and teaches people how to get more enjoyment out of their work, has offered the tips to make you feel good while working.

"Not everyone will be 100 per cent happy 100 per cent of the time," News.com.au quoted Dr Sharp, as saying.

"You have to be realistic, but you can be more satisfied. Being 60 per cent satisfied with your job is better than being 30 per cent satisfied,” the expert added.

According to the expert, be grateful and focus on the good things about your workplace, your role or your co-workers.

"Many of us have a tendency to focus on the bad things," says Sharp.

"However there are very few organisations that are totally terrible and for every problem or colleague you don’t like there are almost certainly good things and nice people,” the expert added.

If something is making you unhappy, try to fix it.

"Don't complain, do something," says Sharp.

Most employees sit back and criticise, but assume management will step in.

"Even if it's turning up with the right mindset, even if it's doing something nice for the other person, or finding a way to bring fun into the workplace," says Sharp.

According to the expert, stop getting bogged down on details and mind numbing daily minutiae. Instead, focus on how your job fits into the big picture.

Also, remind yourself of the purpose of your job – this will make the work more meaningful.

People often spend a lot of time doing tasks we think are essential, but are really optional. Don't quit your job, just quit doing the stuff you hate, and see if anyone notices, says the expert.

This Article has been copied from samcha.com (http://publication.samachar.com/pub_article.php?id=2735217&navname=General&moreurl=http://publication.samachar.com/sify/websites/general/sifynews.php&homeurl=http://general.samachar.com&nextids=2736301|2735740|2735215|2735216|2735217&nextIndex=0)

Posted byPrashanthNaik at 5:22 AM 0 comments  

Software Testing Glossary

Acceptance Testing: Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

Accessibility Testing: Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

Agile Testing: Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

Application Binary Interface (ABI): A specification defining requirements for portability of applications in binary forms across defferent system platforms and environments.

Application Programming Interface (API): A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

Automated Software Quality (ASQ): The use of software tools, such as automated testing tools, to improve software quality.

Automated Testing:

  • Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing.
  • The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

Backus-Naur Form: A metalanguage used to formally describe the syntax of a language.

Basic Block: A sequence of one or more consecutive, executable statements containing no branches.

Basis Path Testing: A white box test case design technique that uses the algorithmic flow of the program to design tests.

Basis Set: The set of tests derived using basis path testing.

Baseline: The point at which some deliverable produced during the software engineering process is put under formal change control.

Benchmark Testing:Tests that use representative sets of programs and data designed to evaluate the performance of computer hardware and software in a given configuration.

Beta Testing: Testing of a re release of a software product conducted by customers.

Binary Portability Testing: Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

Black Box Testing: Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

Bottom Up Testing:An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

Boundary Testing: Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

Boundary Value Analysis: In boundary value analysis, test cases are generated using the extremes of the input domaini, e.g. maximum, minimum, just inside/outside boundaries, typical values, and error values. BVA is similar to Equivalence Partitioning but focuses on "corner cases".

Branch Testing: Testing in which all branches in the program source code are tested at least once.

Breadth Testing: A test suite that exercises the full functionality of a product but does not test features in detail.

Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner.

C (return to top of page)

CAST: Computer Aided Software Testing.

Capture/Replay Tool: A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

CMM: The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

Cause Effect Graph: A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

Code Complete: Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

Code Coverage: An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

Code Inspection: A formal testing technique where the programmer reviews source code with a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

Code Walkthrough: A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

Coding: The generation of source code.

Compatibility Testing: Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

Component: A minimal software item for which a separate specification is available.

Component Testing: See Unit Testing.

Concurrency Testing:Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

Conformance Testing: The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

Context Driven Testing: The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

Conversion Testing: Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

Cyclomatic Complexity: A measure of the logical complexity of an algorithm, used in white-box testing.

Data Dictionary: A database that contains definitions of all data items defined during analysis.

Data Flow Diagram: A modeling notation that represents a functional decomposition of a system.

Data Driven Testing: Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

Debugging: The process of finding and removing the causes of software failures.

Defect: Nonconformance to requirements or functional / program specification

Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

Depth Testing: A test that exercises a feature of a product in full detail.

Dynamic Testing: Testing software through executing it. See also Static Testing.

Emulator: A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.

End-to-End testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

Equivalence Class: A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

Equivalence Partitioning: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test.

Functional Decomposition: A technique used during planning, analysis and design; creates a functional hierarchy for the software.

Functional Specification: A document that describes in detail the characteristics of the product with regard to its intended features.

Functional Testing: See also Black Box Testing.

  • Testing the features and operational behavior of a product to ensure they correspond to its specifications.
  • Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions.

G (return to top of page)

Glass Box Testing: A synonym for White Box Testing.

Gorilla Testing: Testing one particular module,functionality heavily.

Gray Box Testing: A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.

High Order Tests: Black-box tests conducted once the software has been integrated.

Independent Test Group (ITG): A group of people whose primary responsibility is software testing,

Inspection:A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

Installation Testing:Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Load Testing: See Performance Testing.

Localization Testing: This term refers to making software specifically designed for a specific locality.

Loop Testing: A white box testing technique that exercises program loops.

Metric:A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

Monkey Testing: Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

Mutation Testing: Testing done on the application where bugs are purposely added to it.

Negative Testing: Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

N+1 Testing:A variation of Regression Testing. Testing conducted with multiple cycles in which errors found in test cycle N are resolved and the solution is retested in test cycle N+1. The cycles are typically repeated until the solution reaches a steady state and there are no errors. See also Regression Testing.

Path Testing: Testing in which all paths in the program source code are tested at least once.

Performance Testing: Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

Positive Testing: Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

Quality Assurance: All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

Quality Audit:A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

Quality Circle:A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

Quality Control: The operational techniques and the activities used to fulfill and verify requirements of quality.

Quality Management: That aspect of the overall management function that determines and implements the quality policy.

Quality Policy: The overall intentions and direction of an organization as regards quality as formally expressed by top management.

Quality System: The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

Race Condition: A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

Ramp Testing: Continuously raising an input signal until the system breaks down.

Recovery Testing:Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

Release Candidate:A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing.

Scalability Testing: Performance testing focused on ensuring the application under test gracefully handles increases in work load.

Security Testing:Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

Smoke Testing: A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

Soak Testing:Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

Software Requirements Specification:A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/

Software Testing: A set of activities conducted with the intent of finding errors in software.

Static Analysis: Analysis of a program carried out without executing the program.

Static Analyzer: A tool that carries out static analysis.

Static Testing: Analysis of a program carried out without executing the program.

Storage Testing:Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

Structural Testing: Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

Testability:The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

Testing:

  • The process of exercising software to verify that it satisfies specified requirements and to detect errors.
  • The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829).
  • The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component.

Test Automation: See Automated Testing.

Test Bed: An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

Test Case:

  • Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.
  • A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

Test Driven Development:Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

Test Driver: A program or test tool used to execute a tests. Also known as a Test Harness.

Test Environment:The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

Test First Design:Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

Test Harness: A program or test tool used to execute a tests. Also known as a Test Driver.

Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.

Test Procedure: A document providing detailed instructions for the execution of one or more test cases.

Test Scenario: Definition of a set of test cases or test scripts and the sequence in which they are to be executed.

Test Script: Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

Test Specification: A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

Test Suite: A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

Test Tools: Computer programs used in the testing of a system, a component of the system, or its documentation.

Thread Testing: A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

Top Down Testing:An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

Total Quality Management: A company commitment to develop a process that achieves high quality product and customer satisfaction.

Traceability Matrix: A document showing the relationship between Test Requirements and Test Cases.

Usability Testing: Testing the ease with which users can learn and use a product.

Use Case:The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

User Acceptance Testing: A formal product evaluation performed by a customer as a condition of purchase.

Unit Testing: Testing of individual software components.

Validation:The process of evaluating software at the end of the software development process to ensure compliance with software requirements. The techniques for validation is testing, inspection and reviewing.

Verification:The process of determining whether of not the products of a given phase of the software development cycle meet the implementation steps and can be traced to the incoming objectives established during the previous phase. The techniques for verification are testing, inspection and reviewing.

Volume Testing:Testing which confirms that any values that may become large over time (such as accumulated counts, logs, and data files), can be accommodated by the program and will not cause the program to stop working or degrade its operation in any manner.

Walkthrough: A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.

White Box Testing: Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing. Contrast with Black Box Testing.

Workflow Testing: Scripted end-to-end testing which duplicates specific workflows which are expected to be utilized by the end-user.

Posted byPrashanthNaik at 8:28 PM 1 comments  

Take the initiative when your boss is not around

A good leader makes every follower inspired and productive – be it community leaders, spiritual leaders or corporate leaders. In the presence of the master, everyone feels safe and secure. But the real challenge is when the big boss is not around.

There are two eventualities which may force a boss not to come to work. Either it was preplanned and others were informed about his or her absence, or some emergency came up and the boss had to take a quick decision to go somewhere else.

In either case, the subordinates are supposed to take charge. Chanakya says: “The minister should take steps in case of calamity of the king” (5.6.1.). So, if the king is not around, the minister should take charge. If the Director or CEO is not present, the managers; and if the boss is not around, the subordinates.


But how can one go about this?

1) Observe the boss

So many of us follow a leader, yet forget to understand the leader. Following the leader is good, but understanding the leader is much more important. This is a skill that every person has to develop.

Whenever you are around the boss, observe him. Ask yourself: “Why does he do this?” “What does he really want?” Try to read between the lines and listen to the unsaid words. As the great Jesuit priest and psychotherapist Anthony de Mello said: “The words of a master seem ordinary, but have foreign meaning.”

2) Start taking small decisions

Good leaders expect their team to take the right decisions in the overall interest of the company or country. However, if you do not have this habit, start taking small decisions yourself even when the boss is around. Taking small decisions will give you the confidence needed to take big decisions.

3) Take charge

Finally, when the boss is not around, the followers have to take charge. There should not be a vacuum just because the leader is absent. The show must go on. Each person should think like the boss and be a good boss himself.

Once, the leader of a successful organisation was asked how the good performance was continued even after its founder passed away. He replied: “The master is gone, but he left behind master-pieces!”

Posted byPrashanthNaik at 1:53 AM 0 comments  

Husband & Wife - Just for Fun

Husband & Wife - Why divorce?

In a divorce court a woman requested the judge: "Your
honor, I want to divorce my husband." "But why ?"
asked the judge. She replied, "Because he is not
faithful to me." The judge asked, "How do you know ?"
She replied, "My lord, not a single child resembles
him."


Husband & Wife - Love Your Enemy

>From his death bed, the husband called his wife and
said, "One month after I die I want you to marry
Samy." "Samy! But he is your enemy !" "Yes, I know
that ! I've suffered all these years so let him suffer
now."


Husband & Wife - Wedding Ring

At the cocktail party, one woman said to another,
"Aren't you wearing your wedding ring on the wrong
finger? " The other replied, "Yes I am, I married the
wrong man."


Husband & Wife - Why?

" Dad, I was away for a week. Yesterday I sent a fax
to my wife I'd be home that night, and when I got into
my room I found my wife in another man's arms. " Why,
Dad ? Tell me why!" Dad kept silent for a few minutes,
then coolly said, "Maybe, Son, she didn't get the
fax."


Husband & Wife - Same Service

A husband visited a marriage counselor and said, "When
we were first married, I would come home from the
office, my wife would bring my slippers and our cute
little dog would run around barking. Now after ten
years it's all different, I come home, the dog brings
the slippers and my wife runs around barking." "Why
complain?" said the counselor. "You're still getting
the same service!"


Husband & Wife - Talk About Husband

One woman told another : "My neighbour is always
speaking ill of her husband, but look at me, my
husband is foolish, lazy and a coward; but have I ever
said anything bad about him?"


Husband & Wife - Love To Do

A wife, one evening, drew her husband's attention to
the couple next door and said, "Do you see that
couple? How devoted they are? He kisses her every time
they meet. Why don't you do that?" "I would love to."
Replied the husband. "But I don't know her

Posted byPrashanthNaik at 10:38 PM 0 comments  

A Woman's Poem ---

All Woman Will Like this... :-)..Enjoy Maadi..
For Already married guys I can't help it(They may have gone through this scenario)..
This is a warning note for all eligible bachelors ..

Please click on the picture if you can't read it properly.. :-)..

Posted byPrashanthNaik at 12:13 AM 0 comments  

Corporate Culture! - Some Funny Definitions

On a lighter note

1) Project Manager is a person who thinks nine women can deliver a baby in one month.

2) Developer is a person who thinks it will take 18 months to deliver a baby.

3) Onsite Coordinator is one who thinks single woman can deliver nine babies in one month.

4) Client is the one who doesn't know why he wants a baby.

5) Marketing Manager is a person who thinks he can deliver a baby even if no man and woman are available.

6) Resource Optimization Team thinks they don't need a man or woman; They'll produce a child with zero resources.

7) Documentation Team thinks they don't care whether the child is delivered, they'll just document 9 months.

8) Quality Auditor is the person who is never happy with the PROCESS to produce a baby.

And lastly...

9) Tester is a person who always tells his wife that this is not the right baby.

Posted byPrashanthNaik at 12:08 AM 1 comments  

ACI WorlWide India Sports Day.....

Few Moments ..:-)




Group Photo -------

Posted byPrashanthNaik at 11:11 PM 0 comments  

Effort Never Fail........Watch this.. :-)

Posted byPrashanthNaik at 9:51 PM 0 comments  

Software Testing Types

  • ACCEPTANCE TESTING. Testing to verify a product meets customer specified requirements. A customer usually does this type of testing on a product that is developed externally.
  • BLACK BOX TESTING. Testing without knowledge of the internal workings of the item being tested. Tests are usually functional.
  • COMPATIBILITY TESTING. Testing to ensure compatibility of an application or Web site with different browsers, OSs, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.
  • CONFORMANCE TESTING. Verifying implementation conformance to industry standards. Producing tests for the behavior of an implementation to be sure it provides the portability, interoperability, and/or compatibility a standard defines.
  • FUNCTIONAL TESTING. Validating an application or Web site conforms to its specifications and correctly performs all its requigreen functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product's user interface, APIs, database management, security, installation, networking, etcF testing can be performed on an automated or manual basis using black box or white box methodologies.
  • INTEGRATION TESTING. Testing in which modules are combined and tested as a group. Modules are typically code modules, individual applications, client and server applications on a network, etc. Integration Testing follows unit testing and precedes system testing.
  • LOAD TESTING. Load testing is a generic term covering Performance Testing and Stress Testing.
  • PERFORMANCE TESTING. Performance testing can be applied to understand your application or WWW site's scalability, or to benchmark the performance in an environment of third party products such as servers and middleware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.
  • REGRESSION TESTING. Similar in scope to a functional test, a regression test allows a consistent, repeatable validation of each new release of a product or Web site. Such testing ensures reported product defects have been corrected for each new release and that no new quality problems were introduced in the maintenance process. Though regression testing can be performed manually an automated test suite is often used to greenuce the time and resources needed to perform the requigreen testing.
  • SMOKE TESTING. A quick-and-dirty test that the major functions of a piece of software work without bothering with finer details. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.
  • STRESS TESTING. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desigreen result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.
  • SYSTEM TESTING. Testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.
  • UNIT TESTING. Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.
  • WHITE BOX TESTING. Testing based on an analysis of internal workings and structure of a piece of software. Includes techniques such as Branch Testing and Path Testing. Also known as Structural Testing and Glass Box Testing.

  • TEST BED :

    A testbed is a platform for experimentation for large development projects. Testbeds allow for rigorous, transparent and replicable testing of scientific theories, computational tools, and other new technologies.

    The term is used across many disciplines to describe a development environment that is shielded from the hazards of testing in a live or production environment.

    In software, the hardware and software requirements are known as the testbed. This is also known as the test environment.

    Testbeds are also pages on the internet where the public is given the opportunity to test CSS or HTML they have created and are wanting to see the outcome.

Posted byPrashanthNaik at 8:33 PM 1 comments  

WordLinx - Get Paid To Click