Database Systems

Database Systems

Author

Institution

Introduction

System documentation refers to written materials describing the functionality of a computer system so as to ease the performance of business operations. Varied sorts of documentation may be used in SMEs. Administration documentation targets project managers and system administrators. It gives an overview of the system while defining the requirements and prerequisites for use. Installation documentation, on the other hand, would target installers and administrators. It defines the installation and configuration processes through varied scenarios. On the same note, there is procedure documentation which shows the day-to-day users how to carry out system tasks with step-by-step instructions (Yadav, 2006). Reference documentation, on the other hand is alphabetized by command name and component, offering a succinct definition of every component of the system, thereby allowing for quick access to information by experienced technical users. While documentation may be effective in varied aspects, the most effective feature would be functionality and security. These allow the applications or systems to be used for their appropriate functions, while ensuring that the information is not used by unintended or unauthorized individuals to cause havoc to functionality (Yadav, 2006). However, documentation comes with a number of problems including too high costs, time consumption, hard to read and understand, vagueness, and being built on the assumption that readers have certain levels of knowledge which they may not have.

Applications must be tested so as to determine their reliability, usability, as well as safety with regard to the functionality of the entire system. It is imperative that the specialist determine the functionality of varied features of the application. The following checklist would be used in testing applications.

Mandatory fields are shown using an asterisk symbol.

Correct positioning of validation error messages.

Display of all error messages using similar CSS style.

Display of general confirmation messages using CSS style.

Meaningfulness of tool tips.

Delete functionality asks for confirmation.

Dropdown filed have their first entry with a text such as “select” or simply blank.

Amount values are shown in the appropriate currency symbols.

Availability of the default page sorting.

Properly formatted numeric values

All fields have their default values set by the reset button functionality.

Input values are within the accepted limit.

Functionality and applicability of special characters.

Configuration capacity of the timeout functionality.

Page sorting functionality following delete, edit, or add operations.

Grammar and spelling functionality.

Redirection of application crash to the error page.

Proper validation message capabilities.

Functionality of buttons that are available in every page.

However, as much as there is a checklist for testing an application, it is noteworthy that testing never ends. Nevertheless, an application is deemed as having been sufficiently tested in instances where a maximum number of test cases have been executed and passed, budget depleted, deadlines reached and fundamental functionalities determined as functioning appropriately (Yadav, 2006). The optimistic or hopeful stopping rule is followed in instances where reliability of an application meets the requirements, or in cases where the benefits emanating from further testing would not justify the testing cost.

As much as meeting deadlines in making applications is imperative, it is imperative that time is reserved for testing the application. Software testing involves a trade-off between quality, time and budget (Yadav, 2006). Upper manager would be persuaded to set aside time and money for testing applications in spite of the deadlines through outlining its importance and dangers of not carrying out tests. The tests are usually carried out so as to assess the capabilities and attributes of a system and program, thereby determining whether it meets the required parameters and results (Yadav, 2006).

References

Yadav, D. S. (2006). Foundations of information technology. New Delhi: New Age International (P) Limited.