command button - a button that can be chosen by a user to begin, to interrupt, or to end a process. When chosen, a command button appears pushed in, and is sometimes called a "push button."

Delivery Requirements - requirements that specify when the system should be delivered.

description - explanation of the drug, its use and ingredients.

dosage - the strengths of the drug, i.e 10 mg.

Drug Interaction - when two drugs act on each other producing some results patients should be aware of.

Efficiency Requirements - requirements that make the system use as little resources yet still retain its full functionalities.

Ethical Requirements - requirements that makes the system ethically acceptable to social standards.

External Requirements - requirements that arise from factors which are external to the system and it's development process.

frame - provides an identifiable grouping for controls. A frame can also be used to subdivide a form functionally. For example, a frame can be used to separate a group of option buttons from other groups of option buttons.

Functional Requirements - the services or functions the system should provide. They are detailed descriptions and are written in a structured document format. The functional requirements are written for the purpose of a contract between the client and the contractor.

Implementation Requirements - requirements that specify which programming languages to use to implement the system.

Interoperability Requirements - requirements that specify how the system interacts with other systems.

KIOSK - touch screen interaction with the software application.

Legislative Requirements - requirements that contain legal rules and regulations which need to be observed.

list box - displays a list of items from which the user can select one or more. If the number of items exceeds what can be displayed, a scroll bar is automatically added to the list box.

Non-fuctional Requirements - requirements that are the constraints of the system and the development process relating to the functional requirements. It may include specific data representation, response time, memory requirements and product and process standards.

option button - displays an option that can be turned on or off.

Organizational Requirements - requirements which are consequences of organizational policies and procedures.

OTC drugs - over-the-counter drugs.

Performance Requirements - requirements that specify how fast the system must execute and the memory it requires.

pop-up window - a window that appears in the middle of the screen on top of the main window.

Portability Requirements - requirements that specify the compatibilities of the system.

prescription drugs - drugs that are prescribed by a physician, often as a result of a doctor's visit or contact.

Privacy Requirements - requirements to keep user informations private and protected.

Product Requirements - requirements that specify how the delivered product must behave.

Reliability Requirements - requirements that set out the acceptable failure rate.

Repository Model - a model where all shared data is held in a central database, which can be accessed by all sub-systems.

Requirements Specification - a detailed and precise description of the system requirements set out to act as a basic for a contract between client and software developer.

Rx - prescription.

Safety Requirements - requirements to keep data collected secure from the general public.

Space Requirements - requirements that specify how big the hard drive must be in order to save all the user's information.

Standard Requirements - general requirements needed for the system to function correctly.

symptoms - side effects from the drug.

System Evolution - a way of foreseeing changes in the software engineering process of any system.

System Model - a model that presents abstract descriptions of the system to be developed.

tabbed frame - a frame with multiple layers. Each layer contains different information and controls.

type - OTC or Rx

UPS - a backup software that will do a safe shut down in the event of power failure where the power does not restore.

Usability Requirements - requirements that make it easier to interact with the system.

usage - the amount of times the drug should be taken, i.e once or twice a day.