Feature #405
Optionality of DO/DA from the point of view of users
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Requirement Spec of user
Start date:
Due date:
% Done:
0%
Estimated time:
ID:
2.2
Source:
ENTSO-E
TF Unique ID:
2.2 # ENTSO-E
WG10 Proposal:
The user shall include in the requirement specification for a project, what optional information is needed.
Estimated Completion:
Discuss in Upcoming Meeting:
No
To discuss in WG10:
Short Proposal:
If a user requires a particular DO/DA that is optional (and hence the functionality behind), this needs to be specified as a functional requirement by the user.
Standard(s):
Needs More Information:
Assigned TF:
Description
There is a misunderstanding of Optionality concept - By the User, Optional means - if it is required by user, it is available (as options).
By the Vendor/Standard - Optional means - it is not mandatory to implement.
Updated by Vladan Cvejic about 3 years ago
- Description updated (diff)
- Discuss in Upcoming Meeting set to No
Checking done.