Satisfaction Levels
Score | Stars | Title | Description | Suitable for |
---|---|---|---|---|
0 | No functionality | No functionality is provided. The system does not have any such function. | nothing | |
1 | Barebones | Only a very minimal, incomplete and unreliable implementation is present. The system is unusable for vast majority of use cases. There is not enough functionality to even evaluate the potential. | nothing | |
2 | Prototype | Experimental prototype implementation is present. The implementation works for some use cases. However, it far from being complete and lot of improvements is needed. The system can be used to evaluate the functionality and provide feedback to developers. | experiments | |
3 | Insufficient | Some functionality is present, covering most common use-cases. However, there are still significant functionality gaps, prohibiting full production deployments. The system can be used for limited proof-of-concept deployments. Yet much more development is needed for system being production-ready. | limited proof-of-concept | |
4 | Poor | Functionality somehow covers most use-cases. Yet, there are still some functionality gaps. Qualities are very limited (reliability, scalability, visibility). The system may be production-ready for limited cases. However, as the system still does not support all common scenarios, it is not ready for full production deployment. | proof-of-concept, limited production | |
5 | Acceptable | The functionality is mostly complete, covering all common use-cases and some uncommon cases as well. The system is ready for production deployments is simple cases, that does not significantly deviate from common industry practice. Qualities (reliability, scalability, visibility) are sufficient for operation of small and mid-size deployments. | production (simple) | |
6 | Good | The functionality is complete, covering all common use-cases and most uncommon cases as well. The system is ready for production deployments of medium complexity. Qualities (reliability, scalability, visibility) are sufficient for operation of mid-size deployments. | production (medium complexity) | |
7 | Very good | The functionality is complete, covering all common use-cases, all uncommon cases, as well some very exotic cases. The system includes flexibility and/or customization capabilities to handle unforeseen situations. The system is ready for large and complex production deployments. Qualities (reliability, scalability, visibility) are sufficient for operation of mid-size and large deployments. | production (complex) | |
8 | Excellent | The functionality is complete, covering all common use-cases, all uncommon cases, as well most exotic cases. There are pre-configured settings for common scenarios. The system includes powerful flexibility and/or customization capabilities to handle unforeseen situations. The system is ready for large and complex production deployments. Qualities (reliability, scalability, visibility) are sufficient for operation of large deployments. | production (very complex) | |
9 | Almost perfect | Overall, the system is very close to perfection. There is just a couple of minor details to improve. The functionality is complete and it works perfectly for vast majority of cases, including all the exotica. There are pre-configured settings for both common and uncommon scenarios. The system includes powerful flexibility and/or customization capabilities to handle unforeseen situations. The system is ready for large and complex production deployments. Qualities (reliability, scalability, visibility) are sufficient for operation of large deployments. | production (very complex) | |
10 | Perfection | Perfect functionality is provided, covering all imaginable use-cases, including capabilities to easily handle unforeseen situations. There is nothing to improve. | production (very complex) |
Was this page helpful?
YES
NO
Thanks for your feedback