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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






2. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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






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






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






6. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






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






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






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






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






13. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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






15. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






16. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






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






18. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






19. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






20. A stakeholder who provides products or services to an organization.






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






22. A stakeholder who uses products or services delivered by an organization.






23. An analysis model showing the life cycle of a data entity or class.






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






25. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






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






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






31. An informal solicitation of proposals from vendors.






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






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






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






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






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






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






38. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






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






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






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






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






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






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






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






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






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






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






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






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