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. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.






2. A system trigger that is initiated by humans.






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






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






5. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






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






9. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






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






11. A model that defines the boundaries of a business domain or solution.






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






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






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






15. The problem area undergoing analysis.






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






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






18. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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






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






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






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






23. Work carried out or on behalf of others.






24. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






26. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






28. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






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






30. A description of the requirements management process.






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






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






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






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






35. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






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






37. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






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






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






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






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






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






44. A practitioner of business analysis.






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






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






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






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






49. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






50. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.







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