← All Business Analysis Flashcard Decks

Business Analysis Flashcards

11 cards from real Business Analysis practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 11 Business Analysis flashcards as text
  1. David works for the ACME Organization as a business analyst. As part of the requirements development process, David is now working on many work products. He may need to discuss the results of his job with the stakeholders. Which of the following is not a work product example?

    Answer: Requirements documentation

    The question asks for what is *not* a work product example in the context of discussing *results* with stakeholders. Interview questions and notes, presentation slides, and meeting agendas/minutes are all examples of artifacts created *during* the requirements development process or for *communicating* results. Requirements documentation, however, is the *output* or *result* of the requirements development process itself, not merely a work product used to discuss results.

  2. For three processes of data requirements, a business analyst must adopt advanced methodologies. Which of the following procedures is not one of the three?

    Answer: Reporting

    The core processes for handling data requirements in business analysis are typically Gathering (elicitation), Analyzing (structuring and understanding), and Reviewing (validating and refining). While reporting is an activity a business analyst might perform, it's generally considered a communication or output activity rather than one of the fundamental procedures for *developing* the data requirements themselves.

  3. Requirements are used by business analysts to guide the creation or assessment of test cases.

    Answer: True

    This statement is true. Requirements serve as the foundational blueprint for all testing activities in software development. Test cases are designed directly from documented requirements to ensure that the developed solution meets all specified functionalities and non-functional criteria. Business analysts often collaborate closely with testers to ensure test cases accurately reflect the intended system behavior.

  4. The system must allow users to submit free text up to ———— characters in length in the project plan notes.

    Answer: 255

    255 characters is a very common default or standard maximum length for short text fields in many database systems and applications, particularly for fields like notes or comments. This limit often stems from historical technical constraints (e.g., VARCHAR(255) in databases) and is a practical choice for ensuring data integrity, optimizing storage, and maintaining consistent field sizes across systems.

  5. What components go into creating a use case diagram?

    Answer: Actor and Use Case

    A use case diagram in UML (Unified Modeling Language) primarily illustrates the interactions between users (Actors) and the system (Use Cases). Actors represent external entities that interact with the system, while use cases represent the distinct functionalities or services the system provides. These two components are fundamental to depicting system scope and user interactions, showing 'who does what' with the system.

  6. Which example of the quality-of-service (non-functional; not exhaustive list) requirements below is accurate?

    Answer: All the above

    Quality-of-service requirements, also known as non-functional requirements, describe how well a system performs its functions rather than what it does. Security, usability, performance, and scalability are all classic examples of non-functional requirements. They define the system's operational characteristics, constraints, and quality attributes, which are crucial for user satisfaction and system success.

  7. —————— testing is done with Loadrunner.

    Answer: Performance

    LoadRunner is a widely recognized and powerful software testing tool specifically designed for performance testing. It simulates thousands of concurrent users to put a system under stress, measuring its behavior, response times, and resource utilization under various load conditions. This helps identify bottlenecks and ensure the system can handle expected user traffic and performance demands.

  8. For testing___________, Winrunner is used.

    Answer: Regression

    WinRunner was a popular automated testing tool, primarily used for functional and regression testing of software applications. It allowed testers to record and playback user interactions, ensuring that new changes or bug fixes did not negatively impact existing functionalities. While now largely superseded by other tools, its primary use was to automate the verification of previously working features after modifications.

  9. RUP is part of what corporation?

    Answer: IBM

    RUP stands for Rational Unified Process, which is an iterative software development process framework. It was originally developed by Rational Software, which was later acquired by IBM. Therefore, RUP became a product and methodology associated with IBM, providing a structured approach to software development projects.

  10. CMM Level-II & Level-III Differ in the Following Ways:

    Answer: All the above

    CMM (Capability Maturity Model) Level II (Managed) and Level III (Defined) differ significantly in their approach to processes. Level II focuses on managing individual projects, ensuring processes are planned and executed. Level III, however, requires processes to be standardized across the organization, documented, and tailored for specific projects, encompassing procedures, standards, and the scope of these standards, leading to greater consistency and predictability.

  11. Project documentation and product delivery pertain to:

    Answer: Transition

    In the Rational Unified Process (RUP) and similar iterative development lifecycles, the Transition phase focuses on moving the developed system into the production environment. This includes crucial activities like beta testing, user training, deployment, and ensuring all necessary project documentation is complete and the final product is successfully delivered to end-users. It's the phase where the system goes live.