The following are four SharePoint rationale aspects for project information:
1) Reason for the Requirement: Find out via research and communication, the reason for the requirement if not obvious
2) Document Assumptions: Sometimes, a requirement is written assuming the implementation of a technology program, as such, any assumption should be documented.
3) Document Relationships: Relationships with the product's expected operations should be documented.
4) Document Design Constraints: Constraints imposed by the results from decisions made as the design, technology or requirements evolves should be documented.
No comments:
Post a Comment