There are no concrete rules here. The true answer is that it depends on what your team is composed of.
If the person writing the requirements is the technical lead, then it may well dictate the technology choice.
If however the person writing the requirements is a non-technical manager, then it's generally in the best interest to let the technical team decide on specifics while the manager merely dictates specific requirements that must be implemented.
Additionally, things like layout and colors probably don't have a place in technical requirements. Someone (whether it's the development team, or if available, a designer) should come up with mockups or wireframes to review with the users. This is an iterative process and can usually be done in parallel with some of the initial development (ie. developers can usually start writing domain models, database schemas, etc. while the designer iterates the UI with the users/stakeholders).
IMO, obvious things should be left out as they are just clutter, however, business rules such as validation, and screen states should absolutely.
Again, I want to reitorate that it entirely depends on the makeup of the team. The requirements doc is meant to communicate from one tier to another. And all decisions should be left to the tier best equipped to make those decisions.
发布评论
评论（1）
这里没有具体的规则。真正的答案是，这取决于您的团队由什么组成。
我想再次重申，这完全取决于团队的构成。需求文档旨在从一层到另一层进行通信。所有的决定都应该留给最有能力做出这些决定的层。
There are no concrete rules here. The true answer is that it depends on what your team is composed of.
Again, I want to reitorate that it entirely depends on the makeup of the team. The requirements doc is meant to communicate from one tier to another. And all decisions should be left to the tier best equipped to make those decisions.