Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






2. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






3. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






4. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






5. A fixed period of time to accomplish a desired outcome.






6. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






7. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






8. The degree to which a set of inherent characteristics fulfills requirements.






9. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






10. The set of capabilities a solution must deliver in order to meet the business need.






11. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






12. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






13. A practitioner of business analysis.






14. The area covered by a particular activity or topic of interest.






15. Metadata related to a requirement used to assist with requirements development and management.






16. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






17. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






18. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






19. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






20. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






21. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






22. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






23. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






24. An analysis model that illustrates the architecture of the system's user interface.






25. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






26. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






27. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






28. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






29. A use case composed of a common set of steps used by multiple use cases.






30. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






31. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






32. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






33. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






34. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






35. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






36. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






37. A person with specific expertise in an area or domain under investigation.






38. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






39. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






40. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






41. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






42. A temporary endeavor undertaken to create a unique product service or result.






43. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






44. A group of related tasks that support a key function of business analysis.






45. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






46. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






47. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






48. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






49. Creating working software in multiple releases so the entire product is delivered in portions over time.






50. Formal approval of a set of requirements by a sponsor or other decision maker.