What are they?
A bug is an error in design, logic, or coding that causes some portion of a software program to not perform as expected. Bugs are normal part of software development process and exist in every software program you own. Our goal is to minimize bugs as much as possible and to fix the discovered ones as soon as possible.

Why is it called a bug?
The name came form the earliest days of computing. In 1945, when Grace Hopper was working on the Harvard-MARK II computer, she found a moth in the computer, which caused a relay to fail. She taped it in her log book, writing First actual case of bug being found.

Bug Priority
Bugs can be classified into these priorities:

Critical: A required function crashes the application, or a required function is missing or not functioning. The existence of this bug makes the module or the whole software unusable. Example: You try to sign a student in, and the application exits with an error message.
Serious: Any function that should work but doesn't. The absence of this function does not cause an application crash, but may generate an error or the wrong results. Example: the program records wrong sign-in time.
Annoyance: A features or function that works but only in an awkward way. To make this feature work, the user needs to go through extra steps that would be unnecessary if the bug did not exist. Example: A report will not work from staff screen, but will work if launched from the Reports screen.
Superficial: Function or feature that works but can be slightly improved if done differently. Example: A misspelled text label or a clash in screen colors.

How Are they Discovered?
As part of the software development process, the developers tests the software before it is released to the customer. Bugs discovered during this stage are fixed before the release. Some bugs may not be discovered during the developer's tests. Here are some reasons why:

Software or hardware setup: Since there are differences in the hardware and software setup between the developer's and customer's computers, the developed software may behave differently on the customer's computer.
Usage: Customers may use the software in a way different from what the developers anticipated. The difference may uncover some bugs.
Environment: The developer runs the software in simulated settings, while the customer runs the software in real-usage environment.

The developer depends on the user's feedback for identifying bugs that escape testing. This is why it is important that you report all bugs you discover ASAP.

What happens when a bug is discovered?
When a bug is reported, our staff will investigate it. If the bug is confirmed, it will be be fixed in the next maintenance release of the software. A list of fixed bugs appears in the online revision log of the software (available via the Help Center).

Reporting Bugs
Our support staff would like your feedback on any problems you find, so take the time to explore the software thoroughly, even its lesser-known features. If you encounter a bug, get as much specific detail as you can about it. If there is a specific error message or a sequence of events that produces the problem, write it down, as well as the version of the software involved. You can then report the bug either via the online support forum, or via email.