A Blog for quality professional

Archive for September, 2010

To……M.S.S.G.J.S

you said you would never do anything to hurt me. Then why are you causing me so much pain?

deepest love is de biggest sorrow in this world never love a person more than ur life it will hurt yu a lot when yu realise that ur love was not in their life…..

LOVE FEELS LIKE hEAVEN, BUT HURTS LIKE hELL

She lied that she loves me for my happiness… I lied that I hate her for her happiness…

I hide my tears

when i talk with u

But i can’t lie

2 my own eyes.

u left me with all the pain… where i have to take them all alone… but u took all the happiness with u, which i gave u with endless love

I AM STILL AWATING YOU…………

LET SEE TILL WHEN…………………..

S.S.J.S.G.J.S

Concept of S.E.I C.M.M IN International Software Corporate

SEI = ‘Software Engineering Institute’ at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes.

· CMM = ‘Capability Maturity Model’, developed by the SEI. It’s a model of 5 levels of organizational ‘maturity’ that determine effectiveness in delivering quality software. It is geared to large organizations such as large U.S. Defense Department contractors. However, many of the QA processes involved are appropriate to any organization, and if reasonably applied can be helpful. Organizations can receive CMM ratings by undergoing assessments by qualified auditors.

Level 1 – characterized by chaos, periodic panics, and heroic efforts required by individuals to successfully complete projects. Few if any processes in place; successes may not be repeatable.

Level 2 – software project tracking, requirements management, realistic planning, and configuration management processes are in place; successful practices can be repeated.

Level 3 – standard software development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is in place to oversee software processes, and training programs are used to ensure understanding and compliance.

Level 4 – metrics are used to track productivity, processes, and products. Project performance is predictable, and quality is consistently high.

Level 5 – the focus is on continuous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required.

· ISO = ‘International Organization for Standards’ – The ISO 9001, 9002, and 9003 standards concern quality systems that are assessed by outside auditors, and they apply to many kinds of production and manufacturing organizations, not just software. The most comprehensive is 9001, and this is the one most often used by software development organizations. It covers documentation, design, development, production, testing, installation, servicing, and other processes. ISO 9000-3 (not the same as 9003) is a guideline for applying ISO 9001 to software development organizations. The U.S. version of the ISO 9000 series standards is exactly the same as the international version, and is called the ANSI/ASQ Q9000 series. The U.S. version can be purchased directly from the ASQ (American Society for Quality) or the ANSI organizations. To be ISO 9001 certified, a third-party auditor assesses an organization, and certification is typically good for about 3 years, after which a complete reassessment is required. Note that ISO 9000 certification does not necessarily indicate quality products – it indicates only that documented processes are followed.

Engineer’s life

Dear all this poem is based on true story………….

Consider your self as a character of the story (Pappu) and realized the today life

Belive me it realy work…………………….

Dedicated to all my colleagues , senior junior(India & Abroad)

************ ISSUED IN PUBLIC INTEREST*************

Pareshaan thi Pappu ki wife
Non-happening thi jo uski life
Pappu ko na milta tha aaram
Office main karta kaam hi kaam

Pappu ke boss bhi the bade cool
Promotion ko har baar jate the bhul
Par bhulte nahi the wo deadline
Kaam to karwate the roz till nine

Pappu bhi banna chata tha best
Isliye to wo nahi karta tha rest
Din raat karta wo boss ki gulami
Appraisal ke ummid main deta salami

Din guzre aur guzre fir saal
Bura hota gaya Pappu ka haal
Pappu ko ab kuch yaad na rehta tha
Galti se Biwi ko Behenji kehta tha

Aakhir ek din Pappu ko samjh aaya
Aur **** di usne Appraisal ki moh maya
Boss se bola, “Tum kyon satate ho ?”
“Appraisal ke laddu se buddu banate ho”

“Promotion do warna chala jaunga”
“Appraisal dene par bhi wapis na aunga”
Boss haans ke bola “Nahi koi baat”
“Abhi aur bhi Pappus hai mere paas”

“Yeh duniya Pappuon se bhari hai”
“Sabko bas aage badhne ki padi hai”
“Tum na karoge to kisi aur se karaunga”
“Tumhari tarah Ek aur Pappu banaunga”

Prototype Development

The goal of prototyping based development is to counter the first two limitations of the waterfall model discussed earlier. The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an “actual feel” of the system, since the interactions with prototype can enable the client to better understand the requirements of the desired system.

