• English
    • français
    • Deutsch
    • español
    • português (Brasil)
    • Bahasa Indonesia
    • русский
    • العربية
    • 中文
  • English 
    • English
    • français
    • Deutsch
    • español
    • português (Brasil)
    • Bahasa Indonesia
    • русский
    • العربية
    • 中文
  • Login
View Item 
  •   Home
  • OAI Data Pool
  • OAI Harvested Content
  • View Item
  •   Home
  • OAI Data Pool
  • OAI Harvested Content
  • View Item
JavaScript is disabled for your browser. Some features of this site may not work without it.

Browse

All of the LibraryCommunitiesPublication DateTitlesSubjectsAuthorsThis CollectionPublication DateTitlesSubjectsAuthorsProfilesView

My Account

Login

The Library

AboutNew SubmissionSubmission GuideSearch GuideRepository PolicyContact

Statistics

Most Popular ItemsStatistics by CountryMost Popular Authors

A software metrics based approach to enterprise software beta testing design

  • CSV
  • RefMan
  • EndNote
  • BibTex
  • RefWorks
Author(s)
Buskey, Carlos Delano
Keywords
Computer Science

Full record
Show full item record
URI
http://hdl.handle.net/20.500.12424/2556562
Online Access
http://digitalcommons.pace.edu/dissertations/AAI3191871
Abstract
Today, major manufacturers of enterprise software have shifted their focus to integrating the influence of the user community in the validation of software. This relationship is established through the corporate beta testing programs to confirm to the customer base that the software was properly reviewed prior to releasing to the target market. However, there are no industry standards for beta testing software and no structured software beta testing processes that may be used for the common enterprise application. In addition, beta testing models used today lack clear testing objectives. An additional problem in software beta test processes used by most manufacturers, is that there are no organized procedures for developing an effective beta test. Beta testing models strictly focus on error feedback, time of testing, and the number of beta testing sites participating in the program. ^ This research addresses the fundamental problems in poor beta testing design by contributing a software metrics based beta testing design model that uses weakness in the current product to plan an effective beta test. A set of formal beta testing objectives is initiated and essential software attributes are suggested to support each objective. Each objective is quantitatively measured with a set of metric functions used to predict risk levels in a software product. The predicted risk levels are used to assist in prioritizing tasks for the pending beta test. A learning process is provided to demonstrate the effects of the metric functions when the process matures. ^ The metric functions were tested on three real-world enterprise applications to validate the effectiveness of the formulas when employed on a live product. The experiment demonstrated close prediction to the actual risk value for each product and demonstrated how the predictions improved with experience. ^
Date
2005-01-01
Type
text
Identifier
oai:digitalcommons.pace.edu:dissertations-1374
http://digitalcommons.pace.edu/dissertations/AAI3191871
Collections
OAI Harvested Content

entitlement

 
DSpace software (copyright © 2002 - 2023)  DuraSpace
Quick Guide | Contact Us
Open Repository is a service operated by 
Atmire NV
 

Export search results

The export option will allow you to export the current search results of the entered query to a file. Different formats are available for download. To export the items, click on the button corresponding with the preferred download format.

By default, clicking on the export buttons will result in a download of the allowed maximum amount of items.

To select a subset of the search results, click "Selective Export" button and make a selection of the items you want to export. The amount of items that can be exported at once is similarly restricted as the full export.

After making a selection, click one of the export format buttons. The amount of items that will be exported is indicated in the bubble next to export format.