Alpha and Beta Testing-Acceptance Testing

            Alpha and Beta Testing

Acceptance Testing
  • Making sure the software works correctly for intended user in his or her normal work environment.
  • Alpha test (version of the complete software is tested by customer under the supervision of the developer at the developer’s site)
  • Beta test (version of the complete software is tested by customer at his or her own site without the developer being present)
  • Software can be built as a custom software, (e.g. MIS for a particular organization) for one customer or as a product to be used by many customers.
  • When it is developed as custom software, a series of acceptance tests are conducted to enable the customer to validate all requirements.
  • They are conducted by the end-user rather than software engineers and may be conducted over a period of weeks or months.
  • In case of software being developed as a product it is not possible to have acceptance testing by each end-user and hence a process called alpha and beta testing is followed.
  • The alpha test is conducted by a customer at the developer’s site.
  • The developer records errors and usage problems.
  • They are conducted in controlled environment.
  • The beta test is conducted at one or more customer sites by the end-user of the software.
  • The developer is generally not present.
  • The customer records all problems and reports to the developer at regular intervals.
  • Based on these reports the developer modifies the software and then releases to the entire customer base.

Comments

Post a Comment

Popular posts from this blog

Food Ordering System

Image
Food Ordering System 0 (Zero) level DFD context diagram for online food ordering system level 0 dfd for food ordering system er diagram for online food ordering system data flow diagram example for online shopping data flow diagram level 0 1 2 examples data flow diagram symbols level 2 dfd for online food ordering system data flow diagram for pizza ordering system
Read more

Rules for Stopping the Decomposition Process in DFD

Rules for Stopping the Decomposition Process in DFD (1) when you have reduced each process to a single decision or calculation or to a single database operation;  (2) when each data store represents data about a single entity;  (3) when the system user does not care to see any more detail or when you and other analysts have documented sufficient detail to do subsequent systems development tasks;  (4) when every data flow does not need to be split further to show that different data are handled in different ways;  (5) when you believe that you have shown each business form or transaction, computer on-line display, and report as a single data flow;  (6) when you believe there is a separate process for each choice on all lowest-level menu options for the system.
Read more