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 document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






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






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






7. A unit of work performed as part of an initiative or process.






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






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






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






11. Work carried out or on behalf of others.






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






13. Limitations on the design of a solution that derive from the technology used in its implementation.






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






15. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






17. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






18. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






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






21. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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






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






27. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






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






29. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






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






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






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






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






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






35. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






36. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






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






39. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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






44. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






46. An informal solicitation of proposals from vendors.






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






48. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






49. The area covered by a particular activity or topic of interest.






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