I bought this for my two special needs boys (4.5 and 2.5) and waffled between this trampoline and the Galt red trampoline with the handle bar. I decided to get this one because it's a few inches larger than the Galt one although it doesn't have the handle bar which would have been ideal for my 2.5 year old.

Pros: Both boys love it. The 4.5 yr old is getting his much needed sensory fix. The 2.5 yr old loves to get on it but because he doesn't know how to jump with both feet off the ground, he just plays or hangs out on it for now.

Cons: My husband and I put this together in roughly 20 minutes (it probably would have taken less time but my engineering husband was trying to figure out why the holes to bolt together the trampoline weren't aligned perfectly on one side). The directions weren't that clear and while they had b&w photos, it would have been nice if the photos were close-ups.
http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"> name="GENERATOR" content="OpenOffice.org 3.2 (Win32)">

Trampoline with enclosure

By QA Testing
Software testing is a popular risk management strategy. It is used to verify
that functional requirements were met. The limitation of this approach,
however, is that by the time testing occurs, it is too late to build quality into
the product. Tests are only as good as the test cases, but they can be
inspected to ensure that all the requirements are tested across all possible
combinations of inputs and system states. However, not all defects are discovered
during testing. Software Program testing includes the activities outlined in
this text, including verification and validation activities. In many organizations,
these activities, or their supervision, are included within the charter
for the Software Package quality assurance function. The extent to which personnel
independent of design and coding should participate in Computer Software quality
assurance activities is a matter of institutional, organizational, and project
policy.
The major purpose of verification and validation activities is to ensure
that Computer Software design, code, and documentation meet all the requirements
imposed on them. Examples of requirements include user requirements;
specifications derived from and designed to meet user requirements; code
review and inspection criteria; test requirements at the modular, subsystem,
and integrated Software Program levels; and acceptance testing of the code
after it has been fully integrated with hardware.
During Software design and implementation, verification helps determine
whether the products of one phase of the Software Program development life
cycle fulfill the requirements established during the previous phase. The
verification effort takes less time and is less complex when conducted
throughout the development process.

http://cid-0d8af69e7eb78797.spaces.live.com/default.aspx

What is Software Qa Testing?
By QA Testing

Software QA testing is a process designed to • Show that the program is error free • Establish that the software system performs its functions correctly • Establish with confidence that the software system does its job fully If yours matches, you are in for a surprise because computer software QA testing is none of these. Rather it is properly defined as follows (see Concepts): Concepts - software Testing is the task of locating errors. THE IMPORTANCE OF A GOOD DEFINITION: Any definition of Testing is more than a passive description. It has a profound impact on the way computer software Testing is carried out. Since people are highly goal-oriented, the setting of proper goals can mean the difference between success and failure. If the goal of computer software QA testing were to prove [that a program or process functions properly], the tester would subconsciously work towards this goal, choosing test data that would prove that point. The reverse would be true if the goal were to locate and correct errors. Test data would be selected with an eye toward providing the application with cases that would likely cause the program to fail. This would be a more desirable result. Why? We begin with the assumption that the system, like most systems, contains errors. The job of software program test is to discover them before the user does. In that case, a good tester is one who is successful in crashing the system, or in causing it to perform in some way that is counter to the specification. The mentality of the tester, then, is a destructive one -quite different from the constructive attitude of the programmer, the "creator". This is useful information for the analyst. Who is acting as a project leader, and is responsible for staffing. Staff should be selected with the appropriate personality traits in mind. Another effect of having a proper working definition of Testing regards the way the project leader assesses the performance of the test team. Without a proper definition of computer software QA testing, the leader might describe a successful test run as one which proves the program is error free and describe an unsuccessful test as one which found errors. As is the case with the testers themselves, this mind-set is actually counter-productive to the software system test process. GOALS OF software system QA testing: To satisfy its definition, QA Testing must accomplish the following goals: 1. Find cases where the application does not do what it is supposed to do. 2. Find cases where the program does things it is not supposed to do. The first goal refers to specifications which were not satisfied by the application while the second goal refers to unwanted side-effects.

References
1. ^ Exploratory Testing, Cem Kaner, Florida Institute of Technology, Quality Assurance Institute Worldwide Annual Software Testing Conference, Orlando, FL, November 2006 http://www.kaner.com/pdfs/ETatQAI.pdf
2. ^ Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007http://se.inf.ethz.ch/people/leitner/publications/cdd_leitner_esec_fse_2007.pdf