We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »



Must Have Requirement NameBusiness RequirementRequirementVSPECDesired
Simplicity
  • Must be easy to understand and adopt.  
  • Must be human readable
  • Must be easily understood by engineers, analysts
  • Must not be so complex that only a handful of data scientists understand it
  • Must be understandable and useable by engineers within a reasonable period of time (< 1 day?)
  • Must be easy to contribute/add new (signals, elements)
YesThe approach for describing data structures is human-friendly and easy to understand and contribute to.Yes
Technology Agnosticism
  • Must work with a variety of widely industry adopted tools for adoption and cost.
  • Ease of adoption
  • Ease of contribution
  • Must work with a variety of technologies
YesSpecification offers a vocabulary only. It can be exported into multiple formats and could be potentially used in any downstream system, as long as there is a tool for exporting it as desired.Yes
Modularity
  • Adopt and contribute only the pieces needed.
  • Ease of adoption
  • Ease of contribution
  • Must be able to adopt only parts of the model that matter to the user
  • Must be able to extend and override parts of the model as needed for internal and external use
Partly Specification can be split into multiple files that will be read as a whole during the export.Yes
Scalability & Maintainability
  • Ease of adoption 
  • Ease of contribution
  • Flexibility
  • Cost
  • Must support a wide variety of vehicle domains (e.g. Seating, HVAC, Entertainment, Engine, etc...)
PartlyYes in the sense that the vocabulary of vehicle properties can be further extended. However, its expressivity is limited and covering more features requires significant work on the tools.Yes
Metadata Resource Uniqueness

PartlyJust the Fully-Qualified Name (fqn) and the UUID that can be constructed from the metadata are unique. Specification of a concept can appear multiple times.Yes
Support for Multiple Classification Schemes

NoOne tree has one dimension only. Paths of the expanded tree create dependencies and moving a concept to another part in the tree is usually painful.Yes
Support for Cross Domain References

NoVSS tree has one dimension only. One could have multiple trees, but (currently) each tree would continue to be an independent domain.Yes
Support for the Specification of Capabilities

NoVSS focuses on the data structure (e.g., datatypes, units, etc.) But, no possible interactions with the specified data are formally described (e.g., Concept Seat is modeled but not the possible operations on that property).Yes
Community and Tools
  • Must scale across Automotive and adjacent industries
  • Cost
  • Ease of Adoption
  • Ease of Contribution

NoLimited to COVESA community and the vss-tools (mainly exporters). Any change in the modeling language requires rework of the tools.Yes
Support for Automated Reasoning

NoNo mechanism for semantic correctness and consistency. (e.g., what distinguishes a Car from a Motorcycle? etc.)Partly


















  • No labels

Privacy Policy | Cookie Policy