Vizuri is committed to publishing code and content that helps to advance the open source community. We are proud to share a new addition to our content library this week: Non-Functional Requirements for OpenShift Implementations. The following is an excerpt from that free guide, now available for download:
...there is no exact level of detail required for any given requirement. However, efforts to document as much detail as possible have many benefits during implementation:
- More detail enables better definition of system functionality, and better system definition streamlines implementation. Implementers no longer have to stop their work to seek clarification from outside sources. Instead, they need only look to the requirements specifications to determine how the environments should function.
- Greater detail keeps analysts from having to make assumptions about a given process. These assumptions take additional time to verify, increasing the analysis effort.
- More detail during analysis provides a solid understanding of functionality expected by both the users and the implementers. This usually leads to fewer change requests, as well as to a more comfortable relationship between the users and the implementers.
We hope the following checklist of requirements helps you to achieve a smooth and successful implementation.
- When do the environments need to be up? How many 9s?
- Does the requirement vary based on environment?
- ...and more
Backup and Recovery
- What applications, services, data, etc. need to be backed up?
- How often does it need to be backed up?
- ...and more
- How many applications does your environment need to support?
- How many users will each application support?
In the full document, here are just a few of the topics we also cover:
We hope that these points will help you as you consider moving towards the Cloud.