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. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






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






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






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






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






11. Any effort undertaken with a defined goal or objective.






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






13. A system trigger that is initiated by humans.






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






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






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






17. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






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






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






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






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. Information that is used to understand the context and validity of information recorded in a system.






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






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






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






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






27. A prototype developed to explore or verify requirements.






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






29. A practitioner of business analysis.






30. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






31. The number of employees a manger is directly (or indirectly) responsible for.






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






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






34. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






35. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






36. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce






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






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






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






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






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






42. The area covered by a particular activity or topic of interest.






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






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






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






46. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






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






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