| Feature | Overview |
|---|---|
| Application Groups | Ad-hoc groups of applications |
| Asset Costs | Cost information for apps |
| Bookmarks | External bookmark collections |
| Complexity | Application complexity calculations |
| Entity Notes | Unstructured notes that can be attached to entities |
| Entity Relationship | Custom relationships between entities |
| Flow Diagrams | User created diagrams showing flows between applications |
| Logical Flows | High level connections between applications |
| Measurables | Taxonomy items used to describe the technology estate |
| Organisational Units | Organisational structure |
| Physical Flows | Concrete realisations of logical flows |
| Roadmaps and Scenarios | Used to describe how applications may change over time |
| Server / Database Information | Servers and databases associated with apps and flows |
| Surveys | Questionnaires that can be sent to a subset of Waltz users using criteria native to Waltz |
| Admin Feature | Overview |
|---|---|
| Configuration | Setup information |
| Properties | System wide properties |
| Settings | System settings stored in the database |
| Static Panels | Allow for custom information to be displayed in predefined locations |
| Nav Aids | Diagrams to help users navigate complex structures |
The model diagrams do not attempt to show every field and relationship. Instead they try to convey the important aspects of the model with regard to the subject being discussed.
In general Waltz does not specify foreign keys as this poses significant issues when ingesting data from numerous back-end sources.