I. IntroductionFunctional testing is basically testing software based on its functional requirements. This means that it makes sure that the SUT (System Under Test) or program physically works as expected. Now that we have a basic understanding of what Functional Testing is according to the definition provided above; How about we delve deeper into the topic. This document will provide answers to questions the writer had on the topic, as well as the general importance of functional testing. The issues to be discussed will be accentuated throughout the document.II. What is functional testing? Functional testing in a sense consists of testing each function individually; this means testing the feature to the extent that the tester can confidently say that the feature works. Based on the definition previously set out in the introduction; there is much more to functional testing than just defining one or two lines. In fact, there are many components and relationships that need to be introduced before we have a full understanding of what Functional Testing truly is in its entirety. There are several components of the Functional Test that will be elaborated here in the document. Functional tests include: boundary value tests, equivalence class tests, decision table tests and many others. These are just a few examples that the author felt needed to be discussed in more depth. White box functional testing is usually called unit testing and focuses on functions as you might see in the code. Black box function testing focuses on commands and functionality, things the user can do or select. Now that there is a more detailed description of the Functional Test; what are these different components and how do they...... half of the paper ......gather vital information about the software's capabilities and attributes and help expose potential problems.Works CitedBoard, IS (1986). An American national standard, the IEEE Standard for Software Unit Testing. New York: The Institute of Electrical and Electronics Engineers, Inc. Cem Kaner, J. B. (2002). Lessons learned in software testing. New York: John Wiley & Sons, Inc. Jorgensen, P. C. (2008). Software Testing: A Craftsman's Approach, Third Edition. Boca Raton: Taylor & Francis Group, LLC.PCMAG. (2011, July 18). PCMAG.COM Encyclopedia. Retrieved July 18, 2011, from PCMAG.COM: http://www.pcmag.com/encyclopedia_term/0,2542,t=functional+test&i=43588,00.aspPerry, W. E. (2006). Effective methods for software testing. Indianapolis: Wiley Publishing, Inc. Young, M. P. (2008). Software testing and analysis. Hoboken: John Wiley & Sons, Inc.