You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an entry point to the landscape it would be useful to have an overview grouped by domains. This could be oriented at the architectural domain models used by the railway industry. Showing the projects grouped by the specific domain where they are providing solutions would make it easier for people coming from these domains to find relevant projects. This would be more a business-oriented view than a technical view.
For displaying these domains an approach as used for example by the Component Gallery could be suitable. This would be a three-level display, on the first level an overview of domains, on the second level an overview of projects per domain, and on the third level the details view of each project. The card-like display of the component gallery could be a way to on one hand give a good overview and on the other hand show the most relevant details at a glance.
As the specific structure of domain models will vary a bit between different organizations, we would need to find some compromise to have a simple model and corresponding structures, which are easy to map from other models. We probably don't want to go too much in detail there, but keep it at a quite high level. This would also reduce the effort to classify projects.
An example based on the current projects would be:
As an entry point to the landscape it would be useful to have an overview grouped by domains. This could be oriented at the architectural domain models used by the railway industry. Showing the projects grouped by the specific domain where they are providing solutions would make it easier for people coming from these domains to find relevant projects. This would be more a business-oriented view than a technical view.
For displaying these domains an approach as used for example by the Component Gallery could be suitable. This would be a three-level display, on the first level an overview of domains, on the second level an overview of projects per domain, and on the third level the details view of each project. The card-like display of the component gallery could be a way to on one hand give a good overview and on the other hand show the most relevant details at a glance.
As the specific structure of domain models will vary a bit between different organizations, we would need to find some compromise to have a simple model and corresponding structures, which are easy to map from other models. We probably don't want to go too much in detail there, but keep it at a quite high level. This would also reduce the effort to classify projects.
An example based on the current projects would be:
Capactiy planning: OSRD, Netzgrafik-Editor, libLRS
Asset management: RCM OSS, DAC Migration DSS
Journey booking and planning: OpenTripPlanner
The text was updated successfully, but these errors were encountered: