{"id":{"repo_id":"vt","oai_identifier":"oai:vtechworks.lib.vt.edu:10919/39100"},"canonical_url":"https://search.dev.ndltd.org/etd/vt/oai:vtechworks.lib.vt.edu:10919/39100","repository":{"repo_id":"vt","name":"Virginia Tech","base_url":"https://vtechworks.lib.vt.edu/oai/request"},"display":{"title":"Product usability and process improvement based on usability problem classification","abstract":"Although research and practice have shown that the success of a usability engineering program depends on the identification and correction of usability problems, these problems remain an underutilized source of information. Insufficient guidance regarding the capture of usability problem data results in the loss of information during the problem reporting phase as problem reports are often vague, imprecise, and incomplete. In addition, the absence of a framework for understanding, comparing, categorizing, and analyzing those problems, and their relationship to development context, not only constrains product improvement, but hampers efforts to improve the user interface development process. A new taxonomic model (the Usability Problem Taxonomy) is presented which contributes to both product and process improvement. The Usability Problem Taxonomy (UPT) is used to classify and organize usability problems detected on interactive software development projects. Individual UPT categories are associated with two aspects of development context: developer roles and skills, and development activities, methods, and techniques. Two studies were conducted during the course of this research. The first study showed that the UPT can be used to classify usability problems reliably. Findings indicated that level of agreement among classifiers (beyond chance agreement) was statistically significant. Findings in the second study led to the identification of roles and activities that address individual UPT categories as well as those that do not. Procedures for using the UPT in both product and process improvement are outlined. Examples are presented that illustrate how the UPT can be used to generate higher quality problem descriptions and to group those problem descriptions prior to prioritization and correction. In addition, steps that guide developers in diagnosing weaknesses in the current user interface development process are enumerated. Possible improvement strategies are presented that focus on the selection of specific development activities and team members appropriate for a given project.","abstract_html":"Although research and practice have shown that the success of a usability engineering program depends on the identification and correction of usability problems, these problems remain an underutilized source of information. Insufficient guidance regarding the capture of usability problem data results in the loss of information during the problem reporting phase as problem reports are often vague, imprecise, and incomplete. In addition, the absence of a framework for understanding, comparing, categorizing, and analyzing those problems, and their relationship to development context, not only constrains product improvement, but hampers efforts to improve the user interface development process. A new taxonomic model (the Usability Problem Taxonomy) is presented which contributes to both product and process improvement. The Usability Problem Taxonomy (UPT) is used to classify and organize usability problems detected on interactive software development projects. Individual UPT categories are associated with two aspects of development context: developer roles and skills, and development activities, methods, and techniques. Two studies were conducted during the course of this research. The first study showed that the UPT can be used to classify usability problems reliably. Findings indicated that level of agreement among classifiers (beyond chance agreement) was statistically significant. Findings in the second study led to the identification of roles and activities that address individual UPT categories as well as those that do not. Procedures for using the UPT in both product and process improvement are outlined. Examples are presented that illustrate how the UPT can be used to generate higher quality problem descriptions and to group those problem descriptions prior to prioritization and correction. In addition, steps that guide developers in diagnosing weaknesses in the current user interface development process are enumerated. Possible improvement strategies are presented that focus on the selection of specific development activities and team members appropriate for a given project.","abstract_has_math":false,"creators":["Keenan, Susan Lynn"],"institution":"Virginia Tech","degree_name":"Ph. D.","degree_level":"doctoral","degree_discipline":"Computer Science","degree_department":"Computer Science","school":null,"contributors":[],"advisors":[],"committee_chairs":["Hartson, H. Rex","Kafura, Dennis G."],"committee_members":["Arthur, James D.","Hix, Deborah S.","Lee, John A. N.","Schulman, Robert S."],"year":1996,"date_issued":"1996-08-05","date_published":"1996-08-05","updated_at":"2026-07-22T22:19:19Z","subjects":["problem classification","user-interface process improvement","usability"],"languages":["en"],"rights":["In Copyright"],"rights_urls":["http://rightsstatements.org/vocab/InC/1.0/"],"identifier_entries":[{"key":"dc:identifier.other","label":"Dc Identifier Other","values":["etd-08082007-155155"],"render_values":[{"text":"etd-08082007-155155","href":null,"code":true}]}]},"links":{"outbound_url":"http://hdl.handle.net/10919/39100","outbound_label":"Handle","outbound_source":"dc:identifier.uri"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor.committeechair","label":"Committee Chair","values":["Hartson, H. Rex","Kafura, Dennis G."]},{"key":"dc:contributor.committeemember","label":"Committee Member","values":["Arthur, James D.","Hix, Deborah S.","Lee, John A. N.","Schulman, Robert S."]},{"key":"dc:contributor.department","label":"Department","values":["Computer Science"]},{"key":"dc:creator","label":"Author","values":["Keenan, Susan Lynn"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.accessioned","label":"Dc Date Accessioned","values":["2014-03-14T21:17:30Z"]},{"key":"dc:date.available","label":"Dc Date Available","values":["2014-03-14T21:17:30Z","2007-08-08"]},{"key":"dc:date.issued","label":"Date","values":["1996-08-05"]},{"key":"dc:publisher","label":"Institution","values":["Virginia Tech"]},{"key":"dc:type","label":"Dc Type","values":["Dissertation"]},{"key":"dc:type.dcmitype","label":"Dc Type Dcmitype","values":["Text"]},{"key":"thesis:degree_discipline","label":"Discipline","values":["Computer Science"]},{"key":"thesis:degree_level","label":"Degree Level","values":["doctoral"]},{"key":"thesis:degree_name","label":"Degree Name","values":["Ph. D."]},{"key":"thesis:institution_name","label":"Thesis Institution Name","values":["Virginia Polytechnic Institute and State University"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["problem classification","user-interface process improvement","usability"]}]},{"id":"language_rights","label":"Language and Rights","entries":[{"key":"dc:language.iso","label":"Language (ISO)","values":["en"]},{"key":"dc:rights","label":"Dc Rights","values":["In Copyright"]},{"key":"dc:rights.uri","label":"Rights URI","values":["http://rightsstatements.org/vocab/InC/1.0/"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier.other","label":"Dc Identifier Other","values":["etd-08082007-155155"]},{"key":"dc:identifier.uri","label":"Identifier URI","values":["http://hdl.handle.net/10919/39100"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["Although research and practice have shown that the success of a usability engineering program depends on the identification and correction of usability problems, these problems remain an underutilized source of information. Insufficient guidance regarding the capture of usability problem data results in the loss of information during the problem reporting phase as problem reports are often vague, imprecise, and incomplete. In addition, the absence of a framework for understanding, comparing, categorizing, and analyzing those problems, and their relationship to development context, not only constrains product improvement, but hampers efforts to improve the user interface development process. A new taxonomic model (the Usability Problem Taxonomy) is presented which contributes to both product and process improvement. The Usability Problem Taxonomy (UPT) is used to classify and organize usability problems detected on interactive software development projects. Individual UPT categories are associated with two aspects of development context: developer roles and skills, and development activities, methods, and techniques. Two studies were conducted during the course of this research. The first study showed that the UPT can be used to classify usability problems reliably. Findings indicated that level of agreement among classifiers (beyond chance agreement) was statistically significant. Findings in the second study led to the identification of roles and activities that address individual UPT categories as well as those that do not. Procedures for using the UPT in both product and process improvement are outlined. Examples are presented that illustrate how the UPT can be used to generate higher quality problem descriptions and to group those problem descriptions prior to prioritization and correction. In addition, steps that guide developers in diagnosing weaknesses in the current user interface development process are enumerated. Possible improvement strategies are presented that focus on the selection of specific development activities and team members appropriate for a given project."]},{"key":"dc:description.degree","label":"Dc Description Degree","values":["Ph. D."]},{"key":"dc:format.medium","label":"Dc Format Medium","values":["BTD"]},{"key":"dc:format.mimetype","label":"Dc Format Mimetype","values":["application/pdf"]},{"key":"dc:title","label":"Title","values":["Product usability and process improvement based on usability problem classification"]}]}],"canonical_facts":{"dc:contributor.committeechair":["Hartson, H. Rex","Kafura, Dennis G."],"dc:contributor.committeemember":["Arthur, James D.","Hix, Deborah S.","Lee, John A. N.","Schulman, Robert S."],"dc:contributor.department":["Computer Science"],"dc:creator":["Keenan, Susan Lynn"],"dc:date.accessioned":["2014-03-14T21:17:30Z"],"dc:date.available":["2014-03-14T21:17:30Z","2007-08-08"],"dc:date.issued":["1996-08-05"],"dc:description.abstract":["Although research and practice have shown that the success of a usability engineering program depends on the identification and correction of usability problems, these problems remain an underutilized source of information. Insufficient guidance regarding the capture of usability problem data results in the loss of information during the problem reporting phase as problem reports are often vague, imprecise, and incomplete. In addition, the absence of a framework for understanding, comparing, categorizing, and analyzing those problems, and their relationship to development context, not only constrains product improvement, but hampers efforts to improve the user interface development process. A new taxonomic model (the Usability Problem Taxonomy) is presented which contributes to both product and process improvement. The Usability Problem Taxonomy (UPT) is used to classify and organize usability problems detected on interactive software development projects. Individual UPT categories are associated with two aspects of development context: developer roles and skills, and development activities, methods, and techniques. Two studies were conducted during the course of this research. The first study showed that the UPT can be used to classify usability problems reliably. Findings indicated that level of agreement among classifiers (beyond chance agreement) was statistically significant. Findings in the second study led to the identification of roles and activities that address individual UPT categories as well as those that do not. Procedures for using the UPT in both product and process improvement are outlined. Examples are presented that illustrate how the UPT can be used to generate higher quality problem descriptions and to group those problem descriptions prior to prioritization and correction. In addition, steps that guide developers in diagnosing weaknesses in the current user interface development process are enumerated. Possible improvement strategies are presented that focus on the selection of specific development activities and team members appropriate for a given project."],"dc:description.degree":["Ph. D."],"dc:format.medium":["BTD"],"dc:format.mimetype":["application/pdf"],"dc:identifier.other":["etd-08082007-155155"],"dc:identifier.uri":["http://hdl.handle.net/10919/39100"],"dc:language.iso":["en"],"dc:publisher":["Virginia Tech"],"dc:rights":["In Copyright"],"dc:rights.uri":["http://rightsstatements.org/vocab/InC/1.0/"],"dc:subject":["problem classification","user-interface process improvement","usability"],"dc:title":["Product usability and process improvement based on usability problem classification"],"dc:type":["Dissertation"],"dc:type.dcmitype":["Text"],"thesis:degree_discipline":["Computer Science"],"thesis:degree_level":["doctoral"],"thesis:degree_name":["Ph. D."],"thesis:institution_name":["Virginia Polytechnic Institute and State University"]},"updated_at":"2026-07-22T22:19:19Z"}