Personal tools

Bug tracking

by Barthel, William J last modified Mar 03, 2017 03:26 PM

A subject that was brought to my attention this week is the process of bug tracking.  From where I am at in my computer science career there has never been a time when fixing bugs was all that difficult to understand.  The majority of my assignments involve receiving a complex problem and solving it from scratch, testing the program when it solves the given problem, and fixing what errors are found during testing.  Since I was involved with the whole process, it has been simpler to locate and fix these kinks in my programs.

From Karl Fogel's book "Producing Open Source Software", I read a chapter that primarily focused on bug trackers on various software.  In this chapter he describes the lifestyle of a submitted ticket claiming to have information on a flaw in the software.  Once the bug is deemed valid, developers look it over, try to reproduce it, and determine how critical of an issue it is in the current version of the software.  This process is relatively simple for smaller projects, but for larger ones, some additional complications may arise.  An example of this is having many users submitting tickets for the same issue which clots up the repository that stores all the bug reports.  Also, developers may become less appreciative of their users taking time out of their day to send a detailed bug report due to them being away of the problem for a decent amount of time prior.  An efficient but tracking system efficiently filters out duplicate content and passionate developers will take care to appreciate every user who spends their time trying to improve someone else's product.

In other news, Michael and I have decided to develop a workflow in Plone that is different from our initial idea of updating UW Oshkosh's Office of International Education's study abroad process.  To develop a well-rounded workflow that covers all of the points needed is a bit more involved than we have time for in this semester projects.  We have decided to instead develop a mock workflow for a perspective animal shelter.  The goal will be to create a workflow in Plone that represents the lifecycle of an animal being admitted to an animal shelter, being taken care of while there, up to adoption.  This is still a work in progress as to what information should be included in such a workflow.  By the end of next week Michael and I will have most of our research done discovering what is involved in such a process.

 

by Barthel, William J last modified Mar 03, 2017 03:26 PM
CS emphasis accredited by

ABET logo

Contact Us

Computer Science Department
UW Oshkosh
800 Algoma Blvd.
Oshkosh, WI 54901

Phone: (920) 424-2068
Fax: (920) 424-0045
Building: Halsey Science Hall


Rooms: 229 (general office), 221 (David Furcy, chair)

Email: Send mail to chair at cschair@uwosh.edu