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 comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






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






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






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






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






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






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






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






9. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






10. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






12. The features and functions that characterize a product service or result.






13. Software requirements that limit the options available to the system designer.






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






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






16. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






17. A practitioner of business analysis.






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






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






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






21. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






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






23. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






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






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






29. A set of requirements grouped together in a document or presentation for communication to stakeholders.






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






31. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






33. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






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






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






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






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






40. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






41. A state or condition the business must satisfy to reach its vision.






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






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






44. Work carried out or on behalf of others.






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






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






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






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






49. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






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