Assessments

Chapter 1 - Identifying Requirements

  1. A functional requirement describes what the software product does – that is, use case features visible to users.

A non-functional requirement describes how the software product works – that is, quality attributes/properties that are invisible but can be observed.

  1. Some of the non-functional requirements are as follows:
    • Usability
    • Reliability
    • Security
    • Performance
    • Availability
    • Scalability
    • Interfaceable

Chapter 2 - Elicitation and Document Requirements

  1. For a medium-complexity functionality, you do it about three times:
    • The first round to understand current processes (automatic or manual) and high-level business needs
    • The second round to dig deep using tools and techniques to probe further to closely understand ...

Get The Salesforce Business Analyst Handbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial