Advantages of Agile:

Agile methodology has an adaptive team which is able to respond to the changing requirements.

The team doesn’t have to invest time and effort and finally find that by the time they delivered the product, the requirement of the customer have changed.

Face to face communication and continuous inputs from customer representative leaves no space for guesswork

The documentation is crisp and to the point to save time

The end result is high quality software in the least possible time duration and a satisfied customer.

Disadvantage:

In case of some software deliverable s, especially the large ones, it is difficult to assess the effort required at the beginning of the software development cycle.

There is a lack of emphasis on necessary designing and documentation.

The project can easily get taken off track if the customer representative is not clear what final outcome they want.

Only senior programmers are capable of taking the kind of decision required during the development process. Hence it has no place for newbie programmers, unless combined with experience resources.

Ans: The following are the fields the test case will have.
Expected results Test case ID
Description
Precondition
Step Name
Step Description

 All SDLC models have their strengths and weakness. To decide which SDLC model is best for my project I have to look at various parameters of the project like complexity, requirements are frozen out. For small projects with frozen requirements I would recommend waterfall, large project with frozen requirements, I would recommend v-model, for project without frozen requirements. I would recommend incremental iterative model like agile methodology.

Ans: Component testing is white box testing.

A prototype is a 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 interactive dialogues to the customer. This is a valuable mechanism for gaining better understanding of the customer needs. Another important use of prototyping is model is that it helps to examine critically the issues which are technical and associated with the product development.

I have a good idea on what a stub and driver are and how to implement them.  However I have not got any opportunity to write stubs and drivers because component integration was handled by the development team in my earlier projects. If I am supposed to write stubs or drivers in the current project I am confident that I can handle it.

Ans: The test plan is prepared by my manager, but I share views from my module point of view on certain points to be included in the Test plan. A few areas I share my views about my module are:
Anything to include in the out of scope section
Possible and preferred areas to automate
Any specific type of testing required which is very specific to my module.

 No significant issues were reported after the release.

Ans: User story is the method of documenting requirements in agile model.

 A failed test case is one we executed and the result was failed i.e. the actual result was different from the expected result where no run test case is that one we are not able to execute because the functionality cannot be reached due to another failed test case.