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. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






3. A temporary endeavor undertaken to create a unique product service or result.






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






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






6. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






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






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






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






11. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






12. A system trigger that is initiated by time.






13. Work carried out or on behalf of others.






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






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






16. A partial or preliminary version of the system.






17. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






19. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






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






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






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






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






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






27. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






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






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






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






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






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






36. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.






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






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






39. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






40. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






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






44. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






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






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






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






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






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






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