Effective use-case analysis
Requirement elicitation is commonly mentioned among business analysts, but where do these requirements originally come from? It is quite complicated to understand and start collecting the required functionality as the product stakeholders’ explanations are often ambiguous, diverse and lacking of technical terminology. But how do you manage to identify and write down all the functionalities required by the stakeholders, the user roles and their actions? The answer is pretty simple – you have to perform a use case analysis in order to capture the contracts between the system and its users and then refine the system’s use cases and obtain an organized and more complete view.