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."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."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%."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." internal controls such as "corrections of order data must be approved by an accounting manager and be recorded for audit purposes."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.
|Overview: Process Requirements|