What is the correct way to write technical requirements for a user interface component in an application? I think it’s not clear to me whether the technical requirement should determine how the user interface should be implemented, or should it be as general as possible, and describe what is required to satisfy the functional requirements and forget about the implementation details.
Here are my specific questions:
Should he indicate which technology the user interface will implement? (e.g. ActiveX, WPF, HTML).
Should I describe the layout, colors? (given that this may change)
Is it necessary to describe how the data is presented? (for example, is it necessary to say "data is displayed in the format of a table or list" or "a scroll bar appears if the data cannot be placed on the screen"?)
Do I need to describe how the user interface should respond to user input, if this is a functional requirement? (for example, the functional requirement says: "the user should be clear which action is currently active" ... if the technical requirement indicates that the button should change color to red when the user selects parameter a. Blue when the user selects option b .. etc.)
Do I need to point out things that have common sense in the user interface? For example, "should it be positioned so that all content is visible"? or "will it have a shadow to stand out from the rest of the screen"? (note: these are not functional requirements, but they apply to any user interface in general)
source
share