Business & Leadership Flashcards

What are the two types of relationships between use cases?

Answer: Extend and include

In UML (Unified Modeling Language) use case diagrams, 'extend' and 'include' are the two primary types of relationships between use cases. An 'include' relationship indicates that one use case incorporates the functionality of another, while an 'extend' relationship shows that one use case adds optional functionality to another under specific conditions. These relationships help model complex system behaviors and reuse common functionalities.

In the context of systems theory, the term "system" is much broader than an IT system. What else is in a system?

Answer: The people involved and the interaction between them, the external forces affecting their behavior

In systems theory, a 'system' is defined as a set of interacting or interdependent components forming an integrated whole. This definition extends far beyond just IT components to include human elements, their interactions, processes, and environmental factors. Therefore, the people involved, their behaviors, and the external forces influencing them are crucial parts of a comprehensive system.

Which of the following are considered requirements attributes?

Answer: Source of the requirement, stability, and priority

Requirements attributes are characteristics used to manage and track individual requirements effectively. Key attributes include the source (who requested it), stability (how likely it is to change), and priority (its importance relative to others). While ambiguity and conciseness are qualities of a *well-written* requirement, they are not typically tracked as attributes themselves in the same way as source, stability, or priority.

Which model shows how business analysis work is defined and what type of work is involved in the analysis?

Answer: Process models

Process models, such as Business Process Model and Notation (BPMN) diagrams, are specifically designed to illustrate how work is performed within an organization. They define the sequence of activities, decision points, and roles involved in a process, thereby showing the type of work and its flow. This makes them ideal for understanding and defining business analysis work.

Which of the following is a technique used for root cause analysis?

Answer: Fishbone diagram

A Fishbone diagram, also known as an Ishikawa diagram or cause-and-effect diagram, is a visual tool specifically used for root cause analysis. It helps categorize potential causes of a problem to identify the underlying root causes. Brainstorming is a technique for generating ideas, and process modeling is for depicting processes, while 'Five yes technique' is not a standard root cause analysis tool (Five Whys is).

In an international deployment of an intranet, there are multi-language, date, and time issues to consider. How should these needs be categorized during documentation? Stakeholder requirements

Answer: Stakeholder requirements

Multi-language, date, and time issues for an international intranet deployment are specific needs of the users (stakeholders) interacting with the system. These are not broad business goals (business requirements), core system functions (functional requirements), or general performance criteria (quality of service requirements). Instead, they represent the needs of specific stakeholder groups to use the system effectively in their respective contexts.

What elicitation technique is used to examine user manuals, training manuals, service level agreements, or regulatory documentation?

Answer: Document analysis

Document analysis is an elicitation technique where a business analyst examines existing documentation to gather requirements. User manuals, training manuals, service level agreements, and regulatory documents are all examples of existing documents that contain valuable information about current processes, rules, and system functionalities. This technique helps understand the current state and identify potential requirements without directly interviewing stakeholders.

During an interview, it is considered a best practice to ask questions in a particular order. Which of the following choices demonstrates the best order?

Answer: Tell me about the expense reporting process. Who submits expense reports in your organization? Who is responsible for approving those reports? After the expense reports are approved, who reconciles the receipts against submitted expenses?

The best practice for interviews often involves starting with open-ended questions to get a broad understanding, then progressively narrowing down to more specific details and process steps. Option B follows this approach by starting with a general process overview ('Tell me about...') and then moving to specific roles and sequential actions within that process. This allows the interviewee to provide context before diving into specifics.

When eliciting requirements from stakeholders, a business analyst should pay particular attention to __________.

Answer: The role they play and not their title

When eliciting requirements, a business analyst should focus on the actual responsibilities and involvement of a stakeholder in the process or system being analyzed, rather than just their job title. A person's title might not accurately reflect their day-to-day activities or their influence on the project. Understanding their true role ensures that the correct information is gathered from the most relevant individuals.

Elicitation is not limited only to information from stakeholders. Elicitation of requirements for existing solutions can also be done using ______________.

Answer: Document analysis

Elicitation is not solely about gathering new information from stakeholders; it also involves understanding existing solutions. Document analysis is a key technique for this, as it allows business analysts to review existing system documentation, user manuals, process guides, and other artifacts to extract requirements and understand current functionalities. This helps in identifying gaps, redundancies, or areas for improvement in existing solutions.

The description of solution requirements is also referred to as___________.

Answer: Functional and non-functional requirements Explanations:

Solution requirements are detailed descriptions of what the solution must do (functional requirements) and how well it must perform (non-functional requirements). Functional requirements describe the behaviors and features of the system, while non-functional requirements specify quality attributes like performance, security, usability, and reliability. Together, these define the complete scope of the solution.