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 informal solicitation of proposals from vendors.






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






3. A function of an organization that enables it to achieve a business goal or objective.






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






5. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






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






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






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






11. Any effort undertaken with a defined goal or objective.






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






13. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






16. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






17. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






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






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






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






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






22. The product capabilities or things the product must do for its users.






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






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






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






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






27. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






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






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






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






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






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






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






37. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






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






39. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






41. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






42. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






43. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






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