http://www.extremeprogramming.org/rules/functionaltests.html the acceptance test picture is the file that is linked to the questions

please answer the questions according to the word limit please fulfill the requirements of words.

Read: Acceptance Tests in XP http://www.extremeprogramming.org/rules/functionaltests.html 1. When is testing done in the waterfall SDLC? What are the disadvantages? (200 - 300 words) 2. What is acceptance testing and what type of objects are tested? (150 200 words) 3. Describe acceptance testing in extreme programming (200 250 words) 4. Use extreme prototyping SDLC to document the designs and tests for the following web page: Sign in E-mail address or mobile phone number Password Forgot Password Sign in New to Our Store? Create your account By signing in you are agreeing to our Conditions of Use and Sale and our Privacy Notice Acceptance Tests Lessons Learned Extreme Programming Full Size Tex Scenarios Nee U Bir Projecte Rese Eugs Customer System Harning Uncertain Content Estes Esimes Spike arter Acceptance tests are created from user Extreme Programming Project stories. During an iteration the user stories selected during the iteration planning meeting User Stories will be translated into acceptance tests. The customer specifies scenarios to test when a Architectural de Release Pin. Icration Visien. Acceptance or Small Spike Tests Releases user story has been correctly implemented. A story can have one or many acceptance tests, what ever it takes to ensure the functionality works. itself. In either case XP requires development Acceptance tests are black box system to have much closer relationship with QA. tests. Each acceptance test represents some Acceptance tests should be automated expected result from the system. Customers so they can be run often. The acceptance test are responsible for verifying the correctness of score is published to the team. It is the team's the acceptance tests and reviewing test scores responsibility to schedule time each iteration to decide which failed tests are of highest to fix any failed tests. priority. Acceptance tests are also used as The acceptance tests regression tests prior to a production release. changed from functional tests. This better A user story is not considered complete reflects the intent, which is to guarantee that a until it has passed its acceptance tests. This customers requirements have been met and the means that new acceptance tests must be system is acceptable. created each iteration or the development team will report zero progress. Quality assurance (QA) is an essential Portland XP part of the XP process. On some projects QA Pattern is done by a separate group, while on others QA will be an integrated into the development team name was Programming.com Read: Acceptance Tests in XP http://www.extremeprogramming.org/rules/functionaltests.html 1. When is testing done in the waterfall SDLC? What are the disadvantages? (200 - 300 words) 2. What is acceptance testing and what type of objects are tested? (150 200 words) 3. Describe acceptance testing in extreme programming (200 250 words) 4. Use extreme prototyping SDLC to document the designs and tests for the following web page: Sign in E-mail address or mobile phone number Password Forgot Password Sign in New to Our Store? Create your account By signing in you are agreeing to our Conditions of Use and Sale and our Privacy Notice Acceptance Tests Lessons Learned Extreme Programming Full Size Tex Scenarios Nee U Bir Projecte Rese Eugs Customer System Harning Uncertain Content Estes Esimes Spike arter Acceptance tests are created from user Extreme Programming Project stories. During an iteration the user stories selected during the iteration planning meeting User Stories will be translated into acceptance tests. The customer specifies scenarios to test when a Architectural de Release Pin. Icration Visien. Acceptance or Small Spike Tests Releases user story has been correctly implemented. A story can have one or many acceptance tests, what ever it takes to ensure the functionality works. itself. In either case XP requires development Acceptance tests are black box system to have much closer relationship with QA. tests. Each acceptance test represents some Acceptance tests should be automated expected result from the system. Customers so they can be run often. The acceptance test are responsible for verifying the correctness of score is published to the team. It is the team's the acceptance tests and reviewing test scores responsibility to schedule time each iteration to decide which failed tests are of highest to fix any failed tests. priority. Acceptance tests are also used as The acceptance tests regression tests prior to a production release. changed from functional tests. This better A user story is not considered complete reflects the intent, which is to guarantee that a until it has passed its acceptance tests. This customers requirements have been met and the means that new acceptance tests must be system is acceptable. created each iteration or the development team will report zero progress. Quality assurance (QA) is an essential Portland XP part of the XP process. On some projects QA Pattern is done by a separate group, while on others QA will be an integrated into the development team name was Programming.com