F1. Identity Uniqueness¶
Whether the software has a proper, unique and persistent identifier.
The uniqueness of an identifier is necessary to unambiguously refer to that resource and that resource alone.
F1.1. Uniqueness of name¶
What is being measured?¶
- Whether the software has a unique name to identify it that sets it apart from others.
Why should we measure it?¶
- The name is commonly used as the primary identifier of software. Each tool should have a unique name to avoid ambiguities. Different versions of the same software should share a name, but if substantial modifications are done, the identifier should change for the new piece of software.
How do we measure it?¶
- A name is valid.
Types it applies to¶
- all
Weight¶
- 0.8
F1.2. Identifiability of version¶
What is being measured?¶
- Whether there is a scheme to uniquely and properly identify the software version.
Why should we measure it?¶
A clear and consistent versioning scheme is crucial for distinguishing between different software releases, enabling precise communication and effective update management while also aiding in tracking incremental changes, thus ensuring that users can easily reference, use, and provide feedback on specific versions.
How do we measure it?¶
A version of the form X.X is considered valid.
Types it applies to¶
- all
Weight¶
- 0.2