Prototyping is an attractive idea for complicated and large systems for which there is no manual process or existing system to help determining the requirements. In such situations letting the client “plan” with the prototype provides invaluable and intangible inputs which helps in determining the requirements for the system. It is also an effective method to demonstrate the feasibility of a certain approach. This might be needed for novel systems where it is not clear that constraints can be met or that algorithms can be developed to implement the requirements. The process model of the prototyping approach is shown in the figure below.

Prototyping Model
Prototyping Model

The basic reason for little common use of prototyping is the cost involved in this built-it-twice approach. However, some argue that prototyping need not be very costly and can actually reduce the overall development cost. The prototype are usually not complete systems and many of the details are not built in the prototype. The goal is to provide a system with overall functionality. In addition, the cost of testing and writing detailed documents are reduced. These factors helps to reduce the cost of developing the prototype. On the other hand, the experience of developing the prototype will very useful for developers when developing the final system. This experience helps to reduce the cost of development of the final system and results in a more reliable and better designed system.

Choosing Software Testing as your Career

If you are freshers and willing to choose software testing as your career then this is a must read!

a common answer to all questions whether you should choose software testing as your career or not?

Let me first explain in brief about software testing. Software testing and quality control are the processes by means of which application quality is improved. Software testing is done in each phase of product life cycle i.e from requirement specifications , design, coding, to the user acceptance.

Many complex software structures require in depth analytical and technical skill to test the applications. Knowledge of programming languages is required for unit testing, scripting skill essential for Automation testing.

Now we will speak about your career in software testing. No one can guide you choosing your career more than you! Its right and you are the only person to decide your career.
Do self-assessment to figure out where you can fit well. Do study of your skills, interests, strengths, weaknesses.

Ask some questions to your self like:
What is your goal in life?
What will increase your satisfaction and skill?
What is your interest?
Which skills you have developed in your life till now?
Which training you did that can be applied to future job?

By answering these questions you will automatically come to decision.

To switch to software testing career What skills you will require? Is the most important question I think.

In my previous post what makes a good test engineer, I mentioned some of the software testing required skills.

1. Communication: Customer communication as well as team communication most important for this job. Written communication as well!

2. Technical skill: As I mentioned earlier for testing technical domain skill in languages is important.

Some of the Testing skills are:
Project life cycle,
Testing concepts,
Knowledge of testing types,
Programming languages familiarity,
Database concepts,
Test plan idea,
Ability to analyze requirements,
Documentation skill,
Testing tools

3. Leadership quality
4. Analytical and judging skill

Don’t worry if you don’t have some of the skills mentioned above. You can always learn the things if you have interest. Non-IT personas can also grow fast by gaining necessary skills.

So finally selecting testing as your career ask one question to yourself:

———For all upcoming  I.T.M Ambassador


My Real Friends

“Even though we’ve changed (Shobhit,Rohan,Abhi,Satyam,Pankaj and Rucchi) and we’re all finding our own place in the world, we all know that when the tears fall or the smile spreads across our face, we’ll come to each other because no matter where this crazy world takes us, nothing will ever change so much to the point where we’re not all still friends.”

Testing Issues

Dear all,following question is based on my own personal experience and you can say that this question is often asked whenever you are facing some technical face to face. hope so its beneficial  for you

content referenced from  popular Testing sites

Why does software have bugs?

What’s the big deal about ‘requirements’?

What’s the role of documentation in QA?

What steps are needed to develop and run software tests?

What’s a ‘test plan’?

What’s a ‘test case’?

What should be done after a bug is found?

What if the software is so buggy it can’t really be tested at all?

What if there isn’t enough time for thorough testing?

What if the project isn’t big enough to justify extensive testing?

What can be done if requirements are changing continuously

What if the application has functionality that wasn’t in the requirements?

.How can Software QA processes be implemented without stifling productivity?

What if an organization is growing so fast that fixed QA processes are impossible?

How does a client/server environment affect testing?

How can World Wide Web sites be tested? (refer to my web testing post)

What is ‘Software Quality Assurance’?

What are some recent major computer  failures caused by software bugs?

Why is it often hard for management to get serious about quality assurance?

What is verification? validation?

What kinds of testing should be considered?

What are  common problems in the  software development process?

What is SEI? CMM? ISO? IEEE? ANSI? Will it help?

Will automated testing tools make testing easier?

hope so its beneficial  for you

content referenced from  popular Testing sites

Tag Cloud