Application: model components that form an application

[rovats]

Store and display information about an application's components (eg: Web UI, Citrix UI, Database, Business Logic) and allow linking of servers etc with these components.

• Soft coded list of components, so clients can define their own
• Allow linking of servers to components (entity_kind on server_usage?)
• Entity notes / assessments linked to components

[markgeddes]

It would be so useful to be able to capture the technologies used within a component to provide a complete view of obsolescence risk. Also, as we move towards a decoupled micro-service architecture, the ability to capture the various dependent, shared services that comprise an application's functionality would be welcome. btw. Many thanks for contributing this project. Great work.

[davidwatkins73]

Thanks for the comments on this. We've been looking at this feature for a while determining how best to approach it. We'd like Waltz to have better support for modeling (micro) services and also supporting services (e.g. a managed tomcat environment) . Given prior commitments to features for the next couple of releases we're unlikely to get round to this until late Q2/early Q3.

Would be happy to use this issue to collate requirements though. Once it's firmed up I'll write up a more concrete proposal for feedback.

[strangetobefree]

the main requirement i can think of would be to be able to link servers to the component and then see them tree up to the application.

[kamransaleem]

Would a list of the installed software on a host cover this scenario?

Can you share a complete list of applicable component kinds?