The purpose of this guide is provide general information regarding how Integrated Solution, Inc. will handle Product Requirements.

 

______________

The requirement document should describe the requirements for the product based on a given Architecture (2.1). Any category having no requirements, should include the category’s section heading followed by "None." The following areas should be considered:

 

This section briefly describes the product environments, its architectural approaches and how the product is generally used. It should also show how the product be effectively utilized with its functionality and capability.

 

This section covers all aspects of the product requirements.

 

This section states the quality of the product and all critical performance information from every elements of the product the tools associated with the product.

This section also describes what kind of testing (including negative) is required during certification to demonstrate and insure the product availability.

 

This section also make make-buy considerations related to the product (such as tools and software platforms ...etc.), should be based upon quality, cost, and delivery and may possibly include multiple-sourcing options.

 

 

4.3 Performance Requirements

 

This section states the general product performance:

 

The minimum performance criteria: the throughput, the data rate ….etc. The reconstruct time.

 

 

 

 

4.4 Interface Requirements, Concurrency Interoperability and Connectivity Requirements

 

This section describes the interfacing requirements and all features and functions of the product must be available for use concurrently.

This section should describe the product need to be able to interoperate with and support operating environments and the applications it must support.

 

This section describes the upgradeable requirements to support additional systems or products.

 

This section also describes the upgrades and reconfigurations of the product for additional application and expansion strategy being planned.

 

List the standard applications and the platforms the product will support such that no modifications to the standard applications are required.

 

Describe the product cost as measured.

State the cost requirement to set early pricing strategy. This also includes installation , support and maintenance of the product.

 

This section states the resource required to make the product out of the door. It will include all support resources such as management, development, field support, documentation, training, advertising, marketing, sales, and installation….etc.

 

 

This section describes what the product must be able to be migrated with minimal change to future products.

This section states the product MTBF, and the Out of Box Quality target.

It describes the customer perceived availability for the product be stating what the product must achieve to what level and % up time excluding scheduled maintenance periods.

 

Other requirements need to be considered are as below:

8.1 Hardware Environment Requirements

8.2 Security Requirements

8.3 Independent Software Vendors

8.4 Serviceability

8.5 Usability

8.6 Installability

8.7 Recoverability

8.8 Manufacturability

8.9 Documentation

8.10 Packaging & Shipping Requirements

8.11 Software Production and Distribution Requirements

8.12 Customer Education Requirements

8.13 Internal Training Requirements

8.14 Support Requirements

 

 

______________

All the requirements should declared with a Priority factor. They are:

______________