Defining Business Process Steps
From the Plan phase of the USoft Approach onwards, you can describe business process steps. For each business process step you supply at least the following information:
Sequence Numbers are mandatory for Process Steps, but if a Sequence Number is not meaningful or important at entry time, you can set it to some default (e.g. 10) for the time being.
Business process steps may be implemented by columns in database tables, constraints on data manipulation, menu and screen elements, authorization rules, communication with other software, and many more. The relationship between process steps and their implementations can be documented in USoft TeamWork in the form of Implementations.
Defining and sequencing business process steps is the best way of providing an overview of what the various system modules do. In early phases this will help developers understand what they are trying to build, and in later stages it will be an invaluable help in tracing an operational system's structure and functionality.
Business process steps are a Business Rule subtype, i.e., they are seen as a special type of Business Rule. Consequently, they have all the characteristics of Business Rules, such as implementations, motivations and classifications. In addition, and unlike other Business Rules, they have a Name and a Sequence Number.