Answer / saranya c

SDLC:
Software development life cycle
* Development team and testing team both are involved in
the SDLC process
STLC:
Software testing life cycle
* Testing team only involved in the STLC process
Difference:

SDLC:
Requirement
|
Designing
|
Coding
|
Testing
|
Reports
|
Implementation

STLC:
Requirement
|
Test Plan
|
Test CASES
|
Execute the test cases

|

REPORTING

* Both are got the requirement from client
When developer design the product at a time tester doing
the test plan
When develper prepare a coding at a time testing prepare a
test cases
When developer release the 1sr release to testing team ,
now tester execute the test cases

Answer / yogesh d

-> SDLC:- System Development Life Cycle (SDLC) is
structured way to develop a Software product.

We have different steps in the SDLC.

Requirement Analysis >> Design >> Implementation (Coding)
>> Verification (Testing) >> Maintenance.

We have 3 SDLC Models.

1. Waterfall Model
2. Spiral Model
3. Iterative and Incremental development

Waterfall Model:- Waterfall Model having the following
phases

1. Requirements analysis
2. Software Design (or Coding)
3. Integration
4. Testing (or Validation)
5. Deployment (or Installation)
6. Maintenance
In a strict Waterfall model, after each phase is finished,
it proceeds to the next one. Reviews may occur before
moving to the next phase which allows for the possibility
of changes (which may involve a formal change control
process). Reviews may also be employed to ensure that the
phase is indeed complete

2. Spiral Model:- The spiral model is a software
development process combining elements of both design and
prototyping-in-stages, in an effort to combine advantages
of top-down and bottom-up concepts

A top-down approach (is also known as step-wise design) is
essentially the breaking down of a system to gain insight
into its compositional sub-systems. In a top-down approach
an overview of the system is first formulated, specifying
but not detailing any first-level subsystems. Each
subsystem is then refined in yet greater detail, sometimes
in many additional subsystem levels, until the entire
specification is reduced to base elements

A bottom-up approach is the piecing together of systems to
give rise to grander systems, thus making the original
systems sub-systems of the emergent system. In a bottom-up
approach the individual base elements of the system are
first specified in great detail. These elements are then
linked together to form larger subsystems, which then in
turn are linked, sometimes in many levels, until a complete
top-level system is formed

Iterative and Incremental development:- Iterative
development prescribes the construction of initially small
but ever larger portions of a software project to help all
those involved to uncover important issues early before
problems or faulty assumptions can lead to disaster.

What is Equivalence partitioning,Boundary value analysis,Decision table testing,State transition testing,Use case testing. Plz explain with example and differences if any

3 Answers  

---

There are 2 clients for a server and that clients can access the data from the server only for 10 days. so how will you test this scenario manually? Can u pls help me?..

4 Answers   eMids, TCS,

---

IS IT necessary to know different languages like (Chinese,Germany etc) to do localisation/internationalisation testing??? real time ..plsss

1 Answers  

---

How test case is differ from test plan .give an suitable example

5 Answers  

---

where do u store Testcases and where do u store versions

2 Answers  

---

---

what is call-pair ,cross testing,

2 Answers  

---

What is the scope of manual testing?Please let me know because I want my carrer as a tester.

0 Answers  

---

wht is bug, deffect,issue,error

5 Answers  

---

how to write defects in excel sheets when defects occured

0 Answers  

---

What is meant by Testware?

2 Answers  

---

(questions asked in interview)hi every one can any one please answer to this questions.these questions were asked in an interview.i have another interview next week . 1.when the time schedule is tight how will you approch the testing,and the relese is nearing and we need to finish testing how can we follow in that case.do we need to exicute all the test cases or can priortise and leave some to next relase. 2. when a new feature is added to the existing application we need to add new test cases but after that do we need to change all the existing test cases and while running do we need to exicute entire application test cases or only the new feature test cases and related new feature test cases. 3.do you have any situation where you have to write and exicute the test cases same time, how will you follow.does it happens in real time. 4.example of bug which is not reproducible.like tester say that there is bug and developer say no can some example of such bugs. 5.during regression testing some times do we need to add new some additional test cases to test that bug.

2 Answers  

---

Test case on Air conditionar

1 Answers  

---