...
- put a summary or a brief description of the feature in question
- list what is deliberately not supported or what the feature will not offer - to clear any prospective ambiguities
- This feature is supported only when the VM is in stopped state.
- VM can be added to Max 8 Networks.
- list all open items or unresolved issues the developer is unable to decide about without further discussion
- quality risks (test guidelines)
- functionalnon functional: performance, scalability, stability, overload scenarios, etc
- While deploying the VM,select multiple networks. VM will be created with multiple nics and will have configured guest Vlan's on the nic.
- When Add network to VM, if the VM is in stopped state it should be successfull
- When Add network to VM, if the VM is in Running state, Error will be shown "Vm in Running state cannot be addeded to new network"
- for a VM it can be Max on 8 networks. This is because of the Number of Nic's limitation imposed by Hyper-V
- corner cases and boundary conditions
- negative usage scenarios
- specify supportability characteristics:
- what new logging (or at least the important one) is introduced
- how to debug and troubleshoot
- what are the audit events
- list JMX interfaces
- graceful failure and recovery scenarios
- possible fallback or work around route if feature does not work as expected, if those workarounds do exist ofcourse.
- if feature depends other run-time environment related requirements, provide sanity check list for support people to run
- explain configuration characteristics:
- configuration parameters or files introduced/changed
- branding parameters or files introduced/changed
- highlight parameters for performance tweaking
- highlight how installation/upgrade scenarios change
- deployment requirements (fresh install vs. upgrade) if any
- system requirements: memory, CPU, desk space, etc
- interoperability and compatibility requirements:
- OS
- xenserver, hypervisors
- storage, networks, other
- list localization and internationalization specifications
- explain the impact and possible upgrade/migration solution introduced by the feature
- explain performance & scalability implications when feature is used from small scale to large scale
- explain security specifications
- list your evaluation of possible security attacks against the feature and the answers in your design* *
- explain marketing specifications
- explain levels or types of users communities of this feature (e.g. admin, user, etc)
...
{"serverDuration": 83, "requestCorrelationId": "019f3e3a4cc6bae8"}