How do system operational requirements influence the product

How do system operational requirements influence the product/process maintenance concept (if at all)?

What is SMART? How is it useful in establishing “good” requirements?

Solution

A requirement is defined as a feature of a product, service or system to deliver a result which satisfies the needs of an individual, group or organization. Operational Requirements are capabilities, performance measurement and processes required to cater to mission area shortcomings, possible threats, upcoming technologies, or system cost enhancements. They are developed and also validated by the user and enlisted in the Capability Development Document and Capability Production Document . They are the basis for system technical specifications, contract needs and they also guide product development hence solutions specifications solve the stated problems.

Their assessment initiates with the Concept of Operations and progresses to a bigger level of detail in identifying mission performance assumptions and barriers and  shortcomings of or enhancements required for operations and mission success. They are ususally developed in the Material Solution Analysis (MSA) Phase and Technology Maturation & Risk Reduction (TD) Phase of Acquisition Process.

The operational requirements target on how the system should be operated by the users, inclusive of interfaces and interoperability with other systems. The needs establish how well and under which conditions the system should perform