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






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






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






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






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






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






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






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






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






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






11. An informal solicitation of proposals from vendors.






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






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






14. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






15. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






16. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.






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






18. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






20. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






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






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






23. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






24. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






25. A partial or preliminary version of the system.






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






27. A system of programming statements symbols and rules used to represent instructions to a computer.






28. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






29. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






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






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






32. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






33. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






34. The process of examining new business opportunities to improve organizational performance.






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






36. A prototype developed to explore or verify requirements.






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






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






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






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






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






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






43. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






46. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






48. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






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






50. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.