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. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






3. A prototype developed to explore or verify requirements.






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






5. A data element with a specified data type that describes information associated with a concept or entity.






6. A stakeholder who provides products or services to an organization.






7. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






8. A description of the requirements management process.






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






10. The number of employees a manger is directly (or indirectly) responsible for.






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






12. A non-actionable directive that supports a business goal.






13. Information that is used to understand the context and validity of information recorded in a system.






14. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






15. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






16. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






18. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






19. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






21. A partial or preliminary version of the system.






22. A stakeholder with legal or governance authority over the solution or the process used to develop it.






23. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






24. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






25. An analysis model describing the data structures and attributes needed by the system.






26. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






27. A state or condition the business must satisfy to reach its vision.






28. Limitations on the design of a solution that derive from the technology used in its implementation.






29. Software developed and sold for a particular market.






30. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






32. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






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






34. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






35. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






36. The process of examining new business opportunities to improve organizational performance.






37. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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 requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






40. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






41. The product capabilities or things the product must do for its users.






42. A system trigger that is initiated by time.






43. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






44. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






46. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






48. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests