What is compounded requirement and why it is discouraged when documenting requirements?
By the same token, what is fragmented requirement?
What is the impact of compounded requirements and overly fragmented requirements? (Overly fragmented refers to situation where requirements should not be fragmented)
As a software engineer, what would be your strategy when documenting requirements?
This material may consist of step-by-step explanations on how to solve a problem or examples of proper writing, including the use of citations, references, bibliographies, and formatting. This material is made available for the sole purpose of studying and learning - misuse is strictly forbidden.
Fragmented requirements are usually called those requirements which cannot be found as whole pieces within a single place from the documentation; practically their parts are spread across multiple statements and this makes their identification cumbersome. The immediate consequence is that additional time must be spent by Software Engineering for the reassembly process....
This is only a preview of the solution. Please use the purchase button to see the entire solution