The current thinking is that once we've recorded the requirements and use cases we will identify existing cloud repository implementations and select the best one. This deliverable is the document that explains what was selected and why (the criteria). What would be a better name for this deliverable?
The current thinking is that once we've recorded the requirements and use cases we will identify existing cloud repository implementations and select the best one. This deliverable is the document that explains what was selected and why (the criteria). What would be a better name for this deliverable?
Maybe "Evaluation report?"