Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Manual Testing

Manual Testing

Ratings: (0)|Views: 61|Likes:
Published by abhijeetk3
software testing
software testing

More info:

Published by: abhijeetk3 on Dec 18, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Manual Testing 
Testing is process execution of application in controlled manner with the intent of finding the errors. It is nothing but “Detection”.
The Quality Assurance involves through out the software development process tomonitor and improve the process, making sure that agreed upon standards andprocedures are followed and ensuring that problems are found and dealt with it. Itis oriented for “Prevention”.
Solving problems is a high-visibility process; preventing problems is low-visibility.This is illustrated by an old parable.
Software Industry
In India itself, Software industry growth has been phenomenal.
IT field has enormously grown in the past 50 years.
IT industry in India is expected to touch 10,000 crores of which software share isdramatically increasing.
Software Crisis
Software cost/schedules are grossly inaccurate.
Cost overruns of several times, schedule slippage’s by months, or even years arecommon.
Productivity of people has not kept pace with demand
Added to it is the shortage of skilled people.
Quality of software is than desired
Error rates of released software leave customer dissatisfied…Threatening the verybusiness.
Software Myths
Management Myths
Software Management is different.
Why change or approach to development?
We have provided the state-of-the-art hardware.
Problems are technical
If project is late, add more engineers.
We need better people.
Developers Myths
We must start with firm requirements
Why bother about Software Engineering techniques, I will go to terminal andcode it.
Once coding is complete, my job is done.
How can you measure the quality..it is so intangible.
Customer’s Myth
A general statement of objective is good enough to produce software.
Anyway software is “Flexware”, it can accommodate my changing needs.
What do we do ?
Use Software Engineering techniques/processes.
Institutionalize them and make them as part of your development culture.
Adopt Quality Assurance Frameworks : ISO, CMM
Choose the one that meets your requirements and adopt where necessary.
Software Engineering:
Requirements Gathering
Quick DesignBuild PrototypeRefine RequirementsCust
omer evaluation of the prototype
MaintainReuirements Analsis
Software Engineering is an engineering discipline concerned with thepractical problems of developing large software.
Software Engineering discipline tracks both technical & non-technicalproblems associated with software development.
Challenge for Software Engineers is to produce high quality softwarewith finite amount of resources & within a predicted schedule.
Apply Engineering Concepts to developing Software
Apply Engineering Concepts to removing crisis.
Software Engineering Process
Consists of Three generic Phases:
Definition, Development, and Maintenance.1.Definition (What)
Customer Contact, Planning, Requirement Analysis.
2.Development Phase (How)
Design, Coding, Testing.
3.Maintenance Phase (Change)
Correction, Adaptation, Enhancement, Reengineering.
4.Support Activities
Quality Assurance, Configuration Management.
Software Life Cycle Models
Prototyping Model
Waterfall Model – Sequential
Spiral Model
V Model - Sequential
Prototyping Model of Software Development
A prototype is a toy implementation of a system; usually exhibiting limited functional capabilities,low reliability, and inefficient performance. There are several reasons for developing a prototype.An important purpose is to illustrate the input data formats, messages, reports and the interactivedialogues to the customer. This a valuable mechanism for gaining better understanding of thecustomer’s needs. Another important use of the prototyping model is that it helps criticallyexamine the technical issues associated with the product development.
Acceptance by Customer
ValidationValidationOperation and MaintenanceInstallation Testing and IntegrationDetailed Design
Classic Waterfall Model
In a typical model, a project begins with feasibility analysis. On successfully demonstrating thefeasibility of a project, the requirements analysis and project planning begins. The designstarts after the requirements analysis is complete, and coding begins after the design iscomplete. Once the programming is completed, the code is integrated and testing is done. Onsuccessful completion of testing, the system is installed. After this, the regular operation andmaintenance of the system takes place.
ReportRequirement DocumentAnd Project PlanSystem DesignDocumentDetailedDesign DocumentProgramsTest Plan, Test ReportAnd ManualsInstallationReport
Typical Spiral Model

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->