This is the reason you should change your password

Change your password :)

Ramya was about to leave office after finishing her work. She got a call from her husband Karthik ,

RAMYA: "Hello, yes Karthi".
KARTHIK: "Ramya, can you open my gmail and get a print out of the mail from that US consultant I forgot to take it in my office"
RAMYA: "Yes, I can, I need your password"
KARTHIK: "jeni22091980"
RAMYA: "Ok fine"

She takes the print out and logs out. Some thought struck her mind now.
JENI happens to be his college mate. Hmmm...

She decides not to discuss this with Karthik . She simply opens her mail box and changes the password from "mohan143" to "karthikramya" and leaves for home!

Wonderful definitions of Software Jobs

Here are quite wonderful and nice definitions of Softaware Jobs.

 

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.

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

10) HR is a person who thinks that a donkey can deliver a human baby if given 9 month

QUALCOMM BREW and BREW PEK References

Recently, I've researched into BREW PEK to improve the current test framework of which I'm in charge. As a result, I found quite useful web page references. So I share them.

Here are web page references (exactly pdf) regarding BREW and PEK (Porting Evaluation Kit) in QUALCOMM

Generally speaking, layered architecture as well as its test framework is in the limelight especially in embedded software world.

PEK (Porting Evaluation Kit) is well-designed test framework. If you are trying to devise a test framework for your software platform which is taking away time both of developers and of test engineers, refer to BREW PEK.

※ Since pdf files are linked, it would take much time to load pages. You had better download and see them in Acrobat.

[1] What is BREW?

http://www.developer.com/ws/brew/article.php/1454711

Briefly but clearly explains BREW in Developer.com Wireless

[2] Binary Runtime Environment for Wireless

http://en.wikipedia.org/wiki/BREW

Explanation on BREW in Wikipedia

[3] Commercialization, PEK & Custom OAT Modules (2005)

http://brew.qualcomm.com/bnry_brew/pdf/brew_2005/t102_abney_qualcomm.pdf

About PEK and how to extend OAT which verifies functions of ported BREW

[4] Writing an Efficient BREW Porting Layer (2006)

http://brew.qualcomm.com/bnry_brew/pdf/brew_2006/tech601_%20kalyanakrishnan_brewlayers.pdf

Generally, vendors port BREW into their handsets. Namely, they make BREW OEM which is glue between BREW and handset APIs. This slide describes that.

[5] Application Commercialization: The Role of TRUE BREW Testing (TBT)

http://brew.qualcomm.com/bnry_brew/pdf/brew_2006/tech801_toerien_applications.pdf 2006

http://brew.qualcomm.com/brew_bnry/pdf/brew_2005/t601_johnson_qualcomm.pdf 2004

About TRUE BREW Testing (TBT) which verify BREW Applications.

PEK check whether BREW is correctly ported or not, while TBT tests BREW Applications on BREW.

[6] Debugging BRW Porting Layer (June 2, 2005)

http://brew.qualcomm.com/brew_bnry/pdf/brew_2005/t203_ambley_qualcomm.pdf

About BREW Debugging