Open RLiNREL opened 3 weeks ago
Attaching a table for clarification about input field validations. This will be shared through email and individual meetings to ensure agreements across the team. NEB-tool_Input_Form_Validation_Clarification_Table_06-07.xlsx
For the input field:
For the required option (two -tier):
For display results:
- The underlying code base should support Latin1, Double-Byte and any other character sets that will make it possible to be translated in other languages than English.
- Support UTF-8 (Latin1, Double-Byte, other languages)
The NEB tool shall have fields for each KPI in which qualitative and/or historical information, e.g., past energy audits and results, can be entered. Each field should have enough character space to accommodate up to 500 words.
- No limit for qualitative and/or historical information. "Google says that text contains on average 5 characters per word, so we’re talking 2500 characters minimum. Let’s be safe and go with ~10,000 characters. I would advocate to not impose any arbitrary limit other than those necessary for UI or performance reasons."
To add validation for ROI calculations and other inputs to quantify NEBs later
Objective: requirement collection and clarifications for the input form validation.