Why is it difficult to understand software requirements?
Answers
Answered by
2
HELLO FRIEND HERE IS YOUR ANSWER.
system behavior as opposed to non-functional requirements specifications which define attributes as not behavior. This 'functionality' refers to services, tasks or functions the user performs using the system in question.
i hope it will help you
★_______@________★________@_______★
system behavior as opposed to non-functional requirements specifications which define attributes as not behavior. This 'functionality' refers to services, tasks or functions the user performs using the system in question.
i hope it will help you
★_______@________★________@_______★
Answered by
0
Answer:
- One of the most difficult phases of the project is gathering business requirements from stakeholders. Under the best circumstances requirements are often vague, because it is difficult for customers to articulate their needs before they see the end product.
Similar questions