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






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






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






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






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






6. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






7. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project






8. Any unique and verifiable work product or service that a party has agreed to deliver.






9. A partial or preliminary version of the system.






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






11. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






12. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






13. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






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






17. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






24. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






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






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






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






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






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






30. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






31. The problem area undergoing analysis.






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






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






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






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. A model that defines the boundaries of a business domain or solution.






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






38. A system of programming statements symbols and rules used to represent instructions to a computer.






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






40. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






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






42. A fixed period of time to accomplish a desired outcome.






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






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






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






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






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






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






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






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







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