Functional Consultant Certain Ideas

Part 9

FC Approach used in the Requirements Analysis

One needs to follow the standard template for the FS document or use the template followed by Clients
team, if any. In any case, the purpose of documenting the requirements is to clearly define the functional
and non-functional requirements of the project, and to provide direction for the technical project team in
the design, construction and testing of the solution.

Prepare the detailed level activity flow diagrams (with alternate and exception flows)

Document the detailed functional and non functional requirements

For each identified essential business use cases, prepare the expanded essential use cases.

Document the business rules for the proposed system, which are basically management
prescriptions that guide day-to-day business decisions.

If using use cases, consider these steps:

o

Cross reference each requirements to at least one use case

Prioritize use cases based on priorities of the requirements that they satisfy

Examine dependencies that might affect priorities