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. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






3. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






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






5. A prototype that dives into the details of the interface functionality or both.






6. Software developed and sold for a particular market.






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






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






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






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






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






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






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






14. Work carried out or on behalf of others.






15. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






16. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).






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






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






19. The problem area undergoing analysis.






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






21. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






25. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






26. An actor who participates in but does not initiate a use case.






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






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






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






30. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






31. A prototype developed to explore or verify requirements.






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






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






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






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






36. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






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






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






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






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






41. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






42. A partial or preliminary version of the system.






43. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






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






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






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






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






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






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






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