|
| |
Process requirements are documented expectations, targets and specifications for business processes. They may be collected from multiple groups of stakeholders such as business units, customers, internal customers, users and subject matter experts. The following are common examples of process requirements.
FunctionsObjectives and goals that can be accomplished with the process. For example, "The process shall set up new customers in the billing system."FeaturesTools and automation that accomplish functions. For example, "The billing manager shall receive a notification when a new customer is set up in the billing system."Specifications of process orchestration and choreography with artifacts such as a flow diagram and set of business rules.
EventsRequirements for event triggers and handling. For example, "An order with a value over $40,000 triggers the credit review process."IntegrationRequirements for integration between processes, systems and data repositories. For example, a specification of how data will be mapped from a sales system to a billing system.
Logic that is applied by the process. For example, "New customers may not order more than $700 in a day to an address other then their billing address." PerformancePerformance requirements such as "the process shall have throughput of 300,000 orders an hour."
Reliability requirements such as "the order management interface shall achieve availability of 99.99%."The ability to continue when risks become issues. For example, "order data will be backup up in multiple geographical locations on a hourly basis."Usability related requirements such as "It shall be possible to correct order data at any point during the process."
Requirements for internal controls such as "corrections of order data must be approved by an accounting manager and be recorded for audit purposes."Tools for maintaining inflight processes, data and systems. For example, "a button will be provided to delete an order that is in process."
Non-functional requirements is a catch-all term for requirements that don't relate to functions and features. For example, an information security subject matter expert may contribute security requirements for a process.ImplementationImplementation details such as requirements for a pilot launch.
Business Analysis
This is the complete list of articles we have written about business analysis.
If you enjoyed this page, please consider bookmarking Simplicable.
The common types and formats of requirements.
The difference between functional and non-functional requirements explained.
The difference between requirements and specifications.
The difference between functional and behavioral requirements explained.
A few examples of non-functional requirements.
A definition of requirements traceability with examples.
The common types of customer requirements.
The difference between functions and features.
The common types of requirements elicitation.
A definition of requirements management with examples.
The common types of needs analysis.
TrendingThe most popular articles on Simplicable in the past day.
Recent posts or updates on Simplicable.
Site Map
© 2010-2023 Simplicable. All Rights Reserved. Reproduction of materials found on this site, in any form, without explicit permission is prohibited.
View credits & copyrights or citation information for this page.
|
