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. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






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






6. A prototype that is continuously modified and updated in response to feedback from users.






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






8. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






9. A function of an organization that enables it to achieve a business goal or objective.






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






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






12. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






13. Any effort undertaken with a defined goal or objective.






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






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






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






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






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






19. The problem area undergoing analysis.






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






21. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






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






23. 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).






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






25. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






26. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






27. The work that must be performed to deliver a product service or result with the specified features and functions.






28. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






30. A group or person who has interests that may be affected by an initiative or influence over it.






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






32. A structured examination of an identified problem to understand the underlying causes.






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






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






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






36. Something that occurs to which an organizational unit system or process must respond.






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






38. An assessment of the costs and benefits associated with a proposed initiative.






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






40. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






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






42. Software developed and sold for a particular market.






43. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






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






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






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






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






49. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






50. A measure of the profitability of a project or investment.







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