Non-Functional Requirement
	1.0 The system shall be designed to work, at a minimum, on z/OS using IBM Websphere 5.1 to the J2EE 1.3 specification.
	2.0 The system shall use J2SE V1.4.2_05 as the defacto virtual machine.
	3.0 The system shall be modeled and designed to the JTAPI Specification.
	4.0 The system shall migrate from current client interface to a .NET client.
	4.1 The system shall be designed with .NET client interface to the current legacy application.
	5.0 The system shall provide that all boundary interfaces can integrate with the Avaya Speech Application Builder (Fluency Voice Runner).
	6.0 The system shall undertake to meet the throughput metrics of the legacy application. This quality must be balanced with good design principles. When and where appropriate, we will sacrifice good design for throughput.
	6.1 The system shall meet the current MBNA Switch throughput of 40 messages/sec across 47 servers.
	7.0 The system shall handle exceptions and report all relevant exceptions to the client.
	8.0 The system shall minimize the number of parameters that is required from the client (message).
	9.0 User input is Valid

package: Non-Functional Requirement