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 specific actionable testable directive that is under the control of the business and supports a business policy.






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






3. A solution or component of a solution that is the result of a project.






4. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






6. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






7. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






8. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






11. A stakeholder person device or system that directly or indirectly accesses a system.






12. A fixed period of time to accomplish a desired outcome.






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






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






15. A system trigger that is initiated by time.






16. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






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






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






19. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






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






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






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






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






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






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






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






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






31. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






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






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






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






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






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






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






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






39. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






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






43. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






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






48. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






49. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






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