An evaluation of the pragmatics of web-based bug tracking tools

Authors:
Harry S. Delugach
Affiliations:
Univ. of Alabama in Huntsville, Huntsville, AL
Venue:
ICPW '07 Proceedings of the 2nd international conference on Pragmatic web
Year:
2007

Citing 8
Cited 1

Conceptual structures: information processing in mind and machine

Conceptual structures: information processing in mind and machine
Specifying multiple-viewed software requirements with conceptual graphs

Journal of Systems and Software
An approach to conceptual feedback in multiple viewed software requirements modeling

ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
Software Engineering: A Practitioner's Approach

Software Engineering: A Practitioner's Approach
Applying Conceptual Graph Theory to the User-Driven Specification of Network Information Systems

ICCS '97 Proceedings of the Fifth International Conference on Conceptual Structures: Fulfilling Peirce's Dream
Towards a Semantic Metrics Suite for Object-Oriented Design

TOOLS '00 Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 34'00)
Using Issue Tracking Tools to Facilitate Student Learning of Communication Skills in Software Engineering Courses

CSEET '05 Proceedings of the 18th Conference on Software Engineering Education & Training
Experiences in Automating the Analysis of Linguistic Interactions for the Study of Distributed Collectives

Computer Supported Cooperative Work

Creating Process-Agents incrementally by mining process asset library

Information Sciences: an International Journal

Quantified Score

Hi-index	0.00

Visualization

Abstract

Web-based tools are often used to support software development processes. Many of these tools are aimed toward a development process that relies implicitly on particular supported roles and activities. Developers may already understand how the tool operates; however, developers do not understand or adhere to a development process supported (or implied) by the tools. This paper proposes a preliminary formal model of roles and activities in one aspect of software development, namely the problem reporting process, and describes both a standards-based process and a well-known tool with respect to its support for their respective processes. An alternative is proposed for modeling problem status that is based on the analysis of process roles.