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 requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






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






4. A prototype that dives into the details of the interface functionality or both.






5. A solution or component of a solution that is the result of a project.






6. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






7. An analysis model that illustrates the architecture of the system's user interface.






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






9. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






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






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






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






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






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






18. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






19. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






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






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






25. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






27. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






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






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






30. Metadata related to a requirement used to assist with requirements development and management.






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






32. The quality attributes design and implementation constraints and external interfaces that the product must have.






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






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






35. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






38. All materials used by groups within an organization to define tailor implement and maintain their processes.






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






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






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






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






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






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






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






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






47. Any recognized association of people in the context of an organization or enterprise.






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






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






50. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.