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 group of related tasks that support a key function of business analysis.






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






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






4. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






6. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






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






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






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






11. A link between two elements or objects in a diagram.






12. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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






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






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






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






18. The human and nonhuman roles that interact with the system.






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






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






21. Work carried out or on behalf of others.






22. A description of the requirements management process.






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






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






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






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






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






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






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






30. Ability of systems to communicate by exchanging data or services.






31. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






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






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






36. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






39. The set of processes templates and activities that will be used to perform business analysis in a specific context.






40. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






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






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






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






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






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






49. A type of data model that depicts information groups as classes.






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







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