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 description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






3. A temporary endeavor undertaken to create a unique product service or result.






4. Any unique and verifiable work product or service that a party has agreed to deliver.






5. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






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






8. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






9. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






10. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






26. A shared boundary between any two persons and/or systems through which information is communicated.






27. Software developed and sold for a particular market.






28. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






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






31. Work carried out or on behalf of others.






32. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






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






35. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






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






42. A description of the requirements management process.






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






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 system trigger that is initiated by time.






46. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






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






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