In the context of systems theory, the term "system" is much broader than an IT system. It also includes the people involved, the interactions between them, the external forces affecting their behavior, and all other relevant elements and factors.
It's more important to know a stakeholder's role and function than their title.
Root cause analysis is performed using the fishbone diagram and five whys.
International deployment must be categorized as stakeholder requirements. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution.
Solution requirements can be broken down into functional and non-functional requirements.
The requirements attributes are absolute reference, author of the requirement, complexity, ownership, priority, risks, source of the requirement, stability, status, urgency.
Process models can be used in the business analysis process. It helps us understand how to improve those processes and reduce problems from hands-off. It also improves cycle time and alters how business analysis is performed to support improvements in downstream processes.
The two types of relationships between use cases are extend and include.
A good order starts with general (open-ended) questions and moves to specific questions. They cover the process from start to finish and moves from details to summary.
Document analysis is a means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Document analysis is a method of elicitation that does not involve the stakeholders. In it, a business analyst studies documents of existing solution, which include information on business rules, and entities and attributes that need to be included in a new solution.