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 business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






3. A system trigger that is initiated by humans.






4. 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.






5. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






6. A description of the requirements management process.






7. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






8. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






9. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






11. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






12. An actor who participates in but does not initiate a use case.






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






14. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






16. All materials used by groups within an organization to define tailor implement and maintain their processes.






17. A specific actionable testable directive that is under the control of the business and supports a business policy.






18. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






19. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






21. 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.






22. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






23. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






25. A unit of work performed as part of an initiative or process.






26. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






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






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






29. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






31. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






32. 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.






33. The problem area undergoing analysis.






34. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.






35. An analysis model showing the life cycle of a data entity or class.






36. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






37. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






38. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






39. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






40. A stakeholder person device or system that directly or indirectly accesses a system.






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






42. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.






43. Influencing factors that are believed to be true but have not been confirmed to be accurate.






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






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






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






47. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






48. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






50. An analysis model that shows user interface dialogs arranged as hierarchies.