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 generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






2. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






3. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






4. An informal solicitation of proposals from vendors.






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






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






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






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






9. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






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






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






12. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






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






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






15. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






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






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






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






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






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






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






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






23. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






38. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






39. A description of the requirements management process.






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






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






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






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






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






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






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






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






48. A specific actionable testable directive that is under the control of the business and supports a business policy.






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






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