Fifty Examples of Functional Requirement

Functional Requirements are very important system requirements in the system design process. These requirements are the technical specifications, system design parameters and guidelines, data manipulation, data processing, and calculation modules etc, of the proposed system.

Functional Requirements are in contrast to Non-Functional Requirements which are descriptive of the parameters of system performance, quality attributes, reliability and security, cost, constraints in design/implementation, etc. The key goal of determining “functional requirements” is to capture the required behavior of a system in terms of functionality.

Listed below are a total of fifty examples of functional requirements. These examples are from five basic systems:

• Accounts Payable
• Purchasing
• Sales
• Human Resources
• Finance

The following is a running list of possible Accounts Payable functional requirements:

1. Supports three way matching - purchase order, receipts, and supplier invoices
2. Supports the option to place an individual invoice on hold
3. Allows for modifications to invoice account distribution after processing
4. Supports the partial payment of invoices
5. Supports the vendor payments without purchase orders
6. Vendor return processing is fully integrated with the warehouse and accounts payable functionality
7. Vendor return processing provides the user the ability to ties the return to a specific purchase order
8. Vendor return processing supports return of roods received against closed purchase orders
9. Supports the linkage of the return's debit memo to a single purchase order
10. Supports basic Internet based purchasing functionality

The following is a running list of possible Purchasing Functional requirements:

1. Supports user defined vendor types
2. Supports unique vendor address and contact information for vendor corporate address, remit to address, and ship to address
3. Supports automatic purchase order generation default by vendor
4. Supports minimum and maximum receipt allowances by vendor
5. Supports tracking of last price paid for an item
6. Supports calculation of purchased price variances (PPV)
7. Supports online inquiry or report to compare actual vs. expected purchase costs
8. Allows purchase order price to default to last amount paid
9. Tracks vendor performance on late deliveries
10. Tracks vendor performance on order fill rates

Read on to page 2 for more examples of functional requirements in the areas of Sales, Human Resources, and Finance.