CLASS OF CLASS OF INDIVIDUAL - Application Scenario
| Description | An Application Scenario is a story involving the components of an Application (Application Component or MicroService), interacting in order to produce Information Outcome Events. This includes: 1) A course of events represented by Application Flows depicting the story towards the delivery of expected Information Outcome Events. 2) Interacting Application Components who participate to the story.
The Application Functional Architecture domain is used to describe the functional structure and behavior of Business Software Systems. | ||
|---|---|---|---|
| External references |
 C4 Model - Supplementary diagrams -Dynamic Diagram OpenGroup - ArchiMate - Application Interaction | ||
| Super Types | 
Software System Scenario | ||
| Dictionary | 
Dictionary of SysFEAT concepts | ||
| Lexical Scope | 
Architecture Container |
RELATIONSHIPS
Simple Graph Graph & Inheritance Table
Simple Graph
Composition: ➝ Classification: ➝ Specialization: ➝ Instance Of: --> Enumerated definition: ➝ Syntax: ➝
SERIALIZATION FORMAT
TEXTUAL SYNTAX RDF
SEMANTIC TAXONOMY
Sub-Types Super-Types
Click node rectangle to collapse/expand one level. Click triangle for full recursive collapse/expand. Double-click on a node to open its URL. Hover for description.
BORDERS
| Name | Super type | Border Type | Description |
|---|---|---|---|
Business Behavior::Business Start | |||
| Business Input |
Resource Behavior::Resource Input | 
Resource Outcome Event | A Business Input is a border of a Resource Behavior that refers to the consumption of an Business Outcome Event that starts the Resource Behavior. |
| Business Output | 
Resource Behavior::Resource Output |
Business Outcome Event | A Business Output is a border of a Resource Behavior that refers to the production of a Business Outcome Event that ends the Resource Behavior. |
| Produced Information |
Business Behavior::Business End |
INTERNAL STRUCTURE
