Application event template
Examples of use:
These fields are included in the template to describe an application event.
| Field name | Description |
|---|---|
| Application event name | The name(s) of the application event |
| Data objects | The data object that is involved in the occurrence of the application event |
| Application component & interface | The application component for, and/or the application interface via, which the application event will imply a need to perform |
| Initiating application | The application component that will initiate the application event |
| Non-functional requirements | List non-functional requirements that are specific and important for the application event, tag them as one or more of the listed types of non-functional requirements |
| Project Issues | List project issues that are specific and important for the application, tag them as one or more of the listed types of project issues |
The availability of an enterprise architecture - preferably as part of an enterprise repository - will impact the amount of work that must be invested in describing the application events as the scope for an application component is being determined.
Other sub-sections under Requirements templates and patterns
-
Requirements templates and patterns
- Application event template
- Application template
- Business event template
- Business object template
- Business product template
- Business use case (BUC) template
- Data object template
- (Product) use case template (PUC)
- Repository elements
- Stakeholder class
- Stakeholder template
- Types of non-functional requirements
- Types of project issues
Questions, answers and comments
Add a New Comment
